[Rails-spinoffs] Re: scriptaculous, AJAX and search engines

2006-10-08 Thread Thomas Fuchs


Am 08.10.2006 um 00:44 schrieb Michael:

 And the Ajax.Update() thing should be pseudo code. Sorry for the lack
 of clarity. It should be the scriptaculous function Ajax.Updater(),
 see:

   http://wiki.script.aculo.us/scriptaculous/show/Ajax.Updater


Just for clarification, Ajax.Updater is class in Prototype, not  
script.aculo.us
(which is an add-on to Prototype).

Best,
Thomas

--~--~-~--~~~---~--~~
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 rubyonrails-spinoffs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-spinoffs
-~--~~~~--~~--~--~---



[Rails-spinoffs] Re: scriptaculous, AJAX and search engines

2006-10-07 Thread Michael

The single = sign: oops, sorry - you're quite right. Should one of the
following:

if (ajaxSupport == true) {}
if (ajaxSupport) {}
if (Ajax.getTransport()) {}

And the Ajax.Update() thing should be pseudo code. Sorry for the lack
of clarity. It should be the scriptaculous function Ajax.Updater(),
see:

http://wiki.script.aculo.us/scriptaculous/show/Ajax.Updater

Let me describe my idea in another way: on the first page there's a
div-tag with the id=searchengines. This div contains the content
of all pages (very small web-site) or static links to the pages (a kind
of link-list). Furthermore the first page contains the JavaScript part
to check if the current client has AJAX capability. If AJAX is not
supported (ajaxSupport==false) or the JavaScript is not executed (e.g.
the client is a search engine), there is just the start page with the
static links (for human-visitors AND for search engines).

If the client has AJAX capability the content of the div-tag
(id=searchengines) is cleared (or its visibility is hidden) and the
page is updated by Ajax.Updater(...) with content of the second page
(e.g. the first static link on the link-list).

Conclusion: a modern web-browser with AJAX support doesn't see the
content of the div-tag because it's cleared as soon as possible and
the page-content is updated with the second page. A search engine or a
very old browser without AJAX support sees the div-tag with links to
the pages (and may follow them). These are the same pages as updated by
AJAX - but more static... you know?


--~--~-~--~~~---~--~~
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 rubyonrails-spinoffs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-spinoffs
-~--~~~~--~~--~--~---



[Rails-spinoffs] Re: scriptaculous, AJAX and search engines

2006-10-04 Thread Christophe Porteneuve aka TDD



Michael a écrit :
 var ajaxSupport = (Ajax.getTransport()) ? true : false;

a.k.a. var ajaxSupport = !!Ajax.getTransport();

 if (ajaxSupport = true) {

Ahem.  With a single = sign, you'll reassign ajaxSupport, and therefore
ensure it's true.  Beware!  This is why I always put rvalues on the left
side:

if (3 == myVar)

Also, this code is redundant.  It could as well be:

if (ajaxSupport)

 new Element.update('searchengines', '');
 window.setTimeout('Ajax.Update(\'human_page\')', 500);

What is this Ajax.Update thing?

-- 
Christophe Porteneuve aka TDD
[EMAIL PROTECTED]

--~--~-~--~~~---~--~~
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 rubyonrails-spinoffs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-spinoffs
-~--~~~~--~~--~--~---



[Rails-spinoffs] Re: scriptaculous, AJAX and search engines

2006-10-04 Thread Christophe Porteneuve aka TDD

Hello Tobie,

Tobie Langel a écrit :
 Your website might get banned by Google:
 
 http://ma.gnolia.com/people/tobie/bookmarks/scoscuste

This is wonderful FUD.  I see nothing whatsoever on the Google
guidelines referred to by this article, that says anything about
banning.  Especially since Google *is* pretty smart about AJAXy pages.
After all, they use the technology all over the map.

So, what exactly did you mean by that?  What info did you allude to?

-- 
Christophe Porteneuve aka TDD
[EMAIL PROTECTED]

--~--~-~--~~~---~--~~
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 rubyonrails-spinoffs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-spinoffs
-~--~~~~--~~--~--~---