[ghns] KNewStuff2

[Josef Spillner]

Am Sonntag 06 Januar 2008 14:18:39 schrieb Frederik Gladhorn:
> Hi all, hi Josef
> apart from wishing you all a happy new year, I'd like to address a few
> things in kns2.
> KDE 4.0.0 is out, and we have a mostly working ghns implementation.
> Thanks especially to Jeremy.

Yeah, thank to all those who got involved in the past months and did all the 
work.

> A few things came up during the last minute fixes that were not possible to
> be tackled immediately or more on the server side and thus not so urgent
> for 4.0.0.
>
> The .knsrc files which contain config options to be set for ghns in KDE.
> One option is the compression. We discussed on irc and it would be nice to
> be able to set the compression rather per file. In my use case for example
> (vocabulary files) I want to be compatible with the kde3 files. I want to
> use the same feed as KVocTrain for that purpose. No need to duplicate the
> work really. KVocTrain only uses not compressed files.
> But file size and the possibility to include sound/image files for Parley
> makes compression a necessity for the KDE4 files.
> So either compression is set per file (in the .meta files) or we check for
> the mime type and decompress if it's compressed. Right now the config
> setting is respected very strictly - if set to uncompress, only compressed
> files are accepted and vice versa.
> Thoughts on that appreciated.

I'd suggest not using the uncompression handler then and deciding this on a 
per-entry or per-file basis within the application. This is where we probably 
really need to wait for ruphy's package handler which is supposed to 
introduce more logic on what a package actually contains.

> For Kalzium it would be great if the sever could split the feeds included
> in the provider file into categories. This use case of ghns is a little
> different, as molecule files probably won't need much in the sense of
> rating etc but rather a certain molecule is wanted. So I know I want an
> alcohol (who wouldn't) I want to choose the category and select the one I
> want. That's probably to be discussed with Carsten in detail.

This should already be doable from the client side by settings different 
categories such as kalzium/molecule/alcohol and kalzium/molecule/metal, for 
example.
I saw Carsten's recent commit and will try to make something out of it.

> The precommit hook on data.kstuff.org is rather restrictive - it requires a
> strict order of the meta data tags. maybe that could be loosened a bit.
> Carsten also just hit that one (Josef, we discussed this on irc, when
> setting up Marble).

True, I wanted to look into the issue of having a better schema which doesn't 
fix the order of the elements. This is one of the tasks I can thankfully do in 
my work time :-)

> The only trigger for an update is when the date in the .meta file is
> changed. It would probably be more intuitive to use (and maybe easier?) to
> simply update after any change to the .meta file or even file itself.

What I had in mind here is that the date could be taken automatically from the 
commit time. Thus, each commit would produce a new version automatically, 
although not always with an increased version number.

Josef