Most issues have been answered by others already, but just to add a few things..
On Jun 18, 4:05 pm, LittleWaver <[email protected]> wrote: > By building the RTF wave editor we’re actually raping the web … > ... > I know that point 2 isn’t wave specific, but it demonstrates the fact > that we’re forcing the web to be something else as it was designed to > be. You're right that the web itself is evolving -- we're working as part of the HTML5 standardization committees to improve, among other things, text editing on the web. For one concrete example, composition events have been added to the Dom Level 3 spec and we are working to unify all input events to provide a more reliable experience. Wave's underlying data model is quite different from HTML, but that is so that we can achieve the desired operational transform properties (See https://groups.google.com/group/wave-protocol/browse_thread/thread/2c88d0d4b4393273/c63b50a8b45aec72 ) > Advanced formatting - i wasn't able to find any place in the code > released to public, where things like bullet lists, or indentation > were implemented There are some pointers on how to get started with the code and where such features live in: https://groups.google.com/group/wave-protocol/browse_thread/thread/73608bf7a13f2385/5bc68b33febed568 Hopefully this can help you head in the right direction. Regards, Dan -- You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en.
