Hi Pawel, Are you referring to favicons here? Then I'd suggest, generally, looking at the core functions I wrote for my favicon branch, that really should be merged to trunk quite quickly to avoid duplication of work; treating that as a kind of 'API' to retrieve favicons;
then beyond that there is the question of implementing a cache-to-disk, that clearly belongs in a new branch; As for the text input, my only comment is that at current projections, I'd hope to complete the customisation branch perhaps in time for Friday [although my car may need major work so I may have limited time for now], while it may well be that theme support would naturally be a simple addition to the customisation branch; at that stage then the only branch for me to work at would be hotlist, so I'd really encourage you to fully complete your treeview/hotlist branch first, before touching text input — in a new branch please :-) Best Mark http://www.halloit.com Key ID 046B65CF Paweł Blokus wrote: > As I wrote, the major part is done but there are still some less > important issues (of which I'd like to take care of later or which > need some help from other devs): > > - Change the way the icons are loaded. I think having something like > load_image_from_disk would fit better than fetching the image as > regular web content. I have no idea if this would be a hard task and > how it would be done best so some input on this would be very helpful. > - Add the default icons for the tree (either create them or acquire > from the system) > - Making the window auto-scroll when dragging in a tree view > - Improve style, error checking etc. > > During the following week I would like to concentrate on the text > input widget. If I have some time left at the end of it I'd like to > take care of some of the above points
