Re: [mylyn-dev] Vex Editor for Mylyn Docs project

[Kilian Matt <kilian.matt@xxxxxxxxx>]

Hi Holger,

you can use the toll free number (866) with with Skype, that works for me.

Kilian

On Wed, Oct 13, 2010 at 3:29 PM, Holger Voormann <eclipse@xxxxxxxxxxx> wrote:
> I like the idea to move Vex to Mylyn: it makes more sense to group
> subprojects/features according to user requirements instead of technical
> implementation.
>
> The time (20:00 CERT) is fine for me but I would prefer communication via
> something free of charge, e.g. Skype or a German telephone number.
>
> Best regards, Holger
>
> Am 13.10.2010 11:17, schrieb Florian Thienel:
>>
>> Unfortunately I have another appointment tomorrow. So I will write some
>> facts about Vex and some of my thoughts in advance. I hope this helps to
>> see if Vex fits better into the
>>
>> Vex is a WYSIWYG (actually "...what you mean") editor for XML documents,
>> i.e. huge amounts of structured text written in a XML language (eg.
>> Docbook). One of the main reasons to use XML is, that it allows to tag
>> the content's semantic instead of simply defining a layout. This fact is
>> vital for single source publishing.
>>
>> The typical Vex user
>> * writes structured texts in a XML language (eg. Docbook, DITA, TEI P5)
>> * uses the XML toolchain (XSLT + XSL-FO, etc.) to publish the texts in
>> serveral formats (eg. different HTML layouts, HTML-Help, PDF, etc.)
>> * has little knowledge about XML and all the other underlying technologies
>> * sees Vex simply as one of his tools and has little time and energy to
>> fiddle around with Vex
>>
>> Typical fields of application:
>> * technical writing
>> * scientific writing
>> * computational linguistics
>>
>> This is a whole new group of users. I think it is good to have one
>> "documentation" project which concentrates all effort to address this
>> group of users.
>>
>> Holger, me and possibly Igor will be at the ESE in three weeks. Maybe we
>> can make an appointment to meet in person. At least for me this is
>> easier than the 2,7kHz of a telephone line around the half of the globe
>> ;-)
>>
>> Best Regards,
>>
>> Florian
>>
>> Am 13.10.2010 04:19, schrieb David Carver:
>>>
>>> If I can't make it then I hope that Florian, Hogler, or Igor could
>>> make it. Long term I think it is a better fit than wtp, but that is my
>>> opinion.
>>>
>>> Dave
>>>
>>> On 10/12/2010 03:27 PM, David Green wrote:
>>>>
>>>> David,
>>>>
>>>> Your proposal sounds great. Vex is a great fit for Mylyn Docs, and
>>>> visa versa. Would you be able to join a Mylyn conference call to
>>>> discuss the particulars? If so please feel free to add an item to the
>>>> agenda and call in: http://wiki.eclipse.org/Mylyn/Meetings
>>>>
>>>> David
>>>>
>>>> --
>>>> David Green
>>>> VP of Engineering, Tasktop
>>>> Committer, Eclipse Mylyn
>>>> http://tasktop.com
>>>>
>>>> On Fri, Oct 8, 2010 at 9:25 AM, David Carver <d_a_carver@xxxxxxxxx
>>>> <mailto:d_a_carver@xxxxxxxxx>> wrote:
>>>>
>>>> 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 resulting files produced are
>>>> strictly XML, and can be checked into a source code control
>>>> 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 the 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 houses the XML projects, Vex itself is
>>>> more about enabling the collaboration and generation of
>>>> documentation, and the people that are typically interested in Vex
>>>> are those working on documentation or articles for publication
>>>> (i.e. news articles, books, etc).
>>>>
>>>> Here are some relevant links:
>>>>
>>>> http://wiki.eclipse.org/WTP/VisualEditorForXML
>>>>
>>>> The CI Build and FindBugs reports can be found on hudson:
>>>>
>>>> https://hudson.eclipse.org/hudson/view/WTP/job/cbi-wtp-inc.vex/
>>>>
>>>> There is a P2 update site that can be used to install the latest
>>>> versions as well, archived from the vex CI build.
>>>>
>>>> Dave
>>>>
>>>> _______________________________________________
>>>> mylyn-dev mailing list
>>>> mylyn-dev@xxxxxxxxxxx <mailto:mylyn-dev@xxxxxxxxxxx>
>>>> https://dev.eclipse.org/mailman/listinfo/mylyn-dev
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> mylyn-dev mailing list
>>>> mylyn-dev@xxxxxxxxxxx <mailto:mylyn-dev@xxxxxxxxxxx>
>>>> https://dev.eclipse.org/mailman/listinfo/mylyn-dev
>>>
> _______________________________________________
> mylyn-dev mailing list
> mylyn-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-dev
>