Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Webtools incubator » VEX Testing Advice Needed
VEX Testing Advice Needed [message #435085] Tue, 25 November 2008 02:46 Go to next message
Reed Elliott is currently offline Reed Elliott
Messages: 8
Registered: July 2009
Junior Member
I spent part of the weekend playing around with the 0.5.0 version of VEX and
studying DITA and DocBook. I was able to get tables, ordered list,
unordered list, codeblocks, titles and paragraphs to display in VEX using
DITA documents but found myself mainly using the standard XML Editor to
create the document tag structure because I was having trouble navigating
VEX. For example, I could insert an unordered list <ul> tag between 2
parapraphs using VEX but couldn't figure out how to enter the list item <li>
tags. If I entered the <li> tags using the XML Editor and saved the
document, VEX would display the list properly.

As I experiment VEX, should I log the bugs/issues that I find or is it too
early to start logging a bunch of GUI/usability issues?
Re: VEX Testing Advice Needed [message #435086 is a reply to message #435085] Tue, 25 November 2008 15:18 Go to previous messageGo to next message
Eclipse User
Originally posted by: dcarver.starstandard.org

Reed Elliott wrote:
> I spent part of the weekend playing around with the 0.5.0 version of VEX and
> studying DITA and DocBook. I was able to get tables, ordered list,
> unordered list, codeblocks, titles and paragraphs to display in VEX using
> DITA documents but found myself mainly using the standard XML Editor to
> create the document tag structure because I was having trouble navigating
> VEX. For example, I could insert an unordered list <ul> tag between 2
> parapraphs using VEX but couldn't figure out how to enter the list item <li>
> tags. If I entered the <li> tags using the XML Editor and saved the
> document, VEX would display the list properly.

As you mover the cursor through the document, in the lower left corner
it will display which is the current XML tag. So for list item in
DocBook which is what I'm more familiar with, add a listeitem after an
itemizedlist tag.

section\itemizedlist\listitem.

You can use the Document->Element->Insert element dialog to add the
necessary tag.

There are many improvements from a useability side that need to occur
with VEX, the main one I'm working on getting ready is a MultiPage
editor so that you have both a Design and Source tab available to edit
with. Other things that are needed are drag and drop of tags ans
templates into the editor.

Mappings of common wordprocessor items would probably be nice, so that
you can click a button and have it insert the appropriate tags at the
appropriate point. All of these would need to be enhancements done to
the code.


> As I experiment VEX, should I log the bugs/issues that I find or is it too
> early to start logging a bunch of GUI/usability issues?

Never too early to log bugs.


Dave
Re: VEX Testing Advice Needed [message #435087 is a reply to message #435086] Wed, 26 November 2008 01:45 Go to previous messageGo to next message
Reed Elliott is currently offline Reed Elliott
Messages: 8
Registered: July 2009
Junior Member
Dave,

I hadn't noticed the currently selected tag label or the Document menu.
These will definitely help me find my way around the document. I will
continue to test and, when I get a little more confident, will start logging
bugs.

Can't wait to see the multiple page editor! In XMLSpy, I regularly flip
between Authentic and Text views and am glad to hear that this will be an
option in VEX.

Let me know if there is anything specific that you would like me to test. I
am studying plug-in development but may be a little while before I am ready
to contribute any functionality.

Reed

"David Carver" <dcarver@starstandard.org> wrote in message
news:492C174F.3000501@starstandard.org...
> Reed Elliott wrote:
>> I spent part of the weekend playing around with the 0.5.0 version of VEX
>> and studying DITA and DocBook. I was able to get tables, ordered list,
>> unordered list, codeblocks, titles and paragraphs to display in VEX using
>> DITA documents but found myself mainly using the standard XML Editor to
>> create the document tag structure because I was having trouble navigating
>> VEX. For example, I could insert an unordered list <ul> tag between 2
>> parapraphs using VEX but couldn't figure out how to enter the list item
>> <li> tags. If I entered the <li> tags using the XML Editor and saved the
>> document, VEX would display the list properly.
>
> As you mover the cursor through the document, in the lower left corner it
> will display which is the current XML tag. So for list item in DocBook
> which is what I'm more familiar with, add a listeitem after an
> itemizedlist tag.
>
> section\itemizedlist\listitem.
>
> You can use the Document->Element->Insert element dialog to add the
> necessary tag.
>
> There are many improvements from a useability side that need to occur with
> VEX, the main one I'm working on getting ready is a MultiPage editor so
> that you have both a Design and Source tab available to edit with. Other
> things that are needed are drag and drop of tags ans templates into the
> editor.
>
> Mappings of common wordprocessor items would probably be nice, so that you
> can click a button and have it insert the appropriate tags at the
> appropriate point. All of these would need to be enhancements done to the
> code.
>
>
>> As I experiment VEX, should I log the bugs/issues that I find or is it
>> too early to start logging a bunch of GUI/usability issues?
>
> Never too early to log bugs.
>
>
> Dave
Re: VEX Testing Advice Needed [message #493522 is a reply to message #435085] Mon, 26 October 2009 15:36 Go to previous messageGo to next message
Alexej Spas is currently offline Alexej Spas
Messages: 22
Registered: July 2009
Junior Member
Please take a look on DITAworks solution: www.ditaworks.com

It provides a comprehensive publishing support for Eclipse Help based on DITA. It also addresses problems of advanced Eclipse Help support that are not solved in DITA Open Toolkit like:


    Support of Eclipse help contexts
    Integartion of cheat sheets
    Cross-plugin links resolving
    Integration with development IDE
    and much more...


Please take a look on following blog posts:
DITA Eclipse Editor: Using DITA for publishing documentation in Eclipse Help format.
Eclipse RCP Documentation Development with DITAworks

Regards,
Alexej Spas



Re: VEX Testing Advice Needed [message #494037 is a reply to message #493522] Wed, 28 October 2009 21:01 Go to previous messageGo to next message
Holger Voormann is currently offline Holger Voormann
Messages: 16
Registered: July 2009
Junior Member
Hi Alexej,

I appreciate that your company is supporting Eclipse by being a Solution Member but this is not the right place to advertise a commercial, closed-source tool.

DITAworks is based on Oxygen. If you like, you could pay me to implement the features which prevent you replacing Oxygen with Vex. Or you do it yourself - contributions are welcome! This would be a win-win situation: you will save money especially in the long run and Vex will make more progress. That's just the way open source works. Wink

Holger
Re: VEX Testing Advice Needed [message #563044 is a reply to message #435085] Tue, 25 November 2008 15:18 Go to previous messageGo to next message
Eclipse User
Originally posted by: dcarver.starstandard.org

Reed Elliott wrote:
> I spent part of the weekend playing around with the 0.5.0 version of VEX and
> studying DITA and DocBook. I was able to get tables, ordered list,
> unordered list, codeblocks, titles and paragraphs to display in VEX using
> DITA documents but found myself mainly using the standard XML Editor to
> create the document tag structure because I was having trouble navigating
> VEX. For example, I could insert an unordered list <ul> tag between 2
> parapraphs using VEX but couldn't figure out how to enter the list item <li>
> tags. If I entered the <li> tags using the XML Editor and saved the
> document, VEX would display the list properly.

As you mover the cursor through the document, in the lower left corner
it will display which is the current XML tag. So for list item in
DocBook which is what I'm more familiar with, add a listeitem after an
itemizedlist tag.

section\itemizedlist\listitem.

You can use the Document->Element->Insert element dialog to add the
necessary tag.

There are many improvements from a useability side that need to occur
with VEX, the main one I'm working on getting ready is a MultiPage
editor so that you have both a Design and Source tab available to edit
with. Other things that are needed are drag and drop of tags ans
templates into the editor.

Mappings of common wordprocessor items would probably be nice, so that
you can click a button and have it insert the appropriate tags at the
appropriate point. All of these would need to be enhancements done to
the code.


> As I experiment VEX, should I log the bugs/issues that I find or is it too
> early to start logging a bunch of GUI/usability issues?

Never too early to log bugs.


Dave
Re: VEX Testing Advice Needed [message #563068 is a reply to message #435086] Wed, 26 November 2008 01:45 Go to previous messageGo to next message
Reed Elliott is currently offline Reed Elliott
Messages: 8
Registered: July 2009
Junior Member
Dave,

I hadn't noticed the currently selected tag label or the Document menu.
These will definitely help me find my way around the document. I will
continue to test and, when I get a little more confident, will start logging
bugs.

Can't wait to see the multiple page editor! In XMLSpy, I regularly flip
between Authentic and Text views and am glad to hear that this will be an
option in VEX.

Let me know if there is anything specific that you would like me to test. I
am studying plug-in development but may be a little while before I am ready
to contribute any functionality.

Reed

"David Carver" <dcarver@starstandard.org> wrote in message
news:492C174F.3000501@starstandard.org...
> Reed Elliott wrote:
>> I spent part of the weekend playing around with the 0.5.0 version of VEX
>> and studying DITA and DocBook. I was able to get tables, ordered list,
>> unordered list, codeblocks, titles and paragraphs to display in VEX using
>> DITA documents but found myself mainly using the standard XML Editor to
>> create the document tag structure because I was having trouble navigating
>> VEX. For example, I could insert an unordered list <ul> tag between 2
>> parapraphs using VEX but couldn't figure out how to enter the list item
>> <li> tags. If I entered the <li> tags using the XML Editor and saved the
>> document, VEX would display the list properly.
>
> As you mover the cursor through the document, in the lower left corner it
> will display which is the current XML tag. So for list item in DocBook
> which is what I'm more familiar with, add a listeitem after an
> itemizedlist tag.
>
> section\itemizedlist\listitem.
>
> You can use the Document->Element->Insert element dialog to add the
> necessary tag.
>
> There are many improvements from a useability side that need to occur with
> VEX, the main one I'm working on getting ready is a MultiPage editor so
> that you have both a Design and Source tab available to edit with. Other
> things that are needed are drag and drop of tags ans templates into the
> editor.
>
> Mappings of common wordprocessor items would probably be nice, so that you
> can click a button and have it insert the appropriate tags at the
> appropriate point. All of these would need to be enhancements done to the
> code.
>
>
>> As I experiment VEX, should I log the bugs/issues that I find or is it
>> too early to start logging a bunch of GUI/usability issues?
>
> Never too early to log bugs.
>
>
> Dave
Re: VEX Testing Advice Needed [message #570540 is a reply to message #435085] Mon, 26 October 2009 15:36 Go to previous messageGo to next message
Alexej Spas is currently offline Alexej Spas
Messages: 22
Registered: July 2009
Junior Member
Please take a look on DITAworks solution: http://www.ditaworks.com/

It provides a comprehensive publishing support for Eclipse Help based on DITA. It also addresses problems of advanced Eclipse Help support that are not solved in DITA Open Toolkit like:


Support of Eclipse help contexts
Integartion of cheat sheets
Cross-plugin links resolving
Integration with development IDE
and much more...


Please take a look on following blog posts:
http://blog.ditaworks.com/features/using-dita-for-publishing -documentation-in-eclipse-help-format-functionality-preview/
http://blog.ditaworks.com/features/eclipse-help-support-with -ditaworks/

Regards,
Alexej Spas
Re: VEX Testing Advice Needed [message #570581 is a reply to message #570540] Wed, 28 October 2009 21:01 Go to previous message
Holger Voormann is currently offline Holger Voormann
Messages: 16
Registered: July 2009
Junior Member
Hi Alexej,

I appreciate that your company is supporting Eclipse by being a Solution Member but this is not the right place to advertise a commercial, closed-source tool.

DITAworks is based on Oxygen. If you like, you could pay me to implement the features which prevent you replacing Oxygen with Vex. Or you do it yourself - contributions are welcome! This would be a win-win situation: you will save money especially in the long run and Vex will make more progress. That's just the way open source works. ;)

Holger
Previous Topic:[jaxws] error creating web service from pojo
Next Topic:ConsoleView in RAP
Goto Forum:
  


Current Time: Wed Oct 22 03:20:46 GMT 2014

Powered by FUDForum. Page generated in 0.03780 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software