I have made a more detailed proposal of what might be done, including a rough timeline (actually just the time amounts - I put the timeline into Google Calendar). The basic part is what I find both necessary and lasting to tell that KML files can be essentially displayed as SVG.
There are also additional ideas for improvements but I don't feel like I should decide what is important or needed. This is where I am asking you for directions.
Initially I was having many ideas of what could be made in this project. Now I'm afraid there is hardly any chance to touch exporting from SVG to KML (except for an extremely simple cases or some silly assumptions) or the import wizard for Inkscape, as in the first proposal. I would rather focus on the KML->SVG transform. Of course, I would like to know your point of view.
As for the previous version of application: firstly, I realised that those "configuration options" are not really needed and may be considered as an extension or optional part. Secondly, the mentioned web server requirement issue is no more important. I have adjusted my "framework" for this project and it works fine for static XSLT's which may be enough for the project.
I put the reviewed proposal as a comment to the application:
http://socghop.appspot.com/student_proposal/show/google/gsoc2009/piotrekk/t1...
It is still just an estimation. I have taken into account the time needed for basic learning, preparing tools, debugging and unpredicted situations, thus the timeline may be quite realistic.
The next comment contains some ideas how the basic part can be extended or improved. I would need some advice about that "optional" parts, as well as a revision of the "minimal" set. Any clues are welcome :-)
The plan (basic part) seems to be finishable before the mid-term evaluation, so I am asking for suggestions what else should be done. In the meantime I will keep investigating the SVG and KML secrets :-)
Best Regards, Piotrek