Design pattern for standard layout

Anvil Q&A
#1

Continuing the discussion from ImportError: no module named foo; AttributeError: 'module' object has no attribute 'bar':

@AWSOM this is the linked documentation and influences the standard design pattern I follow:
https://anvil.works/docs/client/navigation#replacing-just-the-main-content

Here’s my typical starting template with the material design theme

https://anvil.works/build#clone:YKZVIA3LQH3JRHDF=KSL2N7C4OVYJNE5OIAIWYJCF

user email and password are both empty

sidenote on hash routing

The above dependency includes HashRouting, which I use with all my projects now.

Without the dependency, use the standard

self.content_panel.clear()
self.content_panel.add_component(someForm())
# (I've put this in the comments)

Others will have varying standard design patterns they follow I’m sure…

2 Likes
Navigation Best Practices
#2

Niiiiice! Just what I was looking for thanks Stu…

1 Like
#3

Another example would be @bridget’s ticketing app - it’s awesome, very complete and will no doubt have some interesting design patterns and techniques to dig into:

https://anvil.works/learn/examples/ticketing-system

2 Likes
#4

Thanks for this! Very helpful.

1 Like