thanks for the tweets @jchildress

thanks for the post 🙂 tweets are easy, posts are hard 😉

they're usually easy if you can get in the flow with some inspiration. if anyone wants to make a weekly submission to help with our new year's resolution for weekly tornadofx kotlin, chime in here. also any topic suggestions would help to keep the ideas flowing i'm going to keep going on this shape theme because I've had several clients have me implement these requirements

Off topic... I noticed a project "new" to me this week... early stages, but it's JavaFX/Kotlin and a map component...

@edvin Wondering, why did you decide to mimic InternalWindow as a Stage instead of extending it from Stage...

@abhinay I think because it was intended to be part of the existing Stage, not actually be a new Stage.

@carlw Nice work! Reading it now 🙂

@carlw @jchildress We could consider adding a new part to the guide, in a cookbook style format perhaps? That might be a good way to store these things in a less formal format so it's quick and easy to contribute.

@carlw The AnchorPaneConstraints object should have Number properties instead of Double, it's a hassle writing 0.0. Changing it 🙂

Any reference for the latest implementation of EventBus/ Event handling using tornadoFx ?

@edvin @carlw drag and drop for TilesFX is successful! All I have left is to figure out why animation isn't happening

@carlw in your blog/code, I noticed you added your inflightRect to the view of the class. Is that terribly important? I decided to have my inflightTile initialized once the tiles are picked up and then added (presumably to the root). I might try initializing in the view, then setting the tile settings later and redrawing.

@amanda.hinchman-dominguez uploaded a file:

I'll need to clean up event filters, animate the drag, and clean up the UI a bit, but I'll be leaving a public version of TilesFX drag-and-drop for anyone to use! I'll be moving the remainder of my project over to the company bitbucket.

how you build inflightRect isn't important. i pre-allocate a permanent one as a way to fend off NPEs. there will always be an inflightRect so anyone can move it or make it visible. there still needs to be logic around the inflightRect, but the stakes of an NPE are higher than an invisibleRect

event bus reference: https://edvin.gitbooks.io/tornadofx-guide/content/part2/EventBus.html

@carlw thanks for that 🙂

Just tried to implement a tray icon using TornadoFX and the UI is inconsistent in Ubuntu. The font and colors are very different. The left is the app implemented and the right is another native app (not sure if it's TornadoFX too). Is it the expected behavior?

@r4zzz4k commented on @Lucas’s file : Yes, this is expected behavior. TornadoFX currently uses AWT facilities for providing tray icon, and AWT's UX is based on custom rendering with minimum platform-specific stuff, so AWT UI is consistent between platforms but is not in line with UX of every platform. You can go with some library which uses platform-specific APIs like https://github.com/dorkbox/SystemTray (note that this one does some hacks with AWT stuff and doesn't play well with JDK 9, so you might search for other solutions).

@Lucas commented on @Lucas’s file : Got it. Thank you for the explanation and reference, @r4zzz4k.

of course, no trayicon chat would be complete without my favorite java bug...12 years and counting https://bugs.java.com/view_bug.do?bug_id=6453521

it's related to animating the trayicon which I don't care about. there is a deliberate line of code to transition through a gray background between each frame

Pretty incredible that they haven't squashed that one.

we talked about a cookbook style before

I was fighting with an itemviewmodel yesterday (sorted it this morning) because the current guide constantly assumes you are working on an item that comes from a tableview with a backing list

I needed to add a new entry:

@ron uploaded a file: Untitled

two things to note here and I think they should be in the guide: