(That, unless I’ve missed something)

Chris Boulton said:Do you mean the notification plugin so people get notified whenever I make a new post? Or the one when comments are made? I have the one when comments are made, and I always presumed most people use RSS anyway

I dont use RSS ¬¬
And yes i meant the new post notification. I already use the new reply notification when ever i feel the need

lou_habs said:
Love the new design. Too bad you don’t post too often, and I must agree with Ja, your messenger plus! toolbar is getting lonely over there:P You should put the source of it so people could make their own (a)

Well people shouldnt make it their “own” but should be able to use it and mod it a bit as per their needs as long as they do not claim it to be their own theme.
And i wasnt talking about this theme lou, i was talking about the other ‘concept themes‘ that chris makes (well he makes only half of it) and then abandons it cause he gets bored. With a bit more effort put into it he could release the theme for other less talented desingers. (Not me …. i aint talented at all so i stand in a totally different group :P)

Btw, this quick quote plugin is really good. Good work

Chris

Fixed pixel font sizes aren’t very Web 2.0.

Pixel based font sizing is about ensuring your site appears correctly, especially in different operating systems which have different fonts and default sizes. It also ensures it appears correctly in browsers where the user has the text size set differently.

Don’t be fooled though, any standards compliant browser will still allow you to change the text size despite using fixed height fonts. Internet Explorer is a bad example of this, as it will not allow the text to be resized.

Sort of related to this is that browser incompatibility isn’t very Web 2.0. Web 2.0 is about accessibility, and it’s neither the user’s fault for using IE nor IE’s fault for not violating your CSS’s instructions.

My site appears correctly in Internet Explorer, and functions correctly too. “Web 2.0″ is about accessibility, yes, standards compliance, and enhancing the end user experience. As my site appears fine, I don’t know what your gripes are about there.

Related to this… googlebombing Too Cool For Internet Explorer just isn’t cool. At all.

It isn’t Google bombing. It was designed to show a “too cool for IE” logo which I had in my previous prototype, however haven’t bothered as of yet to move to this one because I don’t know where to put it. I simply set it as display: none; for now until I fix that.

Fluid width pages are cool; fluid width block text articles aren’t. It’s like we went backwards from the time when even pages weren’t formatted (some subsets of the web still don’t bother) and flowing prose was wrapped only by the edge of the browser window. People need short lines to follow what they’re reading better. At my screen resolution of 1280×1024 it’s pushing it.

The page is set to a maximum width of 90em. This means the page will stretch out to that width, and then it will become fixed at that width. It isn’t a totally liquid design, it is semi-liquid.

Web standards are also Web 2.0

I’m not sure about you, but i’m over this whole “buzzword” Web 2.0 thing, which is why I italised it and trid to mention it as many times as I could when I was writing my post.

You need to escape forwardslashes in javascript quotes when they follow a > you need to close the input tag for the Subscribe checkbox; etc already reserves the anchor, and as they’re in the same place has the same functionality.

Yes, I know that, and yes I know that the pages don’t all validate.

Why do I not care? Validation is nice, but validation is not everything. I’ll fix it whenever I have time.

While very cool, the ajax jobby doesn’t update the “you must be new” once I’ve told it who I am and submitted my comment. It doesn’t seem right. If you have to do everything without loading the page you have to make sure that the whole page is up to date.
Edit

That is one minor thing that may need fixing - but at the moment it isn’t a priority. I was aware of this “issue” already.

It is sort of intended too, that after you post a comment, you’ll leave the page so the next time you view one of those pages, it will be different.

Fixed pixel font sizes aren’t very Web 2.0.
Sort of related to this is that browser incompatibility isn’t very Web 2.0. Web 2.0 is about accessibility, and it’s neither the user’s fault for using IE nor IE’s fault for not violating your CSS’s instructions.
Related to this… googlebombing Too Cool For Internet Explorer just isn’t cool. At all.
Fluid width pages are cool; fluid width block text articles aren’t. It’s like we went backwards from the time when even pages weren’t formatted (some subsets of the web still don’t bother) and flowing prose was wrapped only by the edge of the browser window. People need short lines to follow what they’re reading better. At my screen resolution of 1280×1024 it’s pushing it.
Web standards are also Web 2.0 You need to escape forwardslashes in javascript quotes when they follow a <; you need to close the input tag for the Subscribe checkbox; <a name=”comments”> is redundant - the <div id=”comments”> already reserves the anchor, and as they’re in the same place has the same functionality.