From: David Carver [mailto:d_a_carver@xxxxxxxxx]
Sent: October-13-10 7:08 AM
To: Mylyn developer discussions
Cc: Mik Kersten; Florian Thienel; Igor Jacy
Lino Campista; Holger Voormann
Subject: Re: [mylyn-dev] Vex Editor for Mylyn
I'll be on Thursday's call.
As for some screen shots see:
As well, I've attached a screen shot showing Vex with a
DocBook document in the Vex Document perspective.
On 10/12/2010 08:55 PM, Mik Kersten wrote:
Could we add this to this Thursday's meeting agenda and have some of the
Vex folks join?
Also, could someone post links to some recent Vex screenshots?
Dr. Mik Kersten
Tasktop CEO, Mylyn Lead, http://twitter.com/mik_kersten
From: mylyn-dev-bounces@xxxxxxxxxxx [mailto:mylyn-dev-
bounces@xxxxxxxxxxx] On Behalf Of David Carver
Sent: October-08-10 9:25 AM
Cc: Igor Jacy Lino Campista; Florian Thienel; Holger Voormann
Subject: [mylyn-dev] Vex Editor for Mylyn Docs project
I've talked briefly about this with a couple of Vex committers. And
Mik suggested I bring this up on the mylyn-dev mailing list as well.
I've copied the existing Vex committers on this message as well. The
Vex project is a Visual Editor for XML documents. In particularl
document oriented XML files like DocBook, XHTML, DITA, etc. It can be
used to allow a WYSIWYG editing experience with out having to know the
underlying tags. DocBook is one of it's main uses, and it also support
DITA out of the box as well. It uses CSS stylesheets to help control
the rendering. It fits in the same category as Mylyn WikiText editor,
as it allows for a Single Sourcing method to documentation. The
files produced are strictly XML, and can be checked into a source code
system, allowing multiple people to collaborate on the files.
Vex has been a WTP Incubator project for several years, and slowly has
grown a dedicated committer base. The project is shooting for a Spring
graduation, but with the advent of the new Mylyn top level project, and
overal scope of Vex, I would suggest that the Documentation sub
project might actually be a better place for the Vex project itself.
It seems to fit more into the scope there, as we Web Tools while it
the XML projects, Vex itself is more about enabling the collaboration
generation of documentation, and the people that are typically
Vex are those working on documentation or articles for publication (i.e.
articles, books, etc).
Here are some relevant links:
The CI Build and FindBugs reports can be found on hudson:
There is a P2 update site that can be used to install the latest
versions as well,
archived from the vex CI build.
mylyn-dev mailing list
mylyn-dev mailing list