Rails spinoffs - Dec 2007 - Really simple history 0.6 & prototype 1.6

Hey guys,

I''m running the latest 1.6 final release.

I''m investigating rsh in my current ajax based application.
I''ve already got methods which get called to load listing pages/edit
pages
etc, so once I initialized rsh the prototype friendly way, i figured I just
put calls to dhtmlHistory.add in my code...
However, i''m noticing some really weird behaviour.
I don''t know if its prototype related, or rsh 0.6 related but this list
seemed like the best place to post first.
I''m seeing two errors in firefox error console - the first is on
pageload/unload. This is:

handler has no properties
prototype.js
line: 3846
When I take RSH related code out, I still get this - so for now, lets just
assume it''s some strange thing to do with another script i''m
including.

This aside, which seems to not stop RSH from starting up [the dhtmlHistory
object is available], is not actually what''s causing my problem-

When I make a call to the dhtmlHistory.add method, I get a similar error:

this.storageField has no properties
rsh.js
line 642

    loadHashTable: function() {
        if (!this.hashLoaded) {
            var serializedHashTable = this.storageField.value; //this line

From my quick read through the rsh source, it seems that this method is
responsible for ensuring the history hashTable is available, and i''m
starting to think that due to the handler error above, the hash table
isn''t
available- it could also be the scoping change in 1.6 where
''this'' is now
the element that created the event.

My understanding of this error is it occurs when an object is not available
and you try to access a property- Proving this, this.storageField is null,
which explains the error.

I am not sure if rsh 0.6 has been tested with prototype 1.6, I didn''t
read
anything on the google code page about it.
I was thinking about writing my own history implementation but after doing
some reading in the source, I''m not sure I want to even try!

So, it seems to me, that the handler error above, prevents some global
objects from being intialized in RSH- and i''m not sure where the fault
lies...

Can anyone provide any insight?

Gareth

--~--~---------~--~----~------------~-------~--~----~
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Gareth,

First error sounds like an Event.unloadCache issue when 3rd party
extensions try to use it for clearing observers on window''s unload
event (i.e. Control.Modal still suffers from it)
I''m not sure about the storageField one but I''ve heard about
RSH using
"for...in" effectively messing things up.
I think you''re better off asking this question on their list.

best,
kangax
--~--~---------~--~----~------------~-------~--~----~
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Thanks,

I found a reference to unloadCache in the lightbox implementation i''m
using-
and when I commented that line the handler error went away.. right
that''s
the prototype related error solved, I wasnt sure if it was causing the RSH
error but it seems it isn''t.
They don''t use for..in in their code, I just searched src files.. but
i''ll
post on their list and see what they say

Gareth


On Dec 6, 2007 6:58 PM, kangax
<kangax-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Gareth,
>
> First error sounds like an Event.unloadCache issue when 3rd party
> extensions try to use it for clearing observers on window''s unload
> event (i.e. Control.Modal still suffers from it)
> I''m not sure about the storageField one but I''ve heard
about RSH using
> "for...in" effectively messing things up.
> I think you''re better off asking this question on their list.
>
> best,
> kangax
> >
>
--~--~---------~--~----~------------~-------~--~----~
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---