search

rubymotion-community / motion-support

Commonly useful extensions to the standard library for RubyMotion
MIT License
132 stars 28 forks source link

Combining Efforts #1

Closed sxross closed 11 years ago

sxross commented 11 years ago

I'm the creator of MotionModel. It was intended to emulate DataMapper/ActiveModel in many ways and that meant also creating some core extensions to types like Hash and String as well as an Inflector.

I've been wanting an ActiveSupport type of gem outside of MotionModel, and yours looks like a great place. I wonder if you could have a look at the core extensions in https://github.com/sxross/MotionModel/blob/master/lib/motion_model/ext.rb and see whether you agree these might better be in your motion-support than in my MotionModel. This would put us on the road to giving the whole RubyMotion community a single definitive ActiveSupport-like gem.

Thoughts?

tkadauke commented 11 years ago

Hey Steve,

Absolutely. I would love to combine efforts. That was the whole idea behind creating the motion-support gem in the first place. How should we proceed from here? I'm not using motionmodel yet, so maybe you want to fork motion-support? Or would you prefer commit access? Of course I'd be more than happy to help with anything that might come up.

--Thomas

Am 12.03.2013 um 20:03 schrieb "s.ross" notifications@github.com:

I'm the creator of MotionModel. It was intended to emulate DataMapper/ActiveModel in many ways and that meant also creating some core extensions to types like Hash and String as well as an Inflector.

I've been wanting an ActiveSupport type of gem outside of MotionModel, and yours looks like a great place. I wonder if you could have a look at the core extensions in https://github.com/sxross/MotionModel/blob/master/lib/motion_model/ext.rb and see whether you agree these might better be in your motion-support than in my MotionModel. This would put us on the road to giving the whole RubyMotion community a single definitive ActiveSupport-like gem.

Thoughts?

— Reply to this email directly or view it on GitHub.

sxross commented 11 years ago

I think it best that I fork motion-support and add my stuff in. Once you pull it and issue a gem, I can put a dependency in MotionModel.

Steve

On Mar 12, 2013, at 1:13 PM, Thomas Kadauke notifications@github.com wrote:

Hey Steve,

Absolutely. I would love to combine efforts. That was the whole idea behind creating the motion-support gem in the first place. How should we proceed from here? I'm not using motionmodel yet, so maybe you want to fork motion-support? Or would you prefer commit access? Of course I'd be more than happy to help with anything that might come up.

--Thomas

Am 12.03.2013 um 20:03 schrieb "s.ross" notifications@github.com:

I'm the creator of MotionModel. It was intended to emulate DataMapper/ActiveModel in many ways and that meant also creating some core extensions to types like Hash and String as well as an Inflector.

I've been wanting an ActiveSupport type of gem outside of MotionModel, and yours looks like a great place. I wonder if you could have a look at the core extensions in https://github.com/sxross/MotionModel/blob/master/lib/motion_model/ext.rb and see whether you agree these might better be in your motion-support than in my MotionModel. This would put us on the road to giving the whole RubyMotion community a single definitive ActiveSupport-like gem.

Thoughts?

— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.

tkadauke commented 11 years ago

I pulled your changes, did some on my own and just pushed motion-support -v 0.1.0 to rubygems.org. Thanks again!