I go here so every now and then for a “relaxing treatment” http://www.kingsbarbers.nl/

they sharpen if needd

@ron About your issue: I'm making the

workspace.viewStack

property public, so you can actually manipulate it in

onUndock

its a “no women allowed” mens barber shop

why not a simple “removeOnUndock” ?

and not making the viewStack public?

My current solution which seems to work is:

@User uploaded a file: Untitled

Then we don't need anything special to support this. I don't know if it's a common pattern, so you might be the only one using that function.. hehe

and for that you make it public?

this does not feel good. opening the viewStack like that

OK, what about a half way approach then. Adding a function to remove something from the ViewStack?

let me think about a possible solution

leave it for now

OK

I think you should make the view stack public. There are a number of use cases I can think of (coming from android) where the developer will need some fine grained control over the view stack that we don't want to support every use case for.

That sounds like a good argument to keep it public. I was also thinking about something similar, and I think it'd be nice to let the user show the complete view stack as well.

Agreed

then go ahead and I will use it 🙂

Sweet!

I'll add it to the changelog and guide.

Speaking of which, how hard would it be to show a history drop down on right click? Like some web browsers do.

Is that a feature we should leave to the developer to implement?

I had that in my CRM app actually, but removed it because I didn't have a use for it. It's pretty easy to add though.

brb

@Ruckus How would the lifecycle of the history work? Say there's a stack of text documents in the history. Do you save a URL like set of parameters for the filename, etc that is consulted when brought into view?

@Ruckus sounds like an interesting feature

@carlw The view stack is a list of UI components, so you could just show a list of their titles.

brb

@Ruckus Maybe involve a scope so that you navigate through an object graph that might include other wired components like ViewModels? I think if you get something going like this for history, you might have some nice global actions that can be accessed from other places in the app like keyboard shortcuts