Difference between revisions of "Vex/NewAndNoteworthy"

From Eclipsepedia

< Vex
Jump to: navigation, search
(1.0.0 M8 (2011-12-31))
(1.1.0 M3 (2013-10-02))
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
= New and Noteworthy =
 
= New and Noteworthy =
== 1.0.0 M8 (still under development) ==
+
 
* Vex now uses the new namespace <code>org.eclipse.vex</code>. Unfortunately this will break all existing Vex plug-in projects which reference <code>org.eclipse.wst.xml.vex</code>. Those can be fixed with a simple search and replace of the namespace in the <code>vex-plugin.xml</code> file.
+
== 1.1.0 M3 (2013-10-02) ==
 +
* For users of Juno there is separate version of Vex, but be aware that 1.1.0 will be the last version of Vex which supports Juno.
 +
* Starting this milestone we switched to [http://hudson.eclipse.org/vex our own HIPP instance] of Hudson. If you use the latest-gratest-update-site, please update your link.
 +
* The icons in the document outline were polished.
 +
 
 +
[[Image:VexOutlineNewIcons.png]]
 +
 
 +
* Support for processing instructions was added. ([http://bugs.eclipse.org/251955 bug 251955])
 +
* The styling of processing instructions and comments can be controled using CSS and special element names:
 +
**<tt>vex|processing-instruction</tt> for processing instructions
 +
**<tt>vex|comment</tt> for comments
 +
* Find the full list of fixed bugs for this milestone [https://bugs.eclipse.org/bugs/buglist.cgi?list_id=4209680&classification=Mylyn&query_based_on=Vex%20Current%20Release&query_format=advanced&product=Mylyn%20Docs%20Vex&target_milestone=1.1.0%20M3 here].
 +
 
 +
== 1.1.0 M2 (2013-09-03) ==
 +
 
 +
* Vex is now based on Eclipse Kepler.
 +
* The document outline got a major facelift: it shows icons for the differend kind of nodes, inline elements and the textual content can be included in the outline.
 +
 
 +
[[Image:VexOutlineFull.png]] [[Image:VexOutlineNoInline.png]] [[Image:VexOutlineNoInlineNoText.png]]
 +
 
 +
* Plenty of bugs were fixed, especially regarding the support of Docbook (see [https://bugs.eclipse.org/bugs/buglist.cgi?list_id=4209680&classification=Mylyn&query_based_on=Vex%20Current%20Release&query_format=advanced&product=Mylyn%20Docs%20Vex&target_milestone=1.1.0%20M2 the full list])
 +
* Please note that this version of Vex requires <u>JAVA 6</u> and <u>Eclipse 4.3 - Kepler</u> to be successfully installed.
 +
 
 +
== 1.1.0 M1 (2013-01-29) ==
 +
* Vex now has full support for XML comments at every possible position they can have in a document. ([http://bugs.eclipse.org/257806 bug 257806])
 +
[[Image:Bug257806_outer_comments.png]]
 +
* A major cleanup of the DOM has been done. This was the main step to get a public API for the DOM. The new structure of the DOM is described in detail in our new [[Vex/ArchitectureGuide|Architecture Guide]].
 +
* The [[Vex/UserGuide|user manual]] got a little face lift and a [http://vimeo.com/58346326# first video tutorial] has been created.
 +
* Some minor bugs were fixed (see [https://bugs.eclipse.org/bugs/buglist.cgi?list_id=4209680&classification=Mylyn&query_based_on=Vex%20Current%20Release&query_format=advanced&product=Mylyn%20Docs%20Vex&target_milestone=1.1.0%20M1 the full list])
 +
 
 +
== 1.0.0 M9 (2012-05-29) ==
 +
* Vex supports editing of XML comments within the root element (full support for comments still to be done). [http://bugs.eclipse.org/257806 bug 257806]
 +
[[Image:Bug257806_inner_comments.png]]
 +
* The indentation and line breaking rules can be configured in the preferences dialog. [http://bugs.eclipse.org/367925 bug 367925]
 +
[[Image:Bug367925_preferences.png]]
 +
* Some small bugs were fixed.
 +
 
 +
== 1.0.0 M8 (2012-01-04) ==
 +
* Vex now uses the new namespace <code>org.eclipse.vex</code>. Unfortunately this will break all existing Vex plug-in projects which reference <code>org.eclipse.wst.xml.vex</code>. Those can be fixed with a simple search and replace of the namespace in the <code>vex-plugin.xml</code> file. You also have to fix the namespace of the Vex project nature in the .project file.
 
* XML Schema is now supported to define the structure of documents. [http://bugs.eclipse.org/250838 bug 250838]
 
* XML Schema is now supported to define the structure of documents. [http://bugs.eclipse.org/250838 bug 250838]
* The namespace declarations can be edited for each element in a document.
+
* The namespace declarations can be edited for each element in a document. Go to ''Document > Edit Namespaces...''
 
[[Image:Bug253753_vex_edit_namespaces.png]]
 
[[Image:Bug253753_vex_edit_namespaces.png]]
 
* A new plug-in (<code>org.eclipse.vex.projectplan</code>) provides a configuration for the [[Development_Resources/Project_Plan|Eclipse project plan]] schema, which is our reference for document types that use multiple schemas. [http://bugs.eclipse.org/366469 bug 366469]
 
* A new plug-in (<code>org.eclipse.vex.projectplan</code>) provides a configuration for the [[Development_Resources/Project_Plan|Eclipse project plan]] schema, which is our reference for document types that use multiple schemas. [http://bugs.eclipse.org/366469 bug 366469]
 
[[Image:Bug366469_vex_projectplan.png]]
 
[[Image:Bug366469_vex_projectplan.png]]
* The sort order in the "insert element" popup was tweaked: the elements which start with the given search term now appear before the elements which only contain the search term. [http://bugs.eclipse.org/362475 bug 362475]
+
* The sort order in the ''insert element'' popup was tweaked: the elements which start with the given search term now appear before the elements which only contain the search term. [http://bugs.eclipse.org/362475 bug 362475]
 
[[Image:Bug362475_vex_sort_insert_element_popup.png]]
 
[[Image:Bug362475_vex_sort_insert_element_popup.png]]
  

Latest revision as of 11:45, 2 October 2013

Contents

[edit] New and Noteworthy

[edit] 1.1.0 M3 (2013-10-02)

  • For users of Juno there is separate version of Vex, but be aware that 1.1.0 will be the last version of Vex which supports Juno.
  • Starting this milestone we switched to our own HIPP instance of Hudson. If you use the latest-gratest-update-site, please update your link.
  • The icons in the document outline were polished.

VexOutlineNewIcons.png

  • Support for processing instructions was added. (bug 251955)
  • The styling of processing instructions and comments can be controled using CSS and special element names:
    • vex|processing-instruction for processing instructions
    • vex|comment for comments
  • Find the full list of fixed bugs for this milestone here.

[edit] 1.1.0 M2 (2013-09-03)

  • Vex is now based on Eclipse Kepler.
  • The document outline got a major facelift: it shows icons for the differend kind of nodes, inline elements and the textual content can be included in the outline.

VexOutlineFull.png VexOutlineNoInline.png VexOutlineNoInlineNoText.png

  • Plenty of bugs were fixed, especially regarding the support of Docbook (see the full list)
  • Please note that this version of Vex requires JAVA 6 and Eclipse 4.3 - Kepler to be successfully installed.

[edit] 1.1.0 M1 (2013-01-29)

  • Vex now has full support for XML comments at every possible position they can have in a document. (bug 257806)

Bug257806 outer comments.png

  • A major cleanup of the DOM has been done. This was the main step to get a public API for the DOM. The new structure of the DOM is described in detail in our new Architecture Guide.
  • The user manual got a little face lift and a first video tutorial has been created.
  • Some minor bugs were fixed (see the full list)

[edit] 1.0.0 M9 (2012-05-29)

  • Vex supports editing of XML comments within the root element (full support for comments still to be done). bug 257806

Bug257806 inner comments.png

  • The indentation and line breaking rules can be configured in the preferences dialog. bug 367925

Bug367925 preferences.png

  • Some small bugs were fixed.

[edit] 1.0.0 M8 (2012-01-04)

  • Vex now uses the new namespace org.eclipse.vex. Unfortunately this will break all existing Vex plug-in projects which reference org.eclipse.wst.xml.vex. Those can be fixed with a simple search and replace of the namespace in the vex-plugin.xml file. You also have to fix the namespace of the Vex project nature in the .project file.
  • XML Schema is now supported to define the structure of documents. bug 250838
  • The namespace declarations can be edited for each element in a document. Go to Document > Edit Namespaces...

Bug253753 vex edit namespaces.png

  • A new plug-in (org.eclipse.vex.projectplan) provides a configuration for the Eclipse project plan schema, which is our reference for document types that use multiple schemas. bug 366469

Bug366469 vex projectplan.png

  • The sort order in the insert element popup was tweaked: the elements which start with the given search term now appear before the elements which only contain the search term. bug 362475

Bug362475 vex sort insert element popup.png

[edit] 1.0.0 M7 (2011-05-03)

[edit] 1.0.0 M6 (2011-03-15)

  • The multi-page editor was deactivated since it is definitely not ready for use and we do not have the capacity at the moment to maintain it.
  • The EMF content model was replaced with a hand-crafted content model.

[edit] 1.0.0 M4 (2010-12-13)

  • Documentation of the supported CSS subset in the user manual
  • Evaluate the CSS properties width and height to scale images bug 329639
  • Use the WTP XML catalog to resolve document types bug 331462
  • Support for XHTML 1.0 Strict bug 331615

Bug331615 vex xhtml support.jpg

[edit] 1.0.0 M3 (2010-11-08)

Bug298912 vex image support.jpg

  • Configuration is not serialized anymore bug 324927

[edit] 0.5.0

and a lot other small changes