Hi, You can find a demo here : http://surface-sample.elasticbeanstalk.com/ Indeed, I'm reinventing the wheel. I did not known the Wave editor, I will take a look at it, but I'm not sure that handling something else than HTML is the right thing to do in my use case. There is some existing wysiwyg editors that uses the same idea of creating inserters instead of using execCommand (Aloha, as an example). But there is always something missing to me :
- I need a GWT based wysiwyg (Wave editor, XWiki editor are candidates) - I need to create specific inserters - I need to control strictly the HTML output (because the HTML is exported with XSLT processors in my use case) - I need to process the HTML "in-place", by DOM manipulation - and some other things... Firstly, I did not want to reinvent the wheel, but every existing wysiwyg solution always lead me to embarrassing limitations in my use cases. But I repeat, I've not tried Wave editor, and I will do it quickly ; I wish it could be a solution for me. Thank you for your feedback. Le 7 mars 2012 12:53, Thomas Broyer <[email protected]> a écrit : > > On Wednesday, March 7, 2012 11:45:45 AM UTC+1, Damien Picard wrote: >> >> I'm pleased to announce the creation of a new Open Source project called >> stillcollab-surface : >> http://code.google.com/p/**stillcollab-surface/<http://code.google.com/p/stillcollab-surface/> >> >> Surface is a wysiwyg editing surface that doesn't rely on browser's >> execCommand and queryCommandState commands. >> >> Because of using these commands leads to output differences, this is not >> a good behavior for products that need to compute produced HTML elsewhere >> than in a browser. >> >> Furthermore, table, list, paragraph, etc. manipulation can differ from a >> browser to another one, so this wysiwyg try to handle these differences to >> provide the same look and feel for every browser. >> > > Looks great but: > > - is there a live demo somewhere? > - it looks like you're kind-of reinventing the wheel, as Apache Wave > already has that kind of editor. Wave's one is based on an XML-like > document whose schema is not (X)HTML; the added flexible obviously > translates into a more complex design but it works quite well (I've used it > in a project where we had to constrain the input –e.g. no image in a > title–, and handle "semantic links", among other things; and FWIW, the Wave > editor powers the new Blogger comment form), and has already been heavily > tested on many browsers (at Google, before being donated to Apache; though > given its use in Blogger, it's highly probably that it's still heavily > tested at Google, and I guess they'd contribute back to Apache if/when they > fix things) > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/mZlUn62KEwgJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- Damien Picard Axeiya Services : http://axeiya.com/ stillcollab-surface : http://code.google.com/p/stillcollab-surface/ Mon livre sur GWT : http://axeiya.com/index.php/ouvrage-gwt.html -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
