GitLab

Change-Id: Icb898d21027753f633c80e216d0174f541b3dffb

Change-Id: Ifbc57aa50255ffc2935ecc2605644e0f71bd085e

Change-Id: I978d87cdba5533298cae3c89870b213d917d472c

Change-Id: I3ff45bf0aca0163b7a2532388914e0cf8aa18152

Change-Id: I1c8be262333f59f888fde0c0111bd43568b673ac

Change-Id: I902029ad88598ecff611603234d78345e85d1a7a

Change-Id: Ib693b0bd511436a7b363eff16579c341aea8a67b

Change-Id: I3f54c7c2f3db0cfd32b9646f0ca4849cabdd00c6

Change-Id: I61521a8a55856ad18ac07a8c308bc5283cc325d9

When dragging a button or other component with an image from the
palette, its Image property is set, and when it is dropped, the
property is set again. This property is empty by default. In the
network devtools one can observe that this results in a request to the
root of the web server tagged as "img". This is because the
background-image CSS set in response to the Image property uses an
empty string URL, which will resolve against the base URL of the
page. This results in every new button created causing the browser to
fetch index.html twice. In production, we don't cache index.html so
that means every new button created by an App Inventor user causes
them to download ~6 kB of HTML that can't even be used. This fix
switches to setting background-image to none, which foregoes the
unnecessary network requests.

Change-Id: Ifc1165833b2c4aa9d412b0a929dca47381a0cfe8

Change-Id: I0d96f59bfb3e6ac278eaf86757dde10b0a30179b

Change-Id: Ie2bf23e58047bb19d6e0ae289f4021940f1b8324

When we apply colors to buttons, we apply a filter to the background
drawable. However, the default drawable is cached and reused across
all buttons. This causes problems when mixing buttons of the different
colors with buttons using the "default" color.

This change addresses the problem by making a copy of the background
drawable and applying the color to the copy so that the currently
rendered button doesn't adversely affect buttons that come after it in
the view hierarchy. This copy is done lazily at the time the color is
changed from "Default" to something else so that we can still benefit
from the reusability of the default button background drawable.

Change-Id: I2be3b15df32b76a59a29f1e2aed41054f5bdd975

* Add Vagrantfile for development environment bootstrapping

Change-Id: I2fb08206d96f2ff0da73954f820134b7a0684aef

Change-Id: I2fca8de2941613c938eaa0e9be0d391fa67c48f5

Fixes #1140

#1928 fixed being able to use the typeblock to create generic blocks for the Form, but they could still be accessed by using the "Make Generic" context menu item.

This commit removes the "Make Generic" button from the Form blocks.

Fixes #1862

Fixes #1235

Change-Id: Ia697085337cf3aa286f69d3eeba3ccedb7ae643f

Change-Id: Ic9c1a3046c06dcbc582194f013f895d2ed512fc1

the old link was directing to the google group which is not active anymore and it took me a while to join the community via new link. I hope this new link will minimise the confusion and will help other new contributors too.

Change-Id: I3d1846ce60d6b2a4cfedaa4be2895500aad0ee31

In earlier versions of App Inventor, the deprecated flag was stored as
the string 'true' or 'false'. More recently, we made the flag output a
Boolean rather than a string (i.e., `true` or `false`). However, the
code to handle creating the blocks for the drawer wasn't updated to
handle this scenario. Luckily, it was a sensible fallback such that
the block showed, but that means that deprecated blocks show when they
shouldn't. This change fixes this by checking for both the string
version (to support extensions that use the old format) and the
Boolean version.

Change-Id: I6ae272d8e36887ea4259a7948a56badb62f817d6

Change-Id: I76fb8e7f4cfacaa9ad6377790c9cd4d59d379767

The change that produced calls to EventDispatcher's unregister method
for disabled blocks did not account for the scenario where both an
active and inactive event handler exist for the same component-event
combination. This change makes it so that unregister calls are only
output if there isn't a matching active event handler.

Change-Id: If33b577f5af03c64f7abb8fe5b587d576886889b

Moved the FusionTablesControl from the STORAGE to the INTERNAL
category. This means that projects that include the control can load,
but people working on new projects cannot add the control to their
project.

Also updated the documentation to include the warning that it is
shutdown.

Change-Id: Ie05d54b9df0a5bae21661529ded01ce0a549347c

Change-Id: Icd6fd74d49ae11cbc13a6321112e0cf002308186

Change-Id: I7632af43369c42eecc07f2098bb2d4cbf8eb50fe

* Fix environmental sensor documentation
* Fix missing HELPURLs

Change-Id: I44b3780a0475b66555b84a0e3ed94de2196fdb6e

Change-Id: Ib3142c60ecb389da2b304d96c30308cb08939ebb

* Enable multiple component selection using shift key presses
* Add highlight to select components and show number of components selected
* Make selected component properties default when there is no full intersection
* Allow unselection of already selected components

The global keyword that prefixes global variables is translated, and
this translation ends up in the Blockly XML. We need to keep the
translation separate from the underlying representation so that
projects still work when switching between languages.

Change-Id: I7bc88f0a26c8dce6d256010c188d7233d8cc43f8

Autoload behavior can be overriden per session by including
autoload=false or autoload=true in the query string when loading App
Inventor.

This commit also refactors the menu construction into individual
pieces so that they can be called to be reconfigured. At the moment,
this feature is only used for the Settings menu, but it makes the
creation of each menu independent of any other menu.

Change-Id: Id220991cef5f7643465ef9648f663a52be1486ae

Change-Id: I039a5709a4c97f628a03a072a58d58ffd45ca9c7