Re: [qooxdoo-devel] Aliases and Themes in Namespaces

2006-08-04 Thread Jim Hunter
I agree 100%. As soon as I get done chasing down this other bug that I am working on (different application all together) I will be able to get back to qooxdoo and 'solve' my icon problems.Thanks for the detailed assistance. Jim On 8/4/06, Erik A. Onnen <[EMAIL PROTECTED]> wrote: Previous examples

Re: [qooxdoo-devel] Aliases and Themes in Namespaces

2006-08-04 Thread Erik A. Onnen
Previous examples I had seen didn't include the setIconTheme and setWidgetTheme calls. This does work for me in the sense that the app uses the right icons. That is, until I change themes. If I allow users to change themes later, the change in theme will overwrite my aliases. I raised the point in

Re: [qooxdoo-devel] Aliases and Themes in Namespaces

2006-08-04 Thread Jim Hunter
I placed the three lines at the top of my user file before anything else gets called. I;ll try your method to see if that helps.Thanks,JimOn 8/3/06, Dietrich Streifert <[EMAIL PROTECTED]> wrote: Where do you place the defineAlias calls?It's working perfectly for me if I do the calls like this:

Re: [qooxdoo-devel] Aliases and Themes in Namespaces

2006-08-03 Thread Dietrich Streifert
Where do you place the defineAlias calls? It's working perfectly for me if I do the calls like this: qx.core.Init.defineInitialize(function() { qx.manager.object.ImageManager.setIconTheme(qx.theme.icon.CrystalSvgIconTheme); qx.manager.object.ImageManager.setWidgetTheme

Re: [qooxdoo-devel] Aliases and Themes in Namespaces

2006-08-03 Thread Jim Hunter
My problem isn't my images, it's the images for things like the Column Select button on a table and the images to tree views and sort icons for column headers in a table. Those are the images that are not loading. My images for buttons that I create are working fine and always have. So if I knew th

Re: [qooxdoo-devel] Aliases and Themes in Namespaces

2006-08-03 Thread Erik A. Onnen
defineAlias does actually work, unfortunately the themes overwrite application values when loaded. Hypothetically you could get around this by forcing a load of the theme (create a widget with an icon), then invoking defineAlias although I haven't tested this approach. Like Erich, I've been using

Re: [qooxdoo-devel] Aliases and Themes in Namespaces

2006-08-03 Thread Jim Hunter
OK, since the defineAlias doesn't seem to work and since paths were moved around in one of the latest builds, what is the officially recommended set of paths for the images and themes right now? I have tried moving directories around all morning and I can't get them to work and I finally gave up an

Re: [qooxdoo-devel] Aliases and Themes in Namespaces

2006-08-03 Thread Erich Konicek
Erik A. Onnen schrieb: The storage of Qooxdoo on my webserver is not in a standard location and cannot be for various reasons. I had the same problem. My solution is a own Makefile with runtine-setting as shown below. generate-script-build:     @$(GENERATE) \       --script-input $(FRAMEWO

[qooxdoo-devel] Aliases and Themes in Namespaces

2006-08-03 Thread Erik A. Onnen
I'm experiencing issues with the ImageManager.defineAlias method. I'm fairly convinced it's a bug and I'd be happy to patch but I can't quite understand the intent of the code. The storage of Qooxdoo on my webserver is not in a standard location and cannot be for various reasons. Based on some pos