Ready for a new release?
Florent Georges
After a looong (too long) time, I think it is time for a new
release of XSpec. I've made a pre-3.0 release package and ZIP
archive, you can find them at, resp.:
http://fgeorges.org/tmp/xspec-0.3.0dev.xar
http://fgeorges.org/tmp/xspec-0.3.0dev.zip
Can you please have a look at them, and give any feedback in the
next couple of days? Without any comment, I'll release 0.3.0
officially, with the following change list (if you think about
something else that changed since 0.2, please tell me):
- improved XQuery support
- delivered as an EXPath package
- new tests (of XSpec itself)
- numerous bug fixes
- improved shell scripts
- new XProc harnesses for several processors
Regards,
--
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/
Marc van Grootel
Thanks for all the work, great to see a new release.
One comment about the xspec.bat
I think it still needs to have a couple of quotes put in:
line 53: ... -xsl:"%~dp0\generate-xspec-tests.xsl"
line 77: ... -xsl:"%~dp0\format-xspec-report.xsl"
I had the tutorial xspec fail once I had put the whole xspec package under the Oxygen framework dir. Adding these quotes fixed it.
One major gripe I had with the previous xproc harness was that it would not display the xslt compilation error output and only displayed a cryptic xproc error. I'm happy to see that now it does display them and the harness runs fine within Oxygen.
--Marc
--Marc
Tony Graham
...
> Can you please have a look at them, and give any feedback in the
> next couple of days? Without any comment, I'll release 0.3.0
> officially, with the following change list (if you think about
> something else that changed since 0.2, please tell me):
>
> - improved XQuery support
> - delivered as an EXPath package
> - new tests (of XSpec itself)
> - numerous bug fixes
> - improved shell scripts
improved shell scripts and Ant build file
> - new XProc harnesses for several processors
oXygen framework for editing?
Emacs nXML-mode 'schemas.xml' file???
Regards,
Tony.
Marc van Grootel
I attached my Oxygen .framework and templates dir. I'm still on Oxygen 11 not sure if it works for 12 or 13.
The .framework is configured to use the XProc harness.
It's not ideal yet though
- I've configured one fixed absolute path to send the reports to, others may prefer putting the report next to the .xspec itself, or send it to a fixed directory relative to the project url, ${pdu} but the directory has to exist, the XProc will not create it for you.
- the xspec-home option is also an absolute path because in Oxygen 11 the option values do not accept the ${..} variables.
Both need to be changed manually.
Works really well for me and is quite a lot faster than calling an external script or ant build file.
--Marc
Marc van Grootel
George Christian Bina graciously donated an Oxygen 13 license so here are the .framework file and templates dir for Oxygen 13.
This file doesn't have hard-coded absolute paths in them. The xspec-home option to the XProc script is now using a variable.
Also, in v13 the output directory is automatically created if it doesn't already exist.
There are probably different preferences of where you want the HTML report located. I prefer not to have them next to the .xspec because they might accidentally wind up in version control. However, that is the setting I used here. You may want to customize that. Otherwise it's good to go.
Thanks George!
--Marc
Tony Graham
> George Christian Bina graciously donated an Oxygen 13 license so here are
> the .framework file and templates dir for Oxygen 13.
There is an oXygen 11 framework file in Subversion. See
http://code.google.com/p/xspec/source/browse/#svn%2Ftrunk%2Feditors%2Foxygen
> This file doesn't have hard-coded absolute paths in them. The xspec-home
> option to the XProc script is now using a variable.
> Also, in v13 the output directory is automatically created if it doesn't
> already exist.
Your framework appears to expect the complete XSpec distribution under
${frameworks}/xspec/src/. Is that correct?
> There are probably different preferences of where you want the HTML report
> located. I prefer not to have them next to the .xspec because they might
> accidentally wind up in version control. However, that is the setting I
> used
> here. You may want to customize that. Otherwise it's good to go.
The other framework, after running the Ant build file, only provided the
schema. There are references in the build.xml file to css and templates
directories, but I can't remember ever doing anything with them. Given
how the scope of XSpec has expanded, I think it is useful to do as you
have done and include all of XSpec under the oXygen framework.
I think that implies that there could be a second form of the XSpec
distribution as an oXygen framework (though maybe not as part of the new
release) so that users only have to install one thing (and so George can
just pick it up and bundle it with oXygen and so further spread XSpec
usage). What do others think?
Regards,
Tony.
Marc van Grootel
Yep, I assume the complete framework there. Out of lazyness I just added a templates dir and the framework file.
I saw the one in SVN but it didn't contain a transformation scenario. I think that a long time ago I used that and added the transformation scenario.
Having it bundled would be even better.
--Marc
Florent Georges
> I think it still needs to have a couple of quotes put in:
> line 53: ... -xsl:"%~dp0\generate-xspec-tests.xsl"
> line 77: ... -xsl:"%~dp0\format-xspec-report.xsl"
Fixed. Dank u wel !
Florent Georges
> improved shell scripts and Ant build file
> oXygen framework for editing?
> Emacs nXML-mode 'schemas.xml' file???
Good catch, thanks!
Florent Georges
Hi,
> I attached my Oxygen .framework and templates dir
Thanks to you and Tony for this interesting discussion. Tighter
integration of XSpec within oXygen (and any other IDE, by the way)
is indeed very important. As this is not a trivial change and
more like a new feature, I suggest to discuss it more thoroughly
after the next release:
http://code.google.com/p/xspec/issues/detail?id=39