Implementing UI based on iOS 7+ / Google Material (?)

Hi, I can address the overflow of text and see why the codepoint is showing in Windows.  And yes, I will work in your modification too. :slight_smile:

[0.1.84] - 2017-03-17

Changes

  • setSelectorList() method added to set the named drop-down selector with the contents of a list. This makes it easier to dynamically change the list after declaration.  See commented out example in fun.lua.

  • setSelectorValue() method added to set the named drop-down selector’s current text and value content.

Both methods above are listed in the documentation too.  See documentation for it here.

Fixes

  • Fixed newTextBox() contents overflowing out of defined area. The text is now in a container and the text is always aligned to the top (shows first line of content on down).

  • Made it so Windows simulator uses the utf8 assist for the codepoint of the material font. Be sure the “MaterialIcons-Regular.otf” and MaterialIcons-Regular.ttf are in your project root.  This showed the correct drop down arrow and not the ‘text code’ for the drop down. 

[0.1.86] - 2017-03-18

Changes

  • newTextBox() improved editing experience on mobile
  • newTextBox() options for “doneButton” and for the overlay.  Due to mobile devices not having an easy way to edit text boxes an overlay w/ “done” button (on right of textbox) has been added.  The overlay and button is “not” used on non-mobile devices.  Please see documentation and fun.lua for a complete example.  This makes editing in a textbox easier on mobile.

Great!

Hy! Is there a date for a new release or is it finished? It’s just to understard if I can use this tool like the last stable version. Thanks again for all that work

Feel free to use the lastest version. It’s stable.  Some internals are being worked on as improvements.   Work is progressing on adding more controls and extending some of the current ones.

It may become a plugin in the near future as well (free plugin) while keeping the GitHub in place.

Why, why, why…

Why I didn’t see this thread before wasting 50 bucks in an abandoned, outdated ui package like Widget Candy?

Paul, thanks lot for all your hard work on this one. Looking forward to taking a look at your layout framework.

Is there a way to disable widgets? that is, making them unresponsive and with a visual clue of its state (probably increasing its transparency?)

Yep, I can add a visual clue of disabled widgets.  It will allow the developer to use the default settings or specify their own.  Support for extended sprite sheets, SVG (using the free plugin on marketplace) and additional controls are underway.

Widget Candy is awesome and don’t feel bad, I spent $50 myself on it to realize it wasn’t supported anymore.  That’s part of what drove me to creating the new library with a focus on the business App side.  Of course with sprite sheets and SVG support it will move into both business and gaming.

The layout engine is kinda working like “div” tags and minor “css” you find in HTML5.  That approach is in my head due to being a web developer by day.