On 2/27/07, Colin Mollenhour <[EMAIL PROTECTED]> wrote: Hi, thanks for your extensive response!
> I think you should try to design this system more in javascript and less > in HTML. Yes, I suppose you're right. I have everything working quite nicely with Rails, but it uses a more direct, brutal 'replace everything and set up new drag/drops' each time, which isn't taking full advantage of JS. > I.e. Store your draggables in a cache somewhere and add and > remove them via pure JS, not using embedded script tags. > This may not do *exaclty* what you're trying to do but it is a (very > good) start: It is indeed - thanks! > There are likely some bugs in that code as I typed it all into > Thunderbird just now ;) > Using something like this to handle all of your draggable > creation/destruction will make things much easier, not to mention this > actually does proper cleanup whereas before your were leaking memory > each time you created a new one over the top of an old one. I'm curious about the 'leaking memory' thing... isn't this stuff GC'ed? Or are FF and IE bad at that? I'm pretty used to dynamic languages just taking care of stuff when it's not referenced by anything else. Just out of curiousity, does anyone know what the limitations are in IE that are causing the original problem I mentioned? Thankyou, -- David N. Welton - http://www.dedasys.com/davidw/ Linux, Open Source Consulting - http://www.dedasys.com/ --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
