In article <[email protected]>,
John-Mark Bell <[email protected]> wrote:
> Some questions:
> 1. Are we intending to apply this year?
Yes, I think it's certainly worth it. :)
> 2. What projects do we have that can be done over a summer?
FWIW, last years list was:
1. New CSS parser and selector engine
2. Native Windows or Mac OS X ports
3. Keyboard navigation
4. Printing improvements
5. PDF plotter
6. Page reader
7. Dynamic pseudo classes
8. Abstract RISC OS GUI code into a separate library
9. Extracting the core into a library
10. Improved inline element handling
11. Improved GTK front end; tabs, downloads, etc
1. Is currently in progress, as libcss. Dunno what the changes are it
will be done by the time GSoC starts.
4. & 5. Could probably do with some more polishing, but I'm not sure it's
worth a summer project.
7. Depends on libcss.
9. Is currently partially done. We would need to assess exactly how
much more is needed for this.
10. The changes to make rendering take into account margins, paddings,
splittings and nestings when plotting background colours, images
and borders are done. There are still other issues like white-space
property and vertical-align.
11. Obviously this was improved significantly over the last GSoC, but
I think an improving the GTK front end project could be run again.
The rest (2, 3, 6 and 8) can all be run again, as those aspects haven't
been touched.
Also, we can think up new projects. I'll have a think about that for a few
days.
> 3. What should our student application process be?
Same as last time? Maybe we should do more to encourage patches before
student application deadline.
> 4. Who is available to mentor?
I am available to be a mentor candidate. I think it worked quite well last
time, when I was available to help any student when other mentors weren't
around, although I think I could be a mentor for something layout or box
tree related.
Michael
--
Michael Drake (tlsa) http://www.netsurf-browser.org/
