Dear George, It would be most useful if the transformation scenarios had an option that required the document in the editor to be refreshed after the transform (for cases where an XQuery transform is applied to the current document in a database and the editor does not spot the change). Also, use of XSLT result-document to generate multiple documents overrides the default document generated, the transformation scenarios do not handle this case (they always expect a result file). It's annoying to have Oxygen generate a preview of an empty file in these cases. With respect, Steven -- Dr. Steven Ericsson-Zenith Institute for Advanced Science & Engineering http://iase.info http://senses.info
On 1/24/10 10:34 AM, "Steven Ericsson-Zenith" <steven@semeiosis.org> wrote:
Dear George,
It would be most useful if the transformation scenarios had an option that required the document in the editor to be refreshed after the transform (for cases where an XQuery transform is applied to the current document in a database and the editor does not spot the change).
Also, use of XSLT result-document to generate multiple documents overrides the default document generated, the transformation scenarios do not handle this case (they always expect a result file). It's annoying to have Oxygen generate a preview of an empty file in these cases.
In that case, you can simply not have the bogus output document opened in the editor. You manually open whatever result documents you generate and leave them open. Rerunning the transform updates those docs on the file system and Oxygen will either automatically refresh them or ask you if you want to refresh them, depending your auto-refresh settings. Having said that, I agree that it would be handy to be able to specify the name of the result file to open separate from the nominal output file, so that when a transform does use result-document and you can predict what the name of the result will be, Oxygen will open it automatically. I think there's a general case of transforms that take an "output document" XSLT parameter or some other parameter that determines the names of the result documents. Cheers, Eliot -- Eliot Kimber Senior Solutions Architect "Bringing Strategy, Content, and Technology Together" Main: 610.631.6770 www.reallysi.com www.rsuitecms.com
Hi Steven, As Eliot mentioned in case of local files oXygen can automatically detect that they are changes and reload them. What you can do for remote resources if to use the File->Revert action to refresh them. From Options->Menu shortcut keys you can assign a convenient shortcut for this action. We will look to see if it is possible to avoid writing an empty output file if nothing is generated to the standard output from the stylesheet. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Steven Ericsson-Zenith wrote:
Dear George,
It would be most useful if the transformation scenarios had an option that required the document in the editor to be refreshed after the transform (for cases where an XQuery transform is applied to the current document in a database and the editor does not spot the change).
Also, use of XSLT result-document to generate multiple documents overrides the default document generated, the transformation scenarios do not handle this case (they always expect a result file). It's annoying to have Oxygen generate a preview of an empty file in these cases.
With respect, Steven
-- Dr. Steven Ericsson-Zenith Institute for Advanced Science & Engineering http://iase.info http://senses.info
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Thanks for the response George, I am aware of the current options. The particular problem I have is that I, for example, use an XQuery update on an eXist server to insert time-stamps into a document to record the date and time of an update to the document as the current- file in Oxygen. If the author continues without performing a "revert" by hand after performing this action then the time stamp is lost. I have a few cases where I want to run a transformation scenario against the current file and reflect those changes or update a reference resulting from them in that file. When such a file is in the file system Oxygen will see the change and prompt the user. I'd like to force a revert in that case too (without prompting). Using a manual "revert" is counter intuitive and will introduce errors. With respect, Steven On Jan 25, 2010, at 4:34 PM, George Cristian Bina wrote:
Hi Steven,
As Eliot mentioned in case of local files oXygen can automatically detect that they are changes and reload them. What you can do for remote resources if to use the File->Revert action to refresh them. From Options->Menu shortcut keys you can assign a convenient shortcut for this action.
We will look to see if it is possible to avoid writing an empty output file if nothing is generated to the standard output from the stylesheet.
Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
Steven Ericsson-Zenith wrote:
Dear George, It would be most useful if the transformation scenarios had an option that required the document in the editor to be refreshed after the transform (for cases where an XQuery transform is applied to the current document in a database and the editor does not spot the change). Also, use of XSLT result-document to generate multiple documents overrides the default document generated, the transformation scenarios do not handle this case (they always expect a result file). It's annoying to have Oxygen generate a preview of an empty file in these cases. With respect, Steven -- Dr. Steven Ericsson-Zenith Institute for Advanced Science & Engineering http://iase.info http://senses.info _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
-- Dr. Steven Ericsson-Zenith Institute for Advanced Science & Engineering http://iase.info http://senses.info
Dear Steven, I understand the problem. However I am not sure that this functionality should stay in the transformation scenarios. More, it looks like a user defined action that can take the form of a plugin - that should be able to perform different operations and change the content of refresh different editor files. It it true that we do not provide an API for the plugins to have easily access to executing transformation scenarios for example, but this is one of the todo items that we will not be able to postpone soon as it is also very useful when doing a CMS integration. For local files to be refreshed without asking for a confirmation please enable the Options->Preferences -- Global -- "Auto update unmodified editors on file system changes" and if the file is not modified in oXygen it will be loaded automatically from disk if it is changed. You may want to also enable the Option->Preferences -- Editor / Open/Save -- "Save all files before transformation or validation" to avoid having modified files and thus have always the automatic refresh of modified local files. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Steven Ericsson-Zenith wrote:
Thanks for the response George, I am aware of the current options.
The particular problem I have is that I, for example, use an XQuery update on an eXist server to insert time-stamps into a document to record the date and time of an update to the document as the current-file in Oxygen. If the author continues without performing a "revert" by hand after performing this action then the time stamp is lost.
I have a few cases where I want to run a transformation scenario against the current file and reflect those changes or update a reference resulting from them in that file. When such a file is in the file system Oxygen will see the change and prompt the user. I'd like to force a revert in that case too (without prompting).
Using a manual "revert" is counter intuitive and will introduce errors.
With respect, Steven
On Jan 25, 2010, at 4:34 PM, George Cristian Bina wrote:
Hi Steven,
As Eliot mentioned in case of local files oXygen can automatically detect that they are changes and reload them. What you can do for remote resources if to use the File->Revert action to refresh them. From Options->Menu shortcut keys you can assign a convenient shortcut for this action.
We will look to see if it is possible to avoid writing an empty output file if nothing is generated to the standard output from the stylesheet.
Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
Steven Ericsson-Zenith wrote:
Dear George, It would be most useful if the transformation scenarios had an option that required the document in the editor to be refreshed after the transform (for cases where an XQuery transform is applied to the current document in a database and the editor does not spot the change). Also, use of XSLT result-document to generate multiple documents overrides the default document generated, the transformation scenarios do not handle this case (they always expect a result file). It's annoying to have Oxygen generate a preview of an empty file in these cases. With respect, Steven -- Dr. Steven Ericsson-Zenith Institute for Advanced Science & Engineering http://iase.info http://senses.info _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
-- Dr. Steven Ericsson-Zenith Institute for Advanced Science & Engineering http://iase.info http://senses.info
participants (3)
-
Eliot Kimber -
George Cristian Bina -
Steven Ericsson-Zenith