[scribus-dev] Tables GSoC draft proposal

[Elvis Stansvik]

Hi a.l.e,

2011/3/29 a.l.e <ale.comp_06 at xox.ch>:
> hi elvis,
>
> looks like a solid proposal!
>
> looking at the past GSOC projects and considering how important table
> editing is,  i'd like to suggest:

Following your suggestions, I've updated the proposal with the
following changes:

* Cell/column spanning has been made mandatory (removed from contingency plan).
* Scribus trunk integration added to project deliverables/timeline. To
compensate, breaking across pages was removed from the project.
* The "Post-Summer of Code Commitment" section has been folded into a
new section "The Future" where I also list a few possible future
table-related projects.
* Scripting API added to project deliverables/timeline/contingency plan.
* Suggest importing features be implemented as scripts, and give CSV a
higher priority than ODT.

I believe that is it.

The updated version is on the wiki (and in the PDF, which is now
linked from the wiki page under "Printable Version").

Tell me if there's anything more you'd like changed/clarified (that
goes for anyone and everyone).

Otherwise I'll submit the proposal to you guys through Google Melange
as soon as I get an "OK".

Thanks for the input!

Elvis

>
> - integrating the code into the trunk should be part of the GSOC (and not
> happen at some later time; the answer from craig to your mail may suggest
> that this may happen...)
> - you may define the extensions to your implementation which are important
> but you could / may not fit into the time frame of the GSOC (having an idea
> about the future direction may help people interested in single features to
> implement them as an "independent" project in the near future)
>
> some more specific ideas:
> - i'd rather to have some binding to the scripter API than "native" CSV
> import (and i'm not sure how badly i want to have them imported from .odt...
> going through CSV may be enough...)
> - column / rows spanning is imo more important than page breaking (and i
> wonder whether it's also easier to implement)
> - as craig wrote, it would be better to have both table implementations in
> parallel in trunk (and remove the old one when its features are matched by
> the ng one: this has been done for the preferences, the scripter and the
> PP...)
>
> voilà, i wish you good luck with your proposal and -- hopefully -- with your
> GSOC project!
>
> ciao
> a.l.e
>
> _______________________________________________
> scribus-dev mailing list
> scribus-dev at lists.scribus.net
> http://lists.scribus.net/mailman/listinfo/scribus-dev
>