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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
