Fabian asked:

Where's the line between Nitro and Og?

Tags: og nitro tags

They seem to be quite mangled into each other. Like taggable.. You do that in the model (aka Og), but the Nitro part still needs to be written?

(1 attempts)

manveru answered:

Well, it is as you say, but let me explain a bit of MVC before. MVC (Model View Controller) is the structure that Nitro/Og tries to be. On one hand you have got Nitro, wich provides the Controller (Nitro::Controller) and the templates (.xhtml, Elements) - on the other side is Og, wich provides the Model (Og::Entity), cares about the store in the background and provides really neat ways to avoid store-specific SQL - so switching from one store to another is usually just the change of a line :)

However, Taggable is only in the Og-part - of course you interact with it using the Controller, but you don't have to use Nitro to use Taggable, right? You could still create Objects and tag them, for example if you want to write a gmail-like desktop-email-client and tag your mails :) [heh, that would be a nice idea...]

However, the place where Nitro/Og come together is Glue, it sticks them together for easier use in advanced Web-applications. Provides for example global variables, a mailer, localization a logger and so on... (have a look in the testcases for glue to see what it does apart from that)

Rating: 4