Redo iFrames with jinja templating #2
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The iFrames are clunky, hard to style, harder to link javascript to the other templates. Jinja blueprint tempalting should be used instead of this approach
I've worked on this but Only the basic layout is implemented. Right now the footer isn't rendered with a template anymore it's just in the app.html.
I think I can even go without the app html or the footer can be in the layout but only if I redo the rest of the components to be rendered on a template and make more blocks for those things. As it stands if I put the footer in the layout ALL components get the footer.
The problem is the breeds and stats are still not components, they are still shown with iFrames. So there is a need for an app.html that loads and shows them
I wonder if I can make the stats and breeds into templates themselvesThey are formatted properly already :)
i need to extend the other body parts from app to .layout and rename .layout to app and change the render template again.
ie I need components for the header, footer, dropdowns and iFrames. They should extend to what's currently .layout.html
Turns out these need their own render templates and routes as well... Which I would still be displaying with an iFrame. Still unsure if iFrame is the correct route for this...
For now I will keep using iframes to show the individual pages on the root screen. block templating has been implemented, and it's time to close this. api and app.py needs better structure.