World: r3wp

cascadign: that's how CSS works with HTML

Hmm, I can't imagine, how should it work? Because on the low level, 
there is just a face, and a gob. So how do you internally distinguish, 
if the panel is separate, or nested in my-panel, and hence needs 
to use different styling?

the implementation id different topic...the question is though: do 
we need such feature?

id=is

It depends - I would welcome more broader input here. But I am not 
sure much ppl will contribute here :-(

anyway, this is not hi-priority at the moment...just something to 
think about.

The reason why I might be interested in inmplementation detail is, 
that maybe I will be style author too, and hence I would like to 
know, how things get complicated in the low level. So in your above 
example - what does stylize do? Does it create internally named label 
style, to keep its visual configuration somewhere? And then during 
the layout phase, you would have to check on nesting, and use  those 
internal styles in the low-level?

There are two concepts, which might be helpfull (maybe it is one 
concept?):


1) having the same style in various sections of your GUI styled differently


2) having the option to style differently the same style in the same 
level (that can be done by options)

There are multiple ways how to doit....But If you are going to be 
style author you just need to know the syntax used in stylize command, 
nothing more ;)

ad 2) e.g. my example of having panel style, with borders, without 
the borders ...

re "I thought that you might find a way of how to do it in terms 
of just one panel" - it is possible to do it in "just one group". 
Do not forget, that R3-GUI H/Vgroups are more similar to R2 layouts 
than R3-GUI (H/V)panels.

I am trying to come up with usage cases here ....

I think (and maybe I am wrong), that even with VID we kind of had 
cascaded styles. If you needed different style configuration, you 
used stylize, and stored new config under different name, e.g. H1, 
H2, H3, LAB in above example, etc.


While CSS allows you to use just one name, and multiple styling set-ups. 
The question is here, how you identify it in the layout flow, what 
set-up should you use, and if it would be obvious. In CSS, you have 
ID, CLASS helpers ...

I mean "if it would be obvious looking into the layout source code"

Pekr, I think you are wrong here...I suggest to study for example 
this: http://css.maxdesign.com.au/selectutorial/

(especially the 'selectors' part)

I have not intention right now to burry deep into CSS, as I think 
I know enough to understand consequences. Your "you are wrong here" 
does not work for me :-) Wrong in what aspect? I still think, that 
I do understand how you style html pages :-)

By 'you are wrong' I meant your understanding whe 'cascading styles' 
really are is a bit blurry...if you check the 'selectors' section 
you'll see that this topic can be a bit more complex.

And the question still stands the same: Do we really need this? If 
so do we really need it all? If not what we really need? :)

CSS is clearly much more flexible in setups. You use tree of definitions, 
which are then applied in particular cases in document hierarchy. 
 If I am not mistaken, right now we don't have no easy way, of how 
to make e.g. first button in a last row of the panel e.g. red, unless 
you first define red button, and use it in the source of the layout 
:-)

If we need it? Who knows. Maybe not for the business graphics. Maybe 
so, if we would like to make model closer to CSS, from various reasons 
...

yes, no hi-priority at the moment...

Cyphre - I can simply imagine, how we extend stylize to allow such 
definitions. But - in terms of html, you have IDs, CLASSes, and you 
have also the document tree, so you might know, where to apply which 
part of an CSS. What I can't imagine is - we have layout flow ... 
and no ID, CLASS definitions, we also don't keep tree information 
of the layout (faces), or do we? So how do you instruct, in your 
layout, that first button in the panel should use button-red definition? 
Just curious about what possibilities there are :-)

why ID, when you can call face directly? And of course there's tree 
of gobs, that's how gobs works.

I've done a few quite complex CSS setups working with jquery, and 
at some point, CSS selectors become very brittle because the priority 
rules become a bit hard to properly prioritize.   


To reflect this, in some setups not all browsers actually match the 
same CSS selection rules.

Rebolek - what has an ID in common with the face name? Short answer 
- nothing :-)

In R3 GUI, style names themselves act as classes, where in HTML you 
have a fixed set of tags that need to have classes. IDs are set-word!s, 
so there is no need to add any superfluous layer to identify specific 
faces.

Henrik, not quite.


using CSS you effectively "tag" your gui and then you can apply effects 
to multiple types of things which match a tag or pattern.

a tag is a cross-cutting concept, not a family or class/type  like 
concept.

OK, let's say set-words can simulate IDs, then Rebolek is correct, 
sorry.

yup, Rebolek was right.

Maxim, this is necessary in HTML, because of the fixed naming of 
HTML tags. set-words in the R3 GUI do this.

But - it might be a bit different anyway. If you make b1: button, 
it is a set-word, a name. And now how do you use stylize, to refer 
to such a name? Stylize creates new style name, e.g. b1, but that 
is direct name for the style itself

in combination with style names, that is.

Pekr, you don't stylize a singel face. you stylize a style and then 
create an instance of that style as a face.

Henrik - but then ID != set-word

no henrik, its a completely different thing.  you can use a class 
name for completely different classes.


a button and an paragraph can share the same class name.   and you 
can then affect them both in the same way.

stylize [
   b1 button []
]

view [b1] differs to view [b1: button]

so classes are neither types nor serial IDs.

(in html)

Pekr, you are mixing up two things. The style name is not affected 
by the face name.

yes, class in html is just an 'group-id'

classes in html/css really act as associative tags.  

in GLASS I am using #issue to simulate html class="label"

Maxim, I was talking about IDs, not classes.

though this is just something I've played with its probably going 
to stick, and multiple tags will be applicable to any control.

ok, I guess I mis-interpreted the angle of one of your replies  :-)

Henrik - ok, so to be clear - show me possible stylize definition 
of a button variant, and how you refer to it in the layout code?

I suggest that classes in the R3 GUI is not useful for the reason 
that it interferes with the "intelligence" layer, where we already 
have:


1. tags to identify state and capability of a face, such as finding 
the default button in the window or whether the button is disabled.
2. name to identify a specific face

3. style name to identify the style and to create a distinct appearance
4. the ability to group faces by panels

5. have information about the ordering of faces stored in the face 
tree

6. use specific policies on how to act on a particular face with 
particular tags

(good feature list. We should keep this.)

Pekr:

stylize [my-button: button [facets: [text: "Pekr!"]]]

view [my-button]