Many of these issues are WHY we just got done ripping out all EXT-GWT code out of a large financial app.
1) License issues 2) GWT compatibility ( Widget intermixing, events, exceptions ) 3) Look&Feel didn't ( and couldn't be made to ) conform to corporate branding 4) generated javascript size 5) reduce external dependencies 6) rendering speed, especially tables. Financial apps are mostly "Table Driven", so I wrote my own friggin Table Widget, an optimized it for our use cases. I can now say the app totally SCREAMS. I have done a few GWT apps for banks, etc, and I can truly say this is one of the fastest I have ever seen. ALL the fancy widget packages were orders of magnitude slower on rendering our data. My table does sorting, paging, selection, and export to Excel is built in. Cells can have custom properties ( alignment, class ) and even override the renderer so a cell can contain a widget. I wrote it, so I understand every line, we own the source, and can extend it... filtering is next on my list. Screens that used to take 7-8 seconds to render now take < 1 second, and I still have a few tricks up my sleeve.... for instance, ( tho this is not working in IE ), this can render a 300x20 grid, with styling and alignment, in 10ms: http://deansjones.appspot.com/ and it is a proper sub-class of Grid. Try that on any of these toolkits ;-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
