In the latest news batch, Per Wigren
wrote in to inform us that the worthyKonCD has been added to KDE CVS. I've
used this CD burner front-end successfully in the distant past, and it has
evidently progressed in leaps and bounds since then --screenies ici. On the less fun side of things, we have had news of legal wranglings between Future Technologies (site no longer accessible -- this is the FTKDE company) and KDE
developer Mosfet who wrote the popularLiquid style, also named
FTLiquid at some point. SeeMosfet.org, Slashdot andLinuxToday to get some of the story. On a happier note,Benjamin Meyer gleefully points out that Kinkatta 1.00 is out. He
has worked hard to provide a fully functional and stable (not
to mention purty) AOL(TM) chat client. Finally, for those of you having trouble with concurrent KDE installations, Pupeno has nicely written up his experiences on installing another KDE (such as KDE CVS) alongside a stable KDE installation. He uses Mandrake 8.1, but the experience should be useful to anyone having trouble with the regular instructions.

Comments

I'm not sure if the author of kit would like this.. but looking at the fact that kit has a lot less features than kinkatta, would kit be replaced by kinkatta i dkenetwork? Does kinkatta have other depenedences?

Kinkatta has actually gone a long way in intigrating KDE into the main branch. There is a QT "branch" in which I often talk about (getting it to compile it under windows and such). But the main branch has come a long way. We now use KDE itself (as seen by the themes). We use the kde widgets (also can be seen via the themes). We use KProcess for spawning sounds etc. I have upgraded most all of the Qbla -> Kbla widgets. Other then not using the KAbout (crashes for me... and I think it is ugly and needs to be hacked another day) and the KConfig (we use a xml based file settings and I don't wish to have the users go through yet another file format transition.) The icons now install into kde's icon world (which messes up half of the time on the install on suse, mandrake, redhat... somthing intigrating into kde's cvs would fix)

So to make it "fully" kdeish I would a) redo the config file to use kconfig. b) use the kabout. c) make the chat widget xml based.

If someone wishes to submit b as a working patch I will gladly put it into cvs. As for c the base chat widget is getting a redo with the new QT3.0 functionality and while I am at it xml can be done too :)

Download the sources using CVSup
Properly configure and compile QT
Compile all the KDE packages you want, in the correct order
Install it to a directory of your choosing
Log all the output so you can figure out why it didn't finish if it doesn't

It needs a little change to convert it to QT3 and KDE 3, but other than that it works great! You just run it and walk away, the downloading and compiling is done automatically, and it can even do it in the background while you work. If you know a little about Bash scripting, download it and give it a try. Once it is set up, having the newest KDE is as easy as typing one command and waiting a couple of hours :-)

There aren't many changes. In the script itself there is a function BuildQT(). You have to change the make targets because they're changed in QT 3. Comment out the DoCmd lines that are there to make QT and add:

I'm not sure if this is strictly necessary but it keeps make from whining at you at least.

The kde-cvsbuild.conf file is where most of the changes need to be made. The readme for qt-copy in CVS says you need to set the environment variable YACC like so:

export YACC='byacc -d'

Of course this assumes you have byacc installed (apt-get install byacc for the enlightened). Also, the configure line for QT has changed in 3.0. Find the qtcfg line, comment it out, and replace it with:

That's all the changes I remember making to convert the script. Of course, you have to customize the script to your system. You have to choose where to stick the downloaded source and compiled binaries, which CVSup server to use, which packages to download/compile, and what options you want.

Yes, but only one year ago. It s quite slow, formatting a disk takes ages. Writing to a disk sometimes freezes the PC for 20 -20 seconds. Special charcters like öäüß and so on did not work in file names and I got corrputed entries in some directories.
OTOH the files I wrote on the disk worked fine and were readable with MS Windows Roxio packet-cd.

I don't know how much this has improved until now. Maybe you can try it and tell us?

I didn't have a look at the files you mention, but for converting DocBook --> html there is "meinproc". "meinproc index.docbook" should give you the according html files in the same dir. To get the style sheets, insert a symbol link to "$KDEDIR/share/doc/en/HTML/common" in the directory you have the html-files. In this dir are all graphics and stylesheets to get the KDE HelpCenter look and feel.

Hi, this whole summer, I've worked on CD burnning tool, but I've run out of time :(. Chek it out at http://cdbakeoven.sf.net. Now I have to complitely concentrate on my work. The last time I've toched the code was in early september. I've never advertized it on kde.org or apps.kde. IMHO it deserves to be complited. Take a look at it, and maybe some one will take over that thing?

hey this is cool stuff. I've never seen a greater frontend for burning cds under linux/kde. (sorry, koncd an kreatecd are not really functional) I hope for all of us that YOU will go on working on it or another guy will do it.
GOOD work, thank you :)

I was already about to give up on finding a truly good cd recording frontend for Linux (being it for gnome, kde, whatever...), but as a first impression I seem to have found it. I agree, it _really_ deserves to be completed.

This is the coolest CD burning program for Linux that I've ever used. Before I stopped using Windows about half a year ago, I used Nero, but I think CDBakeOven is easier to use and more intuitive than that. (I can't count the number of times I had to look in the help file for Nero.) I'm glad I quit using Windows. Thanks to programs like these, the free software/open-source software community can get a positive response from many Windows-to-Linux converts like me.

I really hope you can find a maintainer for CDBakeOven. I would be willing to do it, except that I'm a busy student and I have little Linux programming experience and almost no GUI programming experience. Anyway, great job.

Why did they choose KonCD? From my point of view, KreateCD is more convinient, has a better interface, from the technical it comes with filters to normalize .ogg .mp3 .au .wav to the same loudness level, which is absolutely necessary if you intend to burn audio cd s with files from different sources.
And even one more thing: It s got a lot more hits on apps.kde!

Or even more provacative: Why had any of the two programs to be chosen? Must KDE3 have a CD burner program on board, in the basic distribution? I don't really think so!

Apart from that, I still use GToaster to create my CDs because, although it's ugly as hell, it seems to be more intuitive to use for me. And sadly WinOnCD beats all Linux frontends for CD burning! I have to admit that the first Linux CD software whicht at least looked good to me is that Bake Oven stuff mentioned above. I have to compile it!