3.2 be vs 3.1.93

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

3.2 be vs 3.1.93
by jgraham on Monday 01/Dec/2003, @00:57

exactly how different is this from the 3.1.93 version?

jgraham

Related Links

·   Articles on Applications
·   Also by jgraham
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: 3.2 be vs 3.1.93
by Andras Mantia on Monday 01/Dec/2003, @01:12

The biggest difference between BE and the upcoming Beta2 is in the parser (and from there it comes a difference between the VPL), some new Kommander functionality and some extra bugfixes that can't be done in Beta2 due the above issues. The parser is about 2 times faster than in Beta2 when it comes to scripts and if it shows to be stable it will be merged to the official 3.2 in order to fix the most annoying bug in Quanta (#63000). Once KDE & Quanta 3.2 is released the BE releases will be the "stable development" releases of CVS HEAD. This way users without knowledge or time to regularly update from CVS will get from time to time the latest and greatest of Quanta. ;-) And unlike the CVS versions which may be broken at some point, we try to make the BE releases stable. BE releases will be English only.

Andras

[ Reply To This | View ]

Re: 3.2 be vs 3.1.93
by Eric Laffoon on Monday 01/Dec/2003, @13:48

> exactly how different is this from the 3.1.93 version?

I don't want to be too exact and reference specific commits. ;-) So in general it is very close. This is built from the quanta_be branch. It is our development branch. Currently much of what has been put in the release has been ported to HEAD so it's synced. There are small differences from HEAD and more from beta1. The parser has been reworked and sped up. A number of fixes for Kafka arrived first and resided there until we could sync the parser. IIRC there are but a few UI differences but I don't remember specifically what. Nothing huge yet. The script tab has some updates it needs I have not done yet so the functionality I hacked as a short term release for viewing the information there has this looking very functional which it is not in HEAD or the quanta_be branch.

One big point here is that many people don't want to run CVS but will download and build an application. Also many distros will end up with builds either internally or contributed. A lot of people don't realize that we have maintained backwards compatibility with KDE 3.1x in CVS too. This is a way to bring these changes to a great many more people. If you're running CVS it will be very similar. Some time before the release of KDE 3.2 I hope to release another BE with a fair number of changes. We set the date for this release and had a lot of changes... Unfortunately a lot of what would have been different from 3.1.93 just wasn't ready. We decided to go anyway considering everything in balance.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"Feature freeze means that everyone has a bad feeling when they change something, almost nothing more." -- Stephan Kulow
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.