libtagaro -> kdereview [-> kdegames]


what is the technical procedure for moving libtagaro.git to kdereview?
I think sysadmins need be informed, and hope that those are reading

Assuming that this goes well: I hereby propose to move libtagaro to
the kdegames module after the usual review period. For the time being,
because kdegames has not yet moved from SVN, this would create a
module that is split between SVN and Git, but a similar situation
exists with kdegraphics, so I hope this is not a problem. In any
event, scm-interest is CCd if anyone wants to discuss this.

Rationale: libtagaro intends to replace libkdegames in the long run.
libkdegames was developed long before such important technologies as
QGraphicsView, QML and OCS, which define how our games work now or in
the near future. Therefore, the scope of the support library that is
libkdegames changes rapidly.

Currently, libtagaro contains
1. an advanced version of KGameRenderer from libkdegames, which adds
some further optimization opportunities and flexibility
2. a simple sound effects API which, if possible, uses OpenAL to
reduce playback latency
3. some basic layouting components for QGraphicsView-based games

Not much of this is new in the kdegames codebase. Number 2 is already
used by Granatier (by means of a static source copy), number 3 is
already used by Kolf (in the same way). Number 1 is, as I said,
heavily based on KGameRenderer which is already used by about a dozen

I want to add more components, especially to accommodate the needs of
mobile form factors, but doing so will be much easier when I can rely
on the games having a hard dependency on it. Previously, I planned to
make libtagaro a private library inside the module, but this approach
is unpractical while the rest of kdegames is still in SVN, or when
kdegames moves to Git with a split repository layout. I therefore plan
to install headers publicly, but explicitly state that there is no
API/ABI stability guarantee for the time being, i.e. SO versions will
likely be bumped often over the course of the next few 4.x releases.

I conclude my explanations with a braindump of what needs to be done:
* TagaroAudio falls back to Phonon when OpenAL is not available, but
the Phonon backend is not yet implemented. (Mathias Kraus of Granatier
helps with that.)
* No CMake find-script etc. is installed at the moment. AFAIK it would
be best to include this with the rest of the kdegames module. Also, it
is probably not state-of-the-art to detect libsndfile through
pkgconfig. Granatier has a FindSndfile.cmake which I plan to copy.
* I have not checked Krazy output for quite a while, though I think it
was empty some two months ago.



Re: libtagaro -> kdereview [-> kdegames]

By Ian Monroe at 04/21/2011 - 22:25

On Thu, Apr 21, 2011 at 06:56, Stefan Majewsky
<stefan. ... at googlemail dot com> wrote:
This doesn't make sense to me. If you want to be part of kdegames, you
should join it where it is. If I were you I would just hold off.

It's way too confusing to split modules between VCS systems and I
don't think it should be allowed (*cough* kdegraphics *cough*).


Re: Re: libtagaro -> kdereview [-> kdegames]

By Torgny Nyblom at 04/22/2011 - 09:39

On Thursday 21 April 2011 21.25.13 Ian Monroe wrote:
+1 a module is a unit and should be treated as such even if the different apps
are in different gits.


Re: Re: libtagaro -> kdereview [-> kdegames]

By Stefan Majewsky at 04/27/2011 - 05:45

On Fri, Apr 22, 2011 at 3:39 PM, Torgny Nyblom < ... at nyblom dot org> wrote:
So should I move the code to SVN then? This discussion was on
kde-games-devel already, and the mass figured it's quite stupid to
move code from Git to SVN while everything's generally moving in the
opposite direction.


Re: libtagaro -> kdereview [-> kdegames]

By Alexander Neundorf at 04/21/2011 - 08:50


On Thursday 21 April 2011, Stefan Majewsky wrote:
Any chance it could get a name which makes you kind of understand what it is ?
libkdegames was clear, and since the "it must have a K" is gone, we have more
and more stuff with weird names which say absolutely nothing to somebody who
is not involved.

How about simply libkdegames2 ?
(e.g. libpng, libjpeg, libz, libxml2, etc. are also quite "boring" names, but
you get an idea what they are good for)

I'll have a look at this on Monday or so.


Re: Re: libtagaro -> kdereview [-> kdegames]

By Shlomi Fish at 04/21/2011 - 15:50


On Thursday 21 Apr 2011 15:50:12 Alexander Neundorf wrote:

I agree with these sentiments and voiced a similar concern previously. Names
should be descriptive and "boring", not artsy. Someone on Freenode's #perl
once said that he likes the fact that in Perl's CPAN, most packages are given
boring names such as XML-Parser, CGI, XML-LibXML, Text-Table, Config-IniFiles,
etc. whereas in Ruby-land they have artsy names that do not describe their use
such as Nokogiri, jesus, god (%-)) , etc.

So I suggest giving it a more boring and descriptive name before inclusion.


Shlomi Fish

Re: libtagaro -> kdereview [-> kdegames]

By Ben Cooksley at 04/21/2011 - 08:08

On Thu, Apr 21, 2011 at 11:56 PM, Stefan Majewsky
<stefan. ... at googlemail dot com> wrote:
Project moved to KDE Review.

Ben Cooksley
KDE Sysadmin