OK. It has been a while since I worked with GWT - does that size include the GWT runtime? Also, you are deploying this archive to a server, correct? To perform an "apples to apples" comparison, you'd really want to look at the size of the uncompressed application, as delivered to the end user.
But either way, the Pivot libraries are still pretty small (~2MB), and they get cached by the Java plugin. So your users only need to download them once. The same applies to your application JAR(s). G On Jan 24, 2011, at 8:15 AM, Ronald Muller wrote: > The size is no problem at this moment. I am totally new to pivot (but > experienced with GWT and Swing). I am evaluating pivot for a new > project, so I am mainly comparing with GWT. Our current mid-size GWT > application is much smaller (gzipped) than the total size of the pivot > jar's. To have a "fair" baseline i was thinking about proguarding the > pivot app. But that turns out to be not so easy ... > > Regards, > > Ronald > > 2011/1/24 Greg Brown <[email protected]>: >> Have you found the size of Pivot applets to be a problem? The platform JARs >> are not terribly large and application JARs (from my experience) tend to be >> even smaller. However, their size could easily be reduced further by >> removing debug info. >> G >> >> On Jan 24, 2011, at 7:46 AM, Ronald Muller wrote: >> >>> Hallo, >>> >>> Has someone succeeded using ProGuard to reduce the size of pivot >>> applets? If so, are you willing to share the configuration? >>> >>> Regards, >>> >>> Ronald >> >>
