GWT and other technologies

[ptr128]

Hi,
I'm learning GWT and therefore planning to write complex application
(webmail interface or calendar or bug tracking system, etc). Do you
have any ideas, how could I involve into my project python, ruby or
other technologies, to learn them too occasionally?

--
Regards
Sebastian

[Tim T]

you could write back-end (server-side code) in whatever technology
you'd like (say Django for Python, or Rails for Ruby) and use JSON/
REST for rpc with the client written in GWT (instead of GWT rpc which
is currently specific to Java). This would work for the learning that
I you are looking for.

However, I would question this approach for a large scale rich client
system, since you'll realize soon enough that GWT RPC offers quite a
bit of productivity gains than other rpc approaches don't and leads to
a more cohesive implementation.

[Tom Davies]

On Apr 28, 2:03 am, Tim T <ttara...@gmail.com> wrote:
> However, I would question this approach for a large scale rich client
> system, since you'll realize soon enough that GWT RPC offers quite a
> bit of productivity gains than other rpc approaches don't and leads to
> a more cohesive implementation.

To enlarge on this point, one of the most important benefits of GWT is
compile-time type checking of the interfaces you call in your client
code with their implementations on the server.

This means that when you change your RPC interface the compiler (and
your IDE) will tell you at once which parts of your client code are
affected.

GWT 1.5, which supports Java 5 generic types allows even better typing
of your interfaces, as your callbacks can be parameterised with the
correct type.

[Peter Blazejewicz]

hi Sebastian,

http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/28bdd67ca0a404b3/5749562782c530de?lnk=gst&q=ruby#5749562782c530de
(also I cannot find that post where someone announced rails plugin for
GWT rpc serialization sadly using search feature)
yeah, Ruby/Python (Rails/Django) that's so much fun compared to java,
if you write your client communication based on JSON you are free from
any server-implementation.
With GWT RPC you're strictly tied to server in java of some kind (that
is becoming BIG stop point for GWT toolkit I think, at least there is
no migration due to server-neutral serialization functionality, only
becuase of client-code generation),
regards,
Peter

[Chii]

there are some custom gwt server rpc implementations out there - check
out grails gwt plugin, and check out the php gwt rpc library.

On Apr 28, 9:36 am, Peter Blazejewicz <peter.blazejew...@gmail.com>
wrote:
> hi Sebastian,
>
> http://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa...

[TheB...@gmail.com]

gwt is mostly just the frontend. the backend could be in anything