@edspencer Thank you for clarifying this. I've read that theming guide a number of times, but it doesn't go into much depth.
Question:
I'm working on a custom theme that uses a special background image for active tabs. I sliced the background image myself, then to override the default CSS for tabs I added my own CSS for modern browsers, and then overrode that CSS with IE-specific CSS activated by conditional comments. This is pretty much how I've always done theming in Ext JS.
Am I doing it the hard way? Would the slicer tool save me a lot of this effort?
Performance on my system of the neptune example is poor.
I'm running an overclocked i7 with a very fast NVIDIA graphics card and 8G
and I'm watching it slowly redraw on FF 7. Icons (in the tree, etc) dont
seem to appear.
If performance of neptune is worse than the current default theme, I would
focus on improving the default.
Interesting. The Kitchen Sink demo does seem to struggle in FF7. For what it's worth, it works fine in Chrome and performance is really good.
I ran some tests a few days ago comparing the performance of an app with the default theme vs the Neptune theme. It didn't seem to make any difference in the browsers I tried but I'm not sure FF was one of them.
Just checked and yes it does run fast in Chrome. FF7 is really slow though, it looks
like something is not totally right because the icons dont appear in the tree on the
left. It takes seconds to respond to a click on the examples tree.
Just checked and yes it does run fast in Chrome. FF7 is really slow though, it looks
like something is not totally right because the icons dont appear in the tree on the
left. It takes seconds to respond to a click on the examples tree.