yep....this isn't a 100% fit, but this is what i've been reading up on...the WPF Page would be like a TornadoFX View

Looking them up and making them searchable automatically would require classpath scanning, or annotation processing. Annotation processing could be a possible way to go, but it's just not ready for Kotlin yet.

Checking.

The NavigationService might do the find() + openModal() based on this extra information

Understand. In any case, the only viable option right now is registering the data somehow IMO.

The metadata could be configured via annotation on the View, though. For later, it could be picked up when you compile with an annotation processor.

Or, like in pre-annotation days, supplement the View or add in a Navigable interface. There could be suitable defaults for the extra information like class name

That's (almost) another way to go. We could avoid the interface by using open vals, like the

root

val for example, but

open

instead of

abstract

.

The problem with this, is that we can't get to the data before a view is accessed, so it's a no go.

To make that work we would need to resort to classpath scanning.

Only if the NavigationService is configured for that app

And then we might as well use annotations.

Yes, that's right.

If we go with annotations, that means we can get rid of the classpath scanning again once KAPT is working.

(And keep the API)

Putting Alyssa to bed, back soon 🙂

@gtnarg It seems I had some more changes since your PR, so now it's in conflict. I think the easiest is if you pull and merge.

Let me know if you run into trouble.

@edvin - the conflict was the changelog entry which I manually resolved

@gtnarg Perfect, merged it now 🙂

@gtnarg Nice work. I'm glad you took care of backwards compatibility with the default implementation that throws an exception. 👏

thanks @edvin - I'm finding that actually contributing something is a great way to learn the framework (and kotlin) 🙂

@gtnarg Yeah, I've had the exact same experience. You have to dig a little deeper before submitting a PR, but it's always worth it. Thanks again 🙂

What's the simplest code for an app that has a text view that says "Hello" followed by whatever you input into a text field? Probably using data binding right?

I haven't tried, but I guess you could use a converter in your binding to do the concatenation of "Hello" and your entered text

@User uploaded a file: Untitled and commented: This works

even simpler, @Ruckus 🙂

use of the string formatting was clever

Technically this works too, though it's a bit of a hack: