Cotonti / Open Source PHP Content Management FrameworkContent Management Framework

Should we merge Modules and Plugins?

61.9% 13
38.1% 8

21 Date 2011-08-10 07:49

Forums / Cotonti / Core Labs / Ideas / Poll: Plugins and Modules merge (again)

Reduce duplicated functionality

Trustmaster
#1 2011-08-10 07:49


Administrators
Thanked: 193 times

This topic has been discussed before and last time we chose to keep them separate. But nowadays that this concept is implemented and is actively used, some of us have realized that Modules and Plugins are so close technically that the differentiation causes more confusion than practical benefit.

So I propose once again to merge Modules and Plugins and use categorization like we do in Downloads section on this site to group plugins by their function in the installer/adminCP, so an administrator can install what he needs easier.

May the Source be with you!
esclkm
#2 2011-08-10 12:06


Senior Developers
Thanked: 57 times

камни первые мы уже получили.... от разделения - а преимуществ пока не было.

littledev.ru - мой маленький зарождающийся блог о котонти.
снижение стоимости программирования и снижение стоимости производства разные вещи. Первое можно скорее сравнить с раздачей работникам дешевых инструментов, чем со снижением зарплаты
Trustmaster
#3 2011-08-10 14:06


Administrators
Thanked: 193 times

English please.

May the Source be with you!
Graber
#4 2011-08-10 16:38


Testers
Thanked: 5 times

I strongly object to Modules and Plugins mergence.

Кто бездействует, тот не завоевывает
pieter
#5 2011-08-10 16:58


Translators
Thanked: 7 times

Why?

 

... can we help you ...
Alex300
#6 2011-08-11 07:06


Developers
Thanked: 22 times

If we are planning for the future are more differences between the modules and plug-in that division should be. For example plug-in performs some system functions: connects JS, performs some validations, plugins executes from hooks. Ie plug-in complements the core or other modules. In this case, combining them would not be correct. I am a supporter of such a path.
The modules in this case are the individual pages (like pages, forum, users)
In this case, in the future it will be easier to build a new admin panel uncluttered.

If between the modules and plug-in makes no difference - then merge. Duplication of code - it is bad.

 

Sorry for my English :)

Приходится бежать со всех ног, чтобы только оставаться на месте. А чтобы куда-то попасть, приходится бежать еще быстрее...
...Sorry for my english...
Portal30.Ru
RaisenBran
#7 2011-08-12 17:32


Members
Thanked: 5 times

Now that I think about it, don't merge them. Just pretend there is another '1' on the 'no' side :)

 

Also as a suggestion for polls, there should be the ability to change it if you make an error or you change your mind.

GHengeveld
#8 2011-08-12 20:42


Administrators
Thanked: 48 times

Definitely not. Although the current technical implementation and capabilities of modules and plugins are nearly the same, in the future I would like to see modules get more advanced capabilities, such as an object-oriented model-view-controller structure and object-relational mapping. This is suitable for modules, but not for plugins. Such extended features will make the difference between the two quite clear.
Formerly known as Koradhil
Trustmaster
#9 2011-08-13 07:34


Administrators
Thanked: 193 times

Thanks guys, that makes sense for future branches like 1.5.

May the Source be with you!