I''m not even sure where to begin with debugging something like this. But I have an application that uses the Ajax.PeriodicalUpdater. It appears that if I leave the page open long enough, at a certain point the update refreshes without any of its css formatting (elements look garbled). Is this a known issue? ...or perhaps a browser issue? If it''s any help... Symfony Framework 1.0 PHP 5.2.1 Prototype 1.5.0 Camino Browser 1.0.3 Maybe someone can point me in the right direction for how to debug the Ajax stuff. Thanks, Doug --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Your best bet for debugging javascript is to use the Firebug extension for Firefox. I have no idea if Firefox extensions work in Camino ... they might since they''re both Mozilla products. But, Firebug can actually let you see and analyze the information that is being sent to and received from the server during Ajax calls. It''ll actually work with any javascript framework, too, not just prototype, since what it''s doing is watching the traffic over the XMLHttpRequest (XHR) object. Other than that, I''m not savvy with respect to the PeriodicalUpdater so I''ll leave that to someone else ;) -- Dash -- Trauma wrote:> I''m not even sure where to begin with debugging something like this. > But I have an application that uses the Ajax.PeriodicalUpdater. It > appears that if I leave the page open long enough, at a certain point > the update refreshes without any of its css formatting (elements look > garbled). Is this a known issue? ...or perhaps a browser issue? > > If it''s any help... > Symfony Framework 1.0 > PHP 5.2.1 > Prototype 1.5.0 > Camino Browser 1.0.3 > > Maybe someone can point me in the right direction for how to debug the > Ajax stuff. > > Thanks, > Doug > > > > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Hello,
If I create nested sortables, only the last sortable created (the one
most nested) seems to survive. I noticed the issue on upgrading one site
to scriptaculous 1.6.X - (and the latest beta)
----Detail Example----
I have an html <ul id="list1"> on which I create a sortable with
Sortable.create(''list1'').
Lets say that one of elements <li id="someImages"> inside list1
includes
three images that I was to make sortable using
Sortable.create(''someImages'',{tag:''img''}).
In this scenario, only the images will be sortable. If I comment out the
sortable.create on the images then the sortable list elements work fine.
---One Solution---
If you create the sortable from most to least nested then it works (i.e.
create the images sortable on ''someImages'' before that on
''list1''. But
in some situations this is a real pain to have to do.
Can anyone shed light on possible solutions?
Thanks,
pete.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
This is the only way, at least according to the Wiki. You can also make one big sortable out of the whole thing, using the tree parameter to make a nested list sortable en masse. Walter On Mar 27, 2007, at 7:31 PM, Peter Robertson wrote:> If you create the sortable from most to least nested then it works > (i.e. > create the images sortable on ''someImages'' before that on ''list1''. But > in some situations this is a real pain to have to do.--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Ahh.. I ran into this problem myself once but didn''t have time to
pursue it, and in that case neither the tree option nor the recreate
sortables bubbling upwards option would work.. This is quite an
annoying limitation, maybe I''ll try to fix it if I ever need sortables
really badly...<br>
<br>
Colin<br>
<br>
Walter Lee Davis wrote:
<blockquote
cite="mid:23d837e7a57868a1104de76132134cca-HQgmohHLjDZWk0Htik3J/w@public.gmane.org"
type="cite">
<pre wrap="">This is the only way, at least according to the
Wiki. You can also make
one big sortable out of the whole thing, using the tree parameter to
make a nested list sortable en masse.
Walter
On Mar 27, 2007, at 7:31 PM, Peter Robertson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">If you create the sortable from most to least
nested then it works
(i.e.
create the images sortable on ''someImages'' before that on
''list1''. But
in some situations this is a real pain to have to do.
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
--~--~---------~--~----~------------~-------~--~----~<br>
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group. <br> To post to this
group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <br> To
unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
<br> For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en <br>
-~----------~----~----~----~------~----~------~--~---<br>
</body>
</html>
<br>
Peter Robertson a écrit :> If you create the sortable from most to least nested then it works (i.e.You always need to do that when nesting draggables/sortables; this issue has surfaced several times in this list. This is fairly normal, as to implement d&d we need to convert a page position into an element, so when you have nested draggables (and sortables rely on draggables), you must create them from innermost to outermost: when going through the draggables queue, we''ll hit a match on the innermost first if the mouse is indeed over it. -- Christophe Porteneuve a.k.a. TDD "[They] did not know it was impossible, so they did it." --Mark Twain Email: tdd-x+CfDp/qHev2eFz/2MeuCQ@public.gmane.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Yes, I can see why it is needed in the code, however it just surprised me that it works if I use dragdrop.js from pre-1.6.x. It is a serious limitation in large nested trees where you don''t want to have to know what the lowest ''branch'' is before you begin. For example, I have one extremely large tree that uses lazy creation of sortables. In the current situation that can lead to unsortable-sortables (!) as you can''t ask a user to always make sure they sort there lowest nested items first ;-) It also seems clumsy to use compared with other scripaculous wizardry, because the user has to remember how to use it depending on the structure of the dom, rather than just using it and the draggables looking after themselves. The ''draggables queue'' is the problem here. Rather than ask a user to place items into the queue in the correct order, we probably need the order to be automated? Or for a different kind of storage. I also use behaviour classes from lowpro, which very efficiently applies by behaviors as soon as elements are available in the dom...which is inconsistent with the bottom-first requirement. Thanks for the feedback, Pete. Christophe Porteneuve wrote:> Peter Robertson a écrit : > >> If you create the sortable from most to least nested then it works (i.e. >> > > You always need to do that when nesting draggables/sortables; this issue > has surfaced several times in this list. > > This is fairly normal, as to implement d&d we need to convert a page > position into an element, so when you have nested draggables (and > sortables rely on draggables), you must create them from innermost to > outermost: when going through the draggables queue, we''ll hit a match on > the innermost first if the mouse is indeed over it. > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Firebug can capture XHR traffic, but Doug''s problems are related to the CSS/secondary stuff loaded by the browser as a consequence. You could try the Mozilla LiveHTTPHeaders extension, which will record all the traffic to a browser, and can save sessions to disk. (Fiddler does a similar job, and can intercept traffic from non-Moz browsers, but won''t run on a Mac unless you''ve got Parallels or VMWare, I guess.) Sounds like a browser issue rather than a Prototype one, as the PeriodicalUpdater will only fetch the content, and then hand off to the browser for any associated CSS, images, etc. Dave On Tuesday 27 March 2007 22:50, David Dashifen Kees wrote:> Your best bet for debugging javascript is to use the Firebug extension > for Firefox. I have no idea if Firefox extensions work in Camino ... > they might since they''re both Mozilla products. But, Firebug can > actually let you see and analyze the information that is being sent to > and received from the server during Ajax calls. It''ll actually work > with any javascript framework, too, not just prototype, since what it''s > doing is watching the traffic over the XMLHttpRequest (XHR) object. > > Other than that, I''m not savvy with respect to the PeriodicalUpdater so > I''ll leave that to someone else ;) > > -- Dash -- > > Trauma wrote: > > I''m not even sure where to begin with debugging something like this. > > But I have an application that uses the Ajax.PeriodicalUpdater. It > > appears that if I leave the page open long enough, at a certain point > > the update refreshes without any of its css formatting (elements look > > garbled). Is this a known issue? ...or perhaps a browser issue? > > > > If it''s any help... > > Symfony Framework 1.0 > > PHP 5.2.1 > > Prototype 1.5.0 > > Camino Browser 1.0.3 > > > > Maybe someone can point me in the right direction for how to debug the > > Ajax stuff. > > > > Thanks, > > Doug > > > > > -- > This email has been verified as Virus free > Virus Protection and more available at http://www.plus.net-- ---------------------- Author Ajax in Action http://manning.com/crane Ajax in Practice http://manning.com/crane2 Prototype & Scriptaculous in Action http://manning.com/crane3 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---