a Traditional Website Structure Using
Coc oon?
Gary:
I've not considered CSS for layout since I'm comfortable with
tables...but I'm open to hearing if there is a better way to layout
header/footer/nav/body in a way that is consistently handled by most
browsers.
David
--- Schultz, Gary - COMM [EMAIL
Gary:
I've not considered CSS for layout since I'm comfortable with
tables...but I'm open to hearing if there is a better way to layout
header/footer/nav/body in a way that is consistently handled by most
browsers.
David
--- Schultz, Gary - COMM [EMAIL PROTECTED] wrote:
Have you considered
Have you considered cascading style sheets (css) for layout instead of
tables. I'm using that for my web sites and I think it tends to simplify
things. Use Cocoon to build the html element structure and css to layout the
web page. This way you do not have to worry about getting the different
parts
I have found that supporting multiple browser is a nightmare when using
CSS. You need to have the test results of all supported browser at hand,
or you will forget something.
If you test on Mozilla, you will be shocked when viewing the results
on IE6, if you develop for IE6 you get problems with
I forgot to mention something.
If I use xsp to generate my xml tree, I use xsl to format
it. It's easy and clear, and it allows you to include or
import other xsl template files. (Each more complex table
type it's own xsl file so it's easier to keep an overview).
If I use JavaScript or Java to
PROTECTED]
Subject: Re: Best Way to Build a Traditional Website Structure Using
Coc oon?
I have found that supporting multiple browser is a nightmare when using
CSS. You need to have the test results of all supported browser at hand,
or you will forget something.
If you test on Mozilla, you
You can use the DOCTYPE switch in the HTML to bring internet explorer
and mozilla browsers together when using CSS positioning, our intranet
site supports IE, Mozilla and Firefox using only one stylesheet.
For details try:
http://gutfeldt.ch/matthias/articles/doctypeswitch.html
If you are in a
What we do is aggregate all the disparate XML parts, including the dynamic
XML generated by the business tier objects, and then process that in one
call to the xslt transformer. The stylesheet invoked is a master that
imports other stylesheets to deal with processing the nav, headers, footers,
Interesting. Our sitemap funnels most everything through this pipeline.
map:match pattern=layout/**
map:act type=auth-protect
map:parameter name=handler value=authenticate/
map:aggregate element=results
map:part element=content src=cocoon://base/{../1}/
map:part
