Re: [wtp-incubator-dev] Re: Why can't we adapt Web Page editor for VEX p

[David Carver <d_a_carver@xxxxxxxxx>]

 A lot of this predates the existing XML Validation of WTP.   One of 
the goals in the current Vex project is to integrate better with the 
existing WTP way of doing things.

Prior to being brought over to eclipse, Vex didn't even use the WTP 
Content Model, but generated it's own content model.  We currently map 
to this old way but provide access to the WTP content model.  Ultimately 
we would just access the WTP Content Model directly.

Changes and patches are appreciated and welcomed to address any of these 
issues.

Dave

On 08/11/2010 11:37 AM, NS Gopikrishnan wrote:
> I get the complexity involved when it has to be generic to multiple
> grammars. That's worth the effort. But we have to keep it simple when
> we have a higher aim. Take for example the validation in VEX - Why
> can't we simply validate the xml against a DTD ? May I know the reason
> why a graph datastructure is used instead ? Was it for providing more
> meaningful validation error messages ?
>
> On 8/11/10, David Carver<d_a_carver@xxxxxxxxx>  wrote:
> >    Take a look at the Vex editor, CSS styles are assigned to XML tags
> > (i.e. when it encounters that tag, it renders appropriately).
> >
> > As an example, a para tag from DocBook, can be rendered as a box using
> > the specified CSS information.
> >
> > Dave
> >
> > On 08/11/2010 08:25 AM, Cameron Bateman wrote:
> > > The renderer in the web page editor is tied to HTML/CSS right now, but it
> > > is feasible that we could try to abstract that out.  What I'm not clear on
> > > is how to render an arbitrary XML schema graphically.  HTML and CSS styles
> > > have implicit meanings when it comes to rendering. i.e. a div renders as a
> > > box and has pre-defined styling attributes.  What is the equivalent in
> > > generic XML?
> > >
> > >
> > > Thanks,
> > >
> > > Cameron
> > >
> > > ----- Original Message -----
> > > From: florian@xxxxxxxxxxx
> > > To: wtp-incubator-dev@xxxxxxxxxxx
> > > Sent: Wednesday, August 11, 2010 7:35:30 AM GMT -08:00 US/Canada Pacific
> > > Subject: 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
> > > _______________________________________________
> > > wtp-incubator-dev mailing list
> > > wtp-incubator-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
> > > _______________________________________________
> > > wtp-incubator-dev mailing list
> > > wtp-incubator-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
> > _______________________________________________
> > wtp-incubator-dev mailing list
> > wtp-incubator-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev