Status on extensions for 1.0?
Hi Martin,
Would you mind giving us a status report on how the extension work is coming? Maybe a list of all the extensions and for each whether they're good to go, in progress, broken, etc.
In reading some user critiques of Inkscape, sounds like some of the extensions may be underutilized, so 1.0 may be a useful point to do some selective curation? Curious about if you already have plans underway there.
Bryce
Hi Bryce,
My plan for getting some visibility on where we are is via the comparison process generated by Thomas. He kindly developed a way of running extensions against 0.92 and then compare them with the same extensions runnings against 1.0. The task is to integrate those as proper tests that will give us information about where we stand in the CI and for developers who want to help.
What we have already is pytest (added by Ryan) which gives us coverage reports and runs empty svg files against every extension. So we can both see what code we're not hitting in the tests as well as maintaining the levels on the old code so they at least run with a blank template. Although many extensions have more tests than that.
I made sure all the tests were passing today and I'm about to set about the comparison test addition.
Best Regards, Martin Owens
On Sun, 2019-03-24 at 11:47 -0700, Bryce Harrington wrote:
Would you mind giving us a status report on how the extension work is coming? Maybe a list of all the extensions and for each whether they're good to go, in progress, broken, etc.
In reading some user critiques of Inkscape, sounds like some of the extensions may be underutilized, so 1.0 may be a useful point to do some selective curation? Curious about if you already have plans underway there.
On Sun, Mar 24, 2019 at 09:29:35PM -0400, doctormo@...400... wrote:
Hi Bryce,
My plan for getting some visibility on where we are is via the comparison process generated by Thomas. He kindly developed a way of running extensions against 0.92 and then compare them with the same extensions runnings against 1.0. The task is to integrate those as proper tests that will give us information about where we stand in the CI and for developers who want to help.
Thanks.
The following wiki page looks like good docs on the changes, is this reasonably up to date?
http://wiki.inkscape.org/wiki/index.php/Updating_your_Extension_for_1.0
Would be great if the "Replace specific functions" section could get fleshed out more prior to beta, particularly for guiding 3rd party extension folks on their updates.
The requirement for test cases going forward is good to see. Is there also an API versioning plan for future changes that may be backwards incompatible?
What we have already is pytest (added by Ryan) which gives us coverage reports and runs empty svg files against every extension. So we can both see what code we're not hitting in the tests as well as maintaining the levels on the old code so they at least run with a blank template. Although many extensions have more tests than that.
I made sure all the tests were passing today and I'm about to set about the comparison test addition.
Is this something that can be run in the gitlab CI and posted somewhere automatically? If not, how do I run the test suite, is it just done via the 'python3 setup.py check' in the extensions module, or is there another way to run it?
Bryce
Best Regards, Martin Owens
On Sun, 2019-03-24 at 11:47 -0700, Bryce Harrington wrote:
Would you mind giving us a status report on how the extension work is coming? Maybe a list of all the extensions and for each whether they're good to go, in progress, broken, etc.
In reading some user critiques of Inkscape, sounds like some of the extensions may be underutilized, so 1.0 may be a useful point to do some selective curation? Curious about if you already have plans underway there.
The requirement for test cases going forward is good to see. Is there also an API versioning plan for future changes that may be backwards incompatible?
So far we had only talked about getting it to 1.0 to match Inkscape's release version. After that we'll start depricating older stuff depending on what we see in the wild. Since we've never done this kind of thing before, we don't know how the community of extension developers will respond.
Is this something that can be run in the gitlab CI and posted somewhere automatically? If not, how do I run the test suite, is it just done via the 'python3 setup.py check' in the extensions module, or is there another way to run it?
It's already running in the CI pipeline, it's failing. But it's running. So hopefully when all the specific issues with pytest and py2/3 are worked out (I noticed for instance that a failure happens in jessyink because Inkscape isn't available on the CI builder, but is on my machine, so doesn't fail for me)
The command is pytest, and you can specify some good options.
Best Regards, Martin Owens
participants (2)
-
unknown＠example.com -
Bryce Harrington