Modules and Plugins

Apr 18, 2009 at 11:16 PM
In the source code notes it says plugins were refactored to be called modules, but then there's a note about another plugin framework being added.  What framework was that?  What will be the difference between modules and this new framework?
Apr 19, 2009 at 6:50 AM
When the time comes, I'll let the team that built it talk about it.  Until then, my lips are sealed (but the code is in there so have at it).  :)

Here's how I think about modules vs. plugins.  Modules are for when you want to build something that can hook into the MVC/Oxite pipeline and build on it.  Plugins are for when you want to write code to do something in one of the extensibility points that Oxite has defined.

Does that make sense?
May 8, 2009 at 11:31 PM
Edited Jul 18, 2009 at 6:14 AM

Erik, if you guys can create a pluggable module architecture and skinning engine like DotNetNuke (DNN), Oxite will replace DNN within a couple of years and become the most successful open source project on Microsoft platform. Keep up the great work! We feel very excited about it.

May 10, 2009 at 3:32 AM

Our plugin model is going to be great.  We're finishing it up this week.  It will be very simple and convention based.  We're still nailing out what our module model will be, but it will be more involved and more powerful.

I don't know how DNN's skinning works, but I think what we've come up with for skinning is really good.

We're not trying to replace DNN, but thanks for your confidence in what we're building.  Glad you're excited!

Jul 18, 2009 at 6:16 AM

Any update on module architecture?

Jul 18, 2009 at 6:18 AM

Yup, go grab the latest code.  Most of the module architecture is implemented.  The way you register them is temporary and is going to change and module settings and UI aren't in place yet, but creating modules and how they get called is done and you can see that we've broken up almost all of Oxite into modules now.  Still more to go, but that's where we're headed so far.  :)