« Return to Thread: [Cooker] New printing system
Re: [Cooker] New printing system
by Marcelo Ricardo Leitner-3
::
Rate this Message:
Tiago Salem Herrmann escreveu:
> Marcelo Ricardo Leitner escreveu:
>> Tiago Salem Herrmann escreveu:
>>>
>>>
>>> For a while, printerdrake and system-config-printer can coexist.
>>> If we decide that the new printing system is ok, we can drop
>>> printerdrake (or provide it in contrib?),
>>> and if we decide it is too early to replace printerdrake by
>>> system-config-printer, we can drop
>>> system-config-printer and go back to the place where we were before.
>>
>> That's a really big move, congrats to all involved, specially Salem :)
> thanks :)
>>
>> I know Salem and Vanessa probably handled theses tests on their shots,
>> but IMHO it's nice to make them public so people can try them out too.
>>
>> There are some combinations that should work too, like:
>> * Boot with the unconfigured printer already plugged in (cold plug),
>> you should be able to setup the printer after the first graphical login.
> Yes, Vanessa warned me about it. It can be useful, but IMO, could be
> annoying in some cases as well. For example, if an user has a printer
> that can't be
> installed on linux (multifunctional?) and uses another operating system
> in the same computer that supports this printer, every time the user
> boots on mandriva it will warn the user about a printer that can't be
> installed. But if the user really wants to install this printer, it is
> possible to access system-config-printer through menu, or mcc, when I
> finish the integration.
Hmm.. I don't know if that would be the case, as (at least printerdrake
had it) should be possible to to mark something like 'do not try to
setup this printer anymore'
Anyway, despite of the feature, IMHO it's a very rare scenario a user
that uses linux and has an unsupported printer. Now remember the common
procedure inherited from Windows: plug in and restart the system. That's
user friendly as it is on their blood already heh.
>> * Remove a configured printer while on system, reboot without it,
>> reboot again and plug it back (it shouldn't trigger 'a new printer..'
>> wizard)
> What you mean remove? remove the queue from cups, or remove the device
> from the computer?
> If you mean remove from the computer, it is working. hal_lpadmin checks
Ops, sorry, that's what I meant, unplug it.
> if there is the same id in cups and only re-enable the queue.
> (and notify the user that it was re-enabled).
Cool :)
> The way it works now: there is no wizard, when you plug your printer and
> you have all the needed software installed, it will
> automatically install your printer and only notify the user about what
> was done in a popup. At least I can't see any reasons someone would
> connect a printer to the computer and refuse the installation. If it is
> plugged, it is because the user wants it to be installed.
For sure, +1!
>> That's what I recall for now, I'll come back if I have new ideas :)
>>
>> I'll do some tests with my hp 1018 as soon as I finish upgrading my
>> box over here.
> It requires firmware upload, right?
> Wait for your feedback :)
Yes, that's the tricky one. I'm downloading tons of updates, maybe
tomorrow or next week at most I can do some testing.
Btw, new test: damn, just forgot.
(4mins after) Oh, remembered: I couldn't check how system-config-printer
is integrated with urpmi, but I assume it is via subprocessing/fork.
That would be less problematic, but it would be nice to test installing
required packages from the 3 CDs set, which I'm almost sure it will
request a media change. Just to be sure that this working properly :)
Cya
Marcelo
> Marcelo Ricardo Leitner escreveu:
>> Tiago Salem Herrmann escreveu:
>>>
>>>
>>> For a while, printerdrake and system-config-printer can coexist.
>>> If we decide that the new printing system is ok, we can drop
>>> printerdrake (or provide it in contrib?),
>>> and if we decide it is too early to replace printerdrake by
>>> system-config-printer, we can drop
>>> system-config-printer and go back to the place where we were before.
>>
>> That's a really big move, congrats to all involved, specially Salem :)
> thanks :)
>>
>> I know Salem and Vanessa probably handled theses tests on their shots,
>> but IMHO it's nice to make them public so people can try them out too.
>>
>> There are some combinations that should work too, like:
>> * Boot with the unconfigured printer already plugged in (cold plug),
>> you should be able to setup the printer after the first graphical login.
> Yes, Vanessa warned me about it. It can be useful, but IMO, could be
> annoying in some cases as well. For example, if an user has a printer
> that can't be
> installed on linux (multifunctional?) and uses another operating system
> in the same computer that supports this printer, every time the user
> boots on mandriva it will warn the user about a printer that can't be
> installed. But if the user really wants to install this printer, it is
> possible to access system-config-printer through menu, or mcc, when I
> finish the integration.
Hmm.. I don't know if that would be the case, as (at least printerdrake
had it) should be possible to to mark something like 'do not try to
setup this printer anymore'
Anyway, despite of the feature, IMHO it's a very rare scenario a user
that uses linux and has an unsupported printer. Now remember the common
procedure inherited from Windows: plug in and restart the system. That's
user friendly as it is on their blood already heh.
>> * Remove a configured printer while on system, reboot without it,
>> reboot again and plug it back (it shouldn't trigger 'a new printer..'
>> wizard)
> What you mean remove? remove the queue from cups, or remove the device
> from the computer?
> If you mean remove from the computer, it is working. hal_lpadmin checks
Ops, sorry, that's what I meant, unplug it.
> if there is the same id in cups and only re-enable the queue.
> (and notify the user that it was re-enabled).
Cool :)
> The way it works now: there is no wizard, when you plug your printer and
> you have all the needed software installed, it will
> automatically install your printer and only notify the user about what
> was done in a popup. At least I can't see any reasons someone would
> connect a printer to the computer and refuse the installation. If it is
> plugged, it is because the user wants it to be installed.
For sure, +1!
>> That's what I recall for now, I'll come back if I have new ideas :)
>>
>> I'll do some tests with my hp 1018 as soon as I finish upgrading my
>> box over here.
> It requires firmware upload, right?
> Wait for your feedback :)
Yes, that's the tricky one. I'm downloading tons of updates, maybe
tomorrow or next week at most I can do some testing.
Btw, new test: damn, just forgot.
(4mins after) Oh, remembered: I couldn't check how system-config-printer
is integrated with urpmi, but I assume it is via subprocessing/fork.
That would be less problematic, but it would be nice to test installing
required packages from the 3 CDs set, which I'm almost sure it will
request a media change. Just to be sure that this working properly :)
Cya
Marcelo
« Return to Thread: [Cooker] New printing system
| Free embeddable forum powered by Nabble | Forum Help |
