Re: how did we miss Echo?

I took a quick look at their demo apps and their widgets and wasn't 
particularly impressed.

Their stuff is still doing round trips and refreshing the whole browser.

 From what I could tell, none of their apps have the same level of rich 
frontend that we're achieving internally by leveraging the nw code. We 
keep doing Cool Stuff(tm) on the interactivity front and I just don't 
see it in their solution. I'd be way happier if they spent their time 
helping implement CSS2 into their favorite browser of choice and 
leveraging a JS lib like nw/domAPI/they_can_pick_whatever and have at it.

I just want to get our current product finished so we can actually 
_show_ ppl what we're up to with nw/dhtml.

--Michael

Alex Russell wrote:

> Hey all,
> 
> Am I smoking crack and living under a rock? How exactly did I miss what Echo 
> was all about? There's a story on /. linking to this article set:
> 
> 	http://www-106.ibm.com/developerworks/java/library/j-echo1/
> 	http://www-106.ibm.com/developerworks/library/j-echo2/
> 
> Basically, it's a set of Java classes that generate the DHTML side of things 
> "transparently". This is the kind of tying I've been trying to avoid, but 
> they seem to have done it somewhat successfully. Now if only I could find 
> somewhere to just look at their JS and not get all the Java crap they want to 
> shove too.
> 



_______________________________________________
The netWindows developers list: [email protected]
http://netwindows.org/mailman/listinfo/devel_netwindows.org