Hello all, I am working on a web application that uses the Prototype "1.5.0_rc0", I want to upgrade to "1.6" I don''t know if "1.6" is backward compatible or if upgrading will make problems in the pages that uses older version. Please advise. Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Ahmad a écrit :> Hello all, > > I am working on a web application that uses the Prototype "1.5.0_rc0", > I want to upgrade to "1.6" > > I don''t know if "1.6" is backward compatible or if upgrading will make > problems in the pages that uses older version.It''s essentially backwards-compatible except mostly for the Hash class: you used to do: myhash.propName or myhash[propNameVariable] Now you can''t use direct access: you need to go through the get/set methods. As a result, however, you can use ANY property name you want, w/o risk of collision with built-in methods and properties. So you''d go something like: myhash.set(propNameExpr, value); myhash.get(propNameExpr); Prototype 1.6 has a ton of new cool stuff too, but as far as backwards compatibility is concerned, that''s the only real snag you should run into. -- Christophe Porteneuve aka TDD 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 -~----------~----~----~----~------~----~------~--~---
To add to Christophe''s reply, for clearing out hash entries, use the unset method... myhash.unset(propNameExpr) Depending on the size of your project, this can be a rather daunting exercise, but well worth it :) -justin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
You might want to consider giving a try to the recently added extension in Prototype trunk, designed specifically for that purpose: http://dev.rubyonrails.org/browser/spinoffs/prototype/trunk/ext/deprecation/deprecation.js Let me know how that goes. Best, Tobie On Feb 8, 6:19 pm, "Justin Perkins" <justinperk...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> To add to Christophe''s reply, for clearing out hash entries, use the > unset method... > > myhash.unset(propNameExpr) > > Depending on the size of your project, this can be a rather daunting > exercise, but well worth it :) > > -justin--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---