Quote:
Originally Posted by ErV
[...]So you'll have to write them. Which means lots of "fun". It took several years to make k3b. Years. Think about it.
|
That's not the worst part. As I said above, most of the k3b functionalities are not part of the k3b source, but the kdelibs source. What you described is just the "tip of the iceberg" (<-- not sure that's used in English,
). You would need to port (or better said, rewrite) a lot of stuff, overall if you want to preserve ripping.
All in all I don't think that's a realistic approach unless you have a dedicated team of expert kde hackers that are also proficient with some other toolkit. And even them, building from the ground would be easier.
