Yes, I remember our conversation on Twitter.
1. We can show this XML as html in browser or any other form. I tried to Transform my XML, it shows the process "Applying transformation" in Oxygen XML editor but does nothing. On the other hand when we create a Dita form and apply transformation it shows output in browser as well.
XML gets published to a specific output, like HTML, by applying XSLT scripts. Oxygen has this concept of a Transformation scenario
, which represents a configuration which tells which XSLT get applied and with what options. For Dita Oxygen comes bundled with all the required XSLTs as well as pre-configured transformation scenarios.
You can also create this transformation scenario inside the document type/framework so that all users have access to it after you distribute the framework.
2. How can we use Eclipse ? Or what is the role of eclipse in Oxygen XML?
There are two situation s in which you would use Eclipse:
a. Besides being a Standalone application, Oxygen also has an Eclipse plugin distribution. Why would people use this plugin? Well, Eclipse has a variety of other plugins, each offering different support, so you can create complex environments.
b. Oxygen has a Java based API which can be used for all sorts of customizations. Eclipse, as an Java Integrated development environment, can be used when working with this Java based API (with our SDK).
From what I understand, in your situation, you would need Eclipse to work with our Java based API, perhaps to create a custom author operation.
As we are in the learning phase of Oxygen XML we just want a demo for it in which we can have a form with some text fields, and a save button (which i already have). Now upon button click i want to add some validations on the text fields and if data is in correct form i want to submit form and show those values under form using <p> or any other label tag.
Perhaps an action based on an XSLTOperation
can help with this use case. The XSLT script can collect the data from the form, check some requirements and then it can build a new fragment to be inserted after the form. If you go with this operation then you wont need the Oxygen SDK anymore as there is no need to create a custom operation. Do you think you can do everything you need from an XSLT script?
Anyway, it would help if you can send what you have so far (the framework, sample XML, CSS). If I see the framework then I could understand why you aren't able to define the action in it, what's missing.
Yes as mentioned in SDK documentation i created the sample project from command line but it gave me error. Then i searched this forum and following one of the posts i was to create the sample project and upon building that project it showed many errors regarding maven, tomcat unavailability etc.
Chances are that you might not need the SDK, yet. For example is the XSLTOperation is enough. Perhaps if I see the log, the error messages, I might understand what's the problem.