Here's a minor nit that's been bugging me for a while.
On many applications I have an app navigation to switch between modes.
I found my designer was repeating entire templates because he wanted to
"distinguish" the mode you were in (highlight, bold, whatever).
After thwaping him and teaching him how to include common content in a
template, I found that we now tedn to have a lot of templates like this
(psuedo'ed to be template system neutral)
Navoption1
Navoption2
Selected Navoption3
Navoption4
include contenttemplate2
Which content template was included, and which nav option was selected
would vary, of course.
The problem with this solution is two-fold:
* Nav options are repeated in every template, which means they all have
to be edited when options change.
* Actual content is not in the "main" template used by my run mode.
So I tried to move to include a Nav template. For that to work,
however, I need to make my run_mode visible to my template, which bugs
me in some way. The template shouldn't care. But then, the template
has to know the OTHER run modes to send you there, so I guess it's not a
big deal, but it does bug me.
The other remaining issue is that even in that case the navigation
template is ugly. A bunch of IF/ELSEs and bolding or alternate CSS ids.
Not very readable, which means less maintainable.
I'm assuming this is an issue others have encountered before. How do
you handle navigation templates?
--
SwiftOne / Brett Sanger
suppressed
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.