GitLab

The components reference page was missing a link to the Experimental component category.

This results in compilation building a single large Javascript download
instead of one for each browser/language combination. In production,
minification reduces the size of this file to something
reasonable. However if you build directly from master, this one file
will be pretty large. However it will work just fine.

This changes significantly speeds up the build process.

Change-Id: I330faf96fd95e538e3c19130c85c3ae8dbb077df

Already added in https://github.com/mit-cml/appinventor-sources/blob/c294e2fc92f726eadc9531c3aa9edcbf497cc5c8/appinventor/components/build.xml#L273

`type.equals("short")` was checked twice

Change-Id: I239b3378d6494cdac20e2034fb0f8667f0811819

* Add menu option to remove block stack from Backpack

Change-Id: Iada620f2d8a425367faf5a05d15f43236fede95d

Change-Id: Icef6b14f0248258189a764989778e0aba9ce4c05

Change-Id: Id93060e5d4a9c9b8ae153a7c2ac57dac92ad99f6

If one deleted a component while on the blocks screen, the drawer
remained open. This commit tracks the last component opened and, if
the deleted component name matches the last component opened, it will
close the drawer. We track the last component referenced so that we
don't hide the drawer in the event a component is deleted when another
drawer, for example the built-in math blocks, is open.

Change-Id: I4808a069b38986e44892e721b2d35132bfdae943

Implementation of the drag and drop support for the designer did not
handle touch events on the help and remove extension buttons in the
palette. This commit adds the corresponding implementations to improve
touch support.

Change-Id: I7a877683da6421c67104f4fb704e7c35fd90f578

Add a Shutdown Hook. In a container swarm, the swarm orchestrator may
choose to shutdown a container (running a buildserver) as part of load
balancing and other maintenance tasks. It will send a SIGTERM signal to
the container which will send it to us. This shutdown hook causes us to
wait until all build tasks are completed before we exit, ensuring that
people's build jobs are not interrupted We combine this code with a
configuration in the swarm service to *not* hard kill a container for a
period of time (say 15 minutes) to give the buildserver a chance to
finish outstanding jobs.

Change-Id: Ie0fed539162e219af3df96a1402f153fc0473f0e

Buildserver progress, as reported in the progress bar during a build,
used to work by having the client poll the App Inventor server, which
would in turn poll the buildserver to learn the progress of the build.

However this code would only work properly if there was only one
buildserver and only one build in progress. In reality we handle dozens
of builds simultaneously via a number of independent buildservers. So
the progress being returned to the user was the progress of *some* build
in the system, most likely not theirs!

The constant polling by the App Inventor server also causes problems
with the load balancer in front of the buildservers. This is because
most “jobs” are not real build jobs, but just polls for progress. This
may result in a non-optimal distribution of jobs between the various
buildservers.

This code changes things so that the buildserver does a callback to the
App Inventor server when appropriate milestones are reached in the
build job. The client still polls to App Inventor server for progress,
but the App Inventor server no longer polls the buildserver. This should
result in a better distribution of build jobs on the buildservers and
also returns to the end user the correct status of their build.

We also removed some obsolete code that attempts to generate the Yail
within the Buildserver. We *always* generate the yail in the client now
and it is sent to the buildserver.

Change-Id: Ibaa9a7e3ff6576335d5ab6261a4121f27a1daf1d

Fixed i18n translation issue

Fix several minor issues (Fixes #928)

Change-Id: Idecd5a1eae1fadcf0b0db105ecc7c2ccc5afb499

Document the AfterFileSaved Event for the File Component

Change-Id: Ice7cbdf7ada7e063897821c20d060bd8f2023445

Author: Evan W. Patton <ewpatton@mit.edu>

Make sure that touches select the components
Implement drag-and-drop to reorder components

Closes #1020

Change-Id: If33b569dbf76d08df411185e0efac546df253409

We no longer use the “AccountName” property and it has been removed from
CloudDB.java. However a reference remained in MockCloudDB which causes a
problem when a project with a CloudDB component is upgraded due to an
increment in YOUNG_ANDROID_VERSION.

Change-Id: I8a6234993df32ff087fbcbd79edf447c3e39c9c5

Fixed #1107

A shared backpack is enabled at SSO login time[1] by providing a
backPackId parameter in the SSO Token. Once enabled backpack contents
are not stored with the user account but instead in a specific location
defined by the backPackId. Multiple users can use the same shared
backpack at the same time. Each time the shared backpack is opened a
fresh copy is loaded from the server.

There is still a race condition if two users attempt to store blocks at
the same time. One will win and the other’s changes will not be added to
the backpack. This may be corrected or mitigated in a future release.

[1] Note: SSO Login is not currently implemented in the App Engine
version of MIT App Inventor. This commit updates the Backpack code to be
in alignment with the code we use in our Hong Kong deployment which is
not run in App Engine. We plan to implement SSO login in the App Engine
version in the near future.

Change-Id: I5957a42999ff14d7263a47993efaf8f3492c016g

Update whitelist.py so it works with the latest App Engine SDK. Also
update permissions on /remote_api to be compatible with the latest App
Engine SDK. Note: The change appears to remove the requirement for admin
rights to use the /remote_api facility. However this admin requirement
is now enforced by the Google supplied code which runs behind
/remote_api. Performing the additional check in web.xml just causes an
error about too many authentication attempts.

Also remove excess catch statement in Whitelist.java that has been
giving us compilation warnings for a very long time. Note:
Whitelist.java is no longer in use, but can be enabled via a simple edit
to OdeAuthFilter.java, so we are not removing it yet.

Change-Id: I30cbb0eba3fba3f20d8443a94dae837c827f0b20

"alignemt" => "alignment"

When importing a project that requires an upgrade involving project
settings, if any screen loaded before Screen1 would fail to
upgrade. Attempting to build a project in this state would only
generate YAIL files for the successfully loaded screens. The build
server would attempt to generate YAIL for the missing screens using
the AI1 YAIL generator, which no longer exists. The error message
doesn't give any indication that this is the problem.

This change defers loading of screens other than Screen1 until
Screen1's form is loaded. At this point the upgrade of the Form and
the project settings will have occurred, and then we can proceed to
load the additional screens.

Change-Id: Ibde055171a8939a9e9ae5ed8ea5ce3954fb5ccf1

DatePicker, TimePicker, and Notifier create dialogs that do not have
the appropriate color. This commit adds behavior to the compiler to
output styling information for dialogs so that these components
properly reflect the user's chosen AccentColor.

Change-Id: I770dcdff555b9f40a28c75e435e938e6258ab3c5

Projects using relatively sized markers are unable to load correctly
because the width/height is set before the MockMap is ready. This
change introduces a needsUpdate flag that is set when this occurs. The
size is then updated when addToMap is called once the map has been
set. This also fixes a minor bug where markers with image assets do
not end up being the correct size in the designer after toggling
visibility.

Fixes #1136 and fixes #1137

Change-Id: Ic800b19241b9bcf33cd07db17308b7c61d13b81e

Setting Theme is sufficient and an interaction with default values
breaks some upgraded apps.

Change-Id: Idf36857bcc314b7fba45d730986c5d2d6749d727

Fixes #1125

Change-Id: I6dbb8cae01fbd1cb556fe9c20f73c82fa2075051

Fixes #1121

Change-Id: I64c464a96614ee9f0d4f5b9f55ab350ddeeb12f5

Fixed #1120

Change-Id: Idd679d701cfad71580cbd841a093dd35b558fc5f

When a string such as "permission," is used with @UsesPermission, it
results in an empty string appearing in the permission list, and in
the <uses-permission> annotation in AndroidManifest.xml. Google Play
Store will reject such apps. This commit filters out empty strings
during component processing and during compilation to fix this issue.

Fixes #1108

Change-Id: Icafe2fa658f83f046dacfec98d3f0cb8f8b90755

Change-Id: If66538c363b19b001a065ebc72e73a73927da7a7

Fixes #1109

Change-Id: Ic34ac78f5fda8af8f2286d2f604f2b4d4c2e84e0

Fixes #1118

Change-Id: Ib08fb391529b26ca107b5e8f67acb329e70e958e