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

t; 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 to d

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:

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

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

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

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

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.

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

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

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

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

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: >

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

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 Carlos, &

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

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 > > >

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

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

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

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

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

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

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

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 >

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

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