GitLab

We now need to build three different companions for every
release. This change makes it so that we can build all three with a
single run of ant rather than having to configure multiple different
companions and performing three separate builds of App Inventor for a
components release.

Change-Id: Ia0ed7e85513081e1fbaff606223f7d88b4dbc638

Remove calls to the Package Installer in order to be compliant with
Google Play Store rules.

Change-Id: Iab89c09e815af14728f08682d02e4447077aed55

The primary rendezvous server is used for the initial rendezvous,
whether using WebRTC or not (Legacy Mode). This change provides the
location for a secondary rendezvous server to use for the WebRTC
negotiation. This is only done if the Companion indicates that it
supports this feature (sets “r2” to true in the JSON object it
posts). Any information provided by the Companion can be used by the
primary rendezvous server to determine which secondary server to use.

Change-Id: I8706c4f0fe66a0e902595689896003feff9cdff7

Change-Id: I0548b10a840678e25baa2636e2891838a5c6775b

Change-Id: I9b23ee39bb46e63d56e4bd7b6cc24b8d32cdade3

* Unified file provider source

The change to make component reference blocks usable in globals
changed the ordering of initialization in such a way that components
that rely on the theme applied to Screen1 end up getting the wrong
theme. This corrects the order of initialization so that Screen1's
properties are set immediately before any other components are
created.

Have the Companion create a unique “InstallationId” which it reports to
the Rendezvous Server. This will help us keep track of how many
Companions are out there and what version of Android (and the Companion)
they are running on.

Note: The id is generated by the ACRA Library and is persistent across
upgrades of the Companion. However it will be re-created if the
Companion is uninstalled and then re-installed. It is not related in any
way to any Android provided identifier, which minimizes the privacy
impact of this identifier.

Change-Id: I7b85afe1451f4d44b4e0d412b3f37904425e3112

Change-Id: Ic56482d73262b9a1ddab955e8560f975f42d87a0

The value of this variable can be changed if any class other than Activity is used as base class for Form.

Changed the extension from PNG to png (because case matters!)

Fixes #1620

Change-Id: I6a334cfb18caa5b2a50ac4ea34109a6325a3586f

Eliminate the single threaded executor because it is not needed. Instead
use Timer.scheduleAtFixedRate() to trigger the Poller once per
second. This approach is more correct and simpler.

Also, ignore an empty response from the Rendezvous server (which means
that it hasn’t received any ICE Candidates from the browser
yet). Previously we attempted to JSON parse it and threw an
exception (which was logged and ignored).

Change-Id: If0bc95c754a3fd052ac32cfa966fcbcfe658f55d

This is a toggle switch component. Functionally, it behaves the same as a checkbox: the ON state is equivalent to checked.

Since iOS does not have a checkbox and only offers toggle switches, this component paves the way for an on/off component that is shared by both Android and iOS.

The toggle switch is a 2-color control, which means that there are 4 configurable colors, 2 for on and 2 for off.

Allow drawing shapes (made up with lines) and arcs (or sectors)

De-Bounce the “Connect with Code” Button in the MIT AI2 Companion

The Companion's design is to setup communications with the user's
browser and get to work. Once this process starts, enough things are in
motion that it is best to quit the Companion and start a fresh copy if a
different code is needed.

If the same code is entered more then once, we just ignore the second
attempt. This often happens when someone scans a QR Code and then
presses the "Connect" Button because they do not know that they don't
have to do that. Effectively we are "de-bouncing"

Change-Id: I06b20c5d9cdb07999a380d9f877edd111e0357c5

The original method, uniform integer modulo 100000, is biased in
distribution. Now it's replaced by built-in sampling method.

Java 7 API has comments on random.nextInt(int n):
https://docs.oracle.com/javase/7/docs/api/java/util/Random.html#nextInt(int)

It is often the case that people will want to construct a list of
components or store some information about a copmonent so that it can
be restored later. this currently requires putting all of the
initialization into the Screen's Initialize event handler. However,
many people intuitively expect that they can construct a list of
components as part of the global declaration. This changes allows for
component blocks and property getters to be used in a blocks tree with
a global declaration root node.

Change-Id: I69d26716ebf4bfcdd52465f15eaf75af1c4170cf

Change-Id: I62ae3fed73342a5f6cb7652903a09e4dd9c6d620

Change-Id: I1925eb15feb0e5f6b51e409538491fb0b5257928

Change-Id: I6d7899a36e7e2ee4dd748948a98ce6693af18650

Change-Id: I09bec5aca529b51746d3b56a5f2c4c9a4bcf5eea

Change-Id: I18e9d3f605b329dc8a307b5d799755f3c6c9ccd0

This commit introduces a new block to list operations that reverses the
order of input list and outputs the result as new list.

Change-Id: If22a6641a2586ecc6586ead9ea046cc119a2a9fc

Change-Id: Ibe249c4de10d8d8213c009728771062eabba9630

Change-Id: I32f1bba6e7f1db17321665612a8ff2c2236446fb

Change-Id: I9409f6f3f503d467b6014461d51c6f213dcb76ff

Change-Id: I4a4b0af5365581cf4663f66181991ca3c747146e

Change-Id: I7d3f5864bd65c3607a0f7083e8df44aef79c8cb9

Fixed Issue #1352:

1. Cursor changes to pointer when hovering over the backpack and zoom elements on the right side of screen.
2. Zoom elements and trashcan are now black to increase their visibility on the screen, especially when the grey sidebar is extended over them.
3. Shifted the positioning of the zoom control images from the sprites.png image so that no more ugly lines display around the controls.

Closes #1431

Change-Id: I07d684643df2f5ceaa63be8c2f45c39c8a3c0099

Change-Id: Ib180d8e18b6056e9f75e882c4bd9b8faf49f5548