Hi guys, As probably most of you guys know, Dash app scripts, especially with callbacks involved can get a bit messy. I wanted to compartmentalize things into modules, but it still is a bit hard to get right. My current solution looks somewhat like this: [image] dash_project_layout · ma…

For multipage apps, I typically structure my projects in a similar way to the first project layout described in the section Structuring a Multi-Page App of the Dash Docs . This means just having a simple layout attribute in each page module containing that pages layout, and having the router register…

Thanks for sharing! The main difference I see is that your setup always assumes the same “app” is used and layout elements’ callbacks are in that sense more or less tied to that app. The multipage-ness is cool though! Never quite used that, yet.

I’m not sure I agree with that suggested limitation. Provided that you take care to namespace your component IDs, I don’t actually think there’s anything stopping you from organising your code into a library of different pages that contain separate pairings of layout+callbacks. You could then have …

If I understand correctly, you import the Dash app instance from ..app import app in every layout Python module directly, binding your callbacks right in the layout module, too. This would make using the same layout components (and callbacks) in a completely different app more difficult (say externa…

Ah yes, that’s true. There’s ways around that; although I haven’t yet come up with a super elegant solution, so haven’t included it in Slapdash. At the end of the day you do need to make some kind of assumption about where the Dash instance is going to come. The approach in those pages in Slapdash i…

Do you have a working solution for this? I was just trying out the current_app thing myself and ran into… problems. Mainly that Dash doesn’t expose this proxy, even though it’s basically an extension of flask. What makes this a problem is that it really clutters architecture having to pass the app o…

Ways to compartmentalize Dash apps

Dash Python

nedned October 1, 2019, 3:02am 8

Yeah, having to pass around the app object makes the architecture more challenging for sure. This is some related discussion about this general topic over at https://github.com/plotly/dash/issues/637.

Topic		Replies	Views
Best choice to work with multi-pages or layouts etc Dash Python tips-and-tricks , question	2	191	November 15, 2024
Splitting callback definitions in multiple files Dash Python	7	15337	September 15, 2020
How do you structure larger applications? Dash Python	3	1870	January 26, 2022
Structure complex multipage app and separate callbacks and components Dash Python question	0	407	April 14, 2023
Dash callback in a separate file Dash Python	24	31672	October 17, 2024

Ways to compartmentalize Dash apps

Related topics