Re: Linux Photoshop
- From: "J. Clarke" <jclarke.usenet@xxxxxxxxxxxxxxxx>
- Date: Sat, 15 Jul 2006 14:36:36 -0400
Floyd L. Davidson wrote:
"J. Clarke" <jclarke.usenet@xxxxxxxxxxxxxxxx> wrote:
My problem is that people on both sides do the denouncing without first
making at least a half-assed effort to research the product that they are
denouncing.
Then you don't have much to argue about with what I had to say.
Point taken!
But lets do look at the contortions you had to go to in an
attempt to claim at least some ground for your own...
(Just keep in mind that *you* brought these topics up, and *I*
am not saying they are particularly significant.)
In your post you go on about GIMP plugins like Photoshop doesn't have this
I did *not* "go on about". I mentioned it in passing simply
because it does exist, and then did in fact "go on about" the
fact that The GIMP does *not* try to be a do it all in one
program, and instead *does* interface well to other programs.
(Perhaps you are unfamiliar with that concept, and with The
GIMP, and didn't realize that I was *not* talking about plugins?
See your first paragraph quoted above...)
With what specific "other programs" that are not plugins do you _want_ to
use GIMP?
As for interfacing to other programs there are standard hooks in Windows to
allow this and any program that uses those hooks can interface to any other
program that uses those hooks. Many Windows applications do use them.
Look up OLE and COM.
capability when in fact not only does it have it, but there are so many
plugins available that other vendors of photo editing and artistic
software>
have been forced by popular demand to support Photoshop plugins. Even
GIMP
supports them in Windows. When there are so many useful GIMP plugins that
Corel finds themselves forced to support them then get back to me.
The point is that Photoshop *still*, with the plugins, is trying
to do *everything* all in one program, and does not attempt to
cooperate well with other tools.
What sort of "cooperation" would you like to see that cannot be handled by
OLE/COM?
That is related to the same way that typically Windows users run
whatever program they are using in full screen mode;
I still can't figure out what you're on about here. Why would one _not_
want to see as much of the image one is editing as possible? In any case,
it's one click to go from full screen to window and back.
while
people who grew up with X tend to never run anything in full
screen mode...
And I still do not understand why you attach such great importance to this.
and Windows users make little use of multiple
desktops, making several of them available is standard practice
for a unix desktop.
Which has absolutely nothing to do with application design so again I cannot
figure out why you are on about it.
Also note that the basic filesystem structure of Windows tends
to be used in a way that to execute a particular application one
should to be in a particular working directory, with a different
directory for each major application.
And I have not the _foggiest_ notion what you are on about here. Would you
be kind enough to clarify?
(On unix a user generally
has a directory for each major project, and may invoke a dozen
or more major apps from that directory. Projects are not
restricted to a single major application, or allowed to mix
applications only when using some sort of "integrated package.
On a unix box *everything* is an integrated package to some
degree.)
So? This is a choice a user makes. Again I fail to see what it has to do
with anything.
One of the, IMHO very unfortunate, results of Microsoft products
being so universal in the PC/Desktop world is that many (most?)
users tend to think that the way MS does things is necessarily
the "right" way, the best way or even the only way!
Actually, they don't. They often complain about having to keep their
documents in a user directory instead of putting them in the application
directory or the root directory or any other place they please.
It
certainly is one of *multiple* *valid* ways. Apple has a
somewhat different mindset, and so does unix. For many people
those are vastly better.
You also talk about spending hundreds of dollars to try a new package--in
fact most vendors of decent Windows software, including Microsoft, have
free trialware available.
Try using it for six months on your "free trialware".
Most Microsoft apps have 180 day time bombed versions.
Of course
one could also restructure that argument as simply stating that
to license a Microsoft product one has to spend big dollars.
For certain values of "big". Everything except the games and the developer
tools can be had with no time bombing and with multiple licenses for
$300/year with the only caveat being "no commercial use unless you are a
computer dealer".
Microsoft itself has just been fined $350 million dollars for
unfair trade practices that reduce competition for their
products. While that of course does not apply directly to
Photoshop, indirectly there is little question that all such
products cost more because Microsoft stifles competition for
Windows software.
We were discussing Photoshop, not the politics of Microsoft.
If GIMP and Linux work for you then that's the tool to use. If Photoshop
works for you that's the tool to use. If Photopaint works for you that's
the tool to use. If something else works for you that's the tool to use.
So you agree with *exactly* what I've been saying all along.
Nice, but why try to act as if you are telling me something new?
That's deceitful.
You're determined to find something to complain about.
I have *never* said there is anything wrong with using
Photoshop, have not made *any* derogatory remarks about what it
can or cannot do, and have more than once suggested that people
who are well adapted to that philosophy of program usage should
indeed use it. It boils down to 1) it is less complex to use,
and 2) you pay for that with less flexibility in what it can do.
There is no free lunch! What else is new?
If you think someone else is doing wrong by choosing a different tool from
your favorite then you're a loon.
Stacey is the only one who has made that sort of statement
(others have, but haven't chosen to belabor the point) which is
why I've been poking holes in those statements.
If you cannot follow a thread better than than, and have to
repeat exactly what other people have said, claiming to tell
them something new, then just who is the loon?
Well, now, I've told you several things earlier that you still don't seem to
understand because you've repeated them again in this post and quite
frankly I think you need to give your tone-arm a nudge.
--
--John
to email, dial "usenet" and validate
(was jclarke at eye bee em dot net)
.
- Follow-Ups:
- Re: Linux Photoshop
- From: Floyd L. Davidson
- Re: Linux Photoshop
- References:
- Linux Photoshop
- From: Anthony Blunt
- Re: Linux Photoshop
- From: Floyd L. Davidson
- Re: Linux Photoshop
- From: Stacey
- Re: Linux Photoshop
- From: Floyd L. Davidson
- Re: Linux Photoshop
- From: Stacey
- Re: Linux Photoshop
- From: Floyd L. Davidson
- Re: Linux Photoshop
- From: Stacey
- Re: Linux Photoshop
- From: Dave Martindale
- Re: Linux Photoshop
- From: Paul Mitchum
- Re: Linux Photoshop
- From: Stacey
- Re: Linux Photoshop
- From: Floyd L. Davidson
- Re: Linux Photoshop
- From: J. Clarke
- Re: Linux Photoshop
- From: Floyd L. Davidson
- Re: Linux Photoshop
- From: J. Clarke
- Re: Linux Photoshop
- From: Floyd L. Davidson
- Linux Photoshop
- Prev by Date: Re: custom white balance/exposure questions ?
- Next by Date: Re: Small Aperture Ranges in Digital Cameras--Is This Why They're Not
- Previous by thread: Re: Linux Photoshop
- Next by thread: Re: Linux Photoshop
- Index(es):
Relevant Pages
|
Loading