@carlw Nice! If you have time, can you describe it in an issue perhaps?

I'll post it. It'll be vague, I'm still coding the navigation piecemeal (ex, open stage is different than transition w/i a scene). But this is needed for the "rules" surrounding the pre-actions which is what the SO person seems to be asking about.

@ron Yeah, nailed the torture actually! I don't think there was a width property like you describe, but I couldn't even think of a use cases that wasn't covered with the options I created, so if you tell me what you want to do for the different columns I can try to describe how it can be done (I might need to read up on it, haven't done UI programming in a little while)

#214 Navigation Service

@edvin I sorted it for now with pctWidth

@ron OK! There are also weights which works roughly the same way.

I know they were in Swing too, never got the hang of them

It's also possible to use the pref width as the min width, that might be what you need in that other case.

percentages I get

I just made a comment on @carlw's Navigation Service issue - maybe we should support parameters for Views and Fragments? I.e when you inject or find a fragment, you could be allowed to pass some parameters as well, making it super easy to for example open and editor and supply it with the customer id you want it to display?

Each UI component could simply get a key/value store of properties it can use as it sees fit?

I was thinking about that

I am working with an accordion at the moment and each fold is a seperate view

so all views need to inject controller to get to the model

This map could even be mutable, making it super convenient to use for message passing.

That worked pretty well 🙂

A View wants to use a Fragment and also pass along some data the fragment can use:

@User uploaded a file: Untitled

The fragment can now extract the

items

parameter from the

params

property:

@User uploaded a file: Untitled

Pretty easy and straight forward. Not type safe, so not for everyone, but I think beginners will enjoy this one.

It also works with

inject

@edvin - can explain this statement

val params = "items" to listOf(SomeItem("Item A"), SomeItem("Item B")).observable()

- the

"items" to

is not familiar

@gtnarg

x to y

is the same as

Pair(x, y)

. Pair is a Tuple. So you basically send in one or more tuples of parameters, and it gets converted to a Map.

You can write

val params = Pair("items", listOf(..))

instead 🙂

thanks - great answer on SO btw...

I sexied it up a little, so now you can write:

val items: ObservableList<SomeItem> by param()

(Updating the example and SO)

For the Navigations object...I think a user-defined parameter is a good idea that supports a master/details pattern. Maybe something like this? Navigations.goto( ContactsView::class ) --> opens a Stage showing the ContactsView Navigations.goto( ContactFragment::class, 101L ) --> replaceWith() to a Fragment with a paraneter

This would be a level of abstraction up from the Transitions, similar to the SlideShow

But I think also mixing the Stage operations with some of the things that @Ruckus was doing would help developers who just want to go from screen-to-screen consistently