Sandman
In article <4acf2296-2d0a-4ada-a056-a87459ff4db6@x25g2000prf.googlegroups.com>, Steve Carroll <fretwizz@comcast.net>wrote:

Steve Carroll
Anyone wanna take a stab at what caused this;)

Sandman
Fixed. My bad, actually :)

Thanks for pointing out an error on my page in a reasonable mannner that I could swiftly fix.

Steve Carroll
I did what any reasonable person would do (hehe;)

Sandman
Indeed you did. What you didn't do was say something like, I don't know:

"your code is pretty damned bad"

Or something like:

"Do you really call yourself a professional?"

Which had set the tone for your remark from the outset and could hardly had been called "reasonable" in any stretch of the imagination.

But then again, who would do something so stupid anyway? :)

Actually, the "system" (CMS) I'm using is called Atlas and is developed solely by me.

Steve Carroll
After having worked (interspersing my own php code, html, css, javascript) with things like Drupal, Wordpress, Joomla, etc. I can certainly see how errors can be tossed out. I can even see how difficult it would be to track them down depending on the error. This is *nothing* like creating a website from a Dreamweaver template or even making your own site from scratch using DW.

Sandman
Of course not. Any given page in Atlas takes CSS instructions from at least 10 different sources, depending on what application you're using. Not only that, with some applications, like the blog application, the users can define their own styles (through a web interface) to style their blog to some extent.

DreamWeaver really is a beginner tool for the newbie to easily create a basic web site. I would be the laugh of the industry if I made my clients web sites with DreamWeaver, and if that's not enough - my workload would not double, it would probably be fifty times higher, and my delivery rates would slow to a crawl so I couldn't invoice my clients in time for me to withdraw my paycheck and so on.

DreamWeaver is only viable if you have very few clients and they have very low standards and expectations on your work.

But hey, whatever kind of points you can score from having automatically validating CSS might be worth it :-D

Steve Carroll
It's hilarious to watch gluehead try to compare these two very different things... I'd like to see that idiot code up a CMS from scratch. He's even aware that you coded the CMS from scratch

Sandman
Indeed, during our "truce" which was quick to break he was given the option to ask questions which I answered (at least most) and those answers are totally forgotten by him now. I answered his questions as I would answer any question you would ask me.

This is the post: <http://groups.google.com/group/comp.sys.mac.advocacy/msg/8f02ba30f8107 47f>

As you can see, all of the points are answered politely and to the point. I tell him how the CSS is created and what kind of errors this could lead to. I also tell him that CSS validatin is of little concern to me (especially when compared to the amount of energy he puts into it).

Steve Carroll
yet, he's still trying to compare his errors to those generated by tons of code that generates markup, code he likely couldn't even recognize. Of course, he is an "IT teacher" so maybe he writes these kind of systems from the ground up all the time and never has any errors (yeah, right;)

Sandman
:)

That means that the CSS (for example) isn't contained as plain text in a text file, it's actually compiled from a number of sources, even database and sent to the browser, at which point errors could be made when parsing or rendering the data.

Steve Carroll
Ah... I've never done this as coming from a database... sounds interesting.

Sandman
It's really not. From the beginning it was a live fetch, meaning that the DB was accessed for each and every page request (hundreds of thousands per month) which was a performance nightmare. It's being cached now, but when the data comes from a DB, it's a lot harder to determine when to recreate the cache, and I am currently aggregating it at certain points (every five minutes) which means that there is a lag between editing the DB and seeing the result. With flat text files, you can always compare the file dates between the original and the cache and determine when to recreate.

But the functionality it provides is very nice for my clients, so I have to live with it.