OK, then.
Here are my priorities then :
1 provide a test framework, based on the following notions : feature testing non regression testing unit testing
-> thus providing - a kind of test matrix - some test cases/documents - a test report template (maybe script/interface) in order to automatically generate test reports
I insist on the fact that having Inkscape being scriptable would be a huge plus for automated tests, especially for : - SVG compliance, rendering, printing (automaticaly loads svg files, compare to 'reference', and provide a status). - editing features (automatically generates svg files according to scenario and compare to reference.
2 Test (of course).
3 Work on a 'help/work needed' page. And a the same time get a look on extensions specifications.
4 work on French translation.
Regards,
Matiphas
Gazal, Geraud (MED) wrote:
I insist on the fact that having Inkscape being scriptable would be a huge plus for automated tests, especially for :
There is a patch floating around for adding python scripting. Maybe you could work on enhancing that? Then I could port my cross-stitch program ;-) [1]
njh [1] Ted: and get that article just for you :)
On Wed, 2004-07-07 at 02:56, Nathan Hurst wrote:
I insist on the fact that having Inkscape being scriptable would be a huge plus for automated tests, especially for :
There is a patch floating around for adding python scripting. Maybe you could work on enhancing that? Then I could port my cross-stitch program ;-) [1]
Yeah, there are some Sodipodi-isms in there that will need to get removed. Also, the whole thing is bound to the SPObject layer, and I think that scripting is probably more useful being bound to the SPRepr layer... So, that patch, while useful, isn't a slam dunk.
--Ted
participants (3)
-
Gazal, Geraud (MED) -
Nathan Hurst -
Ted Gould