Hi Anton, The elements prefixed with l: are rendering implementation detail, similar to a browser's shadow DOM. They are not part of the real model communicated to the server.
It is possible to change the model to be any XML you like, if you don't like the existing one. You just have to write the new rendering and event handling behaviors. Also, the editor itself is not too tightly coupled to XML at all, so it should be quite feasible to change the model to something else entirely. Some additional high level info: http://www.waveprotocol.org/protocol/design-proposals/editor http://www.waveprotocol.org/code/tutorials/writing-a-doodad Στις 23 Ιουνίου 2011 5:45 μ.μ., ο χρήστης Anton Starcev <[email protected]> έγραψε: > P.S. > XML also be approached, but without namespaces > > On Thu, Jun 23, 2011 at 11:42, Anton Starcev <[email protected]> wrote: >> On Thu, Jun 23, 2011 at 11:12, David Hearnden <[email protected]> wrote: >>> When you say "users", do you mean developers? Or actual end users? >> >> I mean front end developers of the site. They make html layout and, in >> some cases, they might want to look in source. >> >>> Can you give some more detail on the scenario you're describing? I might be >>> able to provide a better answer if I understood it a bit more. >> >> Main scenario is html layout and editorial changes in content management >> system. >> >>> On Thu, Jun 23, 2011 at 4:52 PM, Anton Starcev >>> <[email protected]>wrote: >>> >>>> Hi all, >>>> >>>> Keep doing standalone editor based on wave editor. >>>> Have a problem with source code of editor's text, sample output is: >>>> >>>> <doc> >>>> <body> >>>> <line/> >>>> <l:p> >>>> <text>text</text> >>>> </l:p> >>>> <line/> >>>> <l:p> >>>> <text>bo</text> >>>> <l:s fontWeight='bold'> >>>> <text>l</text> >>>> </l:s> >>>> <l:s fontWeight='bold' fontStyle='italic'> >>>> <text>d</text> >>>> </l:s> >>>> </l:p> >>>> <line t='h3'/> >>>> <l:p t='h3'> >>>> <text>headlin</text><text>e</text> >>>> </l:p> >>>> <line/> >>>> <l:p> >>>> <l:s fontFamily='tahoma,sans-serif'> >>>> <text>text</text> >>>> </l:s> >>>> </l:p> >>>> </body> >>>> </doc> >>>> >>>> Tags like "l:p", "l:s" etc are too difficult for potential users (they >>>> expect something like plain html). >>>> Is in this some hidden logic, or I can just replace names in Pretty<N> >>>> and parse class? >>>> >>>> >>>> Anton Startsev >>>> ______________________________________________________________________ >>>> [email protected] | www.artlebedev.com >>>> >>> >> >> >> Anton Startsev >> ______________________________________________________________________ >> [email protected] | www.artlebedev.com >> > > Anton Startsev > ______________________________________________________________________ > [email protected] | www.artlebedev.com >
