So the possible ideas so far are:
1. Native Windows or Mac OS X ports 2. Keyboard navigation 3. Page reader 4. Extracting the core into a library 5. Layout engine improvements 6. LibDOM 7. LibSVGTiny 8. Automated NetSurf layout test suite 9. Improved GTK front end 10. Improved Haiku/BeOS front end 11. Improved RISC OS front end 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 NetSsurf 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? 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. Michael -- Michael Drake (tlsa) http://www.netsurf-browser.org/
