Skip to content

GitLab

A
appinventor-sources
Switch branch/tag
  1. 31 Jan, 2020 1 commit
  3. 30 Jan, 2020 2 commits
  5. 28 Jan, 2020 3 commits
  7. 27 Jan, 2020 2 commits
    • Evan W. Patton's avatar
      Send code after asset refresh, not before (#1959) · 9ae9b122
      Evan W. Patton authored 
      If someone changes the image of a button by using the upload file
feature, we will send the code with the new image property before the
asset is sent to the device. This results in the button not getting
the appropriate image. This change moves the operation to build the
YAIL into the callback of refreshAssets. It also makes sure that the
callback is called regardless of whether there are new assets to be
sent so that YAIL generation doesn't break in the absense of assets.

Change-Id: I14520d8a7945902aa4a9b345d3f9d164a3a9448e
      9ae9b122
    • Jerin Jacob's avatar
      Update build.xml · d172490d
      Jerin Jacob authored 
      A '=' sign was missing in the comment which makes a little confusion for beginners.
      d172490d
  9. 24 Jan, 2020 1 commit
  11. 23 Jan, 2020 1 commit
  13. 22 Jan, 2020 1 commit
    • Evan W. Patton's avatar
      Add ant flag force.builddocs · 68365c94
      Evan W. Patton authored 
      This change adds a property force.builddocs to the build script that
controls whether a failure to successfully execute Jekyll constitutes
a build failure or not. It defaults to false. In Jenkins we will set
it to true so that builds fail if they cause jekyll to fail. This way
people who do not have Jekyll installed can continue to work with the
sources. Since everything needs to pass Jenkins before being merged,
maintainers can run Jekyll to update the docs prior to merging.

Change-Id: I9fb22eea7582fb5ba5a83069778c23a40c14aaa8
      68365c94
  15. 19 Jan, 2020 1 commit
  17. 17 Jan, 2020 2 commits
  19. 16 Jan, 2020 2 commits
  21. 13 Jan, 2020 5 commits
  23. 10 Jan, 2020 2 commits
  25. 09 Jan, 2020 1 commit
  27. 07 Jan, 2020 1 commit
  29. 06 Jan, 2020 1 commit
  31. 05 Jan, 2020 1 commit
  33. 03 Jan, 2020 2 commits
  35. 02 Jan, 2020 1 commit
  37. 21 Dec, 2019 1 commit
    • Evan W. Patton's avatar
      Treat 'global' keyword as untranslatable internally · a29c047e
      Evan W. Patton authored 
      In the block name we store globals as 'global foo' where foo is the
variable name. In Korean and Polish, the 'global' keyword has been
translated for the blocks, but interally we still call the variable
'global foo' even though the keyword shown to the user is
translated. However, because the functionality to unprefix names
references the translated name it causes bad code generation for
languages where the global keyword isn't the string 'global'. This
change introduces a GLOBAL_KEYWORD constant that is checked to
identify globals where the user locale may provide a translation.

Change-Id: Id18331206c28592c145bc2a1d915bcecc0799f13
      a29c047e
  39. 20 Dec, 2019 3 commits
  41. 19 Dec, 2019 1 commit
  43. 17 Dec, 2019 5 commits