Thanks for the answer Régis but that doesn't make sense, we already are in the module directory. These should be top level for easier access.
The only valid reason I see why some elements should be in core in the context of a module is because __Dolibarr's core__ need access to them (module descriptor, box, triggers…). Then placing javascript, css and maybe themes in /core/ could be justified if there is optimization done on them by Dolibarr (i.e. : compression before serving) but I fail to see why my libraries and includes should go in core. Please prove me wrong. 2012/10/29 Régis Houssin <regis.hous...@cap-networks.com> > all that is common to all elements of the module should be in core > > > Le 29/10/12 14:26, Doursenaud, Raphaël a écrit : > > 2012/10/29 Régis Houssin <regis.hous...@cap-networks.com> > >> great ! >> >> but... >> >> move /includes/boxes/ to /core/boxes/ >> > > Aknoledged. This is an old file that sneaked into… > Already corrected. > > >> move /includes/ to /core/inc/ >> >> move /lib/ to /core/lib/ >> >> move /js/ to /core/js/ >> > Would you mind explaining why for these. I still see them in some current > modules and haven't experienced breakage. > I've always had a hard time finding these little bits an pieces. This is > useful for having the right mind set when developing. > > Thanks for the feedback anyway ! > > -- *Raphaël Doursenaud* 05 35 53 97 13 - 06 68 48 20 10 rdoursen...@gpcsolutions.fr -- <http://gpcsolutions.fr> http://gpcsolutions.fr Technopole Hélioparc 2 avenue du Président Pierre Angot 64053 PAU CEDEX 9 SARL GPC.solutions au capital de 7 500 € - R.C.S. PAU 528 995 921
_______________________________________________ Dolibarr-dev mailing list Dolibarr-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
