Routing and Layering

[zoomclub]

Using Z layers is an important feature in modern apps and a logical addition to routing, so that all aspects of layout (nesting and layers) are covered. Is it possible to add layers to components and manage them with react-router to complete all my design dreams?

[ryanflorence]

What is a "Z layer"?

[mjackson]

What is a "Z layer"?

I assume @zoomclub is talking about stacked views (think z-index).

@zoomclub What kinds of things would you want the router to do for you in this regard? Help me understand some use cases.

[zoomclub]

Yes, I meant stacking views using the z-index. My own use case requires several layers:

• background canvas, where accepted edits are rendered
• foreground tool picker, engaged when pointer is detected in specific location
• foreground sheet editor, used to browse and edit various app configs/prefs
• foreground tool editor, where the main editing tools are used
• foreground reporter, transparently displays dynamic info for tool operations

These are just layers, like interactive games or modern apps often have. There is an existing react-layers project (https://github.com/pieterv/react-layers), which makes a simple feature more complex than it need be. It would be best to bring everything under the one roof of react-router. After all layering is also routing, just on the z-index.

[ryanflorence]

Every child route view is going to be above the parent because when z-index is the same, the child element is "above" the parent.

How would the router help with this?

[mjackson]

@zoomclub I see, thanks for elaborating. This is really interesting.

@rpflorence Think of the "nested router" stuff you were talking about a while ago, for modals. That would solve the layering problem perfectly.

[ryanflorence]

but z-index doesn't matter, the child views will always be higher in the z-index "stack" because they are children, if you mount a sub-router on some top-level page, just make sure its later than the parent router's RouteHandlers in your render and it'll still be "higher".

I'll drop out of this thread for a bit, I've got some weird bias against it that I can't identify and I'll just end up killing would might be a great conversation :)

[zoomclub]

Agreed, z-index does not matter, just having Z layers does. Essentially, I'm hoping to use one robust solution for routing at the end of the day and confirm that such a robust solution exists.

So just be be clear, using react-router there can be one main route handler stacked with the layers described above. Each layer component can then also define its own sub route handler as required, which is active when a given layer out of the set of layers is activated? Layers would become activated by a pointer or qwerty trigger or automatically by some other function as desired.

As long as stacked layers in the main route handler can be switched (shown/hidden) along with the option to also have multiple layers showing we are good to go? When multiple layers are active the foremost layers could be made transparent as an option, which is not a direct react-router feature rather just an aspect of the given layer. If layered components can also be transitioned to with some fun animation I'll be content :)

If layered components are a breeze to accomplish with react-router then its a good thing to acknowledge and make note of in the documentation. Maybe a few handy layer friendly functions can be included and demonstrated?

[natew]

I'm attempting to solve this issue by using contexts outside of react router. So far it's working pretty well. Basically all your route handlers should have a mixin that sets a layer, but increments the layer once mounted. It's pretty easy to implement but I've run into some problems with getting the context to pass through RouteHandler.

Could be an issue on my end, or an implementation issue with contexts, but unfortunately it's a blocker for me. Definitely a wanted feature though. Once you start building complex UI's you need to manage a whole variety of z-index edge cases that don't just let you rely on the default layering.

See #549

[zoomclub]

Using the mixin sounds pretty slick. Looks like react-router is still growing rapidly.

[cmwelsh]

This seems like this is a duplicate of #266.

I currently have a UI like this that I'm rendering "manually":

http://instagram.com/github

Notice how the URL changes when you click a photo from the list and the details view is rendered in a modal. However, the background stays rendered as well.

[zoomclub]

The modal dialog and offcanvas approaches are both popular and represent ways of layering divs. This can work for some of what I'm going for but is not then an integrated solution for react-router.

I'm thinking more along the lines of defining react components for each class of editor used in the app. These components contain all their sub-components and react-router is the right solution for managing the layout within each of these editor class components.

Essentially, there are the bigger editor components then, with their inner sub-components that are reused and fed different state data per use case. An onboard react-router is perfect for managing the layout and morphing of the sub-components into alternate layouts within a given editor.

That part works fine. Now we want to work these component editors into layers. Maybe its just easier to create a simple var with an array of these editors and a function to hide, show, blend, send to back, bring to front the editors plus manage nice animations as the layers are transitioned?

It would be straightforward, basically having a stack of editors much like there is often a stack of canvases in drawing apps. I just thought this kind of functionality might go hand in hand with react-router? It would add a little Z dimension to what is now a flat X and Y router landscape.

[zoomclub]

Apparently I Inadvertently closed this issue, that was not the intent :)

[cmwelsh]

You probably clicked Comment and Close instead of Comment.