Re: Using GWT for a large UI project

I completely agree with marius on the plugin requirement for
silverlight. Also, until M$ decides to make a full version of
Silverlight available on Linux it will never become popular. Since
the majority of the people that use Linux are software devs, it would
make sense that you would want to support it to gain acceptance with
devs. Those who argue that Moonlight is an acceptable alternative and
M$ is giving Novell full support I challenge you to try to use the
most popular feature of Silverlight; DRM streaming, which M$ refuses
to license for x86 because they are afraid their architecture isn't
good enough to withstand a barrage of Linux devs. Also, I don't see
what silverlight and business customers have to do with each other
other than the corporate insistence of paying for M$ products. Also,
it has been well documented that with GWT you can architect your
software in such a way that you can output an optimized display for
mobile clients.

On Sep 2, 12:24 am, Maxim <maxim...@gmail.com> wrote:
> Marius
>
> you wrote: but one of our goals is to use plain browser functionality,
>
> available on all devices.
>
> Recently I changed my mind a little bit in connection to that - this
> goal is more technical than commercial. Users want certain
> functionality, if functionality demands plugin - they will install
> plugin. E.g. ref Flash technology. Silverlight gives huge amount to
> business customers ( at least to their certain category).
>
> Next - this goal is not mentioned in your document :) Also note - if
> you try complex GWT application on your phone you will be likely
> disappointed, so "available on all devices" still is not 100% reality.
>
> But of course if you must traget *nix users, then Silverlight is not
> your choice. Just mention that in goals :)
>
> Maxim
>
> On Sep 1, 8:57 pm, "marius.andreiana" <marius.andrei...@gmail.com>
> wrote:
>
> > Thanks Maxim (saw your email),
>
> >http://demos.telerik.com/silverlight/salesdashboard/says"Missing
> > plugin". So I left ;)
> > I'm sure silverlight can have great results for controlled end user
> > environments, but one of our goals is to use plain browser
> > functionality, available on all devices.
>
> > On Sep 1, 4:40 pm, Maxim <maxim...@gmail.com> wrote:
>
> > > Marius,
>
> > > in your document you compare GWT wih ASP.NET AJAX but I think it
> > > should be rather compared with Silverlight, this is a "client-side"
> > > technology like GWT which is not linked to server. ASP.NET AJAX is
> > > something very different and demands IIS to be installed server-side.
>
> > > My story about this comparison. We are having good customer we were
> > > trying to develop forusingGWT. Actually skeleton was developedusing
> > > GWT but then he wanted more modern appearance, and he could pay money
> > > for commercial libs. We figured out that commercial libraries for
> > > Silverlight are light years ahead of what GWT 3rd party libraries can
> > > offer. Price for such libraries are relatively low ( say in comparison
> > > to developer monthly salary), so cost is not a big problem I think.
>
> > > e.g.http://demos.telerik.com/silverlight/salesdashboard/
>
> > > Still we love GWT and use it heavily for sayhttp://www.projectkaiser.com:8080/
>
> > > One more thing: from time to time we have browser-compatibilty-related
> > > issues ( not so big though )  with GWT, especially in Firefox.
>
> > > Maxim

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