I'm probably not looking to replicate todoist though. If there are other things you would like to see (even if they are "optional" features) we can discuss that.

Alright, I got an O'Reilly webcast in about an hour. I better get ready. Will talk later...

@thomasnield Thanks 🙂

@thomasnield Good luck

Interesting, Thomas. I bet a project like this would drive some new features for TornadoFX as well. I'm interested! @ron DagLayout work made me interested in that as well. I'm currently working on an automated Task system at work, it's becoming pretty advanced and utilizes Kotlin features quite heavily. We might even consolidate features from there as well.

@Ruckus thanks! @edvin awesome, let's talk about scoping and I'll check back later. I think I listed my requirements. If it's alright I might leverage Rx into this project, unless you'd prefer not to Edvin.

@thomasnield I'd prefer to leverage Rx, so I can get some experience with it!

Okay awesome!

The daglayout code is on GitHub

The algorithm is ok the FX part is not

@edvin question: for the GitHub sample app, did you manually type out all those styles or did you use some tool to convert the CSS?

@nakamin I did it manually. Wasn't much work though, when I had something to look at (ie. the existing design)

Oh OK

@nakamin That sample might use some outdated syntax, at least for the UI. I can check over it and get it up to speed soon.

Also, is it necessary to have the companion object with all the CSS classes?

@User uploaded a file:

@nakamin Custom CSS classes need to be defined somewhere, so that you can refer to them in the stylesheet selectors and also add them to the nodes in a type safe way. I can't see any way around that, can you?

It might seem like a chore, but it is actually a very, very good thing. It makes it possible to check where a style is used, or if it's used at all. You can even easily go from where you have applied the style to the selector. Quite handy IMO.

Maybe an annotation to generate this code? I don't know if that would work though

Yeah I guess you're right

@nakamin What would that annotation contain? And how would you apply the styleclasses in a type safe way if you don't have a constant to refer to? 🙂

We do support using strings as selectors, but that kind of defeat the purpose. I also thought that this was a chore at first, but I've come to like it, and see the value in it. You simply have to define them somewhere if you want type safety.

Yeah type safety is important

The type safe CSS fits very nicely together with the type safe builders 🙂

@nakamin I'll update the sample to TornadoFX 1.5.8 syntax and introduce injected ItemViewModels instead, much cleaner.

OK thanks Edvin 😀

My pleasure. Thanks for bringing it up, it's good to update those old samples to use all the new sexy syntax and tools we introduced 🙂

@nakamin The GitHub browser syntax and version is up to 1.5.8 standard now 🙂

Damn that was fast 🔥

He is too fast.... I often wonder when he sleeps or eats... 🙂