Hi all,
Due to work-related problems I've had a tough time getting started on
my project. However, all issues have been resolved in that respect
and I intend to really get rolling over the next few weeks. The
probable libraries outlined in my original application included CSS,
Layout, NetSurf, BMP, and GIF libraries.
This week I began with the GIF library as follows:
> Familiarizing myself with the GIF code and how it works within NetSurf
> Moving all necessary code from NetSurf's "gifread" files to an external
> location in my branch
> Callback functions were implemented to allow operation of libnsgif to go
> smoothly regardless of the bitmap functions the caller chooses to use
> Test-case was provided in my branch (nsgiftest) where libnsgif is used
> outside of NetSurf (although the code is entirely based on NetSurf's
> implementation)
The majority of the work was bringing myself back up to speed in C
programming, moving things around, and familiarizing myself with how
NetSurf implements images and other data (fetchers and the like).
Luckily understanding the fetchers should come in handy later when I
get to Layout and NetSurf libraries.
Things I need help with:
> Testing of libnsgif under RiscOS to ensure proper functionality
> Review of the code submitted thus far to catch any mistakes/bugs
> Comments, ideas, and criticisms as far as API, naming conventions, etc.
> regarding this library (especially since this is the first library; I can
> follow a similar path as I move on to the next ones)
Agenda for next week:
> Complete the BMP library from start to finish (should be similar to the GIF
> library, so I'm hoping this will be quick)
> Begin to grasp the code behind NetSurf's layout/HTML rendering to start the
> Layout library
Comments and concerns:
I spoke with John-Mark regarding the CSS library and--all though he
left it up to me--I think we came to an agreement that it would be in
our best interest for me to begin work on the Layout and NetSurf
libraries prior to the CSS work. Because he is currently looking at
developing a new CSS parser, it would be more effective if I tackle
the other projects at my disposal. Any and all comments and concerns
from the development team are welcome. I'd especially love to hear
more regarding the API; the code I've published thus far is really
just a "rough draft" to be molded by everyone.
Sean
