I had a read of some of the Echo3 developer docs this weekend. In particular, the docs on how to create a custom component were very interesting. If you’ve read the custom component docs for Echo2, you know how messy that was. This time around it looks a little cleaner. There are basically three different object hierarchies:
- The client-side JavaScript components, extended from
EchoApp.Component. - Their corresponding client-side JavaScript synchronization peers, extended from
EchoRender.ComponentSync, which deal with manipulating the DOM hierarchy. - The corresponding server-side Java synchronization peers, extended from the convenience
nextapp.echo.webcontainer.AbstractComponentSync, which handles synchronization between the client-side and server-side component. - The server-side Java component.
The docs aren’t quite done yet, but already it looks as if component writers can leverage the framework much more than in Echo2. It’s good to see that event handler hygiene is encouraged in the docs.
Powered by ScribeFire.
I’m very pleasant surprised to hear about a new version of Echo. I’ve used Echo2 in past and it was a pleasure to work with. I’m very curios what new features will the Echo3 will bring.