Hi all,
I would to talk about the next plan to release 5.0.0 in few weeks. This is the current status : 1/ Source code : mostly ready. - It still some points where code is not ported from old KDE to new Qt5, especially the view information on the right side bar of file dialog (metedata). This view was existing in KDE4 version because the file dialog from KDELibs permit to do it. The Qt5 file dialog cannot do it. We need to find a new solution. I think we will delay this feature for later. The old implementation is simply no compiled. - KDE dependencies are now cleaned to the max without to break anything. You must know that it's planed to provide a simple solution to compile digiKam as pure Qt5 application, as Marble do currently for ex. This imply : * translations moved from KF5::i8n to Qt5::tr. This still compatible with KDE architecture to extract strings for translators. * editor as a plugins interface, which is not shared with the rest of KDE. There is no advantage to maintain this. We plan to embed editor tools as static implementation. This will speed up startup a little bit and reduce KDE dependencies (KService, KxmlGui). * KConfig still mandatory to build digiKam core. I think we can move later from KConfig to QSettings, as Clementine do when Amarok have been forked. This will be a long task in all case. * KWindowsSystem still used in digiKam core. Some few entries in source code where we can use native Qt5 implementation instead. * Solid still used in-deep in digiKam core. I think this dependency is fine as it's a pure Qt5 library. There is no equivalent in Qt5 for the moment. * KxmlGui, KService still used in digiKam core. This is the most tedious port to move to pure Qt5 and the last one to do. All the rest is optional. Look well the DEPENDENCIES file resuming all requirements to compile digiKam. This is vcery important for packagers : 2/ Port to OSX : - Macports project still the best way to compile digiKam. This require an Apple computer. A cross compiling solution exists but nothing have been tested for the moment (https://github.com/tpoechtrager/osxcross) - but i write all bash script to prepare PKG file automatically. All compilation work fine, i need to finalize PKG build. - A 5.0.0 OSX PKG file must be provided as release announcement. 3/ Port to Windows : - Here after 3 weeks of work with MXE cross compiling frameworks, i can said that whole digiKam compile for Windows target in 32 or 64 bits "under Linux" as well. - Packaging will be done with NSIS installer also under Linux. Typically, a Windows target will be possible to do all automatically under Linux with a cron-tab. - A 5.0.0 installer for Windows must be provided as release announcement. 4/ Web Site : a lots of work to do. - KDE admin contact me to move current web site from Drupal 6 to Drupal 8 as well, for security issue. - After the migration, the Site design must be fully revamped. - A Web design student working with me in my office is ready to work on it in one week. - A new web site must be started for 5.0.0 release announcement. Voilà for the resume. If you have questions, lets me hear... Best Gilles Caulier _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 05/22/2016 02:10 PM, Gilles Caulier wrote:
> Hi all, > > I would to talk about the next plan to release 5.0.0 in few weeks. > > This is the current status : > > 1/ Source code : mostly ready. > > - It still some points where code is not ported from old KDE to new Qt5, > especially the view information on the right side bar of file dialog > (metedata). This view was existing in KDE4 version because the file > dialog from KDELibs permit to do it. The Qt5 file dialog cannot do it. > We need to find a new solution. I think we will delay this feature for > later. The old implementation is simply no compiled. > > - KDE dependencies are now cleaned to the max without to break anything. > You must know that it's planed to provide a simple solution to compile > digiKam as pure Qt5 application, as Marble do currently for ex. This imply : > > * translations moved from KF5::i8n to Qt5::tr. This still compatible > with KDE architecture to extract strings for translators. > > * editor as a plugins interface, which is not shared with the rest of > KDE. There is no advantage to maintain this. We plan to embed editor > tools as static implementation. This will speed up startup a little bit > and reduce KDE dependencies (KService, KxmlGui). > > * KConfig still mandatory to build digiKam core. I think we can move > later from KConfig to QSettings, as Clementine do when Amarok have been > forked. This will be a long task in all case. > > * KWindowsSystem still used in digiKam core. Some few entries in source > code where we can use native Qt5 implementation instead. > > * Solid still used in-deep in digiKam core. I think this dependency is > fine as it's a pure Qt5 library. There is no equivalent in Qt5 for the > moment. > > * KxmlGui, KService still used in digiKam core. This is the most tedious > port to move to pure Qt5 and the last one to do. > > All the rest is optional. Look well the DEPENDENCIES file resuming all > requirements to compile digiKam. This is vcery important for packagers : > > https://quickgit.kde.org/?p=digikam-software-compilation.git&a=blob&f=DEPENDENCIES > > 2/ Port to OSX : > > - Macports project still the best way to compile digiKam. This require > an Apple computer. A cross compiling solution exists but nothing have > been tested for the moment (https://github.com/tpoechtrager/osxcross) > > - but i write all bash script to prepare PKG file automatically. All > compilation work fine, i need to finalize PKG build. > > - A 5.0.0 OSX PKG file must be provided as release announcement. > > 3/ Port to Windows : > > - Here after 3 weeks of work with MXE cross compiling frameworks, i can > said that whole digiKam compile for Windows target in 32 or 64 bits > "under Linux" as well. > > - Packaging will be done with NSIS installer also under Linux. > Typically, a Windows target will be possible to do all automatically > under Linux with a cron-tab. > > - A 5.0.0 installer for Windows must be provided as release announcement. > > 4/ Web Site : a lots of work to do. > > - KDE admin contact me to move current web site from Drupal 6 to Drupal > 8 as well, for security issue. > > - After the migration, the Site design must be fully revamped. > > - A Web design student working with me in my office is ready to work on > it in one week. > > - A new web site must be started for 5.0.0 release announcement. > > Voilà for the resume. If you have questions, lets me hear... > > Best > > Gilles Caulier > Thanks for these good news, especially "KDE dependencies are now cleaned to the max without to break anything". I dream about a pure qt application, may be some day? Greetings -- Maderios _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
yes a pure Qt5 implementation is planed, but as usual, the last 10% are the most difficult to transform as optional. Gilles Caulier 2016-05-29 13:33 GMT+02:00 maderios <[hidden email]>:
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On 05/29/2016 03:16 PM, Gilles Caulier wrote:
> yes a pure Qt5 implementation is planed, but as usual, the last 10% are > the most difficult to transform as optional. Very good news. Thanks for your work. I hope DK5 will be available in next Fedora-24. -- Maderios _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hi gilles, Do you need some breeze-icon related stuff? With 5.7 the icon colors are themable with the color scheme so no black theme with black not visible icons any more. Riddell told me i can install dk 5 in neon dev. If you need some icon related things, let me know. Andreas kainz Am 29.05.2016 17:16 schrieb "maderios" <[hidden email]>:
On 05/29/2016 03:16 PM, Gilles Caulier wrote: _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Breeze icons ? Well yes and no. For Windows and OSX the installer and PKG image will include breeze icons included as rcc ressource file. I use the same way than Krita. Windows installer is mostly ready to test (created by cross-compiling under Linux with MXE project). Installing it under Windows indicate that some icons are missing in official breeze icon-set from KDE repository (5.22 is compiled with digiKam). This kind of problem is not reproducible under Linux. I don't know yet why. So we need to list a missing files and investigate to see it's something wrong performed while ressource packaging of icons from breeze, or if icons are really missing from official breeze repository. If you is interested to see how while cross-compiling digiKam for windows is performed under Linux, including NSIS windows installer, look in this repository : Best Gilles Caulier 2016-05-29 18:41 GMT+02:00 kainz.a <[hidden email]>:
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Windows can`t use linked icons, please use the not linked icons this would also help when use other icon set's. Am 29.05.2016 18:55 schrieb "Gilles Caulier" <[hidden email]>:
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
It work well... Look the screenshot here : This simplify also the packaging. As i have said, only few icons are just missing, as the first one from the top icons list on the left of setup dialog (Database settings), or the icon from properties tab from right side bar. Gilles Caulier 2016-05-29 19:17 GMT+02:00 kainz.a <[hidden email]>:
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |