I love the idea of having data tables on a separate screen.
This approach does the trick for the data base (thanks to @uat ) but this feature would also achieve this.
I pursue a structure something like this:
Main client-side app
Server-side app (with client-side Python modules that call server functions, therefore also a dependency. This allows for caching and keeps things clean).
App for custom components (dependency)
App for feature 1 (dependency)
App for feature 2 (dependency)
…
App for styling (no Python code, but with css-files brought into the other apps via Native Libraries)
App for db (a no-code app, only showing the db – shared with the other apps)
The “app for db” is really just to be able to have data tables open on a separate screen, so that I can see what’s going on in the db during testing (remember to refresh, e.g. by switch to another table and back to see any change between runs). In general, I find it easier to navigate my project when I can have each sub app open in a separate browser tab (or sometimes in VS Code, if only Python code).
Obviously you can extend the browser window across multiple screens but it is just not the same!
Great idea.
2 Likes