Thomas, I think GWT to SWF compilation is still in its infancy, so I wouldn't base my application on it just yet. It has a lot of potential but I'd stick with what works today.
On Aug 25, 3:58 am, Thomas Broyer <[EMAIL PROTECTED]> wrote: > First, thanks a lot for those details! > > But... > ...how about compiling Java code into SWF through GWT? > (seehttp://www.slideshare.net/cromwellian/gwt-extremefrom slide 44) > > On 25 août, 09:11, Kris Hofmans <[EMAIL PROTECTED]> wrote: > > > Hello, > > > I would like to offer some insights into this, I have had some GWT > > experience and currently I am working on a large Flex project (flex 3 > > + granite ds (like blaze ds but with some additional nifty features)). > > > First I would like to contradict a couple of people in this thread, > > the flash player does NOT provide a similar experience between all > > browsers/operating systems, layout issues arise in for example safari. > > And don't even get me started on the difference on date handling > > between windows and other platforms (linux, mac, ...) which adobe will > > fix with an "enhancement" in flash player 11. They call it an > > enhancement because they documented the difference for flash but not > > for flex .... > > > Then the tooling. Flex builder is a substandard IDE, it offers NO > > usefull refactoring support. We have a flex client of around +-65000 > > loc, the ONLY option you have for refactoring is rename and if we use > > update references it takes up to 25 minutes on a c2d 2,4ghz laptop > > with 2gb ram. No organize imports, no code templates, ... it's more > > like a text editor with some highlighting support. There is a visual > > editor which works fine most of the time, the problem is we never > > really use it because writing mxml/as ourselfs is faster and offers > > more control. F3/ctrl-click support is broken most of the time when > > using more than 1 linked flex project. > > > Gwt is java, so the java tooling works fantastic. You can also just > > once write your model/dto and don't have to build the same objects in > > actionscript that you than have to keep in sync. > > > Now I won't get into a battle about what is best: Actionscript or > > Javascript, they are both ecmascript variants. The mxml declarative > > notation is a nice to have but also not a deal breaker. > > > Another miss on the flex side is the lack of good load/ui testing > > tools mostly because of the AMF protocol, there are some commercially > > available load testing tools. It's still all very new and you can > > definitly experience that when you get deeper into the flex > > "underground". > > > Don't get me wrong, you can do lots of nice things, because of the > > vector based nature you can get nice looking apps, animations run > > smooth and overal the UI is a lot more consistent than what browsers > > have to offer. > > > One of my last annoyances is some of the behaviour of the actionscript > > VM, it bundles server calls into one single request block that gets > > sent as soon as the code stops executing, this request block gets > > handled by a single thread on the server, thus makes it harder to > > scale in paralell per client. > > > Still I wouldn't write off flex completely, neither one is perfect. If > > you would like a lot of eyecandy in you app I would probably suggest > > flex, if you need multimedia support, I know gwt can do it, but I > > would probably also go with flex because when you start mix&matching > > you need to manage different codebases, when you have this nifty util > > in gwt you have to rewrite it in actionscript if you would like to use > > it in one of your multimedia components ... stick to as few languages > > as possible. > > > Good luck with making a well thought out choice! > > > Sincerely, > > Kris Hofmans > > > 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? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
