On Monday, Mar 3, 2003, at 09:38 US/Pacific, Maureen E Fischer wrote: [..]
[..]My Hesitation is that I wrote the system without this in Mind.
I was afraid you would notice that.
the two crucial places you will need to think your way through the frame problem is
a. <a href="...." target="foo">
b. <form .... target="foo">most people do not think about why the target attribute is there to begin with and this is a part of the why.
What can help is if you 'story board' the flow - so you know where things are suppose to be landing. Fortunately ruth worked much of that out, and it was up to me to make the static html mock up actually become dynamic, do the queries, resolve incoming queries, and make sure that the 'output' went where it was suppose to go.
What I finally did was flat out CHEAT
Wetware::Hq::Web::Page
became a module with our basic 'pages' - one of which I showed which is how we lay out the basics at the index.cgi level - there are also methods for making a vertical Navigation page - and the other basic framework for each type of page so that all of the basic 'look and feel' is all managed in one place.
This of course lead to
Wetware::Hq::Web::Page::<specificPageStuff>
These are basically how to cache that we have these specific types of arguments and stuff....
Remember that SSI's can help in a bunch of other ways as long as your client does not have a 'specific look' that requires that things lay out in a given manner.
ciao drieux
---
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
