[jquery-dev] Re: AJAX bookmarks
Full Disclosure: I wrote one of the following browser history managers. In writing my own, I reviewed all of the existing implementations and found these to be the most stable (or actively maintained). JSSM is based upon the approach taken by RSH which has not been updated in a while. Eventually those two will be merged into a single project. dshistory: http://code.google.com/p/dshistory/ Really Simple History: http://code.google.com/p/reallysimplehistory/ JSSM: http://nathanhammond.com/jssm (demo: http://nathanhammond.com/jssmsource/test/) Klaus' (the one you found) hasn't been updated in quite the while if I recall correctly, so I don't know how it does with support on newer browsers. If you're looking for easy integration with jQuery, JSSM provides a plugin that makes it easy to attach handlers to links. Best of luck. On Nov 20, 4:41 am, Alexey [EMAIL PROTECTED] wrote: thanks to all i found some ready stuffhttp://www.stilbuero.de/jquery/history/#Chapter_1 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups jQuery Development group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~--~~~~--~~--~--~---
[jquery-dev] New History Manager - Finished(-ish)!
Okay, before it was just a teaser. Now you can have every bit of it.
Example: http://www.nathanhammond.com/jssm/test/
Source: http://www.nathanhammond.com/jssm/jquery.jssm.zip
The archive includes the absurdly well-documented JavaScript source
file, a plugin for jQuery to make it easy, the example site, and
assorted other goodies. Now that I'm done with it, I won't lie: this
is based on RSH, but intended to replace it--if for no other reason
than it being actively maintained. A later version will remove all
external library dependencies and provide a fully-functioning
JavaScript-library-independent history manager.
What I'm hoping for from this community:
- Somebody to come up with a real name for the project because I'm not
very clever at naming things.
- Somebody so inclined to give it the harshest code review in terms of
optimization, organization, and poor design you can come up with.
- A few good people to take it on a test drive in your favorite (or
not so favorite) browser. (And to let me know if it is broken
anywhere.)
Once I've got a real name for this thing, I'll find it a home on
Google Code, so that is probably the number one priority!
Enjoy! And please have a look!
Nathan Hammond
PS: If you're interested, I have a site that has a much better example
of this in action that I can send out privately.
On Aug 27, 12:27 am, Nathan Hammond [EMAIL PROTECTED] wrote:
I'm going to ask you to use your imagination:
Imagine an AJAX history manager that required absolutely no expertise
to use. Imagine something that could be applied to forms and anchors
to have them automatically be handled by AJAX and still maintain the
browser history (back button, and bookmarking). Imagine something that
works across all browsers supported by jQuery. Imagine something that
still works when JavaScript is disabled or can itself be disabled with
a single line of code. Imagine something that can be added to nearly
any existing static website as a non-intrusive upgrade. Imagine
something that is so stable you can use it on enterprise-level sites.
Imagine something with smart settings that can be easily customized so
you never have to get into the nitty-gritty. Imagine something that
provides callbacks at six separate stages during the AJAX loading
process to accommodate for animating transitions. Imagine something
that provides a page load callback for animating the initial page
load...
And then I'm going to tell you that you don't have to use your
imagination at all. The reason I've disappeared when I said I was
going to be around so much was to focus my efforts on this. To prove
how easy it is, here are two examples that show how easy it is:
$('a').('click');
$('form#someform').('submit');
I'll have an alpha version very soon--possibly tomorrow. I'd love some
help testing it and working out kinks. And if I missed any part of
your wishlist for the perfect history manager in the description, tell
me what else it should do.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
jQuery Development group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~--~~~~--~~--~--~---
[jquery-dev] Re: New History Manager - Finished(-ish)!
Nathan:
Thanks for having a look.
- To the name, I don't want to define it based on what else exists,
more on innate value. *shrug* Branding, again.
- To the idea of appending, if the elements are appended to the body
(document.body.appendChild(mytextarea);) after it has finished loading
the fields are not always repopulated (browser dependent). There are
two approaches to this task found in most history managers:
document.write(), or inclusion of the HTML in the page layout. I went
with the former specifically because I could control it to prevent it
from being executed twice (important where we'll want to allow entry
from any page on the site) and because it seems to be the more tried
and true method. I'm with you, I'd love to use DOM-only methods, but I
don't think that is possible. (Please feel free to prove me wrong.)
Again, thanks.
Nathan Hammond
On Sep 2, 7:44 pm, Nathan Bubna [EMAIL PROTECTED] wrote:
A.S.H. (Another Simple History)
So, why do you require the call to jssm.inline() to be done inline?
why not just append that html to the end of the body tag contents
instead of relying on document.write?
On Tue, Sep 2, 2008 at 4:26 PM, Nathan Hammond
[EMAIL PROTECTED] wrote:
Okay, before it was just a teaser. Now you can have every bit of it.
Example:http://www.nathanhammond.com/jssm/test/
Source:http://www.nathanhammond.com/jssm/jquery.jssm.zip
The archive includes the absurdly well-documented JavaScript source
file, a plugin for jQuery to make it easy, the example site, and
assorted other goodies. Now that I'm done with it, I won't lie: this
is based on RSH, but intended to replace it--if for no other reason
than it being actively maintained. A later version will remove all
external library dependencies and provide a fully-functioning
JavaScript-library-independent history manager.
What I'm hoping for from this community:
- Somebody to come up with a real name for the project because I'm not
very clever at naming things.
- Somebody so inclined to give it the harshest code review in terms of
optimization, organization, and poor design you can come up with.
- A few good people to take it on a test drive in your favorite (or
not so favorite) browser. (And to let me know if it is broken
anywhere.)
Once I've got a real name for this thing, I'll find it a home on
Google Code, so that is probably the number one priority!
Enjoy! And please have a look!
Nathan Hammond
PS: If you're interested, I have a site that has a much better example
of this in action that I can send out privately.
On Aug 27, 12:27 am, Nathan Hammond [EMAIL PROTECTED] wrote:
I'm going to ask you to use your imagination:
Imagine an AJAX history manager that required absolutely no expertise
to use. Imagine something that could be applied to forms and anchors
to have them automatically be handled by AJAX and still maintain the
browser history (back button, and bookmarking). Imagine something that
works across all browsers supported by jQuery. Imagine something that
still works when JavaScript is disabled or can itself be disabled with
a single line of code. Imagine something that can be added to nearly
any existing static website as a non-intrusive upgrade. Imagine
something that is so stable you can use it on enterprise-level sites.
Imagine something with smart settings that can be easily customized so
you never have to get into the nitty-gritty. Imagine something that
provides callbacks at six separate stages during the AJAX loading
process to accommodate for animating transitions. Imagine something
that provides a page load callback for animating the initial page
load...
And then I'm going to tell you that you don't have to use your
imagination at all. The reason I've disappeared when I said I was
going to be around so much was to focus my efforts on this. To prove
how easy it is, here are two examples that show how easy it is:
$('a').('click');
$('form#someform').('submit');
I'll have an alpha version very soon--possibly tomorrow. I'd love some
help testing it and working out kinks. And if I missed any part of
your wishlist for the perfect history manager in the description, tell
me what else it should do.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
jQuery Development group.
To post to this group, send email to jquery-dev@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~--~~~~--~~--~--~---
