Re: Application size due to Internationalization

Dear Tony, Thanks for your suggestions. Yes, I did this. But the main issue I am unable to solve is the size of the code. It is too big to deploy on app.spot. Many thanks Rana On Wednesday, July 18, 2012 5:05:24 PM UTC+2, Tony Rah wrote: I use a special DevModule.gwt.xml module during

Re: Application size due to Internationalization

Hi, Many thanks, I will see if we are deploying the class files in the jar. Thanks a lot for the idea Rana On Wednesday, July 18, 2012 10:48:11 AM UTC+2, Richard wrote: Rana - are you combining class files into a jar? That'll help reduce the file count for GAE, if that's an issue for you.

Re: Application size due to Internationalization

On Wednesday, July 25, 2012 11:34:13 AM UTC+2, Rana wrote: Dear Tony, Thanks for your suggestions. Yes, I did this. But the main issue I am unable to solve is the size of the code. It is too big to deploy on app.spot. Are you also trying to deploy some WEB-INF/deploy folder? If you

Re: Application size due to Internationalization

Hello Tony, No, we don't seem to be putting things we don't need from WEB-INF/deploy, but we are supporting I think 66 languages. And they are making the application very big in size. That is why. Also, originally the application is big, we are doing mathematical drawing and calculations...

Re: Application size due to Internationalization

:) :) Sorry, I got confused with the posting area: No, we don't seem to be putting things we don't need from WEB-INF/deploy, but we are supporting I think 66 languages. And they are making the application very big in size. That is why. Also, originally the application is big, we are doing

Re: Application size due to Internationalization

Thanks for your suggestions. Yes, I did this. But the main issue I am unable to solve is the size of the code. It is too big to deploy on app.spot. I don't think that is the case. Prior to AE1.7, I was over the limit due to permutations as well. AE1.6 was 150MB/app right, and 1.7 is 1gb (total

Re: Application size due to Internationalization

Hi Joseph, Thanks a lot for the information. I will go through both links, and see if it helps in solving the problem. Many thanks again Rana On Wednesday, July 18, 2012 3:07:48 AM UTC+2, Joseph Lust wrote: Rana, I've read that internal Google apps must build to 240 permutations for the

Re: Application size due to Internationalization

Rana - are you combining class files into a jar? That'll help reduce the file count for GAE, if that's an issue for you. Wishlist: upload the code/basic .classes, have GWT compilation happen on Google infrastructure. On Wednesday, July 18, 2012 9:49:19 AM UTC+2, Rana wrote: Hi Joseph,

Re: Application size due to Internationalization

I use a special DevModule.gwt.xml module during development that only compiles the permutations I am interested in. This way I can control the user agent, locale, and other GWT based switches without compromising the production builds. Below is a rough overview of this approach: Create a new

Application size due to Internationalization

Hi, Does anyone have a solution to the huge size of application, when we apply to it internationalization using the static method? We are supposed to support 66 languages. The application takes a long time during compilation and the size of the application is huge, we cannot upload it to

Re: Application size due to Internationalization

Rana, I've read that internal Google apps must build to 240 permutations for the supported browsers and languages. To support this they: - Conduct draft compilations only using their desired dev permutation - Do complete compiles for releases/CI/test on a server farm There are