On Wed, 14 Jan 2009, Michael Drake wrote:
[CSS parser]
1. Is currently in progress, as libcss. Dunno what the changes are it
will be done by the time GSoC starts.
Even if it isn't, there's not enough work left to fill 10 weeks. The
selection algorithm can easily be implemented in a few days of full-time
resource, and that's the only major thing outstanding. The remaining
parsing issues are trivial in comparison.
[PDF export & printing]
4. & 5. Could probably do with some more polishing, but I'm not sure it's
worth a summer project.
Agreed.
[Dynamic pseudo classes]
7. Depends on libcss.
Likely. It's mostly layout, however.
[fandango]
9. Is currently partially done. We would need to assess exactly how
much more is needed for this.
Sean? Can you comment on this?
[Inlines]
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.
Right.
[GTK frontend]
11. Obviously this was improved significantly over the last GSoC, but
I think an improving the GTK front end project could be run again.
[Keyboard nav, other platforms, page reader, RO gui code -> library]
The rest (2, 3, 6 and 8) can all be run again, as those aspects haven't
been touched.
The first three seem reasonable. I have serious reservations about
a) finding someone suitably qualified and b) the utility of extracting a
library from the RO UI code.
Also, we can think up new projects. I'll have a think about that for a few
days.
One that is obvious to me is libdom. It needs the following doing to it:
1) Fixing so it compiles
2) Sort out the mess that is dom_string
3) Use vtables rather than known function names + switching on node type
4) Test suite
5) Write a binding to hubbub
6) The rest of DOM 3/2/1/0 implementing (primarily, Events)
3. What should our student application process be?
Same as last time? Maybe we should do more to encourage patches before
student application deadline.
Here's my comments from last year:
In future, it would be useful to specify our application requirements
more clearly. I don't think it's worthwhile to provide a template, as
that makes things too easy. The idea here is to provide sufficient
hurdles to weed out the majority of poor applications. We could also
require some code contribution prior to application.
In addition to that, any student who suggests their own idea gets a thumbs
up from me. Not least as this implies that they've actually thought about
it. Similarly, anyone who interacts with us well from an early stage is
probably more likely to be favoured.
4. Who is available to mentor?
I expect I am.
J.
