Why do new plugins/modules need to be added to kernel/ ?

Next topic

Author	Message
Paul Forsyth	Tuesday 06 July 2004 1:30:46 am I see the new payment mechanism in pubsvn and was immediately struck with the decision to put the paypal module, tiny as it is, inside kernel/. I have two issues with this that are generic to all kernel/ modules. 1. It is impossible to override modules inside kernel/. This has been long standing issue that should be resolved soon. 2. Items like the paypal module are plugins and should not be given a full blown entry in kernel/. It cannot be overriden only replaced. Are you seriously going to start adding other plugin modules to kernel/? It will get messy very quickly... You should fix the extension system to allow modules to be overriden and develop these new features as extensions. Kernel/ should be used for generic code and not used for plugins in this way. Btw, what happened to defining handlers inside kernel/classes? Are you changing this? paul -- http://www.visionwt.com
Björn Dieding@xrow.de	Wednesday 07 July 2004 1:17:55 am agree... those packages shouldn't be in the kernel, but they should ship with the eZ publish package. I think, I mentioned it at the conference ... It would be nice to have a extension package creatoin handler... bjoern - http://xrow.de Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Jan Borsodi	Friday 09 July 2004 2:03:49 am We will move specific payment features into a separate extension and just leave the general features in eZ publish. As soon as we figure out where we will place these extensions we will move it. Don't worry, we won't bloat eZ publish :) -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq
Paul Forsyth	Friday 09 July 2004 2:16:32 am Excellent, thanks :) To follow up on the extension talk, in the past eZ haven't really used the extension system. I think the only public case is the online editor. Will you be using it more? I see the extensions as being a stepping stone to actively developing with the community. For example if the Paypal extension was put onto pubsvn developers could work with it. Of course, some extensions will have your dual licence but im sure there will be some where it doesnt matter and the GPL could be used. Once begun members could be nominated to ensure a package/extension is versioned/released properly. Once you have your package installer written to pick from known 'package' repositories these can be easily added to the default install from pubsvn. Paul -- http://www.visionwt.com