Richard, John and Tom thanks for your input.
> > Also one more advantage I see if JavaFX complies with w3c CSS (on the
> > things that count) is that CSS is a continuously evolving technology
> with a
> > lot of people already working on it and evolving it (for instance, the
> > broken layout sys
Hi Pedro,
on CSS as a spec: You are right the spec does not only hold a language
definition but also the definition of e.g. the
box-model, ... who simply can not be applied to FX
unless you completely revamp how it works
on CSS: The grammer o
> Also one more advantage I see if JavaFX complies with w3c CSS (on the
> things that count) is that CSS is a continuously evolving technology with a
> lot of people already working on it and evolving it (for instance, the
> broken layout system is being rewritten with things like the box model), i
Hi David,
> Currently, a control has a default style-class. For example, you can use
> .button in a style-sheet to style a Button. I propose to move the default
> style-class from the control to the skin (RT-32186). The impetus for this
> change is two-fold.
>
> Firstly, it can be argued that
I appreciate the feedback and would like to point you to
https://javafx-jira.kenai.com/browse/RT-9272. Your constructive criticism and
input is welcome there, too.
On Aug 7, 2013, at 4:41 PM, Pedro Duque Vieira
wrote:
> Hi David,
>
> I'm not going to directly answer your question but I'm rat
I might have jumped the gun when talking about LESS, I'm not actually
familiar with it and thought it would be along the same lines like SASS.
But still you can't use SASS or Compass with JavaFX CSS.
Cheers,
On Thu, Aug 8, 2013 at 1:05 AM, Pedro Duque Vieira <
[email protected]> wrote:
>
> > So if you invent the same node-types you have on the web (lets face it
> there's only a handful of them most important are most likely div,span) and
> give them the same properties you know from the web you can copy your
> Web-CSS stylesheet to your FX-Application.
> +1 to this idea (in a 3rd
rogrammatic access from Java, which seems
> to be a highly requested feature.
>
> Regards,
> John
>
> -Original Message-
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Tom Schindl
> Sent: Wednesday, Aug
ndl
Sent: Wednesday, August 07, 2013 2:01 PM
To: [email protected]
Subject: Re: Proposal to move default style-class from Control to SkinBase
Oh and one more thing: IIRC you can run e.g. less in rhino so feeding it a less
file with -fx properties should get you css file which you can
Oh and one more thing: IIRC you can run e.g. less in rhino so feeding it
a less file with -fx properties should get you css file which you can
pass on to FX.
Tom
On 07.08.13 22:56, Tom Schindl wrote:
> If I get your complain right what you want has nothing to do with CSS
> but you are requesting
If I get your complain right what you want has nothing to do with CSS
but you are requesting that the complete FX API is remodeled, CSS is
simply a way to set properties of your Nodes in the SceneGraph, in a
none intrusive way.
You need to differiate between CSS as a language and the properties on
Hi David,
I'm not going to directly answer your question but I'm rather gonna touch
on a problem I see regarding JavaFX CSS. Forgive me for not directly
sticking to the subject of your email.
The issue I see is that JavaFX CSS significantly differs from W3C CSS, that
is the CSS that is used on th
Since day 1 of writing controls for JFX I've used the approach that a skin sets
its own style class, and that class is used in the CSS. If a control should not
be aware of how it is rendered, what sense does it make to have visual styling
set on it?
So in a skin I do: this.getStyleClass().add(
13 matches
Mail list logo
