Hopefully we can end this discussion soon, but it may be worth noting that GWT 
was first concieved in an era where javascript libraries hadn't yet evolved to 
what they are today (especially with regard to jquery) and backend developers, 
especially Java ones, were extremely gun-shy at delving into the world of 
client-side scripting languages. 

A few months back, a similar discussion came up on this list about Pyamas and 
someone posted a link to John Resig's thoughts on javascript code generation. I 
can't find it off-hand , but his perspective definately resonated with me.

Does anyone have that link?
 
On Feb 2, 2009, at 6:01 PM, "Mark T." <mark.t...@gmail.com> wrote:


You do seem pretty intent on using GWT, no matter what advice is
offered in this thread.  It sounds as if you were looking more for
confirmation of a decision already made.

However, if you are still open to alternatives, I would suggest that
you give a strong look at Yahoo's UI library (http://
developer.yahoo.com/yui/), which includes a lot of rich components,
not just JavaScript language shortcuts or smaller building blocks
(which it also includes).  I have personally used YUI a lot and I feel
that it is a mature, well designed library.

Here's an example of a "real software application," not just a picture
slideshow:

http://developer.yahoo.com/yui/examples/layout/adv_layout_source.html

You will need to code your server-side logic separately, but if
anything goes wrong, performance is bad, or you need to extend the
functionality, you will be dealing with code that you have written,
not a mess of auto-generated, opaque gibberish.


On Jan 31, 9:19 pm, Tycon <adie...@gmail.com> wrote:
I'm not talking about facebook/youtube type sites, I'm talking about a
real web application
where users access information,  enter information, search and analyze
information, and visualize information.
I'm not creating web sites for popularity contests, but using the web
as a platform for real
software applications that provide an actual (business) service. For
that it's much better to use
more client side (e.g. javascript) code to make it seem like a real
desktop app.
If you just want to create some flicker slideshow derivative, then yes
you can use php or whatever other
server side "application" code.

On Jan 31, 8:25 pm, Michael Bayer <mike...@zzzcomputing.com> wrote:

On Jan 31, 2009, at 4:28 PM, Tycon wrote:

I'm planning on using GWT only for client side code and doing all
server calls
using JSON, and not using GWT's RPC mechanism. So I guess that would
avoid the problem you are talking about ?

or you could just use jquery...ive no idea how you'd use only the  
"client side" portion of GWT.  from what I could tell it seemed like  
the entire server-to-client is spit out from a single monolithic  
compilation and there was certainly no easy way to just use "the  
client".

Correct me if I'm wrong, but neither Perl/CGI not Pylons/Rails etc
CANNOT
be used to create a gmail-like application, unless you resort to hand
writing
the entire UI (which runs wholly on the client) in javascript (good
luck with
that !).

i think there are alternatives which would result in easier to read  
code.   jquery can go a very long way.

were written using GWT-like technology, and IMO google apps are the
best example
of smart efficient next generation web apps.

theyre tremendously complex and reliant upon special build tools.    
facebook AFAIK is just php and is a more compelling client side  
experience than anything I've seen google do.





      

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to pylons-discuss@googlegroups.com
To unsubscribe from this group, send email to 
pylons-discuss+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to