Re: Project status and proposal
Gonzalo Aguilar Delgado <[email protected]> Wed, 16 Aug 2017 18:17:00 +0200
| Newsgroups | gmane.comp.gnome.apps.planner.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============3376624120433735758== Content-Type: multipart/alternative; boundary="------------17176CD65BF42FC4763C075A" Content-Language: en-US This is a multi-part message in MIME format. --------------17176CD65BF42FC4763C075A Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Hello Alexandre, I was taking a look to goocanvas that seems to fit in your design. It's out of development. No new features to be added but still supported. Instead of hacking it for a new gantt widget I'm seeing the possibility to do an intermediate step in porting the current widget to this goocanvas. Latter we can create a specific gantt widget. This allows us to setup everything, be able to step up gtk3 and continue porting meanwhile we evaluate if a full gantt widget does applies... What do you think? Best regards, El 03/08/17 a las 20:19, Alexandre Franke escribió: > On Thu, Aug 3, 2017 at 7:25 PM, Gonzalo Aguilar Delgado > <[email protected]> wrote: >> Hello all, > Hi, > >> It seems you are in the road to rewritting this wonderful piece of software >> that so many happines gave me in the past. So I can see if I can do >> something for the tool. Since the Gantt chart seems to be a problem I >> propose: > […] >> What do you think? > As I suggested earlier, the way forward is to make it a bunch of GTK+ > widgets (i.e. the whole chart is a widget containing widgets that each > represtent tasks, milestones…). > >> I also moved to meson all my projects for building. The difference is GREAT. >> Compilation times and manageability are exceptional. And you don't have to >> wait 20 minutes for a build... I think it would be a win. Everyone is also >> moving. > Yes, meson is the hip thing and could be the way forward. However it > does not play nice for now with Python+C (+FlatPak) projects and there > is no rush to do that. > >> About the use of Vala... will you reconsider it? > No. > >> Lot of wonderful projects >> are written in vala (gnome-builder for instance) and it's working nice. > Builder is not written in Vala. You need to do better research. > >> And no I don't think it will dissapear. Specially if we use it. > I couldn’t care less if it disappeared. I cannot recommend that anyone uses it. > >> About new features... I think the same than Andrew Miloradovsky. Maybe is >> not time for it. But giving a chance for new features it can give a boost to >> the project (but also kill it :-( ). Maybe new developers join... So we can >> propose, then it should be implemented... if possible. > Patching new features into legacy code is bad practice, a waste of > time and energy, and just increases the amount of work. > >> Add a Kanban style chart for the tasks. Grouped on milestones and with >> status depending if it has a resource or not, but also if someone has >> advanced it based on progress. > You’ll have to explain how to map kanban swimlanes and columns map to > Gantt concepts. I think there is a clash between the methodologies > those tools support and I am not convinced a single tool should > contain both. I do use both, but in different contexts. > >> Add Scrum backlog based on the tasks. And maybe grouped on sprints. >> Some progress reporting reports would be nice to have. > I haven’t used Scrum backlogs, but they seem similar to kanban boards > so the same concerns apply. > >> This could be a great win for the project and merging the best of both >> worlds can be a win. Cause the tools I see for Agile are specific for it. >> Not using a merge of Agile and traditional. And can give the project new >> visibility. > How about we make it great again for traditional planning first, then > see where we can go from there? > > Cheers, > --------------17176CD65BF42FC4763C075A Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000099" bgcolor="#FFFFFF"> <p><font face="Helvetica, Arial, sans-serif">Hello Alexandre, <br> </font></p> <p><font face="Helvetica, Arial, sans-serif">I was taking a look to goocanvas that seems to fit in your design. It's out of development. No new features to be added but still supported.<br> </font></p> <p><font face="Helvetica, Arial, sans-serif">Instead of hacking it for a new gantt widget I'm seeing the possibility to do an intermediate step in porting the current widget to this goocanvas. Latter we can create a specific gantt widget.<br> </font></p> <p><font face="Helvetica, Arial, sans-serif">This allows us to setup everything, be able to step up gtk3 and continue porting meanwhile we evaluate if a full gantt widget does applies...</font></p> <p><font face="Helvetica, Arial, sans-serif">What do you think?</font></p> <p><font face="Helvetica, Arial, sans-serif">Best regards,</font><br> </p> <br> <div class="moz-cite-prefix">El 03/08/17 a las 20:19, Alexandre Franke escribió:<br> </div> <blockquote type="cite" cite="mid:CAJ-e=JCZTm_4HE-yegP5oFA3Y6V+LWsghZsmHXQSfRhFDT70aw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org"> <pre wrap="">On Thu, Aug 3, 2017 at 7:25 PM, Gonzalo Aguilar Delgado <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Hello all, </pre> </blockquote> <pre wrap=""> Hi, </pre> <blockquote type="cite"> <pre wrap="">It seems you are in the road to rewritting this wonderful piece of software that so many happines gave me in the past. So I can see if I can do something for the tool. Since the Gantt chart seems to be a problem I propose: </pre> </blockquote> <pre wrap="">[…] </pre> <blockquote type="cite"> <pre wrap="">What do you think? </pre> </blockquote> <pre wrap=""> As I suggested earlier, the way forward is to make it a bunch of GTK+ widgets (i.e. the whole chart is a widget containing widgets that each represtent tasks, milestones…). </pre> <blockquote type="cite"> <pre wrap="">I also moved to meson all my projects for building. The difference is GREAT. Compilation times and manageability are exceptional. And you don't have to wait 20 minutes for a build... I think it would be a win. Everyone is also moving. </pre> </blockquote> <pre wrap=""> Yes, meson is the hip thing and could be the way forward. However it does not play nice for now with Python+C (+FlatPak) projects and there is no rush to do that. </pre> <blockquote type="cite"> <pre wrap="">About the use of Vala... will you reconsider it? </pre> </blockquote> <pre wrap=""> No. </pre> <blockquote type="cite"> <pre wrap="">Lot of wonderful projects are written in vala (gnome-builder for instance) and it's working nice. </pre> </blockquote> <pre wrap=""> Builder is not written in Vala. You need to do better research. </pre> <blockquote type="cite"> <pre wrap="">And no I don't think it will dissapear. Specially if we use it. </pre> </blockquote> <pre wrap=""> I couldn’t care less if it disappeared. I cannot recommend that anyone uses it. </pre> <blockquote type="cite"> <pre wrap="">About new features... I think the same than Andrew Miloradovsky. Maybe is not time for it. But giving a chance for new features it can give a boost to the project (but also kill it :-( ). Maybe new developers join... So we can propose, then it should be implemented... if possible. </pre> </blockquote> <pre wrap=""> Patching new features into legacy code is bad practice, a waste of time and energy, and just increases the amount of work. </pre> <blockquote type="cite"> <pre wrap="">Add a Kanban style chart for the tasks. Grouped on milestones and with status depending if it has a resource or not, but also if someone has advanced it based on progress. </pre> </blockquote> <pre wrap=""> You’ll have to explain how to map kanban swimlanes and columns map to Gantt concepts. I think there is a clash between the methodologies those tools support and I am not convinced a single tool should contain both. I do use both, but in different contexts. </pre> <blockquote type="cite"> <pre wrap="">Add Scrum backlog based on the tasks. And maybe grouped on sprints. Some progress reporting reports would be nice to have. </pre> </blockquote> <pre wrap=""> I haven’t used Scrum backlogs, but they seem similar to kanban boards so the same concerns apply. </pre> <blockquote type="cite"> <pre wrap="">This could be a great win for the project and merging the best of both worlds can be a win. Cause the tools I see for Agile are specific for it. Not using a merge of Agile and traditional. And can give the project new visibility. </pre> </blockquote> <pre wrap=""> How about we make it great again for traditional planning first, then see where we can go from there? Cheers, </pre> </blockquote> <br> </body> </html> --------------17176CD65BF42FC4763C075A-- --===============3376624120433735758== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ planner-dev-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/planner-dev-list --===============3376624120433735758==--