Mailinglist Archive: yast-devel (144 mails)

< Previous Next >
Re: [yast-devel] printer module redesign
  • From: Martin Schmidkunz <mschmidkunz@xxxxxxx>
  • Date: Mon, 04 Feb 2008 15:01:02 +0100
  • Message-id: <47A71A9E.2000102@xxxxxxx>
Hi Michal,

Thanks for the mockups!

Your welcome :-)
It took long enough :-)

I still wonder why do we need more tabs / lists, the vast majority of
users would have just few printers (and usually only 1) for which they
IMHO don't need such a complicated UI.

This is correct for the desktop user, but as the printer module should
also be included in SLES we need to consider larger, complexer
environments as well.

If we want to support print-servers with lots of connected printers then a
more reasonable solution could be one list, but with optional filters for
local/remote/any/whatever (which would be even more flexible for admins).

Yes, we also thought about that.
The point why we dropped it:
* as you can't add/edit/delete a remote queue there would be different
buttons needed for each queue type. This might potentially confuse the user
* if you want to add a new queue you therefore would have click on a
local queue to get an add button. This seemed quite unlogical to me.

But maybe you have any ideas how to solve this?

Moreover, as I have few local printers and few remote I'd still like to
see them all at one place, to have a nice overview.

Yes, I agree with you. The point is, that we don't know whether the user
has only a few printer or whether he uses the module in a SLES environment.

And in addition, I
could then reasonably select the Default printer, which I'm not sure is
easily doable in multi-list/tab design :)

Is it technically possible to select a remote queue as "default printer"?



Martin Schmidkunz
User Experience Specialist
+49 (0) 911 740 53-346
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

Novell, Inc.
SUSE® Linux Enterprise 10
Your Linux is ready
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >