Hello,
I'm looking for the place where digiKam technical choices are documented and it doesn't seems to be in the official wiki <https://userbase.kde.org/Digikam> To technically understand things before contribute to this great libre software, could someone give me a link? Thanks in advance, Jean-Martial ----- Mail original ----- > De: [hidden email] > À: [hidden email] > Envoyé: Lundi 16 Mars 2015 14:35:12 > Objet: Welcome to the "Digikam-devel" mailing list > > Welcome to the [hidden email] mailing list! _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Hello,
I'm looking for the place where digiKam technical choices are documented and it doesn't seems to be in the official wiki <https://userbase.kde.org/Digikam>. To technically understand things before contribute to this great libre software, could someone give me a link? Thanks in advance, -- Jean-Martial (Depuis mon mobile. Excusez ma brièveté.) _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
It's open source. It's all in the source code, which is fun to read ;-) > Hello, > > I'm looking for the place where digiKam technical choices are documented and > it doesn't seems to be in the official wiki > <https://userbase.kde.org/Digikam>. > > To technically understand things before contribute to this great libre > software, could someone give me a link? > > Thanks in advance, _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Marcel Wiesweg wrote:
> It's open source. > It's all in the source code, which is fun to read ;-) While I agree kind of with that, it would actually be awesome to have at least some kind of high-level description available. There are some class hierarchies and some hard to follow pieces of code here and there, where having a design documentation would be useful, considering that the codebase is quite big. -- Best Regards, Teemu Rytilahti _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
I written an old document (in French) when i pass my computer science
exam in 2006, where digiKam project management have been review in-deep. Perhaps this can be a good base to write a wiki page with main technical details. https://drive.google.com/open?id=0B7yq-xFihT0_Q0JBNEFhRzRCZ3c&authuser=0 Gilles 2015-04-05 2:44 GMT+02:00 Teemu Rytilahti <[hidden email]>: > Marcel Wiesweg wrote: > >> It's open source. >> It's all in the source code, which is fun to read ;-) > > While I agree kind of with that, it would actually be awesome to have at > least some kind of high-level description available. > > There are some class hierarchies and some hard to follow pieces of code here > and there, where having a design documentation would be useful, considering > that the codebase is quite big. > > -- > Best Regards, > Teemu Rytilahti > > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Too bad I can't read french .:))
We definitely need something on techbase and of course on user base, maybe Dimitri Popov can help.. About techbase. I suggest to have subcategories with current folder structure, untill we reach to sources then document what is inside. Also, for libs we need to have a short description and a tool to deploy doxygen documentation. what do you think? On Sun, Apr 5, 2015 at 9:45 AM, Gilles Caulier <[hidden email]> wrote: > I written an old document (in French) when i pass my computer science > exam in 2006, where digiKam project management have been review > in-deep. > > Perhaps this can be a good base to write a wiki page with main > technical details. > > https://drive.google.com/open?id=0B7yq-xFihT0_Q0JBNEFhRzRCZ3c&authuser=0 > > Gilles > > 2015-04-05 2:44 GMT+02:00 Teemu Rytilahti <[hidden email]>: >> Marcel Wiesweg wrote: >> >>> It's open source. >>> It's all in the source code, which is fun to read ;-) >> >> While I agree kind of with that, it would actually be awesome to have at >> least some kind of high-level description available. >> >> There are some class hierarchies and some hard to follow pieces of code here >> and there, where having a design documentation would be useful, considering >> that the codebase is quite big. >> >> -- >> Best Regards, >> Teemu Rytilahti >> >> >> _______________________________________________ >> Digikam-devel mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-devel > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
For Doxygen, all is already deployed and documentation generated. Look
links given on "API and Database schema" section from this page : https://www.digikam.org/docs Gilles 2015-04-07 14:24 GMT+02:00 Veaceslav Munteanu <[hidden email]>: > Too bad I can't read french .:)) > > We definitely need something on techbase and of course on user base, > maybe Dimitri Popov can help.. > > About techbase. I suggest to have subcategories with current folder > structure, untill we reach to sources then document what is inside. > > Also, for libs we need to have a short description and a tool to > deploy doxygen documentation. > > what do you think? > > On Sun, Apr 5, 2015 at 9:45 AM, Gilles Caulier <[hidden email]> wrote: >> I written an old document (in French) when i pass my computer science >> exam in 2006, where digiKam project management have been review >> in-deep. >> >> Perhaps this can be a good base to write a wiki page with main >> technical details. >> >> https://drive.google.com/open?id=0B7yq-xFihT0_Q0JBNEFhRzRCZ3c&authuser=0 >> >> Gilles >> >> 2015-04-05 2:44 GMT+02:00 Teemu Rytilahti <[hidden email]>: >>> Marcel Wiesweg wrote: >>> >>>> It's open source. >>>> It's all in the source code, which is fun to read ;-) >>> >>> While I agree kind of with that, it would actually be awesome to have at >>> least some kind of high-level description available. >>> >>> There are some class hierarchies and some hard to follow pieces of code here >>> and there, where having a design documentation would be useful, considering >>> that the codebase is quite big. >>> >>> -- >>> Best Regards, >>> Teemu Rytilahti >>> >>> >>> _______________________________________________ >>> Digikam-devel mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-devel >> _______________________________________________ >> Digikam-devel mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-devel > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Yes, but not on techbase...
and when I have to code something related to KDE, mostly Baloo, I can't find anything relevant ... On Tue, Apr 7, 2015 at 2:39 PM, Gilles Caulier <[hidden email]> wrote: > For Doxygen, all is already deployed and documentation generated. Look > links given on "API and Database schema" section from this page : > > https://www.digikam.org/docs > > Gilles > > > > > 2015-04-07 14:24 GMT+02:00 Veaceslav Munteanu <[hidden email]>: >> Too bad I can't read french .:)) >> >> We definitely need something on techbase and of course on user base, >> maybe Dimitri Popov can help.. >> >> About techbase. I suggest to have subcategories with current folder >> structure, untill we reach to sources then document what is inside. >> >> Also, for libs we need to have a short description and a tool to >> deploy doxygen documentation. >> >> what do you think? >> >> On Sun, Apr 5, 2015 at 9:45 AM, Gilles Caulier <[hidden email]> wrote: >>> I written an old document (in French) when i pass my computer science >>> exam in 2006, where digiKam project management have been review >>> in-deep. >>> >>> Perhaps this can be a good base to write a wiki page with main >>> technical details. >>> >>> https://drive.google.com/open?id=0B7yq-xFihT0_Q0JBNEFhRzRCZ3c&authuser=0 >>> >>> Gilles >>> >>> 2015-04-05 2:44 GMT+02:00 Teemu Rytilahti <[hidden email]>: >>>> Marcel Wiesweg wrote: >>>> >>>>> It's open source. >>>>> It's all in the source code, which is fun to read ;-) >>>> >>>> While I agree kind of with that, it would actually be awesome to have at >>>> least some kind of high-level description available. >>>> >>>> There are some class hierarchies and some hard to follow pieces of code here >>>> and there, where having a design documentation would be useful, considering >>>> that the codebase is quite big. >>>> >>>> -- >>>> Best Regards, >>>> Teemu Rytilahti >>>> >>>> >>>> _______________________________________________ >>>> Digikam-devel mailing list >>>> [hidden email] >>>> https://mail.kde.org/mailman/listinfo/digikam-devel >>> _______________________________________________ >>> Digikam-devel mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-devel >> _______________________________________________ >> Digikam-devel mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-devel > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Free forum by Nabble | Edit this page |