Re: [Glpi-dev] Template Engine
Hi, GLPI is free software and therefore faces two constraints: - The number of features added to each version depends on the available energy - Users request features (technical or functional) and the project attempts to answer as soon as possible Currently, the available energy is not sufficient and we have to make choices. These choices are certainly debatable but we assume. If we can not respond quickly to a request, we try to give you a workaround. We are also completely open to any contribution, if you have a need that we can not respond quickly, you can implement and offer, we usually integrate all constructive proposals(ex : new waiting state) Indeed, the use of a template engine is not currently used for priority for us because adaptation for GLPI is not optimal in the current state of GLPI and . We started working on the heart of GLPI for the use of such an engine is interesting and its adaptation is simple and fast. Currently, the graphic adaptation is done quite simply by changing only the CSS. If there are problematic elements at this level, just tell us. Regards, Julien ___ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
Re: [Glpi-dev] Adding a new state (for tickets)
Le 03/01/2013 17:54, Gustav González a écrit : From my point of view, GLPI should be the application killer of Aranda, but not as a hard copy of it, but as solution that can be customized in an easy way to replace it. I'll expect to share with you all the changes/patches/plugins or whatever I have to do to achieve my goal, and of course, you'll decide what you want to include or not for the future versions of GLPI, finally it's your decision. The only thing I really care about it, it's that reconsider your politics about what requirements should be included as part of the main core of GLPI. Hi, GLPI is free software and therefore faces two constraints: - The number of features added to each version depends on the available energy - Users request features (technical or functional) and the project attempts to answer as soon as possible Currently, the available energy is not sufficient and we have to make choices. These choices are certainly debatable but we assume. If we can not respond quickly to a request, we try to give you a workaround. We are also completely open to any contribution, if you have a need that we can not respond quickly, you can implement and offer, we usually integrate all constructive proposals(ex : new waiting state) Indeed, the use of a template engine is not currently used for priority for us because adaptation for GLPI is not optimal in the current state of GLPI and . We started working on the heart of GLPI for the use of such an engine is interesting and its adaptation is simple and fast. Currently, the graphic adaptation is done quite simply by changing only the CSS. If there are problematic elements at this level, just tell us. Regards, Julien ___ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
Re: [Glpi-dev] Classe Migration : définir un champ de table sans valeur par défaut
Le 04/01/2013 09:42, Julien Dombre a écrit : Bonjour, je comprend bien votre demande mais pas vraiment vos justifications : - Une variable d'environnement peut bien être initialisée mais pas renseignée (la valeur par défaut est alors vide). - Dans GLPI les ids nos renseignés sont positionnés à 0 (valeur par défaut 0), c'est la convention prise. Nous pouvons quand même ajouter l'option (pour la 0.84) même si elle ne me semble pas utile. L'option vient d'être ajouté en 0.84. Cordialement ___ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
Re: [Glpi-dev] Features: Add new tags to notification about tickets
Le 18/12/2012 15:25, wolvverine a écrit : I must add information in first notification about new ticket: What is the position of the ticket in a queue - number of all open and unresolved tickets in this moment. Example: For the entity of the ticket Hi, Ticket added for the 0.84 version : https://forge.indepnet.net/issues/4141 Regards Julien ___ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
Re: [Glpi-dev] Template Engine
2013/1/4 Julien Dombre m...@indepnet.net Hi, Hello there! GLPI is free software and therefore faces two constraints: - The number of features added to each version depends on the available energy - Users request features (technical or functional) and the project attempts to answer as soon as possible Totally agree! My own free software project got the same context. Currently, the available energy is not sufficient and we have to make choices. These choices are certainly debatable but we assume. If we can not respond quickly to a request, we try to give you a workaround. We are also completely open to any contribution, if you have a need that we can not respond quickly, you can implement and offer, we usually integrate all constructive proposals(ex : new waiting state) This is the beauty of the natural language! I mean, it's very (very) different when you say something like that feature is not required that when you say: right now we can't work on it but in the future there's a chance we could. If you check the previews post you'll be agree that this is the first one talking in an open way, as free software development use to be. I'm still learning the GLPI source code, but as soon as I could, I expect to share the code (ugly or not) that I write for the project. Indeed, the use of a template engine is not currently used for priority for us because adaptation for GLPI is not optimal in the current state of GLPI and . We started working on the heart of GLPI for the use of such an engine is interesting and its adaptation is simple and fast. Currently, the graphic adaptation is done quite simply by changing only the CSS. If there are problematic elements at this level, just tell us. Once again, there's a huge difference between saying: the template engine is not required but saying: is not currently used for priority. I really understand the situation, few hands make more difficult to cover more features, but it's very important for the GLPI community are aware that you guys, are working on the project following an open culture is you wish, as free software developers. Before reading this message, I was very worry about the answers I was getting here, but from now I'm very happy to understand that you follow the nice practice of an open development model :) I'll post again as soon as I have an specific tech question about the code or new code to share. Keep up the good work! :) -- Gustav Gonzalez xting...@gmail.com ___ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
