[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [wtp-incubator-dev] Why can't we adapt Web Page editor for VEX purpose
|
NS Gopikrishnan,
the difference IMHO is to create an editor that supports not only one
grammar (like HTML or Docbook or ...) but ALL possbile grammars. Issue
https://bugs.eclipse.org/bugs/show_bug.cgi?id=298912 shows this very
good. Displaying an image is no rocket science. But to create a generic
mechanism that shows the images, independent of the grammar you are
using is (nearly at least). And there are much more complicated concepts
out there in the world of XML (like XInclude for example).
That's the challange and that's what makes it interessting to me.
~Florian
Am 11.08.2010 15:45, schrieb NS Gopikrishnan:
Hi all,
I always had this question in mind:
Why can't we just adapt the web page editor that's belonging to WTP for
the purpose of a Visual editor for XML ?
HTML is also in a way an XML.
What is possibly making the adaption a challenge if at all ? When I used
the Web Page editor, It seemed just perfect and so evolved for me. So I
thought why VEX is not this fluent in handling a structured document ?
Even in WWW I have seen a lot of HTML editors. But XML WYSIWYG editors
are that hard to find that it's so ironical !!!
I would like the people already on VEX team to share their valuable
opinions and views on this.
I am not forgetting all the great efforts that WTP put in for VEX. :)
Especially Florian and Holger who are keen in it's development and for
always being a source of help.
--
Thanks & Regards,
NS Gopikrishnan
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev