New module for KPovModeler
coolo at kde.org
Thu Jan 9 08:25:04 GMT 2003
Am Mittwoch, 8. Januar 2003 21:06 schrieb Andreas Zehender:
> Stephan Kulow wrote:
> >>The number 500 is of course rather arbitrary, if people prefer to have
> >> many seperate CVS modules one could put the treshold at 200.
> > I very much agree with Waldo on this. I can't see what makes kpovmodeler
> > more special or more interesting or whatever than k3b. And we created
> > kdeextragear for exactly that kind of application: well maintained and
> > too special for general distribution.
> The question is only if kpovmodeler is big enough to justify a new
> module. Comparisons with other applications, especially calculating
> source files doesn't help much here.
> I just don't want another move if the size of the program reaches a
> given threshold. We moved often enough already.
> And the program _will_ grow. I am about to finish a plugin framework. I
> expect some big plugins like recursive plant generators or landscape
> generators. We need to add new POV-Ray 3.5 objects. There are several
> POV-Ray variants...
> Don't consider only the current size.
> Don't get me wrong. I can live with a move to kextragear but would
> suggest that such big applications get their own module.
Well, every new module creates more work on me. Not only a couple of scripts
have to be extended, you also have to explain the translators, check one more
module on release, etc. We had that desaster with quanta (which is in it's own
module because it went there when kdeextragear didn't exist and then shortly
before 3.1 it wanted to be part of the release).
My opinion on this module number issue hasn't changed much over the years:
if you don't have another app to be grouped with, leave it in kdegraphics when
you want to be part of 3.2. If you want to release independent, go into
More information about the kde-core-devel