Thanks for the reply, Long. Let's say for example I'm building a NASCAR site on top of Insoshi, so I've got controllers, models, views, etc that are specific to the NASCAR functionality, but are not relevant to the Insoshi community. It would be nice to keep files such as my NASCAR racecar_drivers_controller.rb file in a directory of its own instead of throwing it in with Insoshi files. The only reason I'm after this solution is to keep things visually clean on my local directory tree, so I can quickly determine whether a set of files are Insoshi files that I can fetch and push to the Insoshi repository, or whether they're files that are only interesting to me and my own site.
I hope this makes more sense. Thanks for your patience. Jason On Jun 3, 10:56 pm, "Long Nguyen" <[EMAIL PROTECTED]> wrote: > Could describe in a bit more detail what you mean by non-Insoshi code? > > Do you mean local customizations/updates that aren't part of the official > Insoshi releases? Or are you talking about separate applications that need > to be organized under some structure? Or maybe something complete different? > > Long > > On Tue, Jun 3, 2008 at 1:51 PM, Jason Galvin <[EMAIL PROTECTED]> wrote: > > > What's a good way of keeping Insoshi code organizationally separate > > from code not pertaining to Insoshi on my local directory tree? > > > Perhaps separate namespaces or modules, or even pluginizing Insoshi? > > > Very cool product, by the way. Thanks! > > > Jason > > -- > Long Nguyen > [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ Insoshi developer site: http://dogfood.insoshi.com/ Insoshi documentation: http://docs.insoshi.com/ You received this message because you are subscribed to the Google Groups "Insoshi" 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/insoshi?hl=en -~----------~----~----~----~------~----~------~--~---
