I have been looking into this already about a year ago but never was able to finish this. Therefore I'm glad someone raised this issue again. What I have come up sofar is:

- I feel that loading images at runtime is preferred, as it enables to use alternative image sets (different platforms or prefferences / themes like monochrome, lowres, large). GIMP also does it for instance - I have made a unit that loads images at creation of forms in an imagelist. Although very basic and it supports XPM. - For Lazarus we would need to define a naming scheme as previously mentioned. This "list" will link functionality to some icon and will be the basis for developers to choose from. - I developed a component called TStdImageList, which stores a default list of icons for any developer to choose from. I personally don't see a big need for such a component anymore but I want to be complete here... - I also developed an algorithm for creating a disabled image from any bitmap. This algorithm should be implemented in the LCL so any TToolbar or alike component could use it. Never got that far though. But the algorithm is there.

Well that's about what I did (and didn't) I'm happy to share code or to assist in any work.

Regards, Darius
_________________________________________________________________
    To unsubscribe: mail [EMAIL PROTECTED] with
               "unsubscribe" as the Subject
  archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to