What about the gxt 3 licence? I mean we are talking about GWT performace or
a gxt3 vs gwt ?
El 9 de abril de 2012 09:40, dhoffer escribió:
> Thanks for the updated comparison. I wanted to point out that the
> summary line is not always correct. Examples:
>
> GXT Render Time: 1ms
> GWT Render T
Thanks for the updated comparison. I wanted to point out that the
summary line is not always correct. Examples:
GXT Render Time: 1ms
GWT Render Time: 0ms
GXT was 1x faster...
and
GXT Render Time: 1ms
GWT Render Time: 1ms
GXT was 1x faster...
-Dave
On Apr 4, 5:40 am, Fabrice wrote:
> I do t
I do this quickly : http://gxt3vsgwt.appspot.com/
thanks to code source of previous demo, by replacing GXT 2.2.5 with
Ext GWT 3.0 Release Candidate (http://dev.sencha.com/deploy/gxt-3.0.0-
rc.zip).
Performance are better !
On 27 mar, 16:12, dhoffer wrote:
> Regarding GXT I noticed that comparis
Oops, I meant don't use G*X*T. We've used pure GWT on another project with
all bespoke widgets and despite a bleeding edge HTML5/SVG UI with tons of
animations, data, and windows, the pure G*W*T examples runs circles around
the other, simpler, G*X*T project. Sorry for the confusion, if there was
That should be *"don't use GXT"* I pressume...
Op woensdag 28 maart 2012 00:51:45 UTC+2 schreef Joseph Lust het volgende:
>
> My company just completed a very large intranet UI using GXT. The overall
> lesson learned was *don't use GWT*. For the most part it was much slower
> and the model used
Finally, I've made my application faster.
The idea is not using GridRenderer and prepared the model in the server.
For example I write in the server than
create an Image object in the client. Like I said, the target application
is IE8 (not very performance), and by doing this I managed to redu
On Wed, Mar 28, 2012 at 12:51 AM, Joseph Lust wrote:
> My company just completed a very large intranet UI using GXT. The overall
> lesson learned was don't use GWT. For the most part it was much slower and
> the model used in GXT did not extend well to our MVP setup. Perhaps GXT 3
> has fixed some
Seems this whole thread has more to do with GXT than GWT. We have built a
large app, part of which runs on the ipad as a fullscreen web app and
performance isn't a problem at all. We built most of our widgets ourself to
be very efficient and we make use of HTMLPanels and raw html where it makes
Hi,
>A grid with 23 columns that contains at least 10 GridRenderer
GXT 3.0:
All data widgets support cells (instead of renderers)
Cells support events and can fire events
High performance via flyweight pattern
> the model used in GXT did not extend well to our MVP setup.
for GXT 3.0 (in beta)
My company just completed a very large intranet UI using GXT. The overall
lesson learned was *don't use GWT*. For the most part it was much slower
and the model used in GXT did not extend well to our MVP setup. Perhaps GXT
3 has fixed some of these issues, but we don't want to deploy a framework
Yep - it sounds like GXT grids are overdriving the system. There hardly
seems enough room for content with all that markup. If you don't need all
the bells and whistles that come with a gxt grid - it would pay to port to
lighter weight GWT grids or plain and css. Stripping out excess
forms, eleme
Hi Nino,
Is a catalog application type, you search, list and modify products.
I have to precise some points :
- my application will be used largely by IE8.
- Not all the screen have a performance problem.
- There is some :
- screen that contains : 75 input form, 3 grids (well I have warned my
Not trying to defend GXT or Smart GWT but what kind of applications are you
building ?
We ve build some pretty large apps with GXT and never had any type of UI
performance problems.
2012/3/27 dodo dard
> Stevko,
>
> Yes I'm aware of that too, but I think is not the problem with caching, is
> m
Stevko,
Yes I'm aware of that too, but I think is not the problem with caching, is
more about how many DOM object generated by GXT.
For a simple row in a grid, GXT will produce : a *div ,a table,a tbody, a
tr, a td. *And is not only with the Grid.
I think that makes GXT heavier than GWT.
Bowi
Bowie,
One issue that I've found when working with GXT and GWT is that they use
different models for drawing the page elements. GWT tends towards attaching
the elements into the DOM immediately whereas GXT caches the elements then
attaches them in bulk.
This will tend to make them appear slow but i
Regarding GXT I noticed that comparison website is using GXT 2.2.5 yet
is comparing with new GWT 2.4, if making GWT 2.4 compliant app one
would probably use the new GXT 3.0 which is in beta right now (almost
RC)...I wonder how that compairs to GWT 2.4. I hope not worse.
-Dave
On Mar 27, 6:28 a
Thanks Frank,
I think that too, GXT make pretty component but very expensive and very big.
Btw I found an interesting website : http://gxtvsgwt.appspot.com/ after
looking at your anwser.
Le mardi 27 mars 2012 13:54:52 UTC+2, Frank a écrit :
>
> GXT and SmartGWT have bad performance imo.
> Be
On Tue, Mar 27, 2012 at 1:54 PM, Frank wrote:
> GXT and SmartGWT have bad performance imo.
> Better to write your own widgets (which takes a lot of time) using vanilla
> GWT and make them perform better.
> That is what we did and our GWT projects have very high performance.
Also our experience. G
GXT and SmartGWT have bad performance imo.
Better to write your own widgets (which takes a lot of time) using vanilla
GWT and make them perform better.
That is what we did and our GWT projects have very high performance.
Op dinsdag 27 maart 2012 11:55:14 UTC+2 schreef dodo dard het volgende:
>
>
Helo,
I've got friends complaining about GWT/GXT (GWT Ext) performances, well I
notice that if we put to many component with GXT, there will be a certain
waiting time (3-4s) before it got completely loaded. They said that is
better to write the application directly with Javascript that may I'm
20 matches
Mail list logo
