From: Gianluca S. <gi...@gm...> - 2008-09-30 06:48:09
|
Opening a new thread, this was OT in the Javascript one On Tue, Sep 30, 2008 at 7:48 AM, <vin...@mo...> wrote: >> Gianluca Sforna a écrit : >> >> On Tue, Sep 30, 2008 at 12:14 AM, Tiago Matos <ma...@ti...> wrote: >>> >>> >>> Template Engine? >> >> >> Yeah, but longer term. > > It doesn't make sense to me. Plugins are currently limited by the absence of > template. > I think that plugins and themes should come together. You are probably right, but a reality check says that plugins are here _today_, while templates can't be reasonably added without cleaning up the current html stuff, and that will take time (hence my "longer term" estimation). So what do you propose? I don't think we can reasonably hold the 1.2 release until templates are in place, do we? > There is a lot of > question like: how to remove unused fields in the report page, to build a > custom filter box, to change the view page... Yes, I see that, but to be honest we can't do much with the current code. Since obviously you are able to code PHP and know mantis codebase quite well, why don't you submit some patch to speed up the process? |
From: Jan S. <JanS@DracoBlue.de> - 2008-09-30 07:18:20
|
Hello, I haven't followed the entire previous discussion (before the jquery thread got hijacked), but when switching to a template engine, why not adding smarty-template engine and start to transform just parts of mantis, instead of making all? There is actually an option, to continue executing php-code in the templates, so it would be some kind of backwards compatible to not-yet-converted parts. I know that mantis-code, with all these ..php files for each page and all the html code in the php-files is pretty much work to convert, but it would be a start. As for jquery and javascript usage in mantis - in general - I think it's a nice extra, but I would prefer rendering the entire mantis as need-no-javascript application and initialize the javascript-based extensions after the page has loaded, to ensure that users without javascript can still use all mantis features. Regards, Jan -- http://dracoblue.net |
From: Vincent D. <vin...@mo...> - 2008-09-30 07:18:38
|
> Opening a new thread, this was OT in the Javascript one > > On Tue, Sep 30, 2008 at 7:48 AM, <vin...@mo...> wrote: >>> Gianluca Sforna a écrit : >>> >>> On Tue, Sep 30, 2008 at 12:14 AM, Tiago Matos <ma...@ti...> >>> wrote: >>>> >>>> >>>> Template Engine? >>> >>> >>> Yeah, but longer term. >> >> It doesn't make sense to me. Plugins are currently limited by the >> absence of template. >> I think that plugins and themes should come together. > > You are probably right, but a reality check says that plugins are here > _today_, while templates can't be reasonably added without cleaning up > the current html stuff, and that will take time (hence my "longer > term" estimation). > > So what do you propose? I don't think we can reasonably hold the 1.2 > release until templates are in place, do we? The question is why releasing a new version with plugins now? If you asked me if it was the time, I would say no because template are missing. I have 20 plugins on my website, 11 require a template engine... >> There is a lot of >> question like: how to remove unused fields in the report page, to build >> a custom filter box, to change the view page... > > Yes, I see that, but to be honest we can't do much with the current > code. Since obviously you are able to code PHP and know mantis > codebase quite well, why don't you submit some patch to speed up the > process? All my modifications are available on my website, you are free to take it. |
From: Gianluca S. <gi...@gm...> - 2008-10-01 10:34:29
|
On Tue, Sep 30, 2008 at 9:18 AM, Vincent DEBOUT <vin...@mo...> wrote: > The question is why releasing a new version with plugins now? If you asked > me if it was the time, I would say no because template are missing. I have > 20 plugins on my website, 11 require a template engine... I see you participating in discussions about plugins architecture in archives, but from a rather quick check this is the first time you raise this problem. Unfortunately, even if you raised the point earlier, it would have been made zero difference without some attached patch. >> Yes, I see that, but to be honest we can't do much with the current >> code. Since obviously you are able to code PHP and know mantis >> codebase quite well, why don't you submit some patch to speed up the >> process? > > All my modifications are available on my website, you are free to take it. Sorry, that's not how it works... I don't know what your website has, nor if/how it is possible to integrate your stuff in mantis; you created the code so you know better. So it all boils down to if you want your stuff to be in mantis or you just like to maintain your own patches forever outside it. If you want one of your features in mantis. you submit patches and the current dev team review and commit them. Repeat few times, show commitment to maintain your patches and you get yourself write access to mantis SVN; yes, it is _that_ easy. -- Gianluca Sforna http://morefedora.blogspot.com http://www.linkedin.com/in/gianlucasforna |
From: Vincent D. <vin...@mo...> - 2008-10-02 07:54:53
|
Hi > On Tue, Sep 30, 2008 at 9:18 AM, Vincent DEBOUT > <vin...@mo...> wrote: >> The question is why releasing a new version with plugins now? If you >> asked >> me if it was the time, I would say no because template are missing. I >> have 20 plugins on my website, 11 require a template engine... > > I see you participating in discussions about plugins architecture in > archives, In the wiki too... > but from a rather quick check this is the first time you > raise this problem. I didn't have the opportunity before the release of the 1.2.0*! > Unfortunately, even if you raised the point earlier, it would have > been made zero difference without some attached patch. So you prefer a bad idea with a patch rather than a good idea without a patch? Or you don't care about new ideas if there is no patch with it? >>> Yes, I see that, but to be honest we can't do much with the current >>> code. Since obviously you are able to code PHP and know mantis >>> codebase quite well, why don't you submit some patch to speed up the >>> process? >> >> All my modifications are available on my website, you are free to take >> it. > > Sorry, that's not how it works... I don't know what your website has, Nobody is responsible for watching what is happening around Mantis? > nor if/how it is possible to integrate your stuff in mantis; you > created the code so you know better. > > So it all boils down to if you want your stuff to be in mantis or you > just like to maintain your own patches forever outside it. > > If you want one of your features in mantis. you submit patches and the > current dev team review and commit them. Repeat few times, show > commitment to maintain your patches and you get yourself write access > to mantis SVN; yes, it is _that_ easy. I don't make patch if I'm not sure that it will be integrated, so it's up to you. -- Vincent http://deboutv.free.fr/mantis/ |
From: Victor B. <vb...@gm...> - 2008-10-11 19:33:13
|
Hi Vincent, I can see your point relating to templates. Templates are useful even without plug-ins. We actually started working on templates before plugins. However, the plugins feature was completed and the templates was not. In my mind the failure to fully complete the templates feature was the big bang approach rather than slowly moving into this direction by separation of the HTML from the business logic and introducing templates (we have improved since then, but there is more work to be done). I don't see the lack of templates as a show stopper for plugins or 1.2.x. However, it would be great if we can get some traction on getting templates implemented. We are trying to release more often, and waiting for such big features to be completed has always been the cause for delays in the past. As for the work on your website vs. patches. We always welcome people from the community who are willing to help with the development of Mantis. However, for their effort to be best utilized, we encourage that such contributions are co-ordinated with the team so that we can work together on the design and the planning of splitting the work into phases. This guarantees that the work fits with Mantis guidelines / vision and that it is done in a way to make it practical to integrate. One of the steps I've done to facilitate this was to add requirements pages on the wiki, where features can be specified in co-ordination with the community or the person who is willing to implement the feature, and hence when the feature is implemented it can be integrated with least lag / issues. I can see a lot of passion relating to templates (from team and community), and I would welcome any offers to help with this as far as requirements / planning / development. Our progress towards template support should be done on incremental steps that don't require us to branch or break trunk. On Thu, Oct 2, 2008 at 12:54 AM, Vincent DEBOUT <vin...@mo...> wrote: > Hi > >> On Tue, Sep 30, 2008 at 9:18 AM, Vincent DEBOUT >> <vin...@mo...> wrote: >>> The question is why releasing a new version with plugins now? If you >>> asked >>> me if it was the time, I would say no because template are missing. I >>> have 20 plugins on my website, 11 require a template engine... >> >> I see you participating in discussions about plugins architecture in >> archives, > > In the wiki too... > >> but from a rather quick check this is the first time you >> raise this problem. > > I didn't have the opportunity before the release of the 1.2.0*! > >> Unfortunately, even if you raised the point earlier, it would have >> been made zero difference without some attached patch. > > So you prefer a bad idea with a patch rather than a good idea without a > patch? > Or you don't care about new ideas if there is no patch with it? > >>>> Yes, I see that, but to be honest we can't do much with the current >>>> code. Since obviously you are able to code PHP and know mantis >>>> codebase quite well, why don't you submit some patch to speed up the >>>> process? >>> >>> All my modifications are available on my website, you are free to take >>> it. >> >> Sorry, that's not how it works... I don't know what your website has, > > Nobody is responsible for watching what is happening around Mantis? > >> nor if/how it is possible to integrate your stuff in mantis; you >> created the code so you know better. >> >> So it all boils down to if you want your stuff to be in mantis or you >> just like to maintain your own patches forever outside it. >> >> If you want one of your features in mantis. you submit patches and the >> current dev team review and commit them. Repeat few times, show >> commitment to maintain your patches and you get yourself write access >> to mantis SVN; yes, it is _that_ easy. > > I don't make patch if I'm not sure that it will be integrated, so it's up > to you. > > -- > Vincent > http://deboutv.free.fr/mantis/ > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > |