Application duplication (was: Re: cdbakeoven)

[Volker Augustin]

Hello,

IMO this discussion and the previous kde-devel discrussion are far to 
polarized. Both groups have some good arguments. Let's sum up a few:

As all frontends for cd-related matters have to deal with the various
cd-recording/-grabbing/-reading backends, it might be a good idea to
create a common layer between those backends and the frontends providing
ways for the frontends to determine which services/operations are available
on the system.
   
Depending on the purpose a frontend is developed for it might choose to
provide only some or all those operations to the user.

As the frontends will mostly share at least some operations it might also
be a good idea to share some GUI resources such as widgets, strings, icons.

Advantages:
a) less code duplication
b) more eyes on the same code / less bug reports
c) different frontends targeting different users
d) less work for translators as a lot of strings will be the same
e) maybe less work for documentation writers if there are common wizards, 
configuration dialogs and widgets.

And maybe one day there will be a common media server such as arts, just for 
cd/dvd operations :-)

Regards,
Volker Augustin