Hi, As I have read on previous posts, oXygen classifies mixed content based on the current contents of an element, is this correct? If so, is it possible for oXygen to classify elements based on the declarations made in the DTD or Schema it is associated to? I know that the work around for this is to specify the pattern of elements that you want to preserve the whitespace in the preferences or to manually insert an xml:space="preserve" attributes for these elements, but if an XML is associated with a DTD or a Schema then you can tell whether whitespace in that element is ignorable or not. Currently what I've been doing is for every project I have to specify in the pattern listing all the mixed content elements that are defined in the DTD/Schema so that when I do a pretty print the whitespace is preserved and this method is very troublesome. Is there anymore workaround for this other than the ones I mentioned above? Or can this be considered as an added feature for a future version of the product? Thanks, Jeff
Hello, There are no other workarounds yet. You have to specify the elements for which you want to preserve whitespace in one of the two ways. If you specify them in preferences you can store the Editor / Format /XML preferences at project level to avoid adding all the elements for all the projects in the same Preserve space elements table. We have this request already logged in our issue tracking system for a future version of oXygen. Regards, Sorin Jeff Sese wrote:
Hi,
As I have read on previous posts, oXygen classifies mixed content based on the current contents of an element, is this correct? If so, is it possible for oXygen to classify elements based on the declarations made in the DTD or Schema it is associated to?
I know that the work around for this is to specify the pattern of elements that you want to preserve the whitespace in the preferences or to manually insert an xml:space="preserve" attributes for these elements, but if an XML is associated with a DTD or a Schema then you can tell whether whitespace in that element is ignorable or not. Currently what I've been doing is for every project I have to specify in the pattern listing all the mixed content elements that are defined in the DTD/Schema so that when I do a pretty print the whitespace is preserved and this method is very troublesome.
Is there anymore workaround for this other than the ones I mentioned above? Or can this be considered as an added feature for a future version of the product?
Thanks, Jeff _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Dear, May I propose (once again) a neutral form of indent for Oxygen <root id="2"
<element position="1"> space are important here </element <element position="2"> space are also important here </element </root>
The only thing you can allow or not is to convert newline and tabs to space as an option Regards, Xmlizer On 7/20/07, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello,
There are no other workarounds yet. You have to specify the elements for which you want to preserve whitespace in one of the two ways. If you specify them in preferences you can store the Editor / Format /XML preferences at project level to avoid adding all the elements for all the projects in the same Preserve space elements table.
We have this request already logged in our issue tracking system for a future version of oXygen.
Regards, Sorin
Jeff Sese wrote:
Hi,
As I have read on previous posts, oXygen classifies mixed content based on the current contents of an element, is this correct? If so, is it possible for oXygen to classify elements based on the declarations made in the DTD or Schema it is associated to?
I know that the work around for this is to specify the pattern of elements that you want to preserve the whitespace in the preferences or to manually insert an xml:space="preserve" attributes for these elements, but if an XML is associated with a DTD or a Schema then you can tell whether whitespace in that element is ignorable or not. Currently what I've been doing is for every project I have to specify in the pattern listing all the mixed content elements that are defined in the DTD/Schema so that when I do a pretty print the whitespace is preserved and this method is very troublesome.
Is there anymore workaround for this other than the ones I mentioned above? Or can this be considered as an added feature for a future version of the product?
Thanks, Jeff _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Dear, Is there any chance to have such option soon in Oxygen XML ? Regards, Xmlizer On Sun, Jul 22, 2007 at 1:47 PM, mozer <xmlizer@gmail.com> wrote:
Dear,
May I propose (once again) a neutral form of indent for Oxygen
<root id="2"
<element position="1"> space are important here </element <element position="2"> space are also important here </element
</root>
The only thing you can allow or not is to convert newline and tabs to space as an option
Regards,
Xmlizer
On 7/20/07, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello,
There are no other workarounds yet. You have to specify the elements for which you want to preserve whitespace in one of the two ways. If you specify them in preferences you can store the Editor / Format /XML preferences at project level to avoid adding all the elements for all the projects in the same Preserve space elements table.
We have this request already logged in our issue tracking system for a future version of oXygen.
Regards, Sorin
Hi,
As I have read on previous posts, oXygen classifies mixed content
Jeff Sese wrote: based
on the current contents of an element, is this correct? If so, is it possible for oXygen to classify elements based on the declarations made in the DTD or Schema it is associated to?
I know that the work around for this is to specify the pattern of elements that you want to preserve the whitespace in the preferences or to manually insert an xml:space="preserve" attributes for these elements, but if an XML is associated with a DTD or a Schema then you can tell whether whitespace in that element is ignorable or not. Currently what I've been doing is for every project I have to specify in the pattern listing all the mixed content elements that are defined in the DTD/Schema so that when I do a pretty print the whitespace is preserved and this method is very troublesome.
Is there anymore workaround for this other than the ones I mentioned above? Or can this be considered as an added feature for a future version of the product?
Thanks, Jeff _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hello, I understand that your proposal is to normalize some text nodes (the text nodes with whitespace characters and non whitespace characters but not the text nodes with whitespace characters only) even if that leads to lines that exceed the maximum line length set in Preferences -> Editor -> Format. I consider breaking the lines that exceed the maximum length one of the main factors that make the pretty-printed document more readable. Without enforcing this maximum length the document will not be more readable after the pretty-print operation. If I misunderstand your proposal please give a complete example of what you mean. Regards, Sorin mozer wrote:
May I propose (once again) a neutral form of indent for Oxygen
<root id="2"
<element position="1"> space are important here </element <element position="2"> space are also important here </element </root>
The only thing you can allow or not is to convert newline and tabs to space as an option
Not exactly My proposal is, starting from an xml file to add space and carriage return *INSIDE* tags Doing this, the nature of space (ignorable or not) won't matter anymore since it won't have any impact Let me give a simple example <root><a><b></b><c></c></a></root> into <root
<a <b </b <c </c </a </root
May it would make the will less readable than a full indent, but in some case, it is just sufficient for debbugging and don't need further parametrization Regards, Xmlizer On Tue, Apr 8, 2008 at 1:38 PM, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello,
I understand that your proposal is to normalize some text nodes (the text nodes with whitespace characters and non whitespace characters but not the text nodes with whitespace characters only) even if that leads to lines that exceed the maximum line length set in Preferences -> Editor -> Format. I consider breaking the lines that exceed the maximum length one of the main factors that make the pretty-printed document more readable. Without enforcing this maximum length the document will not be more readable after the pretty-print operation.
If I misunderstand your proposal please give a complete example of what you mean.
Regards, Sorin
mozer wrote:
May I propose (once again) a neutral form of indent for Oxygen
<root id="2"
<element position="1"> space are important here </element <element position="2"> space are also important here </element
</root>
The only thing you can allow or not is to convert newline and tabs to space as an option
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hello, Do you mean debugging an XSLT transformation applied to an XML file formatted as in your example? I think an XSLT debugger is more useful for that and it does not depend on the text format of the XML file. For example when you click on a row in the Context view or in the XWatch view of the oXygen XSLT debugger the start tag of the corresponding XML element is highlighted in the XML editor panel. You need just to click in a view of the XSLT debugger to go directly to the corresponding XML element in the source editor. Regards, Sorin mozer wrote:
Let me give a simple example
<root><a><b></b><c></c></a></root>
into <root
<a <b </b <c </c </a </root
May it would make the will less readable than a full indent, but in some case, it is just sufficient for debbugging and don't need further parametrization
I'm sorry, if I'm not clear but I never spoke about XSLT For it is an option of indenting a file which could be called "neutral indenting", which would allow us to indent a one line xml file without introducing nasty spaces Regards, Xmlizer On Fri, Apr 11, 2008 at 2:01 PM, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello,
Do you mean debugging an XSLT transformation applied to an XML file formatted as in your example? I think an XSLT debugger is more useful for that and it does not depend on the text format of the XML file. For example when you click on a row in the Context view or in the XWatch view of the oXygen XSLT debugger the start tag of the corresponding XML element is highlighted in the XML editor panel. You need just to click in a view of the XSLT debugger to go directly to the corresponding XML element in the source editor.
Regards, Sorin
mozer wrote:
Let me give a simple example <root><a><b></b><c></c></a></root> into <root
<a <b </b <c </c </a </root
May it would make the will less readable than a full indent, but in some case, it is just sufficient for debbugging and don't need further parametrization
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
It seems that proposal has been lost Let me try to rephrase it The idea is to use the space "inside" the tag to indent an XML document Doing it that way, means that, you never change the space "between" the tag which may have nasty effect, or may be hard to parameter Hope this is clearer now Regards, Xmlizer On Fri, Apr 11, 2008 at 3:19 PM, mozer <xmlizer@gmail.com> wrote:
I'm sorry, if I'm not clear but I never spoke about XSLT
For it is an option of indenting a file which could be called "neutral indenting", which would allow us to indent a one line xml file without introducing nasty spaces
Regards,
Xmlizer
On Fri, Apr 11, 2008 at 2:01 PM, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello,
Do you mean debugging an XSLT transformation applied to an XML file formatted as in your example? I think an XSLT debugger is more useful for that and it does not depend on the text format of the XML file. For example when you click on a row in the Context view or in the XWatch view of the oXygen XSLT debugger the start tag of the corresponding XML element is highlighted in the XML editor panel. You need just to click in a view of the XSLT debugger to go directly to the corresponding XML element in the source editor.
Regards, Sorin
mozer wrote:
Let me give a simple example <root><a><b></b><c></c></a></root> into <root
<a <b </b <c </c </a </root
May it would make the will less readable than a full indent, but in some case, it is just sufficient for debbugging and don't need further parametrization
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hello Xmlizer, We will make an Oxygen selection plugin that inserts a newline before any '>' character that is located at the end of a tag so that the '>' will be the first character on the next line. A selection plugin is available on the contextual menu of the text editor and receives as parameter the current selection of the editor. We will post the plugin to the list. You find details about selection plugins in the User Manual: http://www.oxygenxml.com/doc/ug-oxygen/selection-plugins.html http://www.oxygenxml.com/doc/ug-oxygen/how-to-develop-oxygen-plugin.html Regards, Sorin mozer wrote:
It seems that proposal has been lost
Let me try to rephrase it
The idea is to use the space "inside" the tag to indent an XML document
Doing it that way, means that, you never change the space "between" the tag which may have nasty effect, or may be hard to parameter
Hope this is clearer now
Regards,
Xmlizer
On Fri, Apr 11, 2008 at 3:19 PM, mozer <xmlizer@gmail.com <mailto:xmlizer@gmail.com>> wrote:
I'm sorry, if I'm not clear but I never spoke about XSLT
For it is an option of indenting a file which could be called "neutral indenting", which would allow us to indent a one line xml file without introducing nasty spaces
Regards,
Xmlizer
On Fri, Apr 11, 2008 at 2:01 PM, Sorin Ristache <sorin@oxygenxml.com <mailto:sorin@oxygenxml.com>> wrote:
Hello,
Do you mean debugging an XSLT transformation applied to an XML file formatted as in your example? I think an XSLT debugger is more useful for that and it does not depend on the text format of the XML file. For example when you click on a row in the Context view or in the XWatch view of the oXygen XSLT debugger the start tag of the corresponding XML element is highlighted in the XML editor panel. You need just to click in a view of the XSLT debugger to go directly to the corresponding XML element in the source editor.
Regards, Sorin
mozer wrote:
Let me give a simple example <root><a><b></b><c></c></a></root> into <root ><a ><b ></b ><c ></c ></a ></root > May it would make the will less readable than a full indent, but in some case, it is just sufficient for debbugging and don't need further parametrization
Hello Xmlizer, Unzip the attached archive Oxygen-plugin.zip in the subfolder plugins of the Oxygen install folder and restart Oxygen. Edit the XML document in Text mode, select the elements that you want to format with "neutral indenting", right click and in the contextual menu select Plugins -> Format with text preserve. You can find the source code in Oxygen-plugin-source.zip if you want to change the format policy. The Oxygen plugins are explained in the User Manual: http://www.oxygenxml.com/doc/ug-oxygen/how-to-develop-oxygen-plugin.html Regards, Sorin Sorin Ristache wrote:
Hello Xmlizer,
We will make an Oxygen selection plugin that inserts a newline before any '>' character that is located at the end of a tag so that the '>' will be the first character on the next line. A selection plugin is available on the contextual menu of the text editor and receives as parameter the current selection of the editor. We will post the plugin to the list.
Hello Sorin, Indeed, that works fine ! Thanks ! It's exactly what I wanted ! Is there a way to include it more thightly in the application ? Indeed, it would be great to be able to format in such a way on opening the doc Regards, Xmlizer On Tue, Feb 17, 2009 at 3:14 PM, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello Xmlizer,
Unzip the attached archive Oxygen-plugin.zip in the subfolder plugins of the Oxygen install folder and restart Oxygen. Edit the XML document in Text mode, select the elements that you want to format with "neutral indenting", right click and in the contextual menu select Plugins -> Format with text preserve.
You can find the source code in Oxygen-plugin-source.zip if you want to change the format policy. The Oxygen plugins are explained in the User Manual:
http://www.oxygenxml.com/doc/ug-oxygen/how-to-develop-oxygen-plugin.html
Regards, Sorin
Sorin Ristache wrote:
Hello Xmlizer,
We will make an Oxygen selection plugin that inserts a newline before any '>' character that is located at the end of a tag so that the '>' will be the first character on the next line. A selection plugin is available on the contextual menu of the text editor and receives as parameter the current selection of the editor. We will post the plugin to the list.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Currently that is not possible. We will consider allowing the user to set a shortcut for a plugin from Options -> Menu Shortcut Keys. Regards, Sorin mozer wrote:
Is there a way to include it more thightly in the application ?
Indeed, it would be great to be able to format in such a way on opening the doc
Other important point : it doesn't work anymore with 10.1 Xmlizer On Tue, Feb 17, 2009 at 3:14 PM, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello Xmlizer,
Unzip the attached archive Oxygen-plugin.zip in the subfolder plugins of the Oxygen install folder and restart Oxygen. Edit the XML document in Text mode, select the elements that you want to format with "neutral indenting", right click and in the contextual menu select Plugins -> Format with text preserve.
You can find the source code in Oxygen-plugin-source.zip if you want to change the format policy. The Oxygen plugins are explained in the User Manual:
http://www.oxygenxml.com/doc/ug-oxygen/how-to-develop-oxygen-plugin.html
Regards, Sorin
Sorin Ristache wrote:
Hello Xmlizer,
We will make an Oxygen selection plugin that inserts a newline before any '>' character that is located at the end of a tag so that the '>' will be the first character on the next line. A selection plugin is available on the contextual menu of the text editor and receives as parameter the current selection of the editor. We will post the plugin to the list.
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Hello Xmlizer, Thank you for reporting the problem. There is a problem with plugins for the Text mode of the editor. Tomorrow we should have a fix implemented and we will let you know. Regards, Sorin mozer wrote:
Other important point : it doesn't work anymore with 10.1
Xmlizer
On Tue, Feb 17, 2009 at 3:14 PM, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello Xmlizer,
Unzip the attached archive Oxygen-plugin.zip in the subfolder plugins of the Oxygen install folder and restart Oxygen. Edit the XML document in Text mode, select the elements that you want to format with "neutral indenting", right click and in the contextual menu select Plugins -> Format with text preserve.
You can find the source code in Oxygen-plugin-source.zip if you want to change the format policy. The Oxygen plugins are explained in the User Manual:
http://www.oxygenxml.com/doc/ug-oxygen/how-to-develop-oxygen-plugin.html
Regards, Sorin
Hello Xmlizer, Try with the latest build of Oxygen (build numner 2009022712). Your Text mode plugins should be loaded correctly. Regards, Sorin Sorin Ristache wrote:
Hello Xmlizer,
Thank you for reporting the problem. There is a problem with plugins for the Text mode of the editor. Tomorrow we should have a fix implemented and we will let you know.
Regards, Sorin
mozer wrote:
Other important point : it doesn't work anymore with 10.1
Xmlizer
Thanks it works again On Mon, Mar 2, 2009 at 9:54 AM, Sorin Ristache <sorin@oxygenxml.com> wrote:
Hello Xmlizer,
Try with the latest build of Oxygen (build numner 2009022712). Your Text mode plugins should be loaded correctly.
Regards, Sorin
Sorin Ristache wrote:
Hello Xmlizer,
Thank you for reporting the problem. There is a problem with plugins for the Text mode of the editor. Tomorrow we should have a fix implemented and we will let you know.
Regards, Sorin
mozer wrote:
Other important point : it doesn't work anymore with 10.1
Xmlizer
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
participants (3)
-
Jeff Sese -
mozer -
Sorin Ristache