Fork me on GitHub

Rapport de message :*
 

Re: Frameworks moduleadmin_v1.0_final - fichiers langue francais

Titre du sujet : Re: Frameworks moduleadmin_v1.0_final - fichiers langue francais
par mamba sur 24/07/2011 03:07:56

Kris,

1) it has been agreed that the ModuleAdmin framework will be part of XOOPS 2.5.2

2) Sure, each module can create their own "XOOPS 2.5 look & feel", but why waste your time on it? Where is the concept of "code reuse"? It's time to start living up to our name which is "eXtensible Object Oriented Portal System". "Code reuse" is the main premise of OOP, therefore why would we try to do the same thing again and again in each module, instead of extracting common parts and reusing them consistently across all modules?

Just compare how many lines of code do you need to create manually a menu in a module, which is equivalent to this one line?

$modversion['system_menu'] = 1;

3) If we need to change something - fix a bug, change an icon or image, we'll do it in one place, and all the modules will reflect it right away. It is so much easier to maintain modules this way.

4) Also, one of the main problems across XOOPS modules is that every one looks different, is using different icons, images, etc. You look at WordPress and the Admin for each module is consistent and looks the same.

Together, it is easier for the users and developers.
Propulsé avec XOOPS | Graphisme adapté par Tatane, Grosdunord, Montuy337513

98 Personne(s) en ligne (75 Personne(s) connectée(s) sur Forum) | Utilisateur(s): 0 | Invité(s): 98 | Plus ...