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 one can set on DOM/SceneGraph-Nodes. >From the selector point (language) of view FX-CSS support all important selector types, but because the nodes in the DOM (=SceneGraph in FX) are different you have other properties. 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. Tom On 07.08.13 22:41, Pedro Duque Vieira wrote: > 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 the web. > I've already touch this subject before but didn't have much answer from > this mailing list. The reason why I bring it back again is that the more I > do web development the more this seems unappropriated. > > Having JavaFX CSS differ from W3C CSS has the following disadvantages: > > - Designers coming from web development (they are the majority) will > struggle with JavaFX CSS > - Cannot use CSS pre-processors like SASS, LESS, Compass thus missing > out on this tooling that significantly enhances CSS. You can do really cool > stuff with Compass. > - Cannot reuse what already is out there on the web. And there are a > huge amount of examples there. > - Re-inventing the wheel. My personal opinion is that you should try to > harness the work that already exists especially when you have few > resources. People have already spent some time on this, tested and fixed > issues with it. So why not "stand on the shoulder of giants". > > I'm not saying you should introduce CSS layout, that is a headache and a > problem that they're trying to solve in CSS3, but all the rest can be > changed to be the same as CSS. You can even have both working side by side, > the current JavaFX CSS and a newer more W3C conforming CSS so that you > don't break existing apps. > > I don't see any advantage of having a CSS different from W3C one, if I was > going to make one different I would have created a newer more simpler > language to express an apps appearance. Not used CSS. > > Thanks, best regards, > > >
