<p>Just some initial brainstorms. Any syntax here is just for illustration, so if it looks a bit dodgy, don’t freak out :)</p>
<h1>Registering addon</h1>
<p>Call a register method on the Gluttonberg component. The key is so that the addon’s configuration can be recalled later. The constant is the module containing the addon. The rest is a hash of options which will be kept in the configuration. The exact options — I have no idea at this point.</p>
<pre><code>
Gluttonberg::Addons.register(:forum, Forum, :navigation => "Forum")
</code></pre>
<h1>Registering routes</h1>
<p>Unlike stand-alone slices, addons will not register their own routes, instead they defer to Gluttonberg, which will namespace them and add the routes at the same time it does it’s own.</p>
<p>Here is an example of how an addon might define it’s routes;</p>
<pre><code>
Gluttonberg::Addons.prepare_routes(:forum) do
match("/").to(:controller => "posts", :action => "latest").name(:latest)
resources(:posts)
resources(:users)
resources(:categories)
end
</code></pre>
<h1>Backend Integration</h1>
<p>Most addons would need to integrate with the admin in someway — parts of it will need protection, need to appear in the nav, have the same form styles etc. For example, when registering an addon, there will be an option to specify if it needs to appear in the main navigation and how it should be labelled.</p>
2008-10-12T23:10:13-07:00
66522
customcomponents
55020
CustomComponents
2008-10-12T23:10:33-07:00
109