Hi,
On Fri, Jun 14, 2002 at 03:23:24PM +0200, stef wrote:
> I came across the last discussion of GUI for sane configuration. I
> agree that
> a backend should be good enough to work out of the box. But in some cases, it
> just
> can't happen. For instance the umax_pp backend cannot detect
Hello,
I came across the last discussion of GUI for sane configuration. I
agree that
a backend should be good enough to work out of the box. But in some cases, it
just
can't happen. For instance the umax_pp backend cannot detect properly which
model is
attached. Even UMAX provid
Hi,
On Thu, Apr 18, 2002 at 01:04:41AM +0200, Christian Fughe wrote:
> My suggestions:
>
> 1.) After several successful years of sane it is up to the time ( Die Zeit
> is reif :-) ) to make sane an official member of /etc/services and
> /etc/inetd.conf. I use SuSE 7.1.
I'm really surpris
Hi,
On Wed, 17 Apr 2002, Henning Meier-Geinitz wrote:
> Examples? Do you mean something like
> `./configure --net-hosts="some.server.domain"'?
Yes!
> In my opinion, we shouldn't mix installation and run-time
> configuration. After runnning ./configure ; make ; make install; SANE
> runs, that me
Hi,
On Tue, Apr 16, 2002 at 10:55:39PM +0200, Christian Fughe wrote:
> I suggest to add more options to the './configure ... and Makefile.in'
> scripts to make the knowledge of the wizards available to the wide area of
> general users as well as for generating a personal configuration.
Examples?
On Mon, 15 Apr 2002, Oliver Rauch wrote:
> But this only works when the users send enough feedback to
> the programmers so that programmers know what they have to change.
Feedback:
When I switch to a newer version of sane, it nearly works out of the box
for me. Since I do scan over a local Ethe
Hi,
> > Consider for example the path to a firmware file which has to be
> > configured. Since firmware files cannot be freely redistributed this
> > would be very hard to do without user interaction.
>
> I am not sure if we need a gui for this, a simple error message of the
> kind:
>
> copy agfa
Oliver Schwartz wrote:
>
> I think there are cases where user interaction is still necessary. Consider
> for example the path to a firmware file which has to be configured. Since
> firmware files cannot be freely redistributed this would be very hard to do
> without user interaction.
I am not sur
Hi,
> I also thought about a sane GUI configuration tool about 2 years ago.
> But this is not the correct approach. The backends and the backend
> configuration files have to come in a way that all scanners work
> without any user interaction. The sane standard allows this.
I think there are case
Yves Duret wrote:
>
> Oliver Rauch writes:
>
> > I also thought about a sane GUI configuration tool about 2 years ago.
> > But this is not the correct approach. The backends and the backend
> > configuration files have to come in a way that all scanners work
> > without any user interaction. The
Oliver Rauch writes:
> I also thought about a sane GUI configuration tool about 2 years ago.
> But this is not the correct approach. The backends and the backend
> configuration files have to come in a way that all scanners work
> without any user interaction. The sane standard allows this.
>
>
Richard wrote:
>
> It's nice to think ahead and look forward.
> But how about simplifying the backend setup ?
> Henning I did not answer your previous answer as to what i meant.
> First printconf gui is a simple interface to make printer setup easy.
> Yes i do understand that there are manuals and
12 matches
Mail list logo
