Cart
[Home] [By Thread] [By Date] [Recent Entries]
At 08:17 PM 9/22/2006, Alexander Johannesen wrote:
>The word "style" and its "meaning", I suppose. :) To me, style is
>presentation and as such only a part of an application of something.
>Links is more than presentation, they speak of things "larger" than
>that. That's all.
Yes, and it's a part of the application that's woefully unrepresented.
>>tricks? I'm willing to bet it's quite a few. An example: the Flickr
>>sidebar at http://www.shelter.nu/.
>
>Not sure I follow you here. What scripting tricks? What is the *trick*?
I mean this code on your site:
<script type="text/javascript"
src="http://www.flickr.com/badge_code_v2.gne?show_name=1&count=5&display=random&size=t&layout=v&source=user&user=93544306%40N00"></script>
How much work went into creating the Javascript to display
that sidebar? Wouldn't it have been much nicer to simply say:
<flickrBar userID="93544306" />
And have CSS do the rest by intelligent placing an embedded,
"onLoad" link?
><confused> Which part of "80/20 of linking" doesn't xhtml:href cover?
></confused>
Actuation and display of anything beyond single, unidirectional links.
Examples:
A menubar link - one click gives you multiple choices.
Sounds like a multi-ended resource to me!
A document compiled from multiple document fragments - like
what people are doing with inclusion scripts all over the place,
specifically in CMS applications.
Embedding dynamic content into a document - like your Flickr sidebar.
When we think of rendering links, we need to think beyond
"click and you go there," and we need to think beyond <a>. When
defining where the 80/20 is on links, we need to look at how
resources are being used today -- not how <a> links are being used,
but <img>, <object> and more to the point, the host of scripting
tricks commonly used on the Web.
--->Ben
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
