On Sun, 2008-02-24 at 11:53 -0800, Ted Gould wrote:
On Sat, 2008-02-23 at 23:18 -0800, Bryce Harrington wrote:
But I think there is a compromise which will solve this, if we set two criteria for this year's involvement:
- All Inkscape GSoC projects this year must be implemented as extensions, with no changes required to Inkscape's core
Agreed.
- All mentoring be done by developers who will not be focusing on the 0.47 codebase refactoring efforts. (In particular, developers with good extension development experience.) We will limit the number of candidates we accept to the number of mentors available.
I think it should depend on the individual mentor. I think almost everyone should have some kind of hand in the refactoring, so by definition that would give us no mentors. Also, it would depend on the time that each mentor has to give.
Now, I think that this is a good time to discuss ideas for projects, and I'll dump my Tomboy note :)
* Extension to spell check whole document. Perhaps grammar check also. This extension should go through all of the text boxes, separate text and comments and allow the user to correct the problems. While we have the spell checking in the text dialog, it's a pain to go through as a "final proof" and ensure that all your text is sane. * Run diff tools on the XML document created by scripts so that only the diffs are merged into the tree. Currently the scripting interface basically sends an XML file, and takes the returned XML file at face values. What would be better is if the scripting interface detected the change in the document, and only applied those to the tree. There are some good algorithms for this from the folks that did Union. It would increase the speed of execution for the scripts and reduce the amount of data that they throw on the undo stack. * KML/SVG exchange scripts. I have mentors for these already committed. Seriously, good people. This is a high visibility project, probably get you friends at Google :)
Yeah, intro me to them, and I'll intro to my friends who are working on KML stuff :)
* Openstreetmaps Import. Currently OSM generates a set of XML data, transforms it via XSLT into SVG and then renders it in Inkscape. I'd like to see an import extension that allows you to specify the data you want, pulls it from OSM, and then imports it into Inkscape. This would be useful for people making a maps.
Totally useful!
Jon
Okay, those are my ideas :)
--Ted
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel