One thing that I found problematic with the mdl implementation was that there was a feeling of thin wrappers on a blackbox. Whatever default theme we choose, I think we should implement it so the core functionality is easily understandable to an AS3 programmer with some CSS knowledge. That should also help create new good looking components (and themes) easier by looking at the existing examples.
________________________________ From: carlos.rov...@gmail.com <carlos.rov...@gmail.com> on behalf of Carlos Rovira <carlosrov...@apache.org> Sent: Tuesday, November 14, 2017 5:10:21 PM To: dev@royale.apache.org Subject: About Semantic UI and our UI Set + look-and-feel effort Hi, I was looking at Semantic UI and it has most of the things we want to get with our UI set + Look and feel effort. I need to investigate it more, but maybe we don't need to reinvent the wheel here. Supposing licenses are ok, we could base the new UI Set to be based on Semantic UI or make our own Semantic UI implementation. Regarding look -and-feel you can get most of the main actual look and feels out-of-the-box (material, amazon, bootstrap, twitter,...) The main concepts behind are great as well: * Use concise and natural HTML * Intuitive JS https://semantic-ui.com It has already integrations with React, Angular,... Maybe our potencial is not in this area but in our composition concepts and this could be integrated. This would need to make a new UI Set as we did with MDL, but this time this could be the main UI Set since it could have all we need, different look and feels, all controls needed... We can as well use it to reach 1.0 and from there think if we need to create out own. Another thing to think about it is how this will deal with other outputs far beyond javascript (SWF, WebAssembly,...), maybe those outputs will need to be develop by us Semantic-UI is under MIT license what I think is compatible with create what we need or take parts from here right? Thoughts? -- Carlos Rovira http://about.me/carlosrovira
