First, if this is not the place to post, then please ask me to repost to the proper list so we can handle this thread there. I''m currently working on d-rails (http://github.com/foobarfighter/d- rails/tree/master) which is a plugin for a Dojo implementation of RJS and other helpers which currently use the Prototype library for client side support. I was wondering if there was any thought given to a more JS toolkit agnostic approach for Rails 3. My ideal implementation would be something that provided a basic architecture and a standard API for passing callbacks and options which could be implemented by a toolkit specific driver and configured by the user. A friend of mine recently told me that this approach was currently underway, but I can neither confirm nor deny his claims. I would love to help from the Dojo perspective if possible. Who do I need to talk to and are my friends claims true? Regards, Bob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Bob Remeika wrote:> First, if this is not the place to post, then please ask me to repost > to the proper list so we can handle this thread there. > > I''m currently working on d-rails (http://github.com/foobarfighter/d- > rails/tree/master) which is a plugin for a Dojo implementation of RJS > and other helpers which currently use the Prototype library for client > side support. I was wondering if there was any thought given to a > more JS toolkit agnostic approach for Rails 3. My ideal > implementation would be something that provided a basic architecture > and a standard API for passing callbacks and options which could be > implemented by a toolkit specific driver and configured by the user. > > A friend of mine recently told me that this approach was currently > underway, but I can neither confirm nor deny his claims. I would love > to help from the Dojo perspective if possible. Who do I need to talk > to and are my friends claims true?This is currently *intended* to get underway after we ship 2.3 final, e.g. for the 3.0 release. However I''m not aware of anything underway at present. My advice would be to start experimenting on the changes you think you''d need to accomplish your goal. Then let us know what it looks like. That''d be the easiest way for you to ensure that whatever happens meets your needs. -- Cheers, Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Michael, Thanks for the reply. When I am finished with d-rails for the current version of Rails (expected in about two weeks or so) then I will get started on a proposal for how a more JS toolkit agnostic approach could work in Rails 3. Regards, Bob On Fri, Feb 13, 2009 at 1:15 AM, Michael Koziarski <michael@koziarski.com>wrote:> > Bob Remeika wrote: > > First, if this is not the place to post, then please ask me to repost > > to the proper list so we can handle this thread there. > > > > I''m currently working on d-rails (http://github.com/foobarfighter/d- > > rails/tree/master) which is a plugin for a Dojo implementation of RJS > > and other helpers which currently use the Prototype library for client > > side support. I was wondering if there was any thought given to a > > more JS toolkit agnostic approach for Rails 3. My ideal > > implementation would be something that provided a basic architecture > > and a standard API for passing callbacks and options which could be > > implemented by a toolkit specific driver and configured by the user. > > > > A friend of mine recently told me that this approach was currently > > underway, but I can neither confirm nor deny his claims. I would love > > to help from the Dojo perspective if possible. Who do I need to talk > > to and are my friends claims true? > > This is currently *intended* to get underway after we ship 2.3 final, > e.g. for the 3.0 release. However I''m not aware of anything underway at > present. > > My advice would be to start experimenting on the changes you think you''d > need to accomplish your goal. Then let us know what it looks like. > That''d be the easiest way for you to ensure that whatever happens meets > your needs. > > -- > Cheers, > > Koz > > > > >-- Bob Remeika http://bobremeika.com http://d-rails.org http://cometdproject.dojotoolkit.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---