GitLab

* Raise error when using boxed primitive types in component APIs
* Make ComponentProcessor error messages private

* Cache checkbox state for each screen
* Make hidden components checkbox screen-dependent

Change-Id: I34fc7bb333208d59e9186800fe2696621c9971af

* Reenable convert number block translations in zh_tw, zh_cn

On macOS, the application icon preparation step causes Java AWT to
create an app window. This window gains focus, even though the
buildserver is a background process. This really only affects
developers working with the sources on OS X. This change sets a flag
to inform AWT to run in headless mode, which prevents it from creating
the app window.

Change-Id: Ida725b80e67c55777437cdd69392a3fab4dcf00a

Change-Id: I9338893e68d64d67207c107b039dc4d7cfbfb556

Also supports Windows, Linux & Mac OS all in one file
Co-authored-by: Evan W. Patton <ewpatton@mit.edu>

* Add GitHub templates

Change-Id: Ib3e663aae8135694ddf423611ebcf7a7caffbd39

Give a warning when a project that uses the FusiontablesControl is
loaded. Google will be shutting down the Fusiontables service on
December 3rd, 2019.

Change-Id: I6a56853ea8a56790495b4462b1c59d5c3059eaef

Change-Id: Ic374dbabd9fad57c06b1b070ab3d84a63ba0b4e6

Change-Id: I9802f22cbe9fba8ed768de995d40b315ec3483ed

Prior to this change, YaFormEditor and YaBlocksEditor are registered
in loadDesigner, which is called from onShow. This is problematic
because if the screen hasn't been opened in the current session and
the user deletes an extension, the unopened screens are not notified
of the change. When the project is reloaded, it will fail to load
because the unopened screens still referenced the deleted extension.

This change moves the registration of YaFormEditor and YaBlocksEditor
as FormChangeListeners to the onFileLoaded method so that they are
made aware of project-level changes (like removing an extension) even
if they are never viewed in a session.

Change-Id: I8306ede85f5fb3576d810c9bd213e5e00df938ff

Change-Id: If1fe3358fb87be47a90dd90a79c794a751ab7288

App Inventor doesn't present a type hierarchy even though internally
it makes sense for objects to have shared methods defined in super
classes. However, the documentation for the properties, methods, and
events of an App Inventor component shared in this way must typically
be written generic enough so that they make sense when shown on
concrete classes. This can lead to either awkward/generic sounding
documentation or requires that the component author override all of
the relevant features on the component to provide component-specific
descriptions.

This change makes it so that descriptions of components, properties,
methods, and events can contain one or more %type% tokens that can be
substituted with the name of the concrete representation shown to the
App Inventor user. This allows for documentation to be shared at the
super class level while still making it sound specific to the
individual component type.

Change-Id: Ida4eb22bec12b2e33ac73de2bb5706d1683b227a

Change-Id: I6702e49a89777c1aa65c6a9fb766e0980d0fc380

* Implement substring search on components palette

Change-Id: I7fdc2d77430473420ed2d0e17d798a485ea16325

Change-Id: Ia4964537d457316824325bdf351a26820a51144a

* Fix missing tooltips in extension blocks
* Add regression testing for component blocks translation

Change-Id: I524b4639234b51d55b82f84a02abdca0db40a4a7

Change-Id: I004e2beda3cd26a1f25e19f38370cca4f2f1fbf5

Change-Id: I6ffef0b3bc66d55adea643bccf34ed4dae2d6d57

Change-Id: Ibe01541a106b37bffbde21f05ea7f1b2c134070a

Change-Id: Ied75987e7ca273d32923342963b54028335d8a46

Change-Id: I3f616e1a4c42416b8e33b40fb3183e65cc862e58

Change-Id: I558443f2afbe08ee192d06f468bcd173f31997d0

Change-Id: Ibacdc5f81f57ab6e49dc906daec47ae593fc94bc