I love K3B. I hate the fact you have to have 50 megabytes of KDE installed to use it, given I don't use KDE. Is there any program that comes close to the functionality of K3B that doesn't require KDE or Gnome? I have XFCE installed so I have at least the minimal amount of desktop environment type software available to me.

I tried to install xfburn, but apparently it required a library I didn't have. And, on their site it says it is under "heavy development". Does that mean everything works, but they are improving speed, or that it is a nice frontend with no functionality? I think I'm just missing the libburnia libraries. If anyone has actually had luck with xfburn, I'll try it out again.

Anyone know what I can do?

X-CD-Roast ?
http://www.xcdroast.org/#overview

I like nero for linux , that and 2 bucks will get you a ride on the bus

Regards,
JKZfixme

there is a list of GUI front ends for CD Burning here: http://www.yolinux.com/TUTORIALS/Lin...ialCDBurn.html

Almost looks like it'd be easier to learn the command line utilities than to find an interface to them. Something interesting is the lack of DVD burner GUI's out there. Most of the programs on the list above support CDs only. Oh well. Looks like I have some reading to do.

If you really want to go for commandline tools, then you will have to face cdrecord and dvdrecord (lately called wodim). Equipped with some scripting skills you can create tools for your custom needs.

The other option would be to get the k3b source code and replace all KDE code with some other GUI library. If I would have to do something like that, I would go for FLTK or FOX-gui, because these libraries are quite small, they do not have any requirements except the X libs and they are quite portable. I you want to get rid of X as well, then use the allegro libraries with a framebuffer device. SDL is also an option.

Linux Archive

Short answer: no.

Long answer: k3b does *lots* of things, not just burning cds. Let us know *what* is the subset of functionalities that you use from k3b, and we might be able to suggest something that fits you. xcdroast is a very complete frontend and can suit almost anyone. However it's not the most friendly thing. I see very little difference between using xcdroast or using command line, since the options in cdroast are most times just literal transcriptions of the command lines options.

A simple -yet powerful- interface to the burning tools that I like and use is bashburn. However not everyone feels comfortable with a text only interface. It's really simple to use though. It also has some (if not most) of the ripping capabilities of k3b, so maybe in that respect is even closer to k3b than any graphical frontend that I know of (not that I tried so much of them lately anyway).

Replacing all the kdelibs stuff is not that easy if you want to preserve all the features. A lot of the things that make k3b an easy thing to use depends on kio-slaves and some other kde technologies that have not an immediate equivalent on any other toolkit that I know of. From memory, k3b list *at least* to kio, kdeui, kpart, kdefx and probably some other things like kdesu and kdewallet. It also needs dcop.

Remember that it has not even been ported to kde4 yet, because a lot of the stuff it depends on is either kde3-only stuff or needs important changes to work on kdelibs 4... For what it seems, it would be easier to start from the ground, even if the toolkit you want to use it qt.

I'm not really interested in the ripping as much as I am being able to burn data and iso images to CDs and DVDs. I don't burn music much so thats not really an issue, but I just need a tool that can burn and ISO with the accuracy that K3B does. I said accurate because I have even used windows tools that don't seem to boot correctly, let alone the Roxio suite thinks it has to add a file to make the CD bootable.

That makes the thing a lot better. Almost any frontend will comply with your requisites if all you need is to burn isos. Note that most apps in linux are just frontends to cdrecord and/or dvd+rw-tools. So, they all should work mostly the same provided that you use the same options.

A simple gtk frontend is graveman.

A question like this depends a lot on your perspective. For the machines that I am running at the moment, using another 50MB of HD space is of no consequence. (The smallest hard drive is 80,000 MB)
If the 50MB were in files that had to be loaded at boot time, then I suppose that might slow things down slightly, but the CD-burning SW is surely not auto-booted on most systems.

I fuss a lot over things that will make booting faster, and over things like efficiently switching users. With CD-burning SW, I just want something that works.

I've got an 80gb drive I'm installing on, so the space isn't really a huge issue. Its just that I feel it is completely unnecessary to install the core system of a bloated desktop environment to use one program and one program only. Not to mention, the 50 megs is only that size when it is still compressed, not when it is installed. I'm a barebones kinda guy. If I don't absolutely need it, I won't use it. If I like it, but it comes with too many strings attached, I'll use a scissor. Thats just me.

I recently went through a similar search for cd/dvd burning utilities with gui...I ended up with graveman for cd burning and tkDVD for dvd burning. I believe I came across tkDVD after I'd found graveman. For some reason, I couldn't get graveman to burn DVD from iso (though it would work for burning data)

Anyway, I suspect that tkDVD would work for both cd & dvd, but I'm holding on to graveman just in case...

cheers,

Graveman looks like it might do the job. Thanks for the help! We'll see how it works..

Besides wodim there are genisoimage, dvd+rw-tools tools and a few other programs.

It is not a realistic approach, not a good idea, and you can safely forget about it. Total k3b source right now takes 19 MEGABYTES, where program sources take 3 megabytes. This is 700+ files and 111230 lines of code. Can you imagine amount of work you are supposed to do to replace GUI? This will take at least 1 month (if you are genius, and you won't do anything else besides rewritting - i.e. you won't sleep, eat and go outside), and at least 6 month to catch bugs, because, basically, you'll have to rewrite everything from scratch. For comparison: developing (alone) program that has 200+ kilobytes of source code normally takes month or two, and it is said that programmer normally writes 500 lines of fully debugged code per day. So you can easily calculate how much time it'll take to replace gui. Idea about SDL/allegro wasn't good. I do not know about Allegro, but SDL has no gui functions (yes, there are libraries with GUI functions, but still there is no standard library for SDL gui functions). So you'll have to write them. Which means lots of "fun". It took several years to make k3b. Years. Think about it.