Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Vex/NewAndNoteworthy"
< Vex
(→1.0.0 M3 (2010-11-08)) |
|||
(12 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
= New and Noteworthy = | = New and Noteworthy = | ||
+ | == 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] | ||
+ | * The namespace declarations can be edited for each element in a document. Go to ''Document > Edit Namespaces...'' | ||
+ | [[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] | ||
+ | [[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] | ||
+ | [[Image:Bug362475_vex_sort_insert_element_popup.png]] | ||
+ | |||
+ | == 1.0.0 M7 (2011-05-03) == | ||
+ | * The internally used DOM now supports namespaces according to [http://www.w3.org/TR/xml-names/ XML Namespaces 1.0]. [http://bugs.eclipse.org/253753 bug 253753] | ||
+ | |||
+ | == 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. | ||
+ | |||
+ | == 1.0.0 M4 (2010-12-13) == | ||
+ | * Documentation of the supported CSS subset in the [[Vex/UserGuide|user manual]] | ||
+ | * Evaluate the CSS properties ''width'' and ''height'' to scale images [http://bugs.eclipse.org/329636 bug 329639] | ||
+ | * Use the WTP XML catalog to resolve document types [http://bugs.eclipse.org/331462 bug 331462] | ||
+ | * Support for XHTML 1.0 Strict [http://bugs.eclipse.org/331615 bug 331615] | ||
+ | [[Image:Bug331615_vex_xhtml_support.jpg]] | ||
== 1.0.0 M3 (2010-11-08) == | == 1.0.0 M3 (2010-11-08) == |
Revision as of 15:04, 29 May 2012
Contents
New and Noteworthy
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
- The indentation and line breaking rules can be configured in the preferences dialog. bug 367925
- Some small bugs were fixed.
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 referenceorg.eclipse.wst.xml.vex
. Those can be fixed with a simple search and replace of the namespace in thevex-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...
- 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
- 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
1.0.0 M7 (2011-05-03)
- The internally used DOM now supports namespaces according to XML Namespaces 1.0. bug 253753
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.
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
1.0.0 M3 (2010-11-08)
- Basic image support bug 298912
- Configuration is not serialized anymore bug 324927
0.5.0
- Find/Replace bug 293239
- Menu Structure bug 252628
- Content Assist bug 297675
and a lot other small changes