[scribus-dev] Tables GSoC draft proposal

[a.l.e]

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:

- 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