Ah, that was the example I tried to use for the 2.2 branch, but didn't work.
Thanks!
On 2013-08-16 14:23, David Grieve wrote:
The changes are significant in that many of the class names were changed and
there were some other API changes. I was able to make a good number of changes
using perl substitution. But, other than how pseudo-class state is handled, the
model didn't change.
You might also want to look here -
https://wiki.openjdk.java.net/display/OpenJFX/CSS+API+to+support+custom+UI+Controls
On Aug 15, 2013, at 10:20 AM, Tom Eugelink <[email protected]> wrote:
No, this is still 2.2, since that is the production version of JFX. The user is
creating an actual production application with JFX.
My next step is to port this to 8.0. Are the changes major?
On 2013-08-15 16:16, David Grieve wrote:
I'm assuming this is 8.0? If so, what com.sun classes did you need to pull in
and why? I'd like to know from the perspective of the owner of the styleable
API. If you have to pull in com.sun, then I might have missed something
somewhere since all you should need is in the javafx.css package.
On Aug 15, 2013, at 9:16 AM, Tom Eugelink <[email protected]> wrote:
I've created my first control with custom CSS Styleable properties. Ignoring
the fact that com.sun classes are involved, it worked pretty easily. Jim
suggested that I also post the question about the CSS prefix I asked on the
JFXtras mail list here is well. So:
I would like to suggest is to use the "-fxx" prefix for JFXtras CSS properties,
so:
-fxx-arrow-direction:VERTICAL;
-fxx-arrow-position:LEADING;
If there is a good reason not to use "-fxx" I'd love to hear it.
Tom
