IMHO We need to move forward to using HTML5 and responsive design for a future major release. We simply can't ignore this technology anymore.
A templating framework would have greatly simplified this refactoring. Unfortunately we don't really have such a tool. We should stop thinking only in raw, bit-crunching performance and also think about readability, versatility, and ease-of-development when evaluating if templating fits our use case. Unfortunately, an idea and even a POC is not enough in a small community like ours to generate enough momentum to bring contributors into motion. You need to code the feature or GTFO (sorry for the strong language). I also vote for the removal of unmaintained bits and integrating menu system in themes. Any volunteers to do the heavy lifting? My 2 and a half cents. 2015-01-14 13:46 GMT+01:00 [Kreiz IT]Cédric GROSS <[email protected]>: > Thank you Philip J > > > > And about “excuse” : > http://wiki.dolibarr.org/index.php/Language_and_development_rules#External_templating_framework_.3F > > > > Cedric > > > > *De :* [email protected] [mailto: > [email protected]] *De la part de* > Philip Lehmann-Böhm > *Envoyé :* mercredi 14 janvier 2015 13:38 > > *À :* [email protected] > *Objet :* Re: [Dolibarr-dev] Auguria and Eldy menu > > > > I think moving to Twig would be utterly important. There is simply no > excuse not to use a templating system IMHO and Twig is really great. > > Am 14.01.15 um 13:35 schrieb [Kreiz IT]Cédric GROSS: > > Hello, My 2 cents also : > > > > Adopt a template manager so we could totally separate business code and > template. This should also permit development of new one easily. > > > > Yes. I know Eldy is totally against this. But we could really get great > benefit adopting a tool like this against a really small lost of speed. > (Twig use cached file, not sure we lost speed) > > > > Anyway, sometime I dream about a Dolibarr v4 based on that ;) > > > > Cedric > > > > *De :* [email protected] [ > mailto:[email protected] > <[email protected]>] *De **la part de* > [email protected] > *Envoyé :* mercredi 14 janvier 2015 12:46 > *À :* 'Posts about Dolibarr ERP & CRM development and coding' > *Objet :* Re: [Dolibarr-dev] Auguria and Eldy menu > > > > My 2 cents, > > remove menu lib and define menu on modules definition file > > > > > > *De :* [email protected] [ > mailto:[email protected] > <[email protected]>] *De la part de* > Florian HENRY > *Envoyé :* mercredi 14 janvier 2015 12:13 > *À :* [email protected] > *Objet :* Re: [Dolibarr-dev] Auguria and Eldy menu > > > > Hi, > > My point of view, remove auguria theme and affilate files, it is no more > maintened. > Theme I often see on my customer deployment are Amarok, Eldy and Cameleo > (this one to my point of view ugly, but give hight contrast on table lines). > As we see problem with Oblyon theme, theme and menu should be linked, when > change theme => menu manager should be updated as well. > > Regards. > > Florian Henry > > +33 6 03 76 48 07 > > [email protected] > > http://www.open-concept.pro > > Twitter : @_Open_Concept_ > > Google+ : https://www.google.com/+Open-conceptPro > > Le 14/01/2015 12:01, Doursenaud, Raphaël a écrit : > > Good question! > > > > Can't spot many differences. > > Looking at the code, I see that eldy one is maintained and more up to > date. > > I suspect the auguria one is (was?) tailored to fit the auguria theme. > > > > Don't know more. Anyone? > > > > 2015-01-13 20:01 GMT+01:00 Marcos García <[email protected]>: > > Hi all, > > > > Just a quick question... Which is the difference between Auguria menu > handler and Eldy menu handler? > > > > Regards, > > > > *Marcos García* > > [email protected] > > > _______________________________________________ > Dolibarr-dev mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > > > > > > -- > > *Raphaël Doursenaud* > > Directeur technique (CTO) > > Expert certifié en déploiement Google Apps > <https://gpcsolutions.fr/raphael-doursenaud-google-apps-certified-deployment-specialist> > > +33 (0)5 35 53 97 13 - +33 (0)6 68 48 20 10 > > > > [image: Image supprimée par l'expéditeur.] <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 > > [image: Image supprimée par l'expéditeur.] > <http://wiki.dolibarr.org/index.php/Dolibarr_suppliers_France#GPC.solutions>[image: > Image supprimée par l'expéditeur.] > > > > > _______________________________________________ > > Dolibarr-dev mailing list > > [email protected] > > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > > > > > > > _______________________________________________ > > Dolibarr-dev mailing list > > [email protected] > > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > > > > _______________________________________________ > Dolibarr-dev mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/dolibarr-dev > > -- *Raphaël Doursenaud* Directeur technique (CTO) Expert certifié en déploiement Google Apps <https://gpcsolutions.fr/raphael-doursenaud-google-apps-certified-deployment-specialist> +33 (0)5 35 53 97 13 - +33 (0)6 68 48 20 10 -- <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 <http://wiki.dolibarr.org/index.php/Dolibarr_suppliers_France#GPC.solutions>
_______________________________________________ Dolibarr-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/dolibarr-dev
