Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Carlos, If it turns out you can create a default look for us without any SVG, that's fine with me. SVG-as-skins could always wait for some other day. I don't think potential users have said they must draw their visuals. So I leave it up to you to decide what to work on. If it turns out you

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Alex, 2017-11-14 18:26 GMT+01:00 Alex Harui : > Hi Carlos, > > You and others are definitely welcome to integrate SemanticUI like you did > for Material Design Lite. > Ok, but as I stated before, if I invest in integrate SemanticUI the proposal would be as I

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Carlos, You and others are definitely welcome to integrate SemanticUI like you did for Material Design Lite. Regarding a more sophisticated option, I first want to see if SVG for visuals is possible before we build a whole tool chain around it. So, IMO, you could just use your favorite

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Alex, what you propose would be the more sophisticated option we can do. I could invest in that, but I need to work with you, Peter closely to complete something. I see more probable that I can design each component, at least for a first round, but I can't do the infrastructure we need to get

Re: About Semantic UI and our UI Set + look-and-feel effort

Maybe we need to pause for a minute to agree on the implementation goals related to our default theme. I was under the impression that an implementation goal was to create a component set where you could "draw" just about any visuals for the components. These other 3rd party themes (Material

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Peter, IMHO, dataProviders+itemRenderes in Royale List and Tablets is without doubt the way to go. Is some of the features that made Flex so successful, like RemoteObject or other "Flex" things, is what will make migration from flex more easy and what a flex developer expect to see in Royale.

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Peter, I mention it in my email at the end. We can talk with legal first, but in theory MIT license allows us to do whatever we want as is the most permissive open source license I know. But you're right, before pushing project barebones for this, we'll be talking with legal. Thanks! :)

Re: About Semantic UI and our UI Set + look-and-feel effort

haha, sometimes planets align Piotr! :) 2017-11-14 16:53 GMT+01:00 Piotr Zarzycki : > Carlos, > > Just quick from me. Today I have found exactly the same :D :) > > Piotr > > 2017-11-14 16:25 GMT+01:00 Yishay Weiss : > > > One thing that I found

Re: About Semantic UI and our UI Set + look-and-feel effort

Hi Yishay, that's the main problem I see in MDL too. And that it was not our own foundation. I said that MDL was only something quick for people coming that see Royale can do good looking UIs quickly. But the problem was that we can't plan anything "cross" to all Royale since Material has its own

Re: About Semantic UI and our UI Set + look-and-feel effort

For things like lists and tables, we have our dataProviders and itemRenderer factories. Could probably be more streamlined to produce list and table elements for the itemRenderers. Being able to make a quick in-line list with some text and buttons ought to be easy and not require a dataProvider

Re: About Semantic UI and our UI Set + look-and-feel effort

I did a quick look. Seems pretty cool and definitely useful. Plus it gives us direction. But please, please, please, figure out licensing before going a step further. This is what I found: https://semantic-ui.mit-license.org ‹peter On 11/14/17, 10:10 AM, "carlos.rov...@gmail.com on behalf of

Re: About Semantic UI and our UI Set + look-and-feel effort

Carlos, Just quick from me. Today I have found exactly the same :D :) Piotr 2017-11-14 16:25 GMT+01:00 Yishay Weiss : > 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 >

RE: About Semantic UI and our UI Set + look-and-feel effort

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