Troy,
on Friday, February 3, 2006 at 04:30 Troy Brophy wrote:
Now, the wonderful thing about this app is that it has dozens of pages with
unique designs. Each of these unique designs requires many elements to be
positioned, floated, padded, margined, bordered or backgrounded uniquely.
This
Martin Heiden wrote:
If you have too many rules, you can add page level external css-files.
Personally, I cannot see the purpose in having page-level external files
in addition to shared group-wide or site-wide files, except for one
thing: media types. If you link to external style sheets you
I prefer having an [external] css file for each page because 1) VS.Net
[for some strange reason] gives me CSS IntelliSense and CSS designer
support when css is either in an inline-style tag or in a .css file but
*NOT* when the css is put into a style/style tag set in the HEAD of
a document. The
Sorry about the sensationalist subject line. I couldn't resist.
For the past six months I've been building a massive, consumer Web
application. I took over the development from a guy who was keen on
standards-compliant XHTML (yay!) and keeping every style rule in an external
CSS document (kinda
to open the HTML (actually .JSP) file, find the element in question, grab
the class name, then open the associated CSS doc, search for the class name
and finally make the change. (And of course, the requests are seldom so
simple, which means the fixes tend to involve a lot more scrolling
On 2/2/06, Troy Brophy [EMAIL PROTECTED] wrote:
This worked great up until I hit line 6000 of the
external CSS doc and Dreamweaver started choking a little each time I saved.
I'm surprised you waited so long!
Then I began grouping pages of the site into sections and creating CSS docs
for
