> > Secondly - and please feel free to point me to existing > > documentation > > on this one, as I can't find any - I'd like an overview of which > > functions I need to write as a starting point. I can glean some of > > this from looking through the ui source, but I'd like to avoid > > anything unimportant for now - just enough to get the page rendered > > and displayed. Everything else can come later! > > desktop/gui.h contains most of the API that platform frontends need > to > implement. There are probably a few other bits and pieces scattered > around > elsewhere, but they should be obvious, as it won't link without them > :) > > Your best bet is to stub out the things defined in gui.h, then work > from > there. It should be pretty obvious which bits are vital.
For the BeOS port I just copied files from the GTK code and rewrote them one by one until it linked. Maybe not as clean though. You'll certainly want to start with *_gui.c as it contains init code, then _scaffolding.c which handles top-level windows, _window is the canvas for rendering, and _plotters the actual drawing funcs. François.
