There exist many layouts schemes for dynamic web app frameworks.
Usually they involve a header, footer, navbar, and main content. What
practices are seaside users using to get this?
I'm just making one instance variable called 'main' in a "border" or
"framework" component, and populating it with whatever other component
is called for via some links in the navbar. "main" gets a blog
component if that's clicked, an "about us" static sort of component if
that's clicked, etc. "main" is rendered via "html render: main",
naturally.
Is this the emerging best practice?
Bill in Texas
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
