i'm converting FXML to Type Safe Builders in the Todo app. I still have some FXML and css in there as well so maybe once i pull that out, scenic view will work

Yep. I've even tried just using the live stylesheet configuration option and it works fine.

I don't have any on hand that are a mix of builders and FXML/CSS to try though.

don't worry about it. i'm ripping out the rest of the FXML / CSS and will report back

Alright

while i have you...would i write something like this with an and()?

.content_box .button { -fx-background-color: none; }

or

.strikethrough .text { -fx-strikethrough: true; }

i'll use transparent instead of none like we discussed earlier

NVM, this is working for me content_box { button { backgroundColor += c("transparent") } }

Sorry, I got busy for a bit there.

and()

is for combining them, so

content_box {
    and(button) {
        backgroundColor += c("transparent")
    }
}

would become

/* No space, this applies to elements with both classes, not buttons inside content boxes */
.content_box.button {
    -fx-background-color: none;
}

Your example with nesting works, or you could use

content_box contains button { ... }

if you didn't want to nest your blocks.

@User uploaded a file: Untitled

becomes

@User uploaded a file: Untitled

@Ruckus THX. i re-implemented one of the two FXML files. if you're curious, this is my version of the todo app. It's fully functional. https://github.com/bekwam/todomvcFX/tree/master/examples/tornadofx

Those a/b rules would be a great reference table to put in the documentation. I don't see it in the CSS section of the PDF.

It's in the issue Edvin filed to get back to

It would be a good appendix if you think it would break up the flow of the CSS section

@Ruckus do you have any experience with edvin's fontawesome builders? it looks like they're in the controls-fx project

I don't. I've used fontawesome in my own projects in the past, but I did it directly.

It seems JavaFX doesn't like the next (

.a + .b

) and sibling (

.a ~ .b

) rules. I get warnings when I use them.

It would be nice if this was in the documentation somewhere.

@edvin I fixed fxlauncher the PR is green again, if you check it and find it ok, I think we are ready for release

@edvin @Ruckus Is there a capability to set a Type Safe CSS style based on an id? ex, set a style for #title NVM I found cssid() from code completion. Trying to link this up with an id assignment in the builders (Update: worked). This would be a good addition to the guide to follow the classes section.

@edvin Do you have a standard package structure for TornadoFX? I was looking in -samples and didn't see one. Maybe something like 'app', 'view', 'viewmodel', 'model'? 'controller' if needed

if you create a maven project with intellij you will see that @edvin has some structure there

@edvin has a jui jutsi camp this weekend, so I dont expect him to be online much