In article <[email protected]>, Pawe³ Blokus <[email protected]> wrote:
> Since the last progress report I have completed the hotlist and added > the sslcert window. I also removed all known bugs as well as > unintuitive tree behaviour. John-Mark has a look at the way treeviews work. Right now, the implementation details of frontend treeview widgets need to be exposed for all their clients to see. He suggests changing it so that the front end's treeview code creates an empty tree. This means that front end treeview widgets can be nicely abstracted. Example: for cookies, you create a frontend treeview widget (which creates a core treeview with the treeview callback vtable), can then you pass the freshly created tree to cookies_initialise(). This means that the frontend treeview implementation can be kept private. Also, the treeviews shouldn't care about where they're located globally, that's down to the client to deal with. (Like the scrollbar widget.) The textarea widget should also not care about its global location. Michael -- Michael Drake (tlsa) http://www.netsurf-browser.org/
