ways to work around the size issue in the new jars

[Gary]

The current (Dec 20) jars can not load as big a project as the Google server  http://code.google.com/p/mit-cml-app-inventor/issues/detail?id=13

There is a comment that the problem may be fixed in the next release of the jars.

Till then, what we talked about in the tAIR web chat a few hours ago is splitting the big project into smaller pieces. That lets you work on your app regardless of what happens.

If you have an app that is using 4 screens, save the source as app1, app2, app3 and app4.

In app1 cut out the code for app[2-4]

see if the 4 smaller apps load in a new server.

It does not have to run, just load.

When you have parts that all load, look at each part and determine what data one part sends to another part.

Then you get the data the one part sends, put it into a text field 

  AND

use Activity Starter to pass the data there and back.

That lets you work on the Google App Inventor server for the next few days.

and!!!

the blocks you use with Activity Starter are pretty much the same as the blocks the new multiple screen code uses.

https://groups.google.com/d/topic/theairepository/MgqhjfpXeu0/discussion

  and

https://groups.google.com/d/topic/theairepository/0a_veRWsNiE/discussion

should help

Gary

[Anthony Barnes]

Utterly Brilliant!!!

--

tAIR - Main Site   |    tAIR - Forum   |   tAIR - Code Site   |    tAIR - Webchat
tAIR Companion App - Download From Market
Tony Barnes   |   barne...@gmail.com

[Bryan de Valdivia]

It's a Really Good idea, but mileage will vary with every app.

I've been working on implementing it since the tAIR chat [except for some shuteye] and unfortunately, it won't work with my app :(

Although I do have multiple screens, all the heavy lifiting is done by one screen, and the others are just window dressing.  Therefore, not able to break up the code in any meaningful way.

Hopefully, this will help others with large apps though.

b.

[Bryan de Valdivia]

Oh, and something else that was talked about last night:

If you have a large app where media makes up a bulk of the size, it may be that the mit jars will accept it.

b. 

[Gary]

> Therefore, not able to break up the code in any meaningful way.

Who said anything about meaningful. :-)

Get the parts so it loads I like using a big ax.

then you have fallback if the next update still does not get you developing.

Gary