For graceful degradation, you should really do:
<a href="/guestbook/view" id="guestbook">
Then in your javascript, at the end do return false; That way, if the
user does not have JavaScript, they can still access the page!
Tane
On 3/13/07, Kjell Bublitz <[EMAIL PROTECTED]> wrote:
>
> Whoops.. of course it should read:
> <a href="#" id="guestbook">Guestbook</a>
>
> On 3/13/07, Kjell Bublitz <[EMAIL PROTECTED]> wrote:
> > From my perspective, the whole Ajax Helper (may it be for Prototype or
> > jQuery) is not an option for an application that seeks a serious
> > implementation. I know that this helper aims at people who don't know
> > javascript, but such people should ask themselves why they try to use
> > something they do not understand. On the other hand.. if they do know
> > javascript and even better the libraries behind this helper, they
> > would rather choose to make up their own external js-file and start
> > from the scratch in a way that is unobstrusive. I think the whole idea
> > or functionality of this helper needs to be reconsidered. The attempt
> > to control an entire library and in fact the complete javascript via
> > array-keys is madness. But that's another story.
> >
> > Going from this point you should not ask yourself how you can
> > implement jQuery using a helper. You should ask yourself how to get
> > your scriptfile into your view and how to tell jQuery to interact with
> > your interface. If the helper does not work for you, leave it alone
> > and go for a jQuery tutorial. It is not that hard.
> >
> > <a href="#guestbook">Guestbook</a>
> >
> > Then in some Javascript File:
> >
> > $(function() {
> > $('#guestbook').click(function() {
> > $('#spinning_image').ajaxStart(function() {
> > $(this).show();
> > $('#content').hide();
> > }).ajaxStop(function() {
> > $(this).hide();
> > $('#content').hide();
> > });
> > $('#content').load('/ajaxpages/guestbook/');
> > }
> > });
> >
> > This code is untested, but should do the trick. I must add that i am
> > not a jQuery guy. I abondend it for some reasons that relate to their
> > Ajax implementation. I myself love prototype and it's readability.
> >
> > My lead is to avoid those crazy javascript helpers. You are better off
> > by learning the basics of each library, add their functions the way it
> > is ment to be and then choose the one that works best for you. It is
> > fun and worth it. I would not choose a javascript library based on
> > helpers that are available
> >
> > I hope this helps.
> >
> > On 3/13/07, Sam Sherlock <[EMAIL PROTECTED]> wrote:
> > > I have amended the todo list to use jquery instead of prototype
> > >
> > > http://grahambird.co.uk/cake/tutorials/ajax.php
> > >
> > > as abba bryant mentions I just took out the onclicks etc and wrote
> > > jquery routines to unobtrusively bind the events to the elements. Was
> > > really simple too!
> > >
> > > I plan on extending it a little soon.
> > >
> > > - S
> > >
> > >
> > >
> > > On 12/03/07, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote:
> > > >
> > > >
> > > > > 2. When will CakePHP have a jQuery helper?
> > > > yeh its good sugestion !
> > > >
> > > >
> > > >
> > >
> > >
> > > > >
> > >
> >
> >
> >
> > --
> > Regards, Kjell
> > www.m3nt0r.de
> >
>
>
> --
> Regards, Kjell
> www.m3nt0r.de
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
