Plan/KGantt
There are issues with KGantt that needs to fixed. It seems to me KGantt was imported from KDAB right? At least some of the enhancements made for Plan is not in KGantt. Some are but maybe those where sync'ed back to KDAB, I don't quite remember, it was a looong time ago. Anyway, is it ok to merge the missing stuff into KGantt or is there other users that may have issues with that? Afaics kdepim still has it's own copy, but there are maybe others? Dag ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Plan/KGantt
Am Montag, 4. Juli 2016, 14:05:58 CEST schrieb Dag: > There are issues with KGantt that needs to fixed. > It seems to me KGantt was imported from KDAB right? > At least some of the enhancements made for Plan is not in KGantt. Some > are but maybe those where sync'ed back to KDAB, I don't quite remember, > it was a looong time ago. When KGantt (as part of KDiagram project) was created from a dump of then latest state of KDGantt, I tried to go through all custom modifications done to the Calligra fork of KDGantt and applied them to KGantt. Of course possible I missed something :) Which enhancements are you missing exactly? > Anyway, is it ok to merge the missing stuff into KGantt or is there > other users that may have issues with that? > Afaics kdepim still has it's own copy, but there are maybe others? Right now I do not know of any other users of KGantt itself (KChart is shared with KMyMoney & Massif-Visualizer). And ideally the PIM people would start to adapt to KGantt as well, that is the whole idea here, to reduce the number of forks :) So should be fine to commit directly. There also was no release yet (high on my TODO list to get this scheduled though), so no API to break yet (though ideally only done on Mondays :) ). (In matters of KDE CI, when doing a ABI change, best first wait for KDiagram build to have finished and only then push the respective changes to the Calligra repo. That should save us a failed build of Calligra :) (because right now there is no dependency tracking when it comes to ABI changes)) Cheers Friedrich ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Plan/KGantt
On Mon, 04 Jul 2016 14:05:58 +0200, Dag wrote: There are issues with KGantt that needs to fixed. It seems to me KGantt was imported from KDAB right? At least some of the enhancements made for Plan is not in KGantt. Some are but maybe those where sync'ed back to KDAB, I don't quite remember, it was a looong time ago. Anyway, is it ok to merge the missing stuff into KGantt or is there other users that may have issues with that? Afaics kdepim still has it's own copy, but there are maybe others? there is a released library kdgantt2 http://download.kde.org/stable/applications/16.04.2/src/kdgantt2-16.04.2.tar.xz It might be possible to use that. Regards, Treeve Dag ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Plan/KGantt
Friedrich W. H. Kossebau skrev den 2016-07-04 14:32: Am Montag, 4. Juli 2016, 14:05:58 CEST schrieb Dag: There are issues with KGantt that needs to fixed. It seems to me KGantt was imported from KDAB right? At least some of the enhancements made for Plan is not in KGantt. Some are but maybe those where sync'ed back to KDAB, I don't quite remember, it was a looong time ago. When KGantt (as part of KDiagram project) was created from a dump of then latest state of KDGantt, I tried to go through all custom modifications done to the Calligra fork of KDGantt and applied them to KGantt. Of course possible I missed something :) Which enhancements are you missing exactly? Seems handling constraintitems when hide/delete taskitems is missing, along with year scale and zoom slider. Also there are some paint issues with taskitems/itemtexts but that might be straight bugs. And there is a crash but haven't investigated yet. Anyway, is it ok to merge the missing stuff into KGantt or is there other users that may have issues with that? Afaics kdepim still has it's own copy, but there are maybe others? Right now I do not know of any other users of KGantt itself (KChart is shared with KMyMoney & Massif-Visualizer). And ideally the PIM people would start to adapt to KGantt as well, that is the whole idea here, to reduce the number of forks :) Indeed, it would be nice to avoid doing this again, this is not the first time... So should be fine to commit directly. There also was no release yet (high on my TODO list to get this scheduled though), so no API to break yet (though ideally only done on Mondays :) ). Ok, will have a look at this tomorrow. (In matters of KDE CI, when doing a ABI change, best first wait for KDiagram build to have finished and only then push the respective changes to the Calligra repo. That should save us a failed build of Calligra :) (because right now there is no dependency tracking when it comes to ABI changes)) Cheers Friedrich ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Plan/KGantt
Thanks, but we have a copy, which we hope will become the original also for kdepim (or anybody that needs a gantt chart) Regards, Dag Treeve Jelbert skrev den 2016-07-04 14:35: On Mon, 04 Jul 2016 14:05:58 +0200, Dag wrote: There are issues with KGantt that needs to fixed. It seems to me KGantt was imported from KDAB right? At least some of the enhancements made for Plan is not in KGantt. Some are but maybe those where sync'ed back to KDAB, I don't quite remember, it was a looong time ago. Anyway, is it ok to merge the missing stuff into KGantt or is there other users that may have issues with that? Afaics kdepim still has it's own copy, but there are maybe others? there is a released library kdgantt2 http://download.kde.org/stable/applications/16.04.2/src/kdgantt2-16.04.2.tar.xz It might be possible to use that. Regards, Treeve Dag ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Adding stable/l10n-kf5 translations for "krita/3.0" branch
Am Montag, 4. Juli 2016, 20:53:08 CEST schrieb Burkhard Lück: > Am Montag, 4. Juli 2016, 13:07:50 CEST schrieb Friedrich W. H. Kossebau: > > Hi translation admins, > > > > seems we forgot to set up translations for stable/l10n-kf5 when Krita 3.0 > > was branched off. > > > > The branch name for the stable release version is "krita/3.0". > > > > Please add that in the setup. > > > > If I learned things correctly last WE that the fix would be to add in > > branches/stable/l10n-kf5/scripts/get_paths for the function get_branch an > > entry like this? > > > > calligra_krita) > > > > echo "krita/3.0" > > ;; > > > > Though seems also other functions need more fixes, when I compare to the > > get_paths one for trunk, e.g. get_po_path and get_path > > > > Well, you know your scripts and I for now better try to not also mess > > around there :) > > kde_projects.xml still has: > > none > none > master > none Aha, missed that things also need to be set there. Who can do that these days? IIRC (now) that was done via projects.kde.org settings before, what is the replacement? > And what about other Calligra apps? Scripty tracks stable kde4 from > calligra/ 2.9 While the krita repo is inside the calligra domain, Krita is now an project completely independent of Calligra. Just for legacy reasons krita is still there in the repo tree, could also be extragear/graphics. "stable kde4" for "calligra/2.9" is fine still, at least kexi has some inofficial maintenance in that branch still. Hopefully what remains Calligra these days also sees a 3.0 release soon, we are working on that, will take a few more weeks. Cheers Friedrich ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Adding stable/l10n-kf5 translations for "krita/3.0" branch
Am Montag, 4. Juli 2016, 13:07:50 CEST schrieb Friedrich W. H. Kossebau: > Hi translation admins, > > seems we forgot to set up translations for stable/l10n-kf5 when Krita 3.0 > was branched off. > > The branch name for the stable release version is "krita/3.0". > > Please add that in the setup. > > If I learned things correctly last WE that the fix would be to add in > branches/stable/l10n-kf5/scripts/get_paths for the function get_branch an > entry like this? > calligra_krita) > echo "krita/3.0" > ;; > > Though seems also other functions need more fixes, when I compare to the > get_paths one for trunk, e.g. get_po_path and get_path > > Well, you know your scripts and I for now better try to not also mess around > there :) > kde_projects.xml still has: none none master none And what about other Calligra apps? Scripty tracks stable kde4 from calligra/ 2.9 -- Burkhard Lück ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
