nanogui@linuxhacker.org

Shane,
    I am slightly revising my ideas on how to port fltk, after
spending most all day looking into it.

I think at this point, that it would be best to try to get
fltk linked, even if it barely runs...  So, I suggest that
you comment out many, many calls with //FIXME
or something like that, and then work on getting
the window creation, main loop and basic
painting going...  pick the simplest fltk demo
you can find and get that running.

following are my revised ideas on which functions I 
can implement easily....

I have all the region calls, in, but they don't all work the way
we may need yet.  I will post a 0.88pre3 soon that has them.  In the
mean time, we'll want a single BeginPaint/Endpaint combo for ALL
painting

: : SetAlignText - NO

: : PeekMessage NO
: (note: fltk uses a strange mechanism where win32 select() AND
: PeekMessage() are called to handle sockets and messages...  This
: will need rewriting to just GetMessage or PeekMessage in the
: beginning, unless the fltk program uses sockets)

Just rewrite and use a single GetMessage call in fltk's main loop.


: : GetCursorPos done
: : SetCursor NO
: : SetWindowPos complicated - use MoveWindow instead
: : LoadIcon NO
: : LoadCursor NO
: : RegisterClassEx no - use RegisterClass instead
: : IsIconic NO
: : OpenIcon no
: : BringWindowToTop use ShowWindow instead for the time being.

I know what we can get fltk running with Microwindows quickly.  But
the key is keeping the number of calls into Microwindows DOWN, rather
than UP.  Then we can add functionality after you/we get a simple demo
running.  So, as I said, I think just getting the window creation, basic
display and painting, and message loop going are the best bet...

Regards,

Greg