[Nitro] Dir structure
george.moschovitis at gmail.com
Wed Feb 28 02:44:41 EST 2007
I have put Og related mixins to:
Raw related mixins go to:
btw, for extra consistency I removed the notion of helper what used to be in
is now in:
you now have to use the standard
On 2/27/07, transfire at gmail.com <transfire at gmail.com> wrote:
> On Feb 27, 5:47 am, "George Moschovitis"
> <george.moschovi... at gmail.com> wrote:
> > Ok,
> > point taken, but I would like to keep Og simpler. There are so many
> > things that could be implemented as mixins I don't want to include
> > everything in the default distribution. I will think about this a bit
> > more. I will most probably keep an Og namespace for mixins as you
> > suggest.
> Why so bare bones? I would think a user of Og would want to have
> access to these Og specific mixins without having to install yet
> another package (and would deter usage otherwise). I could understand
> it if it was some esoteric mixin with a very specific usecase, but in
> that case I would expect the mixin it to have it's own project all
> As for Raw, of course any mixin that is specific to Raw belongs with
> it too. If we put Raw specific mixin in Nitro then I don't think the
> Nitro/Raw split was worthit in the first place.
> Of course it a harder question for parts that use both Og and Raw, but
> I suspect they would much less common, and would probably do just as
> well as stand-alone projects, but if they are general/vital then Nitro
> seems the place to be.
> Query: Not that I would do this, I'm asking a theoretical quesiton
> here: could one use Raw with ActiveRecord (no Nitro no Og)?
> Nitro-general mailing list
> Nitro-general at rubyforge.org
More information about the Nitro-general