Hello, I've create a scenario associated with a document type xml (only one). Is it possible to apply this scenario without selecting it in the Configure Transformation Dialog when I click on Apply Transformation Scenario button? Is it possible to 'Save To URL' the result of a transformation? Best Regards, _______________________________________ Isabelle Rogie Database Chief project Wolters Kluwer France
Hello, It is necessary to select it once in the Configure Transformation dialog because it is necessary to create an association between an XML document and the XSLT stylesheet that will transform it. In the current version Oxygen does not assume that an XML document of document type X must be transformed with the unique scenario of document type X because the Configure Transformation dialog lists also the global scenarios but we will consider assuming that as an enhancement for a future version. The result of a transformation can be saved only to the local computer. Saving to a URL is another enhancement for a future version. Regards, Sorin Rogie Isabelle wrote:
Hello,
I’ve create a scenario associated with a document type xml (only one).
Is it possible to apply this scenario without selecting it in the Configure Transformation Dialog when I click on Apply Transformation Scenario button?
Is it possible to ‘Save To URL’ the result of a transformation?
Best Regards,
_______________________________________
**Isabelle Rogie**
Database Chief project
Wolters Kluwer France
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Sorin, it would be nice to have in addition a default scenario for the current project, maybe associated with the file type. It's a little bit inconvenient to pick up again and again the same scenario, especially when my list of scenarios is longer then the viewport in the window. BTW: It would also be nice if the layout manager could safe size and position of the scenario list window. Best regards, Stefan Sorin Ristache schrieb:
Hello,
It is necessary to select it once in the Configure Transformation dialog because it is necessary to create an association between an XML document and the XSLT stylesheet that will transform it.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKHvuJ6m+l2LO+BGwRArGsAKCUAFiIaR+FqfYwlUooX2uLi9nx+QCgmBu7 1STK98+2LJleTPJ27biqyrc= =HKh1 -----END PGP SIGNATURE-----
Hello, A project usually contains files of different types so a scenario cannot be usually associated with all the files of a project. You can run the action Apply Transformation Scenario instead of Transform With ... for applying the scenario associated with the file for each file of the project or the current selection in the project. This avoids selecting a scenario from the list which is required by the action Transform With .... If an association was already created for a file it will be used for that file as in a normal transformation applied only to that file. If an association was not created but there is only one scenario in the document type the feature which we will add (requested by Rogie) will create and apply the association with this scenario by default. I think this will help you to avoid picking up again and again the same scenario. Regards, Sorin Stefan Krause wrote:
Hello Sorin,
it would be nice to have in addition a default scenario for the current project, maybe associated with the file type. It's a little bit inconvenient to pick up again and again the same scenario, especially when my list of scenarios is longer then the viewport in the window. BTW: It would also be nice if the layout manager could safe size and position of the scenario list window.
Best regards,
Stefan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Sorin, I apologize for insist, but if you take hands on the scenario manager, you can take my use case in account: Usually I have for each of our costumers one project. Each scenario has from 5 to 10 transformations, which are all necessary at different stages or in special cases, but only one of them is the default scenario (it provides checks for consistency and schematron-like assertions). In every project I have to handle from 10 to 100 files, and after every stage the files are saved in a different folder (consider folders for rough OCR, corrected text, and final xml). Usually I process the files sequential. The main reason is that rarely more than 3 files are at the same stage, another reason is that Oxygens transformation result pane is global (i.e. not file associated like the xpath result pane), and messages from the xslt processor get overwritten. So with Oxygens current behavior I have to associate every xml file up to 5 times with the default scenario (one click per stage). I think it is clear that a real default scenario, which is called by pressing the Apply Transformation button or ctrl-shft-t would make this process much easier. Thanks, Stefan Sorin Ristache schrieb:
Hello,
A project usually contains files of different types so a scenario cannot be usually associated with all the files of a project. You can run the action Apply Transformation Scenario instead of Transform With ... for applying the scenario associated with the file for each file of the project or the current selection in the project. This avoids selecting a scenario from the list which is required by the action Transform With .... If an association was already created for a file it will be used for that file as in a normal transformation applied only to that file. If an association was not created but there is only one scenario in the document type the feature which we will add (requested by Rogie) will create and apply the association with this scenario by default. I think this will help you to avoid picking up again and again the same scenario.
Regards, Sorin
Stefan Krause wrote:
Hello Sorin,
it would be nice to have in addition a default scenario for the current project, maybe associated with the file type. It's a little bit inconvenient to pick up again and again the same scenario, especially when my list of scenarios is longer then the viewport in the window. BTW: It would also be nice if the layout manager could safe size and position of the scenario list window.
Best regards,
Stefan
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFKH7a26m+l2LO+BGwRAl3AAKDabVEDJR/ZwcTn+wOkTFkhjZIH/wCghyFj aIqQ5yBHyEbrI+JUc809ZCU= =4VVD -----END PGP SIGNATURE-----
So you want to be able to select and set a scenario in the list of scenarios created at the document type level (5 scenarios in your case created in the Transformation tab of the Document Type dialog) as the default scenario of that document type and run the current default scenario when an XML document of that type is transformed with the Apply Transformation button or Ctrl-Shift-T? Regards, Sorin Stefan Krause wrote:
Hello Sorin,
I apologize for insist, but if you take hands on the scenario manager, you can take my use case in account:
Usually I have for each of our costumers one project. Each scenario has from 5 to 10 transformations, which are all necessary at different stages or in special cases, but only one of them is the default scenario (it provides checks for consistency and schematron-like assertions).
In every project I have to handle from 10 to 100 files, and after every stage the files are saved in a different folder (consider folders for rough OCR, corrected text, and final xml). Usually I process the files sequential. The main reason is that rarely more than 3 files are at the same stage, another reason is that Oxygens transformation result pane is global (i.e. not file associated like the xpath result pane), and messages from the xslt processor get overwritten. So with Oxygens current behavior I have to associate every xml file up to 5 times with the default scenario (one click per stage). I think it is clear that a real default scenario, which is called by pressing the Apply Transformation button or ctrl-shft-t would make this process much easier.
Thanks,
Stefan
participants (3)
-
Rogie Isabelle -
Sorin Ristache -
Stefan Krause