wrap a GUI Fragment object?

yem, in an FXEvent

because i wanted to decouple the small application parts from the main view

I need to be able to open tabs from everywhere in the application - so from any component I can fire an event via the EventBus

then the main view listens to that and adds the view to its tabpane

you can't fire an OPEN_WINDOW_X event and pass in the just the data on the Event bus?

yeah .... im rethinking this right now: Originally I tried exactly that

then I realized, that rather often I want to depend on the scope from the application part that wants to open the new tab

passing gui node objects sounds problematic because they can't be added twice to the same scene graph

so the event thing got complicated

the idea of the event bus is to decouple, but this sounds coupled

ah - im getting them with find and not attaching them anywhere - only the main view subscribes to them ...

initiators -- buttons, shortcuts -- pass around very general app events and leave it to other to interpret what to do with them

but you're right, thees nothing that really prevents another part of the application to do so too

you can show() a view, add a Fragment to a Tab, both, etc

yeah it is coupled in one direction: the part of the application that opend a certain tab has to know the tye of that tab

but I thoguht thats ok with me

i mean coupled in a runtime, javafx sense because the scene graphs could get tangled

back to the find() and parameter passing...say you have a Project File Browser. right click or select an item in the menu brings up Properties (they're equivalent). post a Open Properties event and then pass whatever the argument is...last selected item, current item. a subscribe receives that and builds the window, say a Fragment. then other properties can be shown

the key is that the parameter could come from a selected item in a tree view or a right-click on a tab pane. the action is de-coupled from the handling. that's scalable across a whole project

OK, but independently of at what point I do the find<> and pass the arguments to the Fragment, I still dont know, how i can at that point treat the 2 cases differently:

case 1. the window type is not already open - then just do a regular find<> using a scope with the appropriate parameters necessary passed via find

case 2.: the window type has already been opened (and the user has not decided to override the default behaviour of having just one instance of that window type)

then in case 2, I want to get a reference to the existing open window, and pass the parameters to it anyways.

And the windows should be able to decide, how to deal with them in that case

ideally

I'd like to have some abstract "CanBeAppendedTo" Fragment class that allows this behaviour

i would push the find to the location that's going to add the window. It's the initiator's job (keyboard shortcut, menu item, treeview select) to gather that event and data...probably best to pass some code around

the subscriber decides whether or not to open a window. the subscriber can also decide on getting parameter updates. maybe the window itself becomes a subscriber

Yeah ... I'm thinking i will do that