Roland Krause
rokrau at yahoo.com
Tue Mar 26 22:53:04 UTC 2002
--- kdevelop-devel-request at barney.cs.uni-potsdam.de wrote:
> Send Kdevelop-devel mailing list submissions to
> kdevelop-devel at barney.cs.uni-potsdam.de
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
> or, via email, send a message with subject or body 'help' to
> kdevelop-devel-request at barney.cs.uni-potsdam.de
>
> You can reach the person managing the list at
> kdevelop-devel-admin at barney.cs.uni-potsdam.de
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Kdevelop-devel digest..."
>
> > Today's Topics:
>
> 1. Re: Status of KDEVELOP_2_BRANCH? (Roland Krause)
> 2. Re: KDE_2_2_BRANCH closed now, KDevelop Roadmap (Christoph
> Cullmann)
> 3. Re: gideon refactoring (Victor Roeder)
> 4. Re: kdevelop & gideon's parts (Roland Krause)
> 5. Re: Kdevelop-devel digest, Vol 1 #182 - 14 msgs (Roland Krause)
> 6. Re: KDE_2_2_BRANCH closed now, KDevelop Roadmap (Roland Krause)
> 7. Re: codecompletion's port (Mathieu Chouinard)
> 8. Ported Gideon core to KTextEditor interface (Harald Fernengel)
> 9. Re: KDE_2_2_BRANCH closed now, KDevelop Roadmap (Harald
> Fernengel)
> 10. Re: gideon refactoring (Sandy Meier)
> 11. Crisis of a marriage? (Victor Roeder)
> 12. Re: gideon refactoring (Harald Fernengel)
> 13. Re: gideon refactoring (Matthias
> =?iso-8859-1?q?H=F6lzer-Kl=FCpfel?=)
> 14. Re: Crisis of a marriage? (ian reinhart geiser)
>
> ATTACHMENT part 3.1 message/rfc822
> Date: Tue, 26 Mar 2002 11:41:50 -0800 (PST)
> From: Roland Krause <rokrau at yahoo.com>
> Subject: Re: Status of KDEVELOP_2_BRANCH?
> To: kdevelop-devel at kdevelop.org
> Reply-to: kdevelop-devel at kdevelop.org
>
> > 10. Re: Status of KDEVELOP_2_BRANCH? (Roberto Raggi)
>
> > Subject: Re:
> > Reply-to: kdevelop-devel at kdevelop.org
> >
> > hi roland, hi all,
> > i've just added gideon sdk and implemented part loader.. what do
> you
> > think
> > to replace gideon's keditor-interface with kate/ktexteditor?
>
> Where? In gideon? KDevelop-2.1 should not have keditor-interface, it
> is
> obsolete.
>
> Roland
>
>
> >
> > ciao robe
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Movies - coverage of the 74th Academy Awards®
> http://movies.yahoo.com/
>
>
> ATTACHMENT part 3.2 message/rfc822
> From: Christoph Cullmann <cullmann at babylon2k.de>
> To: kdevelop-devel at kdevelop.org
> Subject: Re: KDE_2_2_BRANCH closed now, KDevelop Roadmap
> Date: Tue, 26 Mar 2002 20:44:54 +0100
> Reply-to: kdevelop-devel at kdevelop.org
>
> On Tuesday 26 March 2002 17:30, gigafalk at yahoo.com wrote:
> > Hi!
> >
> > The cvs release tag for KDevelop-2.1 is done. Means, KDevelop-2.1
> is
> > technically out now.
> > Seems to be a good version...
> > Let's wait for the packages and the official KDE announce.
> >
> > That is why I want to have a confirmation in the KDevelop team
> about a
> > roadmap for the next weeks:
> >
> > 1.) KDE_2_2_BRANCH is now closed for further development
> > 2.) all further changes on KDE_2_2_BRANCH will get into
> KDevelop-2.1.x
> > versions.
> > 3.) each commit to KDE_2_2_BRANCH requires a sent patch to
> > kdevelp-devel at kdevelop.org and the OK of at least one KDevelop core
> > developer. (Just to keep the stability and KDE2 portability)
> > 4.) All feature commits will be rejected
> > 5.) KDE-3.0.1 will release KDevelop-2.1.1
> >
> > 6.) The next KDevelop version is 2.2 made from KDEVELOP_2_BRANCH
> which
> > is for KDE3, only
> > 7.) We will not release KDevelop-2.2 with KDE-3.1, if it isn't as
> stable
> > as version 2.1. In that case we don't want to get bundled or give
> them
> > just another bugfix version of 2.1
> > 8.) We need a roadmap for what can be adapted from Gideon to get a
> > stable KDevelop-2.2 as soon as possible.
> >
> > Everybody, please, confirm to (or deny) these with your reply to
> the
> > list.
> Sounds like a good idea ;) (even I I wouldn't have to much time for
> help out
> ;)
>
> >
> > Next, I would like to update www.kdevelop.org with these decisions.
> >
> > Cheers
> > F at lk
> >
> >
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >
> > _______________________________________________
> > Kdevelop-devel mailing list
> > Kdevelop-devel at barney.cs.uni-potsdam.de
> > http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
> --
> Christoph Cullmann
> Kate/KDE developer
> cullmann at kde.org
> http://kate.kde.org
>
>
> ATTACHMENT part 3.3 message/rfc822
> From: Victor Roeder <victor_roeder at gmx.de>
> To: kdevelop-devel at kdevelop.org
> Subject: Re: gideon refactoring
> Date: Tue, 26 Mar 2002 22:09:21 +0100
> Reply-to: kdevelop-devel at kdevelop.org
>
> Hi, Matthias!
>
> > as I have not been active on this list for a long time, I think I
> should
> > start telling this story from the beginning:
> >
> > I recently learned to know IntelliJ's IDEA, a very cool Java IDE (I
> have a
> > new job, so I have to do stuff like Java more and more often...).
> Well, I
> > fell in love with that tool.
>
> Hey! Very cool! We (at our university) are using this tool, too! And
> it is
> really great. AND: I thought that this IDE(A) could be very cool
> model for
> Gideon. I had a little talk about IDEA with Sandy, so that this
> situation is
> REALLY cool :-)!
>
> > Three weeks ago, I told Cornelius about IDEA's incredibly user
> interface,
> > and he said something like "How long can it take to put something
> like that
> > into gideon?" Well, the answer is: about three weeks.
>
> Three weeks? Hacking 24/7 :-)?
>
> > So I took the rest of spare time I have left, and started to hack
> on gideon
> > again. Stupid as I am, I did several things at once:
> >
> > 1) I completely refactored the core.cpp code. It is now contained
> in about
> > 5 small classes, each serving a single purpose.
> >
> > 2) I implemented a first version of a zoom-tab-widget like the ones
> used in
> > IDEA and put them in place. (You have to have a look at IDEA, you
> will
> > never be able to live without them).
>
> :-)
>
> > 3) I dropped the old editor interfaces, and made use of the new
> ones.
>
> Very COOL!
>
> > Well, I didn't completely follow through with 3, as I didn't want
> to start
> > changing all the parts right now.
> >
> > The result of this work can be obtained from:
> >
> > http://verein.lst.de/~mhk/gideon/newframe.tgz
>
> I will have a look ASAP!
>
> > It is just a tarball that you can put beside the 'src' directory in
> gideon.
> > Do the usual Makefile.cvs, configure, make stuff, and you get a new
> binary
> > to play with. (You might have to disable some of the plugins in
> gideonrc,
> > as some of the parts don't like the new structure yet.)
> >
> > Now from the three steps I did, I think that 1) is smart if one
> intends to
> > continue the gideon development, as it makes live a lot easier. (It
> isn't
> > nearly finished, as there is a kludge in place to account for the
> KDevApi
> > class, which should be refactored next. Rather see it as a first
> step).
> >
> > Step 3 I guess has been agreed on by everyone here, so this will
> have to be
> > applied to the parts sooner or later anyway.
> >
> > This leaves 2), and this one will be controversial, I guess. But if
> you
> > look at toplevel.cpp, you will see that changing the UI model is a
> matter
> > of replacing 50 lines in a single class, so it is nothing really
> important.
> >
> > So I would ask you to have a look at the tarball and tell me if you
> like
> > it. I would love to replace the code in src with the new one, and
> go on
> > doing a lot of necessary refactorings, like putting the new editor
> > interfaces completely into use, refactoring the lib interfaces etc.
> etc.
> > But I won't do something like that without consent from this list,
> not
> > again ;)
>
> I think I don't have to tell more about my agreement :-).
> Really cool!
>
> Bye,
> Victor
>
>
> ATTACHMENT part 3.4 message/rfc822
> Date: Tue, 26 Mar 2002 12:15:44 -0800 (PST)
> From: Roland Krause <rokrau at yahoo.com>
> Subject: Re: kdevelop & gideon's parts
> To: kdevelop-devel at kdevelop.org
> Reply-to: kdevelop-devel at kdevelop.org
>
> > 5. kdevelop & gideon's parts (Roberto Raggi)
> > From: Roberto Raggi <raggi at cli.di.unipi.it>
> > Subject: kdevelop & gideon's parts
> >
> > hi all,
> > kdevelop2.2 can load gideon's part ;-)
> > see http://klint.sourceforge.net/kdevelop/kdev_parts.png
> >
> > ciao robe
>
> Awesome!
>
> Robe, you just earned a bottle of wine, send me your address and I
> get
> it on the way today.
>
> Roland
>
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Movies - coverage of the 74th Academy Awards®
> http://movies.yahoo.com/
>
>
> ATTACHMENT part 3.5 message/rfc822
> Date: Tue, 26 Mar 2002 12:17:14 -0800 (PST)
> From: Roland Krause <rokrau at yahoo.com>
> Subject: Re: Kdevelop-devel digest, Vol 1 #182 - 14 msgs
> To: kdevelop-devel at kdevelop.org
> Reply-to: kdevelop-devel at kdevelop.org
>
> > 8. Re: kdevelop & gideon's parts (Mathieu Chouinard)
>
> > Subject: Re: kdevelop & gideon's parts
> > Can you change the name of the executable so we can have
> kdevelop2.1,
> > 2.2 and
> > gideon on the same machine
> > Mathieu
>
> No!!!
> Please do not change names, either install KDevelop in it's own
> directoru or use --suffix or --prefix. The name is and will remain
> KDevelop.
> Roland
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Movies - coverage of the 74th Academy Awards®
> http://movies.yahoo.com/
>
>
> ATTACHMENT part 3.6 message/rfc822
> Date: Tue, 26 Mar 2002 12:23:31 -0800 (PST)
> From: Roland Krause <rokrau at yahoo.com>
> Subject: Re: KDE_2_2_BRANCH closed now, KDevelop Roadmap
> To: kdevelop-devel at kdevelop.org
> Reply-to: kdevelop-devel at kdevelop.org
>
> Falk,
> I agree with you mostly, but:
>
> Let us make bugfixes into KDEVELOP_2_BRANCH please. One has to tag it
> once before and once after the commit and then merge the change into
> KDE_2_2_BRANCH. This is a little extra work but will greatly enhance
> the time needed to get KDEVELOP_2_BRANCH stable.
>
> Btw:
> Congratulations to you all. Very good work, I use it and I love it.
>
> Roland
> > 8.) We need a roadmap for what can be adapted from Gideon to get a
> > stable KDevelop-2.2 as soon as possible.
>
> Yes, we do, see an earlier post.
>
> > Cheers
> > F at lk
>
> Wow, what a day!
> Roland
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Movies - coverage of the 74th Academy Awards®
> http://movies.yahoo.com/
>
>
> ATTACHMENT part 3.7 message/rfc822
> From: Mathieu Chouinard <chouimat at videotron.ca>
> To: kdevelop-devel at kdevelop.org
> Subject: Re: codecompletion's port
> Date: Tue, 26 Mar 2002 15:24:09 -0500
> Reply-to: kdevelop-devel at kdevelop.org
>
> [Roland Krause reply]:
> > > 3. Re: codecompletion's port (Mathieu Chouinard)
> > >
> > > Subject: Re: codecompletion's port
> > >
> > > Does this gideon part support will enable me to build part
> > > standalone, or I
> > > will need to build them in kdevelop or gideon.
> > > Mathieu
> >
> > What do you mean? You want to work on parts for KDevelop but not
> use
> > KDevelop?
> > I dont understand?
> >
> > Roland
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Movies - coverage of the 74th Academy Awards®
> > http://movies.yahoo.com/
> >
> > _______________________________________________
> > Kdevelop-devel mailing list
> > Kdevelop-devel at barney.cs.uni-potsdam.de
> > http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
> I want to compile my part without recompiling kdevelop
> Mathieu
> --
> You'll feel much better once you've given up hope.
>
>
>
> ATTACHMENT part 3.8 message/rfc822
> From: Harald Fernengel <harry at kdevelop.org>
> To: kdevelop-devel at kdevelop.org
> Subject: Ported Gideon core to KTextEditor interface
> Date: Tue, 26 Mar 2002 21:29:11 +0100
> Reply-to: kdevelop-devel at kdevelop.org
>
> Hi,
>
> okay, my third rewrite now works:
>
> http://www.bnro.de/~harry/gideon/
>
> as you can see I commented out quite a bit of code, but that's only a
> matter
> of changing KEditor calls to KTextEditor calls and should be quite
> trivial.
>
> What works: You can use any editor that implements the KTextEditor
> interface
> (currently hard-coded to Kate :))
>
> What doesn't work: Most of the parts, they have to be changed to
> KTextEditor
> first and anything that includes more than opening, changing and
> closing a
> file ;)
>
> Consider this a proof of concept that KTextEditor actually works in
> Gideon
> without too heavy code changes.
>
> The road ahead: Finish this patch, change all the parts to
> KTextEditor
> interface, finish the KTextEditor document/view manager.
>
> Roland: If KDevelop 2.2 operates on KTextEditor, it would be very
> easy to use
> Gideon parts also for KDevelop 2.2. Also, do you think we could use
> my
> generic doc/view manager in both branches (if it gets a bit more
> mature...)?
>
> Best regards,
> Harry
>
>
> ATTACHMENT part 3.9 message/rfc822
> From: Harald Fernengel <harry at kdevelop.org>
> To: kdevelop-devel at kdevelop.org
> Subject: Re: KDE_2_2_BRANCH closed now, KDevelop Roadmap
> Date: Tue, 26 Mar 2002 21:44:01 +0100
> Reply-to: kdevelop-devel at kdevelop.org
>
> Hi,
>
> > 1.) KDE_2_2_BRANCH is now closed for further development
> > 4.) All feature commits will be rejected
>
> ... except those by harryF ... ;)
>
> > 8.) We need a roadmap for what can be adapted from Gideon to get a
> > stable KDevelop-2.2 as soon as possible.
>
> I totally agree.
>
> On my TODO:
>
> * port Gideon to KTextEditor interface
> * port Gideon's KEditor parts (NEdit, QEdit...) to KTextEditor and
> put them
> into kde-addons module so that all apps can use them
> * port KDevelop 2 to KTextEditor interface (if possible) so that
> Gideon
> Plugins should work nicely in both KDevelop versions.
>
> Best regards,
> Harry
>
>
> ATTACHMENT part 3.10 message/rfc822
> From: Sandy Meier <smeier at kdevelop.org>
> To: kdevelop-devel at kdevelop.org
> Subject: Re: gideon refactoring
> Date: Tue, 26 Mar 2002 21:55:52 +0100
> Reply-to: kdevelop-devel at kdevelop.org
>
> Hi!
> > So I would ask you to have a look at the tarball and tell me if you
> like
> > it. I would love to replace the code in src with the new one, and
> go on
> > doing a lot of necessary refactorings, like putting the new editor
> > interfaces completely into use, refactoring the lib interfaces etc.
> etc.
> > But I won't do something like that without consent from this list,
> not
> > again ;)
>
> You get my vote. There were no commits in the last weeks so go ahead.
> :-)
>
> Ciao!
> Sandy
>
>
> ATTACHMENT part 3.11 message/rfc822
> From: Victor Roeder <victor_roeder at gmx.de>
> To: kdevelop-devel at kdevelop.org
> Subject: Crisis of a marriage?
> Date: Tue, 26 Mar 2002 23:08:59 +0100
> Reply-to: kdevelop-devel at kdevelop.org
>
> Hi!
>
> After talking to Roland and Sandy, I see the reason talk some clear
> words.
> First of all the situation right now:
> 1) KDevelop 2.2 will be able to load several Gideon plug-ins.
> 2) The development of Gideon is everything but positive and
> coordinated.
>
> Roland (and I think the whole 'KDevelop2-Developer') are not willed
> any
> longer to develop Gideon parts. And that's quite comprehensible.
> Roland wrote
> a sentence that nearly brings the facts in perspective: We are
> communicating
> via the source codes of each other and not via email.
>
> Now I have some questions to be answered:
> 1) Is there an exorbitant interest in Gideon (under this developers
> here)?
> 2) Does it make sense to separate Gideon development from KDevelop
> development? In this case (I think) KDevelop 2.2 will keep the name
> KDevelop
> and Gideon (if there are developers) will relocate to Sourceforge (or
>
> something comparable).
>
> Please tell me your matured opinions! The situation right now is
> *not* good.
> When it comes to a separation, please keep cooperative and
> compatibility :-),
> because I think that KDevelop is more or less compatible to Gideon is
> really
> cool.
>
> Bye,
> Victor
>
>
> ATTACHMENT part 3.12 message/rfc822
> From: Harald Fernengel <harry at kdevelop.org>
> To: kdevelop-devel at kdevelop.org,
> Matthias Hölzer-Klüpfel <mhk at kde.org>
> Subject: Re: gideon refactoring
> Date: Tue, 26 Mar 2002 22:09:39 +0100
> Reply-to: kdevelop-devel at kdevelop.org
>
> On Tuesday 26 March 2002 21:14, Matthias Hölzer-Klüpfel wrote:
> > 2) I implemented a first version of a zoom-tab-widget like the ones
> used in
> > IDEA and put them in place. (You have to have a look at IDEA, you
> will
> > never be able to live without them).
>
> Is it a good IDEA to have those tabs floating in front of the editor?
> :) Where
> can I get some screenshots of IDEA, I browsed the site but all I got
> was
> their feature matrix...
>
> > 3) I dropped the old editor interfaces, and made use of the new
> ones.
>
> PLEASE don't spend any work on it since I basically already did it. I
> think
> there shouldn't be much trouble to merge our patches as soon as your
> work is
> in CVS.
>
> I vote for "commit it".
>
> Best regards,
> Harry
>
>
>
>
> ATTACHMENT part 3.13 message/rfc822
> From: Matthias Hölzer-Klüpfel <mhk at kde.org>
> To: kdevelop-devel at kdevelop.org
> Subject: Re: gideon refactoring
> Date: Tue, 26 Mar 2002 23:34:58 +0100
> Reply-to: kdevelop-devel at kdevelop.org
>
> Tue, 26 Mar 2002 23:30:17 +0100On Tuesday 26 March 2002 22:09, you
> wrote:
>
> > Is it a good IDEA to have those tabs floating in front of the
> editor? :)
>
> Well, yes and no. IDEA has two modes: In the normal one, you get the
> tabs on
> top of the editor. As soon as you select a file, e.g. in the FileSel,
> the tab
> closes and put's you right into the editor. (In fact, it will close
> when you
> double click, and stay on top if you single click). This is _very_
> neat, as
> you get maximum screen space, and can still access classes and files
> quickly.
> I will implement the auto-closing, it will just need a small
> modification to
> the part interfaces.
>
> The second mode will get you a splitter and put the tab next to the
> editor.
> This is nice, but a bit more work to implement, so I left it for
> later ;)
>
> > Where can I get some screenshots of IDEA, I browsed the site but
> all I got
> > was their feature matrix...
>
> Well, you can download the IDEA. It is a Java app, and runs well.
> Only problem
> is that the eval key expires after 3 week ;(
>
> > > 3) I dropped the old editor interfaces, and made use of the new
> ones.
> >
> > PLEASE don't spend any work on it since I basically already did it.
> I think
> > there shouldn't be much trouble to merge our patches as soon as
> your work
> > is in CVS.
>
> Well, after the restructuring, I essentially got this one for free ;)
>
> > I vote for "commit it"
>
> Ok, will do.
>
>
> Bye,
> Matthias.
>
>
> ATTACHMENT part 3.14 message/rfc822
> From: ian reinhart geiser <geiseri at yahoo.com>
> To: kdevelop-devel at kdevelop.org
> Subject: Re: Crisis of a marriage?
> Date: Tue, 26 Mar 2002 16:24:33 -0500
> Reply-to: kdevelop-devel at kdevelop.org
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have been wanting a fork for some time, I think both KDevelop and
> Gideon are
> now wanting to go down two different paths, and the developers all
> share
> different ideals. I think it would be best for both projects (and
> yes there
> are two) to go there separate ways and mature on their own paths not
> chained
> to eachother.
>
> Just my 2c, but as soon as April 1st hits I am free to finish my
> gideon
> packageing plugin.
>
> I like what gideon is becomming, and I like the direction it can go,
> if we let
> it.
>
> - -ian reinhart geiser
>
> On Tuesday 26 March 2002 05:08 pm, Victor Roeder wrote:
> > Hi!
> >
> > After talking to Roland and Sandy, I see the reason talk some clear
> words.
> > First of all the situation right now:
> > 1) KDevelop 2.2 will be able to load several Gideon plug-ins.
> > 2) The development of Gideon is everything but positive and
> coordinated.
> >
> > Roland (and I think the whole 'KDevelop2-Developer') are not willed
> any
> > longer to develop Gideon parts. And that's quite comprehensible.
> Roland
> > wrote a sentence that nearly brings the facts in perspective: We
> are
> > communicating via the source codes of each other and not via email.
> >
> > Now I have some questions to be answered:
> > 1) Is there an exorbitant interest in Gideon (under this developers
> here)?
> > 2) Does it make sense to separate Gideon development from KDevelop
> > development? In this case (I think) KDevelop 2.2 will keep the name
> > KDevelop and Gideon (if there are developers) will relocate to
> Sourceforge
> > (or something comparable).
> >
> > Please tell me your matured opinions! The situation right now is
> *not*
> > good. When it comes to a separation, please keep cooperative and
> > compatibility :-), because I think that KDevelop is more or less
> compatible
> > to Gideon is really cool.
> >
> > Bye,
> > Victor
> >
> > _______________________________________________
> > Kdevelop-devel mailing list
> > Kdevelop-devel at barney.cs.uni-potsdam.de
> > http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
> - --
> :-- Ian Reinhart Geiser --:
> GPG Key: D6A6 7E16 13A9 B5A7 9E18 D1A7 3F2E B64D 19BC 76F8
> - -----BEGIN GEEK CODE BLOCK-----
> Version: 3.12
> GE d- s+:+ a- C++++ UL+++ P--- L+++ E- W++ N- o- K--- w-
> M+ V-- PS+ PE- Y+ PGP++ t-- 5-- X R++ tv- b+ DI++ D++
> G++ e++ hasciicam-0.9 r+++ y**
> - ------END GEEK CODE BLOCK------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iD8DBQE8oOcSPy62TRm8dvgRAswcAJ9jm5U3WAYYzQR58Sum8LWQ9UwkaACdES4p
> fBANE0HvAanPJ08ncIb8f4g=
> =CshK
> -----END PGP SIGNATURE-----
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
>
>
> > _______________________________________________
> Kdevelop-devel mailing list
> Kdevelop-devel at barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Movies - coverage of the 74th Academy Awards®
http://movies.yahoo.com/
More information about the KDevelop-devel
mailing list