Hi, I have just release a new plugin for the oXygen XML IDE, in order to support XProject, the XML Project Manager tool. More infos on the XProject page at http://expath.org/modules/xproject/. XProject (loosly) defines a directory structure for an XML project: my-project/ src/ ... xproject/ project.xml The subdir src/ has whatever structure you want for your XML files, XSLT stylesheets, XQuery modules, XProc pipelines, resource files, and everything that is part of your project. The subdir xproject/ contains meta informations about your project. E.g. project.xml contains its name and version number, as well as several processors configuration for unit-testing purposes. Based on conventions for the components filename (i.e. *.xsl for stylesheets, *.xql for XQuery library modules, *.xq, *.xqy or *.xquery for XQuery main modules, etc.) it detects them in src/, and based on annotations in those files, it generates automatically a package descriptor and create the package for you. You can also generate a "delivery file" that contains the package, a README file, examples and source code. Or automatically launch unit- tests using XSpec. Or generate documentation for your XQuery modules using xquerydoc. Every dependency is already included in the plugin. To install, download the file xproject-oxygen-plugin-0.3.0.zip from: http://code.google.com/p/expath-pkg/downloads/list and unzip it in your oXygen install dir, in the subdir plugins/ (or copy the dir xproject/ which is at the root of the ZIP file into <your-oxygen>/plugins/). The next time you start oXygen, you will have 4 more buttons in the toolbar, named "Build", "Test", "Doc" and "Release". While editing any file within your project directory, you can click one of those buttons to execute the corresponding XProject target. "Build" creates a new package in dist/ based on src/, "Test" run the XSpec tests in test/ and place the reports in the same dir (see the sample project in the ZIP to see how to configure your processors and XML databases to run the tests), "Doc" places the XQuery documentation in dist/xqdoc/, and "Release" creates a new delivery file in dist/. The packages created by "Build" can be installed automatically in any EXPath Packaging System-compliant system. Any feedback, help, request for improvement is welcome! In particular, I would like to know how I can help a user creating a new project from within oXygen (e.g. by displaying a form to fill in the basic info like its name, version, etc. and create the project structure, and possibly by creating an Author mode for the project.xml files). Enjoy! -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/
Thanks Florent! I gave it a try and you can find some feedback below: * 1 * All operations end with "Build successful!" while it will be more useful to get some more information at the end, for example if there was something generated and where (is possible, of course). If I run the Doc action on the sample hello-world project I get a success message but I cannot find anything added to the project. * 2 * I do not get any output from the Doc and Test actions. I commented all the entries in the config under test except the ones for Saxon and I updated the XSpec home property: <tests> <processor name="http://expath.org/tmp/saxon/xquery" report="$1reports/$2-saxon-xq.html"> <property name="xspec-home" value="file:/Users/george/Documents/workspace/eXml/frameworks/xspec/"/> </processor> <processor name="http://expath.org/tmp/saxon/xslt" report="$1reports/$2-saxon-xsl.html"/> </tests> * 3 * The Author mode for the config file will not be difficult, it should be done in the form of a framework. However, while there are no problems rendering attribute values the Author mode will not be very friendly for editing them - as it does not present the attributes as content and what you edit directly in the document is content (text nodes) not attribute values. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 2/25/12 3:27 PM, Florent Georges wrote:
Hi,
I have just release a new plugin for the oXygen XML IDE, in order to support XProject, the XML Project Manager tool. More infos on the XProject page at http://expath.org/modules/xproject/.
XProject (loosly) defines a directory structure for an XML project:
my-project/ src/ ... xproject/ project.xml
The subdir src/ has whatever structure you want for your XML files, XSLT stylesheets, XQuery modules, XProc pipelines, resource files, and everything that is part of your project. The subdir xproject/ contains meta informations about your project. E.g. project.xml contains its name and version number, as well as several processors configuration for unit-testing purposes.
Based on conventions for the components filename (i.e. *.xsl for stylesheets, *.xql for XQuery library modules, *.xq, *.xqy or *.xquery for XQuery main modules, etc.) it detects them in src/, and based on annotations in those files, it generates automatically a package descriptor and create the package for you.
You can also generate a "delivery file" that contains the package, a README file, examples and source code. Or automatically launch unit- tests using XSpec. Or generate documentation for your XQuery modules using xquerydoc. Every dependency is already included in the plugin.
To install, download the file xproject-oxygen-plugin-0.3.0.zip from:
http://code.google.com/p/expath-pkg/downloads/list
and unzip it in your oXygen install dir, in the subdir plugins/ (or copy the dir xproject/ which is at the root of the ZIP file into <your-oxygen>/plugins/).
The next time you start oXygen, you will have 4 more buttons in the toolbar, named "Build", "Test", "Doc" and "Release". While editing any file within your project directory, you can click one of those buttons to execute the corresponding XProject target.
"Build" creates a new package in dist/ based on src/, "Test" run the XSpec tests in test/ and place the reports in the same dir (see the sample project in the ZIP to see how to configure your processors and XML databases to run the tests), "Doc" places the XQuery documentation in dist/xqdoc/, and "Release" creates a new delivery file in dist/.
The packages created by "Build" can be installed automatically in any EXPath Packaging System-compliant system.
Any feedback, help, request for improvement is welcome! In particular, I would like to know how I can help a user creating a new project from within oXygen (e.g. by displaying a form to fill in the basic info like its name, version, etc. and create the project structure, and possibly by creating an Author mode for the project.xml files).
Enjoy!
-- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hi, On 2/27/2012 5:00 AM, George Cristian Bina wrote:
* 3 * The Author mode for the config file will not be difficult, it should be done in the form of a framework. However, while there are no problems rendering attribute values the Author mode will not be very friendly for editing them - as it does not present the attributes as content and what you edit directly in the document is content (text nodes) not attribute values.
That sounds like a feature request for oXygen. :-> A CSS extension that supports displaying an attribute value as an editable field? (Is this a bad idea?) Cheers, Wendell -- ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
Hi Wendell, This is already recorded and we will get to this soon - it is currently planned to be fixed during version 14. I added your vote for it. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 2/28/12 10:37 PM, Wendell Piez wrote:
Hi,
On 2/27/2012 5:00 AM, George Cristian Bina wrote:
* 3 * The Author mode for the config file will not be difficult, it should be done in the form of a framework. However, while there are no problems rendering attribute values the Author mode will not be very friendly for editing them - as it does not present the attributes as content and what you edit directly in the document is content (text nodes) not attribute values.
That sounds like a feature request for oXygen. :->
A CSS extension that supports displaying an attribute value as an editable field?
(Is this a bad idea?)
Cheers, Wendell
Hi, I use File/Reopen a lot. But I also work with lots of different files in lots of different projects, so I find that files may drop off even a long "File/Reopen" list. I wonder if individual projects couldn't keep their own lists of files to reopen? Maybe this would be a "File Reopen" option in the projects menu. Then when I'm in a project it would retain a history of files to reopen, even when I haven't felt it worthwhile to add them to the project itself. (Yes, this does happen.) Silly idea? Some other way to do this already? Cheers, Wendell -- ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
Hello Wendell, Thank you for the feedback. That's an interesting idea to keep the file history on a project basis. I have logged it to our issue tracking tool and we will analyze and implement it in a future version of Oxygen. The only concern I have with this is that if we keep the file history in the project file (.xpr), some people might find it annoying when working with a version control system since the file keeps getting modified. So maybe we should use a separate file to store the project file history. Regards, Adrian Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support@oxygenxml.com Wendell Piez wrote:
Hi,
I use File/Reopen a lot. But I also work with lots of different files in lots of different projects, so I find that files may drop off even a long "File/Reopen" list.
I wonder if individual projects couldn't keep their own lists of files to reopen? Maybe this would be a "File Reopen" option in the projects menu. Then when I'm in a project it would retain a history of files to reopen, even when I haven't felt it worthwhile to add them to the project itself. (Yes, this does happen.)
Silly idea? Some other way to do this already?
Cheers, Wendell
Hello Adrian, I think a project file (.xpr) might already contains data that changes regularly, such as the documents that are currently open. My experience is that my project files are frequently different from a version control systems point of view; it is possible that I have changed important project properties, but find it surprising on the regularity at which I am told that the project files are different. Possibly, it might be worth thinking about what information would be better left out of them from a version control perspective. Regards, Anthony. -- -- ------------------------------------------------------------------------- Michael Anthony Smith, DeltaXML Ltd "Change control for XML" T: +44 1684 891992 E: anthony.smith@deltaxml.com http://www.deltaxml.com Registered in England 02528681 Reg. Office: Monsell House, WR8 0QN, UK On 03/05/2012 15:07, Adrian Buza wrote:
Hello Wendell,
Thank you for the feedback.
That's an interesting idea to keep the file history on a project basis. I have logged it to our issue tracking tool and we will analyze and implement it in a future version of Oxygen. The only concern I have with this is that if we keep the file history in the project file (.xpr), some people might find it annoying when working with a version control system since the file keeps getting modified. So maybe we should use a separate file to store the project file history.
Regards, Adrian
Adrian Buza oXygen XML Editor and Author Support
Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support@oxygenxml.com
Wendell Piez wrote:
Hi,
I use File/Reopen a lot. But I also work with lots of different files in lots of different projects, so I find that files may drop off even a long "File/Reopen" list.
I wonder if individual projects couldn't keep their own lists of files to reopen? Maybe this would be a "File Reopen" option in the projects menu. Then when I'm in a project it would retain a history of files to reopen, even when I haven't felt it worthwhile to add them to the project itself. (Yes, this does happen.)
Silly idea? Some other way to do this already?
Cheers, Wendell
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Dear Adrian, On 5/3/2012 10:07 AM, Adrian Buza wrote:
That's an interesting idea to keep the file history on a project basis. I have logged it to our issue tracking tool and we will analyze and implement it in a future version of Oxygen. The only concern I have with this is that if we keep the file history in the project file (.xpr), some people might find it annoying when working with a version control system since the file keeps getting modified. So maybe we should use a separate file to store the project file history.
Quite true. Not that sharing project files is ever non-trivial; it seems to require a bit of art. But you're right that doing this incorrectly would make it worse. Cheers, Wendell -- ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
Adrian and listers, On 5/3/2012 12:05 PM, I wrote:
Quite true. Not that sharing project files is ever non-trivial; it seems to require a bit of art. But you're right that doing this incorrectly would make it worse.
Maybe the fact that I'm confused between "trivial" and "non-trivial" illustrates the point. Cheers, Wendell -- ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
participants (5)
-
Adrian Buza -
Florent Georges -
George Cristian Bina -
Michael Anthony Smith -
Wendell Piez