Comments - Plugins - Erik Porter's Blog

RE: Oxite Plugin Extensibility Points Discussion

Erik — Fri, 15 May 2009 08:27:52 GMT

@Aamir Maniar Just to make sure you saw my reply to you on twitter about how you can participate... http://twitter.com/HumanCompiler/status/1797478089 As for "Oxite Processors" the only problem with that is that I think most people will probably think of CPUs when they hear the word "Processor".

RE: Oxite Plugin Extensibility Points Discussion

Aamir Maniar — Thu, 14 May 2009 12:15:11 GMT

Processing methods can be called as 'Oxite Processors'.

RE: Oxite Plugin Extensibility Points Discussion

Aamir Maniar — Thu, 14 May 2009 12:10:58 GMT

It seems Oxite is still in its infancy if you compare it with Word Press, and there is a long journey ahead. But I am interested in this project particularly because its clean architectural style. And hence I am planning to use this in my comply's corporate blog www.maniarcorporation.com. I would also like to take part in development of this project. Any idea how should I?

RE: Oxite Plugin Extensibility Points Discussion

Erik — Fri, 24 Apr 2009 18:16:21 GMT

Thanks for the links! @Thomas Freudenberg Yah, I'm running an older version of Oxite. Need to take the time to upgrade to the latest build. That was one of many bugs we've fixed. Another one is that you may not even ever get email notifications on the build my site is running. :( I'll try to upgrade this weekend (assuming we're at a stable enough point...need to check).

RE: Oxite Plugin Extensibility Points Discussion

andrexx — Fri, 24 Apr 2009 13:56:32 GMT

Also found interesting link in comments http://blogs.msdn.com/hammett/archive/2009/04/23/mef-and-asp-net-mvc-sample.aspx

RE: Oxite Plugin Extensibility Points Discussion

andrexx — Fri, 24 Apr 2009 13:50:02 GMT

Link for Maarten article http://blog.maartenballiauw.be/post/2009/04/21/ASPNET-MVC-and-the-Managed-Extensibility-Framework-(MEF).aspx

RE: Oxite Plugin Extensibility Points Discussion

Thomas Freudenberg — Fri, 24 Apr 2009 10:17:41 GMT

Hamilton Verissimo just wrote another MEF and ASP.NET MVC sample: http://blogs.msdn.com/hammett/archive/2009/04/23/mef-and-asp-net-mvc-sample.aspx

RE: Oxite Plugin Extensibility Points Discussion

Thomas Freudenberg — Fri, 24 Apr 2009 06:22:14 GMT

Most Windows messages wor this way. On WM_MOVING you can influence the way a window is moved, manipulate it or even suppress it. WM_MOVED however is sent *after* the windows position has changed. Here's the URL to the article I mentioned: http://blog.maartenballiauw.be/post/2009/04/21/ASPNET-MVC-and-the-Managed-Extensibility-Framework-%28MEF%29.aspx BTW, I subscribed to the this post of yours, and the notification email included my raw comment including the URl ;)

RE: Oxite Plugin Extensibility Points Discussion

Erik — Thu, 23 Apr 2009 17:02:58 GMT

Yes. Pre and Post events are good. Since the intent with a pre event is to manipulate the object before being saved with the list above you would actually use "ProcessPostInput". We currently separate the idea of notification vs. manipulation. You do have me thinking though that this might not be a necessary separation and having a PostAdding instead might be better. I'll discuss that one with the team. Yes, context is very import and rendering of feeds vs. web output is actually one we discussed yesterday in our meeting. These methods will definitely get context. As this gets more fleshed out, I'll do more blog posts about the details. We have thought about packaging. MEF has come up, but we're wanting to follow the team building out the plugin architecture we're using. That said, THEY are talking to team that builds MEF so you may see MEF in the future. I didn't see a url to the article. I'd definitely take a look if you provided one. :)

RE: Oxite Plugin Extensibility Points Discussion

Thomas Freudenberg — Thu, 23 Apr 2009 15:06:15 GMT

I'm convinced that you already thought about packaging of plugins. Nevertheless I want to point you to an article by Maarten Balliauw about using MEF to manage plugins for ASP.NET MVC.

RE: Oxite Plugin Extensibility Points Discussion

Thomas Freudenberg — Thu, 23 Apr 2009 12:30:15 GMT

That's what I've waited for :) Sounds good so far, but I have two annotations: a) It might be interesting to get notifications before *and* after something happens, e.g. AreaAdding and AreaAdded. This way a plugin might change the area's properties before it is persisted, but another plugin relys on that the area is already stored in the db. b) A plugin might render web output and ATOM feeds differently, so Oxite should pass some kind of context to the processing methods.