GitLab

Change-Id: I8dfb4482028f96bfe05937600cb6ab930ff4c0fd

Change-Id: I1ea1edae060ad5434b67e89f39442fb5496b126a

Change-Id: If46915890381f0b05165804d802281a4b28c174c

Change-Id: I5c60984f502f361f0080f9310800fcb5c95cb84c

Change-Id: I42031d23208d99b93d92a6fe07abc8dfa7b60efd

* Add HTMLContent property to Label

Change-Id: I59c74e29d1ba2d339c0df2d88d25b06a143bfc9d

Change-Id: I46cd7fb149dbf2ce4349431744ae7a394a09c82e

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

* Migrate Android JSON lib tests to use Robolectric and Junit4

Change-Id: Icf472c1b694cd7b19436b7b55626e8bc0eba9f0b

* Repackage org.json dependency to prevent link issue on Android

Change-Id: I1913914f3182f14963d7531115a30af08e4d9624

* 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

Translation Credit to: Krzysztof Kucner

Change-Id: I29298525dd017abdf4880e9d2f80a23aa4936a82

Change-Id: I331cfcebc9e9053dec399d5b724495f8ef7a51f0

Change-Id: If71bbaee9000dc6332d1452cb02be63a1c3402e2

Previous versions of ScaledFrameLayout saved the entire layer. This
isn't great for performance reasons, but it also had the side effect
on Android > 8.0 of messing with how WebView draws to the screen since
it is drawing to a back buffer. This change switches to only calling
save(), which saves the various transformations without creating a
secondary buffer. This seems to make the WebView happy again.

Change-Id: I9188e68d943fdc56bca7a57a24d0d17b2f9b49e7

The knownIssues and ReleaseNotes pages here are ancient. These pages are
now served from our website (and have been for the last 7 years!), so it
is time to flush them from here!

Change-Id: If109b83c02b6454ec1ae7c55ec7e96efd83f9547