In article <EMEW,l1MJufd8e8c0962a57e79af07b52f8996d00d8,jmb%netsurf-browser.org,1235418990.12903.39.ca...@duiker>, John-Mark Bell <[email protected]> wrote: > On Tue, 2009-01-27 at 20:01 +0000, Michael Drake wrote:
> > 4. Extracting the core into a library > This either needs specifying properly or dropping from the list. The > issue we had with this last time is that it's far too open-ended. OK. > > 5. Layout engine improvements > As above. What improvements? Off the top of my head: - Stacking order - Fixed position - Fixed backgrounds - Table stuff (various issues with row style) - Vertical align - White-space property There's more, but I think any student would be lucky to get their head round layout and do all of that in the time. > > 6. LibDOM > This one, like Hubbub was last year, is well constrained (although, > unlike Hubbub, it has the potential to get out of control). Best, I > think, is to limit it to Core, Events, and possibly HTML. OK. It would be good to have a few paragraphs of prose explaining what has been done, and what needs doing with links to relevant docs and spec sections. > > 8. Automated NetSurf layout test suite > Again, needs specifying properly. OK. > > 9. Improved GTK front end > > 10. Improved Haiku/BeOS front end > > 11. Improved RISC OS front end > What improvements (for all 3)? For RISC OS: - Tabs - Better config e.g. web page language choice option - Richer status bar, perhaps progress bar and icons for SSL, and to indicate what it's doing - OLE - Favicons Some of these obviously need some work on the core, but that's no bad thing. > > It would be good to have some more core related ones, I think. How > > about that idea that's popped up a few times about allowing NetSurf > > to make a report of all errors and problems found with the HTML and > > CSS of a page and the rewrite of NetSurf's internal logging handling? > Rewriting logging is desirable. That said, I don't envisage it being a > full summer's work for a half-competent student. Note that logging parse > errors from the current CSS code is probably somewhat of a waste of > time, given it'll likely be replaced some point during the GSoC cycle. OK. > > Also how about an idea related to general browsing efficiency, for > > example only decoding images when they need to be displayed, making a > > disc cache, and other stuff? Don't know how much work there is in that > > kind of thing. > Again, this needs specifying properly. I think first it needs some ideas from people about where there is room for improvements, to see if it's viable. Another idea is a completely plotters based treeview for global history, cookie manager and bookmarks, to make that stuff all able to be handled by the core, lessening the amount of front end specific code that needs to be written and making sure the code is well tested. Also there's the generic data storage in urldb. You also mentioned that how URLs are handled needed careful consideration after 2.0? I'm not sure why or if it's relevant to this? Michael -- Michael Drake (tlsa) http://www.netsurf-browser.org/
