Re: Working on UI Controls styling

Hi Harbs, That looks like good starting point, but this last approach where we for example generate UIDs for every component. This UID at the end will have to end up as an id in HTML or compiler will have to bind together css with that uid. The first approach where you have created couple of css

RE: Working on UI Controls styling

D] > Envoyé : mardi 7 novembre 2017 12:40 > À : dev@royale.apache.org > Objet : Re: Working on UI Controls styling > > A couple of questions: > > How expensive is generating and applying CSS on the client? > > How do developers that use CSS regularly feel about having

Re: Working on UI Controls styling

AFAIK, generating should not be any slower than any other DOM node. Here’s some data on applying CSS (although I’m not sure how useful the info actually is): https://benfrain.com/css-performance-revisited-selectors-bloat-expensive-styles/

Re: Working on UI Controls styling

A couple of questions: How expensive is generating and applying CSS on the client? How do developers that use CSS regularly feel about having to declare that many styles for all the buttons? Maybe tools like Dreamweaver make it simpler and we just need IDEs that could provide assistance. Peter

Re: Working on UI Controls styling

Some food for thought: I created a custom component for “buttons” which allow simple skinning using image files. It works like this: https://paste.apache.org/tc8f Specifying different states can be done using the following css: .bug { background-image: url

Re: Working on UI Controls styling

+1. > On Nov 6, 2017, at 8:22 PM, Carlos Rovira wrote: > > Hi Harbs, > > If we go with Basic as seems everybody suggest, I think we should not mix > with Express. We can "copy" some Express knowledge, but not make it > dependent, to avoid having a Frankenstein > Basic is the core, and from the

Re: Working on UI Controls styling

Hi Harbs, If we go with Basic as seems everybody suggest, I think we should not mix with Express. We can "copy" some Express knowledge, but not make it dependent, to avoid having a Frankenstein Basic is the core, and from there we have Express and the new stylizable set 2017-11-05 22:01 GMT+01:0

Re: Working on UI Controls styling

I creates the element structure that Topcoat expects and adds APIs to set the correct CSS class names. From what I recall, the structure for style-able checkboxes is pretty standard across css frameworks, but it probably pays to do some research on the topic before making assumptions. If someo

Re: Working on UI Controls styling

Hi Piotr, Remember that any top-level component is a composition of beads. We should be able to create most top-level components by take UIBase and adding beads to the strand. So, if we find when implementing skinning/themeing that there are re-usable pieces from Basic great, but what is most im

Re: Working on UI Controls styling

Alex, You are saying about simple case where we can extend UIBase for create new Button, but what about more sophisticated for example Panel ? Do you want us to create from scratch again all of that instead use Basic ? This is how I see reading your last email or maybe I missing something. Thanks

Re: Working on UI Controls styling

I'm not quite sure what the meaning of "based on Basic" means. I think someone is about to go and move a bunch of classes around to better organize our packages and classes, and I think that IUIBase and maybe UIBase should end up back in Core (where it was before Harbs temporarily wrapped the Spri

Re: Working on UI Controls styling

Basic is going to be the base for anything. I don’t think Express is going to be very helpful. It should probably just be built out from Basic components and/or copied from Basic. For an example of a styleable component, take a look at CSSCheckbox. I think that’s a good example of a styleable c

Re: Working on UI Controls styling

I was thinking about that and new component set is the approach which we should try, but we need to base on something. My first thoughts was that it should be Basic, cause I bet that once we start create style for each component we will end up with some issue or we would like to create some additio

Re: Working on UI Controls styling

I would suggest starting a new component set with a fresh slate called Themed (or something like that). The Themed component set should give priority to style-ablitity and ease of use over just about every other consideration. I think of Express as more of a middle-of the road approach to make

Re: Working on UI Controls styling

ok Alex, so if I understand correctly, you mean that we create our own set, with Basic as base right? but we should go with Express? It's great that we could create many sets in Royale, and I think the Basic use you commented is very licit and didn't think about that. But we must think in some *ma

Re: Working on UI Controls styling

Hi Carlos, I think we're pretty much in agreement. Regarding Basic, for me, I have created plenty of web pages with non-styleable checkboxes. I don't care that the checkbox looks different on different browsers. I just want the smallest simplest output. Just like taking an HTML editor and slap

Re: Working on UI Controls styling

Carlos, I just wanted to point to your last sentences. I think we don't know for sure what can we do with Basic. Let's go and try if we came up that something is not achievable let's discuss what need to be done. Piotr On Sat, Nov 4, 2017, 16:19 Carlos Rovira wrote: > HI Alex, > > > 2017-11-03

Re: Working on UI Controls styling

HI Alex, 2017-11-03 17:52 GMT+01:00 Alex Harui : > Hi Carlos, > > I skimmed through https://material.io/guidelines/# last night. > > My impression is that there were two parts to it. First was the > environment/principles section which talked about physical objects and > light (and motion), and

RE: Working on UI Controls styling

gt; Envoyé : vendredi 3 novembre 2017 20:58 > À : ngra...@idylog.com; dev@royale.apache.org > Objet : RE: Working on UI Controls styling > > I largely agree with your comments here. > > > My enterprise/corporate web app actually used the default styling -- > neutral (g

RE: Working on UI Controls styling

fits us perfectly ! > > OF course, our usage might not be typical... > > Nicolas Granon > > > > ---Message d'origine- De : Alex Harui [mailto:aha...@adobe.com mailto:aha...@adobe.com .INVALID] Envoyé : vendredi 3 novembre 2017 17:53 À : dev@royale.apache mailto:d

RE: Working on UI Controls styling

rse, our usage might not be typical... Nicolas Granon > -Message d'origine- > De : Alex Harui [mailto:aha...@adobe.com.INVALID] > Envoyé : vendredi 3 novembre 2017 17:53 > À : dev@royale.apache.org > Objet : Re: Working on UI Controls styling > > Hi Carl

Re: Working on UI Controls styling

Hi Carlos, I skimmed through https://material.io/guidelines/# last night. My impression is that there were two parts to it. First was the environment/principles section which talked about physical objects and light (and motion), and then there were choices of widgets. For example, I didn't see

Re: Working on UI Controls styling

ok Piotr, thanks! :) 2017-11-03 11:23 GMT+01:00 Piotr Zarzycki : > Carlos, Harbs, > > I was speaking with Angelo some time ago off list. Let me ask him and bring > this thread to the attention. > > Piotr > > > 2017-11-03 11:19 GMT+01:00 Harbs : > > > Maybe you want to email them off-list and ask

Re: Working on UI Controls styling

Carlos, Harbs, I was speaking with Angelo some time ago off list. Let me ask him and bring this thread to the attention. Piotr 2017-11-03 11:19 GMT+01:00 Harbs : > Maybe you want to email them off-list and ask if they are still interested > in helping? > > Harbs > > > On Nov 3, 2017, at 10:55

Re: Working on UI Controls styling

Maybe you want to email them off-list and ask if they are still interested in helping? Harbs > On Nov 3, 2017, at 10:55 AM, Carlos Rovira wrote: > > The problem with Trevor and Angelo is that are not very active here.

Re: Working on UI Controls styling

Hi Harbs, 2017-11-03 8:57 GMT+01:00 Harbs : > Great start! > > Glad you liked it! :) > Some comments: > > > But for Vivid, I'm still figuring if it should be > > something "flat" and very simple, or go with something more elaborated > > since the thing I did in the example with orange button. >

Re: Working on UI Controls styling

Hi Alex, 2017-11-03 7:39 GMT+01:00 Alex Harui : > Hi Carlos, > > Looks good to me. Thanks for doing this. > Thanks :) > > I'm not sure I understand all of the aspects of this effort. My current > understanding is that Google Material is under the Apache License and thus > we can use it if we

Re: Working on UI Controls styling

Great start! Some comments: > But for Vivid, I'm still figuring if it should be > something "flat" and very simple, or go with something more elaborated > since the thing I did in the example with orange button. “Flat” is still “in”, but the trend has been moving a bit towards odd blocky relief

Re: Working on UI Controls styling

Hi Carlos, Looks good to me. Thanks for doing this. I'm not sure I understand all of the aspects of this effort. My current understanding is that Google Material is under the Apache License and thus we can use it if we want to. Am I correct that MaterialDesignLite is one implementation of Goog

Re: Working on UI Controls styling

Hi, I want to expose my initial work (very very initial) on two styles for Royale Wireframe: https://snag.gy/tDFxQT.jpg (Wireframe intention is for quick Royale App prototyping, people will use this to start their applications, and then moving to it's own styling that could be another royale th

Re: Working on UI Controls styling

Thanks Harbs! very useful, I'll be keeping this info as I make some work Carlos 2017-11-02 12:13 GMT+01:00 Harbs : > BTW, the kind of thing we should be striving for in theme-able components > is something like this: > > https://vcalendar.netlify.com/ > > > On N

Re: Working on UI Controls styling

BTW, the kind of thing we should be striving for in theme-able components is something like this: https://vcalendar.netlify.com/ > On Nov 2, 2017, at 12:01 PM, Harbs wrote: > > FYI, I worked out a theming class for my (Royale) InDesign extensions which > allow

Re: Working on UI Controls styling

FYI, I worked out a theming class for my (Royale) InDesign extensions which allows for setting global CSS at runtime. The approach might be useful in your theming effort: https://paste.apache.org/cOBC (Some of the code is specific to Adobe Extensions.) Some point

Re: Working on UI Controls styling

Hi, I think I could start to try what Harbs expose, although I think what I will need in the end is to control some SVG parts with variables. Maybe with the showed SVG/CSS relation could be sufficient. I'll be showing how limitations I find. As well as Alex said having inline SVG as HTML would be

Re: Working on UI Controls styling

I’m not sure. I haven’t seen problems. The only issues that come to mind are: 1. There’s no load events on SVG images on Microsoft browsers. 2. Chrome has issues with SVG, transforms and fractional pixels. 3. There’s some blending issues that different browsers handle differently depending on iso

Re: Working on UI Controls styling

A couple of years ago, I thought I had learned that some browsers had issues with SVG background-images. Maybe psuedo-states were involved, but a Button might "blink" as it changed states and loaded an SVG background-image. Do we know if that was just a bug in some browser or is that still a conc

Re: Working on UI Controls styling

JFYI: the svg classes have been tested very well despite there being very few test cases in Royale. 90% of the rendering in my app is using these SVG classes. Our current SVG support is pretty solid. Harbs > On Nov 1, 2017, at 3:12 PM, Harbs wrote: > > We also have an SVG package. Look in Bas

Re: Working on UI Controls styling

You can also use a GraphicShape class and set the element to any random SVG. This would work as long as you don’t need access to the SVG structure using normal Royale methods. Harbs > On Nov 1, 2017, at 3:12 PM, Harbs wrote: > > We also have an SVG package. Look in Basic org/apache/royale/svg

Re: Working on UI Controls styling

We also have an SVG package. Look in Basic org/apache/royale/svg. It might make sense to pull the SVG classes out into its own project. The current implementation of SVG wraps each element in a separate svh element, so you get lots of nested SVG elements. We considered adding raw non-wrapped SV

Re: Working on UI Controls styling

> On Nov 1, 2017, at 2:45 PM, Carlos Rovira > wrote: > > Hi Harbs, > > could you post some basic snippet for this to look at your approach? > > Thanks! > > 2017-11-01 13:42 GMT+01:00 Harbs : > >> You can use SVG files instead of PNG files. I’m doing that extensively in >> my app, but tha

Re: Working on UI Controls styling

Hi Harbs, could you post some basic snippet for this to look at your approach? Thanks! 2017-11-01 13:42 GMT+01:00 Harbs : > You can use SVG files instead of PNG files. I’m doing that extensively in > my app, but that will only work for components which have src or > background-image. > > > On N

Re: Working on UI Controls styling

You can use SVG files instead of PNG files. I’m doing that extensively in my app, but that will only work for components which have src or background-image. > On Nov 1, 2017, at 2:14 PM, Carlos Rovira wrote: > > Hi, > > I started a new project as Piotr suggested. After setup I only put one > s

Re: Working on UI Controls styling

Hi, I started a new project as Piotr suggested. After setup I only put one single button to start figuring how to do this. I'm starting for now with Basic, but as we discussed, don't know if this should go directly to express or not...it seems like something we could plug into Basic at any time a

Re: Working on UI Controls styling

I can say at this point that I really like idea with swappable view. In most cases view is an ActionScript class where we may have more possibility to do things. When I was looking last time into the checkbox it for sure need to more love, some part of the logic should be moved to the View. Piotr

Re: Working on UI Controls styling

Ugh, Something has gone bad in the Basic components. Things like CheckBox and RadioButton should be creating simple and elements. The ability to style everything belongs in a different set of components. Basic is supposed to generate the simplest tree of HTMLElements even if they can't be full

Re: Working on UI Controls styling

Hi Carlos, I think you should start looking into the Basic module and later make an upgrades to Express once you have all components visually created. I would not think on that stage about how we implement them rather look how they look like currently. 1) Create small app or run example with that

Working on UI Controls styling

Hi, I'm trying to find a valid workflow to start working in two initial faces for Royale components. I'm talking about to generate some kind of UI sheet with all controls and a basic wireframe style and another one that would be what more people will be using as default in Royale. From here, will