desktop

Since we also expose the Skia-bindings for a Canvas-like API I think it might be a good idea to start refactoring the API to utilise more named arguments e.g. ~x=..., ~y=....

What do you others think?

My menubar is full. Even with "menubar mode" turned off it still appears up there. It should not force an icon up there.

AppState is declining to remove the currently-selected version, which is reasonable, but there's no UI feedback explaining why nothing happens when the button is clicked.

I'm not sure what the Right Thing to do here, but some easy solutions:

• Maybe the button should be insensitive for the currently-selected version?
• Maybe a tooltip should explain why it's insensitive?
• Maybe AppState s

Problem:

There is no way to define an array or object in the customize properties section of Lively. This can make it much more difficult to allow properties that have multiple variables without bloating the customize menu.

Solution:

Allow support for arbitrary length arrays and object creation as customizable properties.

A mock-up image is attached below
![Lively Object and Array

These localized folders are not getting updates anymore (deprecated by touchdown localization)
bn-BD
ha-Latn-NG
sw-KE
uz-Latn-UZ

we can remove those folders from the build to avoid confusion since those files don't get updates.