other CMS extensions

Involved Joined: Nov 19, 2003 Posts: 282

The biggest plus of nuke - the only plus if you ask me - is that there are alot of third party modules for the software. This third party participation is what gives nuke its power.

To raise the bar of the CMS would be to create extensions that allow ... by example .. nuke EVO modules to function properly with the CMS.

You could get really crazy from here ..... and build extensions for the other nuke spinoffs of your choosing. i.e. No matter which flavor of the nuke the module was written for you could "suck it in" and it would function properly.

Also - depending upon the complexity - you could create other extensions for other even non-nuke cms's that have good third party support. Now I know all thats a ton of work and I'm sure Bill Gates would just love it if he were here Laughing

and in some cases is probably way too far off scope but it was worth mentioning IMHO.

Really I post this because I notice alot of RNYA issues being mentioned other places on the site and going too far off the normal 'nuke' track here could reduce the third party module support available to this CMS. And thats never a good thing ... even if we all agree some of those third party modules are just awful.

Posted: Sat May 30, 2009 3:13 pm

I think what you are referring to is called an 'adaptor pattern'. Whilst it is good in theory, my concern (as a user) would be the overhead of having to run the 'adaptors' all the time regardless of whether they were used or not.
The problem with adding support for code which is not native RavenNuke (tm) is the number of supporting files that might be required. As an example, I believe EVO has a different log-in function that passes variables to the function which are not present in RN.

registered · Site Admin Joined: Jun 04, 2004 Posts: 6437

Quote:

Really I post this because I notice alot of RNYA issues being mentioned other places on the site and going too far off the normal 'nuke' track here could reduce the third party module support available to this CMS. And thats never a good thing ... even if we all agree some of those third party modules are just awful.

Can you give some examples of this? I'm curious because the user table didn't change and, although registration surely did, the login function shouldn't be significantly impacted. I'm not sure what else could be impacted as far as other modules / addons, but maybe Guardian's point is correct regarding modules developed for other distributions like Evolution that don't play well with standard Nuke functions.

Also, though we hope to minimize the impact of improving RN, it's possible and even likely that we will deviate (as Evolution did). As for addons, we and addon authors will have to decide whether its better (easier, faster, etc.) to bridge or replace interfaces that don't work.

Posted: Sun May 31, 2009 5:18 pm

Don't know what you think , as it's from Joomla, worth the look ,
http://www.jfusion.org/

it's an idea I had in mind for unlucky modules.