Indeed, for the vast majority of GNU/Linux users nowadays, it is 
trivial to open xsane, and later the GIMP.

What we do have to keep in mind is that the tide is turning. Free 
Software is getting more and more used across corporations and 
governments alike.

People who works with Images and are used to proprietary software will 
sometimes search any excuse to tell bad things about free software. 
Nt being able to scan straight into the GIMP, when a Paint Shop Pro 
under windows 3.1 could do that, would be nearly shamefull. 

Actually this plugin may not be that important for the current GIMP 
users. I am worried to the upcoming ones. 

I think that bringing the xsane plugin up to date with gimp 2.0 would 
be quite an interesting thing to be done in time for the next 
releases of the big distros (witch at the moment seen to be Mandrake 
and SuSE) .


On Monday 12 January 2004 03:50, Carol Spears wrote:
> On Fri, Jan 09, 2004 at 04:40:56PM -0200, Joao S. O. Bueno wrote:
> > On Thursday 08 January 2004 23:34, Conrad Newton wrote:
> > > What is the state of scanner support for GIMP-1.3?
> > >
> > > I have been reading statements on the web that say
> > > that SANE works with GIMP-1.2 but not GIMP-1.3.
> > > Is this still the case, or has the situation changed?
> > >
> > > Thanks, Conrad
> >
> > I don't know, but IMO this issue is a __totally blocker__  for
> > 2.0 final.
> > Not only it would hurt the GIMP but the whole GNU/Linux and free
> > software, if there came out a major distribution in which a
> > previously "working"  scanner would stop working. And distros
> > will include GIMP 2, and send out GIMP 1.2.
> can you explain to me what the problem with using two different
> software apps is?
> i have a totally different perspective on this.  to me, scanning is
> scanning, pixel manipulation is pixel manipulation.  one involves a
> devise.  a scanning app manipulates a devise.  a graphics app
> manipulates pixels.
> i get grumpy because i was taught to do things this one way, and i
> liked it.  where one project does not keep another project down. 
> the complexity of keeping two projects working at the same time is
> enormous. gimp already does this with gtk+.  in return it gets all
> those widgets and a way to tell the computer what to do.  what you
> just called a blocker is one little menu entry.  and you want to
> shut the whole project down for this?
> i am trying to understand whatever could make this such an issue? 
> is there a bigger list of things that this one menu entry can do
> that i do not know about?  i would love to understand this.
> i used sane the other day.  i typed xsane& while my console was
> within the directory i wanted to save the scan to.  once the
> scanning was accomplished, i chose File-->Quit (or whatever it is)
> and then typed gimp& within this same directory.  File-->Open and
> choosing the file i had scanned and my image was there.
> is it that difficult in kde to open apps that the whole world has
> to stop for a completely separate project?  i guess i just need to
> know what you get from such a, eh, marriage of projects.  one that
> none of the good "volunteers" are willing to get into.  i know, i
> need more than one menu entry to keep a friend.  i need call backs.
>  i need help with my projects.  Computers are not people, but
> projects are.
> thanks
> carol

Gimp-user mailing list

Reply via email to