- Posted by: Tod Liebeck
- Posted on: March 13 2008 10:19 EDT
- Congratulations! by Ashley Aitken on March 13 2008 21:03 EDT
- Re: Open-source Ajax Framework Echo3 Goes Beta by Maik Jablonski on March 14 2008 04:06 EDT
- Congrats and Thanks for your efforts by Sunil Guttula on March 14 2008 06:15 EDT
- tables? by Ed O Neill on March 14 2008 08:19 EDT
- What about performance? by Nemanja Kostic on March 14 2008 10:49 EDT
- Dual web AND desktop application? by Roshan Shrestha on March 17 2008 09:49 EDT
- Nice! by Eelco Hillenius on March 18 2008 17:10 EDT
- Re: Open-source Ajax Framework Echo3 Goes Beta by Pawel Glowacki on March 20 2008 06:21 EDT
- Client side performance with 100% Java server side control by Chris Golfman on June 17 2008 22:28 EDT
Thanks all for the compliments, really great to hear all that.
Any plans on Echo for mobile browsers?It currently runs on Mobile Safari (iPhone), though I'd recommend not using any pane components in that environment, as the iPhone does not support scrolling DIVs as far as I can tell. Apps can run entirely offline on a iPhone, as bookmarklets using RFC 2397 ("data") URLs: http://echo.nextapp.com/site/node/4945 I'll be taking a look soon at some Windows Mobile stuff, hope to get some support in for Opera/IE Mobile as well (have not tested with these yet though).
Nice API and easy to understand framework's architecture.
We started using it on one project and have hit a performance wall. There were so many events being sent over to server that the overall application was terribly slow. We've tried different optimizations, but didn't gave expected results.
Any changes in Echo3 regarding performance?
Echo3 is very impressive work, because of its wonderful and clean framework design. The best I've ever seen... I'm a long term Echo-user (running Echo-applications since version 1) and I was a little bit sceptical about the huge effort of redesigning Echo2 to Echo3 at first. But I must really admit that it definitively was worth this big effort. I'm going to migrate all my applications to Echo3 in the next days, because it is so much easier to develop / debug client-side code with Echo3 than with Echo2. Thanks for this wonderful piece of technology. Maik
Tod, Echo is an awesome product and thanks for all your efforts. I have used it since it's first version and found it to be a top quality product. I have introduced it at my previous workplace and found it to be a good fit for enterprise apps. Any plans on Echo for mobile browsers? Thanks Sunil
I'm not familiar with echo2/3 at all, but the demo is really impressive. Is there a control like a datatable, sortable and pageable? I didn't see it in the demo app or did I just miss it? Ed
Echo provides a basic Table-Component (server-side-java-only at the moment), which works like a Swing-Table. So it's quite easy to feed your Pageable/Sortable-TableModel into the Table-component. A basic knowledge with developing Swing-applications helps a lot to get into Echo.
Echo provides a basic Table-Component (server-side-java-only at the moment), which works like a Swing-Table. So it's quite easy to feed your Pageable/Sortable-TableModel into the Table-component. A basic knowledge with developing Swing-applications helps a lot to get into Echo.I believe there was a component that provided this functionality. Either it was in the [externally maintained] extras project or in the Sierra product. But like Majik said, it is pretty easy.
Echo provides a basic Table-Component (server-side-java-only at the moment), which works like a Swing-Table.ok, good to hear that. Just wondered, because web framework demos usually contain all their components as an example. Ed
Tod probably just wanted to get it out there. A quote from the demo - "This application was developed using the open-source Echo3 framework, and a few open-source Echo3 components." (bold is mine)
Echo provides a basic Table-Component (server-side-java-only at the moment), which works like a Swing-Table.
ok, good to hear that.
Just wondered, because web framework demos usually contain all their components as an example.
I was pretty impressed first time I saw Echo2. Nice API and easy to understand framework's architecture. We started using it on one project and have hit a performance wall. There were so many events being sent over to server that the overall application was terribly slow. We've tried different optimizations, but didn't gave expected results. Any changes in Echo3 regarding performance?
Echo is modeled after Swing, but diverges where it makes sense, because of the restricted "web-application-runtime-environment" (a browser talking to a server via http). So you cannot code an single application which works as desktop- and server-application out of the box with Echo.
For dual Swing/web client you can use AjaxSwing
That looks very nice; cool demo and some really nice ideas as part of the new API. Congrats and good luck with the framework!
Hi Tod, The demo web app looks VERY NICE! Are there any examples of client-side only Echo3 web app communicating with web server using AJAX? What is the preferred approach for interacting with an RDBMS from client-side only Echo3 app?
What is the preferred approach for interacting with an RDBMS from client-side only Echo3 app?That approach sounds like a lot of work and a potential security threat - direct access to your RDBMS from within JS code running on a browser? The benefits of the new Echo3 is that you can take advantage of many of it's client side performance benefits while still benefitting from it's 100% java server side control API. It means that you can still use a transparent persistence solution with your Echo app. We use JPOX/JDO for very large enterprise level Echo2 based apps we have developed and it's a perfect fit. Being Echo2 it's all server side Java so we have no problem using the latest gear from JPOX (JDO) and Hibernate would work just as well. We're about to move to Echo3 which maintains backwards compatibility at the API level with Echo2 (except for some simple package name changes). We envisage faster performance - especially as the RichTextArea component runs completely in the browser until the form is closed unless you want to set up special events (which we don't). So in that sense we're taking advantage of the client side performance boost while maintaining all interaction via a 100% Java server side API - so we can still develop with a zero effort persistence archicture. With desktop like web app development plus 100% transparent persistence and we're in Java developer's nirvana here. Our total framework set is: Echo2 - soon to be Echo3 JPOX - a JDO 2.1 compliant, transparent persistence, object relational mapper (ORM) solution MySQL - JPOX handles all our RDBMS interactions for us exPOJO - open source, extremely lightweight dependency injection, no XML config, exposed POJO domain model framework + provides a level of ORM independence (port between JDO<->Hibernate easily) Javelin used for UML modeling of the domain model and automatic generation of the ORM meta data.