@User uploaded a file: Layout the overlay window and honor offsets calculated by drag

(

window

is actually a

BorderPane

, that's why it has a

top

property. I use it to contain the window top bar)

@User uploaded a file: Floating window feature and commented: Floating windows are opened inside an existing element. It can be just a node or a whole scene. It tries to be smart when the window is resized and looks for it's old position when the window grows again.

Wildly eventful day today. O'Reilly finalized approval for my "Reactive Python for Data" course. Then Packt Publishing reached out to me randomly. They want me to write a "Learning RxJava" book for them. I think I need to clone myself guys.

Wow, congrats on all the book writing success 🙂 Just don't burn yourself out on this!

Nothing is impossible with an espresso IV pumping into me. Haha but I gotta keep the momentum going, I may never get it again. TornadoFX, Rx, Kotlin, data science... they all are part of the big picture in what I want to push for.

This floating window... is awesome!!!!!

Thanks 🙂 It has a long way to go before it's complete, but I think it has some valid use cases.

Does it stay within the parent window I take it? And it doesn't create an extraneous icon?

This is something I've wanted for awhile, just never got around to ask for it.

That's correct. And you can actually choose if you want to to cover the parent window or just a specific node. That's what makes it a bit unique IMO.

@thomasnield good thing you're into kotlin https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-cloneable/clone.html

@carlw Python has always bothered me because its so wildly mutable. Even the types are mutable. You can add and remove methods at runtime. Kotlin and immutability, with some flexibility offered with data classes and

clone()

functions... it just makes sense from a tactical and maintainability perspective.

I have a brutal headache. Need some sleep 🙂 From tomorrow morning I'll be in Oslo until Sunday evening, but I'll try to work on this during the weekend.

@edvin feel better! I'm going to continue reading through the guide and make sure it's complete throughout the weekend.

Great Thomas! After this feature I will release 1.5.8 and only work on documentation and bug fixes. No new features. I (hope) I mean it this time!

Never say "no" to innovation

Nah, but people need to know about it for it to matter.

Indeed. What's the point of innovation if nobody knows about it.

We (you)'ve come so far with the guide, so I'm pretty sure we'll have it ready for christmas! hehe.. Good night 🙂

That is my timeline goal. Despite how fast the scope of it changed and the number of features that were added, we did a good job keeping it wrangled. Good night!

@edvin I was watching this video and thought of your floating window component. Their component can be seen around 0:40

@jchildress: Nice. I will try to make it styleable and subclassable as well so it can be tailored to fit any app design.

@edvin No pressure 🙂 Just thought of you when I saw that video...

@jchildress It should be as extensible as possible anyways, no problem 🙂

@edvin I have a bug report, a feature request and a call for help in one

I am trying to create a

combobox

with a custom cell factory

@User uploaded a file: Untitled

The catch is that the

ButtonCell

does not change with the

cellFactory

And the standard solution

comboBox.setButtonCell(cellFactory.call(null));

gives NPE