Nicolas.Brisset at eurocopter.com
Thu Dec 3 12:23:20 CET 2009
as a hobbyist programmer I don't have any valuable opinion on the technical details. I just want to make 2 points:
1) it may be worth asking ex-Staikos Inc's people (particularly George, Adam, Mike) who led the effort towards kst2 what they had in mind. I am sure they know all the new stuff in Qt4 and what the original intentions were and with that big picture in mind they could certainly give us good hints, even though they are no longer contracted to do the work. Hey guys, any of you still listening on this list and willing to give advice?
2) kst2 has been in preparation for a very long time now, and it has lately become useful for real work, especially on Windows where there is no kst 1.x option. I would not like to see it being postponed by weeks for such a change, even though in the long run I fully support the intention to maintain a clean code base.
In fact, it reminds me a bit of the pre-KDE 4.0 Plasma situation: if you promise great things and let people wait too long, frustration grows. That's certainly part of the reason why there is a short-term straight port going on in parallel. We should remember the so-called open-source mantra: release early, release often. That said, the quality has to be acceptable (there again, remember KDE 4.0 experience...).
The bottomline could be: once we've ascertained that Peter's proposals are the right way to go (or found a still better approach), do it now if it's short enough and there are enough developers working on it so that we get over it quickly, otherwise maybe postpone it to 2.1.
Just my 2c,
Eurocopter Deutschland GmbH
Sitz der Gesellschaft/Registered Office: Donauwoerth
Registergericht/Registration Court: Amtsgericht Augsburg HRB 16508
Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: Dr. Lutz Bertling
Geschaeftsfuehrung/Board of Management:
Dr. Wolfgang Schoder, Vorsitzender/CEO; Friedrich-Wilhelm Hormel; Ralf Barnscheidt
This communication and the information it contains is intended for the addressee(s) named above and for no other persons or organizations. It is confidential and may be legally privileged and protected by law. The unauthorized use, copying or disclosure of this communication or any part of it is prohibited and may be unlawful.
If you have received this communication in error, kindly notify us by return e-mail and discard and/or delete the communication. Thank you very much.
It is possible for e-mails to be intercepted or affected by viruses. Whilst we maintain virus checks on our e-mails, we accept no liability for viruses or other material which might be introduced with this message.
> Von: Peter Kümmel [mailto:syntheticpp at gmx.net]
> Gesendet: Donnerstag, 3. Dezember 2009 11:51
> An: kst at kde.org
> Betreff: Re: [Kst] branches/work/kst/kst1kde4/kst/src/libkst
> Peter Kümmel wrote:
> > Barth Netterfield wrote:
> >> Well...
> >> I've been grinding through doing the changes listed below.... Tedious!
> But it is worth the effort. Should I help? Then check in you changes and
> try to get a compiling branch within the next days.
> >> I admit I am a little confused about what you mean about removing the
> >> ObjectStore, and what you would replace its functionality with.
> > I thought ObjectStore is mainly used for memory management which becomes
> > obsolete when we use shared pointers.
> > The only usefull thing which I currently see is
> > DataSourceList dataSourceList() const;
> > and related functions. But this could be moved to a update class
> > splitted out from 'Object'.
> Looking again into the code it shows up ObjectStore is essential
> to current design of kst, removing it is like a redesign.
> But I simply don't like the "all is a Object" ansatz (I assume as
> you know this word ;) with all the down casting and getting objects by
> Anyway I would not touch it. We should proceed with your changes.
> Kst mailing list
> Kst at kde.org
More information about the Kst