| Summary: | xml source tab only in multipage editor but not in vex editor | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | bjørn wikkeling <bjorn> |
| Component: | Mylyn | Assignee: | Project Inbox <wtp.inc.vex-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | David Williams <david_williams> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | eclipse, florian, icampista |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
bjørn wikkeling
This is exactly the difference between both editors. And there are plenty of use cases where you do not want to reveal the underlying XML to the user. -1 for this one from me Pacx (pacx.sf.net) is one example in which the Source tab is unwanted. But we like to provide two Vex editors: one without the Source tab for end-users without computer skills and one with the Source tab for XML experts like you. Maybe the naming of the Vex editors is misleading. I like to avoid acronyms and I propose to rename: "Vex XML Editor" into "Visual XML Editor" and "Vex XML Multipage Editor" into "Visual/Source XML Editor (Experimental)" Experimental because of http://dev.eclipse.org/mhonarc/lists/wtp-incubator-dev/msg01341.html). Bjørn, Florian, what do you think? (In reply to comment #2) > Pacx (pacx.sf.net) is one example in which the Source tab is unwanted. But we > like to provide two Vex editors: one without the Source tab for end-users > without computer skills and one with the Source tab for XML experts like you. > > Maybe the naming of the Vex editors is misleading. I like to avoid acronyms and > I propose to rename: > "Vex XML Editor" into "Visual XML Editor" > and > "Vex XML Multipage Editor" into "Visual/Source XML Editor (Experimental)" > Experimental because of > http://dev.eclipse.org/mhonarc/lists/wtp-incubator-dev/msg01341.html). > > Bjørn, Florian, what do you think? +1 (In reply to comment #3) Well I would really like that! But the Multi page editor only shows the XML right now. Visual editing doesn't seem to work. I also read http://dev.eclipse.org/mhonarc/lists/wtp-incubator-dev/msg01341.html so I figured it might be easier to have an extra tab for the visual editor. I'm totally for the separation into a Visual Editor and a more Advanced editor that also includes the source/xml Tab. so +1 it is. > (In reply to comment #2) > > Pacx (pacx.sf.net) is one example in which the Source tab is unwanted. But we > > like to provide two Vex editors: one without the Source tab for end-users > > without computer skills and one with the Source tab for XML experts like you. > > > > Maybe the naming of the Vex editors is misleading. I like to avoid acronyms and > > I propose to rename: > > "Vex XML Editor" into "Visual XML Editor" > > and > > "Vex XML Multipage Editor" into "Visual/Source XML Editor (Experimental)" > > Experimental because of > > http://dev.eclipse.org/mhonarc/lists/wtp-incubator-dev/msg01341.html). > > > > Bjørn, Florian, what do you think? > > +1 +1 We decided to temporarily deactivate the multi-page editor, since it is definitely not ready for use and we do not have the capacity at the moment to maintain it. There is a workaround if you need both the WYSIWYG mode and source mode in parallel: you can open your XML file with Vex and a source code editor of your choice in parallel. The contents will be synchronized when you save either of the editors. Moved to Mylyn Docs Vex. |