Topic: After all...

Self esteem is not about sitting on one's arse on top of "past achievements".
It's a constant movement forward - reinventing oneself matters to me.

As my home/toy site front page won't change much (except for the final radio interface tweaks), it's time
to get feedback from the best.

I have a problem with the size of the active hover area for the buttons, the click able area should only be the size of the text.

I've checked out the code and it's not difficult to fix.

Also if it wasn't for the splash page/portal you wouldn't know the three sites are connected, is this intentional?

Thanks, will rework.

www.mauro-colella.com should not link back to www.beyondwonderland.com
One is professional, the other is personal.
Personal visitors can go to the professional side of things, no prob, but the other way round, I'd rather not -
you never know how people react to "toys".

Cosa will migrate to the professional side of things, and it is a standalone platform for a web app.
Cosa may (should) echo the main (present) area, visually, while being distinct - that is right - and still possible.

I've fixed the image size, but I still refuse to use CSS matrix trick because of the very word "trick" : it may be elegant,
it may be supported for now in main browsers, I will adopt that 100% when the time is right.

Anyhow, if you still get 1 kilometer high images when rolling over my links, please clear your cache.

Cheers,
Argo

I still don't get why you refuse to use at least pure CSS hover effects and favor obsolete image swaps ( let alone with no preload ).

Also the markup could be a tad more semantic, and please don't autoplay the music


However the overall design if fine.

Thank you.

Because "c'est dans les vieilles marmites qu'on fait les meilleures soupes". No preload is nasty, agreed,
and the code could use some cleanup.
Finally, as soon as I am done blogging the madnesses of the weekend, I'll kick autoplay to the curb for you my friend.
---------------------------------------------------------------------------------
The CSS matrix thing IS slick, but when I disable CSS in my browser, the layout of my page "degrades" better (eg. images still appear)
when using plain old images, than it would do with a css matrix.

(Btw, it's great that we have so different points of view, more power to the community, we will explore our separate ways greatly and certainly for the best).
(You do a great job at defending your views, keep it up).

I have many things "against" what I consider excessive CSS, all arguable :
1) CSS is implemented differently in all browsers.
2) It's an added layer, so it's added complexity
(and risks for code issues - minor, granted, but see how painful it is to obtain some clean centering for one).
3) Some people disable it by conviction.
4) Some mobile devices implement it even differently than pc browsers.

All in all, I am very reluctant to using "more recent" css trickery - if it has not been proved to work in all the main browsers
for a year or so, I don't do it - whatever "it" is. Hope it answers some of your questions.

Skipping alt attributes was plain stupid and wrong, definitely - and the rabbit logo could, and will certainly benefit some tweaks.

?! Who disables their CSS by default? Where did you research this?

I'm not saying it would never happen, but let's be honest here, they're expecting a degraded experience aren't they, so why cater for them?

In general with CSS one should always be mindful of what issues there will be with the _likely_ devices it will be viewed on. But essentially valid CSS is always what should be put down first and the quirks should be dealt with after.

Most CSS trickery is just combinations of techniques that have been around for years, CSS image rollovers for one have always been possible since CSS 2.

Love a direct debate and direct communication.

quote:

---

?! Who disables their CSS by default? Where did you research this?

---

Some friends hell bent on security on simplicity (the kind of "I Linux because I am an elite (friggin' dork) who loves black text on a white background").

quote:

---

I'm not saying it would never happen, but let's be honest here, they're expecting a degraded experience aren't they, so why cater for them?

---

Excellent point.

quote:

---

In general with CSS one should always be mindful of what issues there will be with the _likely_ devices it will be viewed on.

---

_likely_ is the problem here. A rule of thumb in development is : "never assume your users will _likely_ do things you expected".
In real world, they NEVER EVER do, the very first days a new software is published, whatever it is, you'll see the bug reports AND hacks posted somewhere.
I treat webdesign as software design.

quote:

---

CSS image rollovers for one have always been possible since CSS 2.

---

My point here is the "stacking" of technologies, and of elements subject to evolution within a given technology (eg. evolving implementations
of CSS for a given browser). That's another development paradigm : "the more abstraction layers you had on top of a given functionality,
the more opportunities for (unexpected) failure(s). Reduce complexity to maximize robustness."

One thing you can easilly confirm with my previous works is that they are compatible with a broad range of platforms,
and that their structure resists time quite well.

It does because of rules like the above ones.

And a consultancy rule of thumb (or NLP principle) : "if what you are doing works, STICK TO IT. Do whatever it takes to get the job done."

My only *problem*so far has been the input of poi, you, a few others, which comes from a web designer perspective, and web designers
are not my clientele - but they are my best source for advice regarding web stuff.