You need to log in before you can comment on or make changes to this bug.
Golden Widget Rule #7: bug 97 comment 3 Widget Parameters that deal with paths should always be relative to the template the user is building. eg. "./images/icon_*.png Otherwise if it is an image that is found under the chameleon application eg /htdocs/images/icon_*.png this should be a url. This is even if it is on the same server. To many times the image path causes the biggest confusion for users, and varies greatly from widget to widget is located.... I am expecting a stink about the above comment from the developers, but I only wish to get feed back on this major limitation to the usability of this technology. Thanks
The new button architecture works like this: * if reference is absolute then the image is left alone and assumed to be in the location specified. * if the reference is relative then the code tries to find the image in the following locations: - relative to application directory - relative to the application's web path - relative to chameleon so if you say 'images/icon_query.png' and this is not in your application then it will use the icon_query from chameleon. But if it is in your application then it will the one in your application. All image paths related to buttons are handled consistently in this way. Other widgets should also work this way and if they don't then it is a bug and should be filed when found. Widget documentation should be updated to reflect the above (for Button attributes for images/fonts) for 1.99 release The Widget development documentation should reflect the same rule, bug can be closed once that is written.
excellent! accepting bug
updated version to 1.99
Question and comment about this process. If chameleon cannot find the image I specify, does that get reported to the error widget to let me know I have done something wrong? If not, I think it sould do this too.
I don't think it does, you should probably file a separate bug for this since it is a new feature.
filed bug 362 as an enhancement to discuss my prevuious comment
Changed target to 1.99 Final
There is nothing in the Application Developer's Guide on skinning, which there should be and it would include this. Post 2.0 I guess.
