On 13.03.2011 16:53, Rob Kendrick wrote:
People have created ports inside a week. Look at the OS X port, which
took only a couple of weeks. It's not difficult. It's easy.
I don't think so - there is no doc for the gui_ functions, and no doc
for other parts like browser_window_redraw. etc.
And ports pass different values to that function - gtk always passes
zero as scroll value, other frontends pass scroll value as negative
value...
And there is a difference between plain text content and html content...
there is no guideline for creating a port and no information on how
things have to be.
And there is no info on how to implement frames - sometimes gui_create(
frameset ) is called - sometimes it is not ( instead, gui_create( frame
) is called.
And it took me weeks to understand the bitmap plot function - the
clipping rectangle isn't described anywhere - at least not for bitmaps
which are *not* repeating. It's not clear if the clipping is for the
resized, or for the not-resized bitmap - that's undefined.
And then the active flag within gui_poll... it's not enough to just
check that flag to see if gui_poll can go to sleep - because that would
break the rendering process (the active flag just indicates network
activity). To be honest, I haven't understand why it is working. I
assume the core is not using the schedule functions, so there is no way
for the core to controll sleep of the gui_poll.
You always have to read the core code before can implement that, or you
just make the right assumptions...
It's not really hard to setup an port, but it's isn't easy, too.
Greets,
m
