KDEPrint on other *NIX platforms.

[Nick Bartolotti]

Chris,

Thanks for the information.  We are considering writing a front end and
filter chain for CUPS for a specialized printer but I do not want to
force the user to use KDE for the utility if they are on HP-UX 11 or
Solaris 8/9.

That is, if we write this front end using Qt/KED, how does the end-user
use the program from within CDE?  My guess is that they can't without
first reconfiguring the system to use KDE instead of CDE.  If they do
this, what affect will this have with respect to all the other
already-installed GUI applications on the system?

My guess is they will no longer work.

So what this boils down to is whether or not I have to develop and
maintain one or two sets of source code for the GUI (ignoring CPU for
the moment).

That is,

Set 1:
GUI for CDE (assuming CDE is *really* common) for HP-UX 11 and Solaris
8/9.  I expect to have to recompile on each system to get the
appropriate binaries.  I also expect minor differences that may require
conditional compilation.

Set 2:
GUI for KDE on Redhat 8.0.

What do you think?



Thanks,
Nick.
=20
Nick Bartolotti
Ten Technologies, LLC
300 Main Street, Suite 4-207
East Rochester, NY 14445
Voice: 585-586-6031, ext. 204
Fax: 585-586-4187
Web: www.tentechnologies.com
FTP: ftp.tentechnologies.com
=20

-----Original Message-----
From: Chris Howells [mailto:chris@chrishowells.co.uk]=20
Sent: Monday, March 24, 2003 11:31 AM
To: kde-print@mail.kde.org
Subject: Re: KDEPrint on other *NIX platforms.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On Monday 24 March 2003 16:19, Nick Bartolotti wrote:


> We wrote a C++ class library that wrapped the CUPS API and planned on
> using it as a middle tier between a GUI and the lower-level printing
> sub-system (CUPS).  We were planning on using this class to support a
> specific printer (although, in theory, it could support any printer).
> We did this because CUPS is supported on Linux, HP-UX, and Solaris,
our
> three target systems.
>
> Later, we found KDEPrint essentially does what we want which is why we
> started investigating its possible use on other platforms (HP-UX and
> Solaris).

Well, all that KDEPrint is is a front end to CUPS (and other print
spoolers=20
such as lpr, though CUPS is best).

> From this investigation, it seems that the desktop environment's GUI
> library must match the library used for the GUI apps.  For Redhat, I
> have read that GNOME and KDE apps are mostly compatible, but for
Solaris
> and HP-UX, the default desktop environment is CDE.  My guess is that
any
> GUI app that I want to run under CDE must be linked against the CDE
> libraries (whatever they are) as opposed to the Qt libraries.

There's nothing you installing Qt and KDE on Solaris.

And when you install KDE on Solaris it most definitely does not link to=20
Motif/CDE etc.

- --=20
Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org
Web: http://chrishowells.co.uk, PGP ID: 33795A2C
KDE: http://www.koffice.org, http://printing.kde.org,
http://usability.kde.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE+fzK5F8Iu1zN5WiwRAs9zAJ0SzcVkjIabzzjcKuBY3XvlHzaXOQCbBSDx
gPvD8vOXtNhgZDVQ7g718Ck=3D
=3DV09f
-----END PGP SIGNATURE-----

_______________________________________________
kde-print mailing list
kde-print@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-print