> > I've attached a small patch to get it to the linking stage and a copy > > of the linking errors. > > Thanks. Paul: please consider merging this into your branch. Note that > I've not looked at it, but I'm assuming that Chris knows what he's > doing :)
The patch has been applied :) > > I'd like to see some documentation on how to migrate my treeviews to > > use the new ones and how to call the new hotlist, cookie and global > > history browsers (I'm assuming all this has been moved across to the > > core?) > > That's the intention, yes. I'm not sure if all of this has been done > yet. The treeview is meant to be generic (just like the textarea widget) > so these kinds of specific uses of it will require some extra code. > Whether this code needs reside in the core or whether it's the > reponsibility of the frontend code, I'm not sure yet. Perhaps Paul can > enlighten us. What goes for the migration, I tried not to change the API drastically so there will be, hopefully, not many changes to be done. Both treeview and textarea need redraw_start and redraw_end callbacks provided by the front end. Additionally for treeview there is a set of functions declared as platform specific code, which I have altered a little. The implementation or comments are done for the GTK front end so you can find some useful clues there. I will be working on hotlist/cookie/global history once treeview and textinput get merged to trunk. Once they are ready, the only thing the front end has to provide (in addition to mouse/keyboard event passing and redraw callbacks) will be a toolbar connected to the API which will be created.
