Community
Participate
Working Groups
Created attachment 166596 [details] current visual category When using the new wizard, its a bit hard to find visually the VEX. Could we move he VEX wizard extensions to a more attractive category other than "other"? Perhaps something like 'Documentation Tools'
Yes, but I would prefer to put the Vex "New" wizards into the existing "XML" category. Documentation is only one use case of Vex. What do you think?
In a sense, you are right, its XML. What I feel is that we can make the VEX more visible. I don't want to invent a category, but thinking in the VEX vision (which happens to also be what I envision for a e2e DITA tooling), it covers wide concepts such as authoring, publishing, DITA advanced concepts, and perhaps things that go beyong like documentation automation or continous integration (I will talk about this in the mailing list). If more wizards for other new features are created, the XML category won't fit any longer to accurately group them. I also think that having more specialized wizards can help users. For example a subcategory for DITA and wizards for the common things without the need to configure too many combos. Instead, offering innnovative choices to speed up the authoring experience. Here are some slides presented at EclipseCon 2010, they are made by Max Anderson which is the project lead for JBoss Tools and Developer Studio. (I use JBoss Tools quite a lot) http://www.slideshare.net/maxandersen/how-to-make-a-framework-plugin-that-does-not-suck Is the XML category still right place?
(In reply to comment #2) I know what you mean: a person who writes documentation in DITA should not need to know that DITA is an XML format. Because there are very different use cases for Vex my idea was to split Vex into a framework part and a Visual XML Development Environment (see bug 293517). The framework part should not contribute to the UI but may contain (abstract) wizard implementations. On top of the framework the DITA plug-in would then add its domain specific category and wizard(s). A technical writer would install the DITA plug-in which requires the Vex framework only but not the Visual XML Development Environment.
Another proposal: A new category "XML Authoring" where we provide the existing generic wizard for creating XML documents. This will get part of the Visual XML Development Environment later on, on behalf of bug 293517. Plug-ins that provide document types can contribute special wizards to this new category (e.g. "New TEI P5 Document"). I have the TEI P5 mind, a highly customizeable document type. A special wizard for TEI could provide an implementation of the TEI pizza chef (http://www.tei-c.org/pizza.html) to create a customized document type. I also think, an own category is needed, because the current XML category is mainly used for "XML development" (creation of DTDs, Schemas, Stylesheets etc.), which is most likely not our target user group.
"XML Authoring" sounds attractive. A subcategory in it for dita sounds also very good. I will provide a patch, when there is an agreement. ;)
(In reply to comment #5) > "XML Authoring" sounds attractive. A subcategory in it for dita sounds also > very good. > > I will provide a patch, when there is an agreement. ;) +1 Looking forward to the patch. :-)
Created attachment 167204 [details] update visual category image
Created attachment 167206 [details] Patch that corrects the category of the wizards Corrected the existing IDs, that were wrong and too long. Updated the description. Assigned the category to the 2 existing wizards.
Patch applied. Thank you for the contribution, Igor.
fixed
Moved to Mylyn Docs Vex.
