Form properties overrides the css style ?

Classic Servoy
1

I’m confused after playing arround with css, because i did’nt found the logic behind.
a view thoughts with the example borderType of a field:

  • does a field propertie borderType = Etched override the css style border-style: ridge; of a Field ?

  • doesn’t it make sense to store this css field style to border-style: Etched; (but Etched is not supported in css so far i understand)?

  • what is the reason that the actual supported Servoy-css (none, solid, double, groove, ridge, inset, outset) is not the same like the
    possible field properties in Formdesigner ?

  • where does the DEFAULT of a field propertie in Formdesigner come from (override by css or not )

Sorry for all this, i tryed to find out the logic behind, but was not able…
Thanke you for help

2
  • does a field propertie borderType = Etched override the css style border-style: ridge; of a Field ?

yes, the values set from editor override the values set from css; so css will be taken into account only if no value is set from editor

  • doesn’t it make sense to store this css field style to border-style: Etched; (but Etched is not supported in css so far i understand)?

The problem here is that we have to accommodate two separate things, the css standard properties and the swing properties (for Smart Client). Here is the standard CSS property: http://www.w3schools.com/css/pr_border-style.asp . As we like to use standards the css values that we support are a subset of the values from the standard. As you can see, Etched is not a valid value in context of css. Its corresponding css value is “groove”.

what is the reason that the actual supported Servoy-css (none, solid, double, groove, ridge, inset, outset) is not the same like the
possible field properties in Formdesigner

Supported css values are: none,solid,groove,dotted,dashed, inset,outset. The css values come from CSS standard, the values from designer come from swing values. So, we had to do a mapping between the two. You can create a case if you want to simplify this issue as indeed it can be confusing.

  • where does the DEFAULT of a field propertie in Formdesigner come from (override by css or not )

Not sure I understand this, DEFAULT usually means null value.

In Servoy 6.0 there will be a new CSS Editor so editing of CSS files is much easier (and autocompletion tells you what is supported).

3

“DEFAULT usually means null value”, and if it’s so, then the value (of border for instance) it’s taken from your CSS (style) file (I think)

4

Yes, when set to default the styling of the element will be taken form the applicable StyleSheet and it there is none, then the LAF (Smart Client) or the default Web Client stylesheet (in the Web client of course) will control the styling.

Paul

5

jcarlos:
“DEFAULT usually means null value”, and if it’s so, then the value (of border for instance) it’s taken from your CSS (style) file (I think)

For my understandig till now:

  • NULL ( often less then 0, really NOTHING)
  • and DEFAULT (a predefined, given value in case of no choice)
    was not the same.

For me it is quit clear now, how the overrides and defaults work. I think i was confused because i didn’t know about the swing/CSS problematic.

Thanke you to all, helping me.