If your team is experienced in Java/J2EE and your server architecture will be J2EE based two other factors weigh in favour of GWT:
1) debugging the entire application from your Java IDE 2) GWT RPC which is easy to use and very fast compared to JSON or SOAP These are killer GWT features if you are using a J2EE back end. The three questions I would consider in evaluating Flex as a better option would be: 1) Are the additional features available to Flex applications (as mentioned above, by virtue of it being a native plug-in) central to the application? 2) Does the application have to look and feel exactly like a native desk top application? 3) Is the application an internal business application run entirely within the enterprise intranet (or controlled Internet access to it)? With a J2EE back end and an experienced Java team, unless you are getting a resounding "yes" to at least two of these questions I would think the case for GWT is pretty strong. I think one major issue with browser based business applications is access to the local file system, but I also think there is a increasing trend (although in its infancy) for corporate documents and data to be stored centrally and homogeneously so that KM, indexing and search engines can work on it behind the scenes. If your organization shares that view, then GWT's lack of access to the local file system can be seen as a strategic advantage in hastening change in custom and practice. Google Gears provides the mechanisms to enable such applications to work off line when required. regards gregor On Aug 23, 10:58 am, dflorey <[EMAIL PROTECTED]> wrote: > GWT is the better choice when you want to > - create mashups (include html snippets from other sources) > - adopt the style of an existing site that is html based (might be the > case when running in a portal) > - develop in java > - have full access to the sources to be able to fix stuff yourself > - be indexed properly for internet search > - create new widgets > > When using gwt on the other hand you'll have to deal with a lot of > browser specific layout quirks as they simply cannot be solved by gwt > alone. Flash is using its own rendering and will look exactly the same > on all supported browsers/platforms. > I personally don't like the Flex development approach, but this is > just a matter of taste. > > On 23 Aug., 11:14, taurinus <[EMAIL PROTECTED]> wrote: > > > CRITERIA 01: Flash Player Plug-in > > Thank you for your clear overview of the main problems concerning the > > pros and cons of a plug-in. > > You are absolutely right, that this is a major choice to take from the > > beginning. > > ? How important is it to have the capabilities of a Flash-Player and > > what would be the major shortcoming of GWT when developing a > > Enterprise RIA that has to be OpenSource and has to be as easy to use > > as possible (Working with large sets of data, Usability, User > > Experience, Accessibility, Collaboration) ? > > > CRITERIA 02: Developer Skills > > Most of the developers are experienced JavaEE developers (UI- > > Technology Knowledge is poor). > > ? Goal is to have a browser based Application, that still remains > > flexible (Integration into a Portal)? > > > On 22 Aug., 23:05, Thomas Broyer <[EMAIL PROTECTED]> wrote: > > > > On Aug 22, 7:56 pm, taurinus <[EMAIL PROTECTED]> wrote: > > > > > We are evaluating what UI technology to use for a Enterprise Rich > > > > Internet Application. It turns out to be difficult to find the right > > > > criteria and trusted sources that can help us finding the right > > > > decision. Can you tell what criteria would be most important and the > > > > dis-/advantage of Adobe Flex 3 (with/-out Blaze DS) vs. Google > > > > Webtoolkit? > > > > First, their might already be answers in this (or GWT-Contrib) > > > archives. > > > > My answer (disclaimer: I don't know Blaze DS): > > > 1. choice of technology depends on your developers skills > > > (ActionScript vs. JavaScript, desktop-like UI building vs. web/HTML) > > > 2. being a plug-in, Flash/Flex gives you more power: playing sounds > > > and videos (can be done with flash objects with GWT, see GWT- > > > Incubator), dealing with ByteArrays, non-HTTP sockets, access to > > > webcam and/or microphone, or even filesystem (with v9 of the player), > > > etc. > > > 3. being a plug-in, Flash/Flex gives you cross-browser support > > > "without compromise" (no CSS hacks, etc.) > > > 4. but, being a plug-in, it first has to be installed (with a minimum > > > required version) on the client > > > 5. and, being a plug-in, cross-browser is at the detriment of cross- > > > platform > > > > For an *enterprise* app, 3, 4 and 5 depend on the company's internal > > > rules, might weight more or less in the balance depending on the > > > company... So basically it all depends on: > > > 1. who you (your team) are, > > > 2. what you need/want to do, > > > 3. 4. 5. where you want to deploy it.- Zitierten Text ausblenden - > > > - Zitierten Text anzeigen - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
