Forum: Ruby on Rails Developing reusable components?

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Adam F. (Guest)
on 2006-02-17 20:07
(Received via mailing list)
Is there a development guide for best practices when making reusable

For example, none of the login generators fit my requirements, and I
want to write my own. But after I'm done, I'll want to share it with
multiple applications.

Is there documentation for the right way to go about doing this?

				- Adam

** Expert Technical Project and Business Management
**** System Performance Analysis and Architecture
****** [ ]

[ ] ............ Blog
[ ].. Experience
[ ] ... Photos
[ ].............Wiki
[ ] ............. Links
Jeremy Voorhis (Guest)
on 2006-02-17 20:19
(Received via mailing list)
Right now, some alternatives include

* Building your own generators. This is not hard to do. Check out
Rails' migration generator for a simple example.
* Building a plugin.
* Sharing code with svn:externals or something similar

Another approach would be to place a generator inside of a plugin.
This would allow you to easily install/uninstall the generator across
many projects. We have used this approach with some success at PLANET


On Feb 17, 2006, at 10:04 AM, Adam F. wrote:

> 				- Adam
> _______________________________________________
> Rails mailing list
> removed_email_address@domain.invalid

  * Jeremy Voorhis, Lead Architect
  * PLANET ARGON, LLC Rails Development, Consulting & Hosting
  * Portland, Oregon  | p: 503.351.4730 | f: 815.642.4068
  * |
This topic is locked and can not be replied to.