Always, always, always remember that this is the Real world(tm).

If you need to spend hours for finding a workaround for something  
that works fine using "proprietary" stuff, it may be because the  
standards are wrong or broken. Keep it mind mind that a browser is  
there to display a workable interface to the user, not to test if  
standards are correctly followed. ;)

The bookmarklets are a really nice example of where creative use of  
something that's not really standardized but available in most  
browsers totally adds value for the user.
Standards will eventually follow what is used in real-life  
applications, but will always be a few years behind (Ajax, anyone?).

Be pragmatic, use what works. :)

Best,
Thomas

Am 12.02.2007 um 13:45 schrieb Christophe Porteneuve:

>
> Hey Thomas,
>
> Thomas Fuchs a écrit :
>>> Nor do I know of a single use case that cannot be better
>>> addressed through W3C-compliant techniques, instead of using URLs
>>> for a purpose that was never their concern.
>>
>> There is the use case of  Bookmarklets, which rely heavily on the
>> javascript:... syntax.
>
> D'oh!!
>
> /me hides in dark corner
>
> However, bmklets are for use in, well, bookmarks.  Not in a web page's
> markup (mmm'kay, sort of grasping dead branches to arrest the fall  
> here).
>
> -- 
> Christophe Porteneuve aka TDD
> [EMAIL PROTECTED]
>
> >

--
Thomas Fuchs
wollzelle

http://www.wollzelle.com

questentier on AIM
madrobby on irc.freenode.net

http://www.fluxiom.com :: online digital asset management
http://script.aculo.us :: Web 2.0 JavaScript
http://mir.aculo.us :: Where no web developer has gone before





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to