[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-promo
Subject:    Re: [kde-promo] Singlesource KDE programs database,
From:       Emil Sedgh <emilsedgh () gmail ! com>
Date:       2009-02-26 6:27:08
Message-ID: 96427b90902252215w42556a20p840650acc1e2109f () mail ! gmail ! com
[Download RAW message or body]

ah, yes, i had the same problem when creating games.kde.org and since
maintaining these data needs a lot of time i gave up on this feature
for usekde.

On 2/25/09, Friedrich W. H. Kossebau <kossebau@kde.org> wrote:
> Hi,
> 
> Le mercredi, 25. février 2009, à 16:59, Emil Sedgh a écrit:
> > but, Jos, i dont think its a lot.all we have there is just a domain
> > name and a few lines of text (which are going to be changed soon).The
> > rest is a plain cms waiting to be filled with data.
> 
> Regarding the data:
> Wouldn't it be great if there was a common database filled with all the data
> about the programs and libs in the KDE repository, the contributors
> (coders/translators/artists/ui-designers/...), the versions etc.?
> 
> A possible solution might be something kaboutdata.xml:
> 
> At the moment a lot of this data is repeated in a lot of places (KAboutData
> in
> code, handbook, userbase, homepages, bugzilla, apidox, ...) and has to be
> maintained manually, thus often isn't.
> 
> When I created the website utils.kde.org, but also when writing the manual
> for
> Okteta, I first stumbled about this problem. And thought it would be cool if
> there would be a single source for all this data. Well, for the website
> utils.kde.org there now is already a single data source for each program, so
> at least all the webpages share one data source.
> 
> Just compare
> http://websvn.kde.org/trunk/www/sites/utils/projects/okteta/development.php?view=markup
>  with
> http://utils.kde.org/projects/okteta/development.php
> 
> The clue is the line
> 	include( "project.inc" );
> which is in all <$page>.php and fetches e.g.
> http://websvn.kde.org/trunk/www/sites/utils/projects/okteta/project.inc?view=markup
> 
> The next, yet to be done, step would be to design a schema for all this
> data.
> This could be used for a file aboutdata.xml, which would be put for every
> program in the main directory of the sourcecode (in the repository) and be
> used to
> * generate the KAboutData stuff (cmp. KXConfig)
> * generate the handbook &tags;
> * generate some more data for the apidox
> * feed all the websites about the programs, like
> {$program,userbase,bugs,...}.kde.org
> * <your idea here>
> So like scripty runs to fetch the i18n data, it could also run and update a
> central database open to anyone wanting to fetch data from it, even
> 3rd-party
> (like kde-apps.org).
> 
> I would be happy to cooperate with those willing to make their hands dirty
> on
> this, by giving utils.kde.org and Okteta as testing environments (being the
> maintainer there).
> 
> So please contact me if you are working in that direction :)
> 
> Cheers
> Friedrich
> --
> Okteta - KDE 4 Hex Editor - http://utils.kde.org/projects/okteta
> 
> _______________________________________________
> This message is from the kde-promo mailing list.
> 
> Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set
> digest on or temporarily stop your subscription.
> 
 
_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on \
or temporarily stop your subscription.


[prev in list] [next in list] [prev in thread] [next in thread]