We have been working on a number of changes to improve App Inventor. These changes have been compiled into a version available on https://ai2-test.appinventor.mit.edu. You will need Android companion 2.65t1u from the test server or you can use iOS version 2.64 or later from the App Store or TestFlight. If you encounter any bugs, please report them in this thread.
The tentative change log is as follows:
Features:
Add functional list operators like map, filter, reduce, and sort (@siyaoL1)
Add new math stats blocks like average, standard deviation, min/max over lists
Thanks for pointing that out as the documentation could be more clear. I'll ask some folks on our end to review and make suggestions on how it could be better worded.
Now I see the upload option after the category list.
Familiarity with the four options blinded me to the new upload option under the category list.
Now I know where to put my WingDings.
That I do not know. I imagine that it is any font format supported by Android (possibly different depending on Android version). @preetvadaliya might be able to expand on that.
...except you need a license from Microsoft to use any of their fonts (probably the same for any big names in the font business, Apple springs to mind).
costly too.
It would be worth mentioning in the Documentation that you cannot simply copy a font from your computer to your App Inventor Project without buying a license.
It is useful together with the advanced blocks...
Currently we have to create a list, which contains all for example checkbox components... now we can use that new block instead...
As usual, I can not use this ai2-test server and ai2 server, since the google account problem. We in China can not use google server.
Is there other way to log in the server with no google account?
I've used @Taifun's sample code pattern with generic blocks in several projects already.
However, the every block would fail me if I had more than one radio button (list of checkboxes) or if I was dealing with components lined up in rows and columns, where enumerating the components in lists was needed to establish context (row and column number) working backwards from a component, using the INDEX IN LIST block.
Maybe an EVERY COMPONENT in CONTAINER block would be more useful for cases more complex than single radio button samples.