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
<address@hidden>
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
<address@hidden>
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 !