[Gimp-developer] Re: What's new in GIMP-1.3 so far

2003-06-19 Thread Shlomi Fish

From what I expected and understood from the Future of Gimp RFC:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg03656.html

Gimp 2.0 will indeed have 16-bit per colour value, CMYK, integration with
GEGL, etc. If there's still work in this direction, then I suggest making
it version 2.0, and keeping the next stable release as 1.4.

Note that a 1.4 version does not devaluate of all the hard work that was
put into the Gimp. By all means, a new secondary version in Gimp is always
a big deal, and will be very appreciated.

Best regards,

Shlomi Fish



--
Shlomi Fish[EMAIL PROTECTED]
Home Page: http://t2.technion.ac.il/~shlomif/

An apple a day will keep a doctor away. Two apples a day will keep two
doctors away.

Falk Fish
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


[Gimp-developer] Re: What's new in GIMP-1.3 so far

2003-06-19 Thread Branko Collin
On 19 Jun 2003, at 12:56, Sven Neumann wrote:
 pcg( Marc)@goof(A.).(Lehmann )com writes:
 
  Ok, here's _my_ deal: *If* you say that not calling it 2.0 would
  cause problems in fundraising, then you simply win... While my
  concerns were, for me, important enough to mention them (and argue
  about them), and while the gtk+ has 2 etc.. style of arguments
  were not convincing, this one is.
 
 We already have problems in fundraising, I can not tell you if the 2.0
 would solve them but I had that plan that involved announcing the 2.0
 release number plan. If we decide that we stick to 1.4, I'll have to
 make up a new one.

Can we know what that plan is? Perhaps we can help. I benefitted a 
lot from the feedback I got on my GIMP for Windows 1.2.3 press 
release.
 
  I still disagree on that, people are eagerly waiting for 2.0 for the
  very features it should have. Unfortunately.
 
 Are they? I don't really know what people are expecting from GEGL
 integration but it will certainly not be another GIMP once this has
 happened. When GEGL is used, users will probably not notice that the
 crappy code that provides the basis for pixel manipulations in the
 current GIMP has been replaced. We should go for GEGL soon after the
 next release but it will not be a substantial change from a GIMP users
 point of view. Only if we then add CMYK as a new colorspace and add
 proper color management functionality, really new features will be
 available. These enhancements are not provided by GEGL, GEGL only
 provides a framework that allows to do such changes in a nice and
 clean way.
 
 From all the people that addressed me and asked for CMYK support,
 only one so far was able to explain to me what benefits one can get from
 working in CMYK. All others would have made things worse since they
 would have attempted to do color separation w/o any knowledge of the
 inks and paper used to print the result. To get to a point here, CMYK
 support is IMO a bit overrated. We surely want to add it but we need
 to do it proper.
 
 You also mentioned integration with FilmGIMP or CinePaint. Well, it
 seems there is little interest from the CinePaint people, but if you
 look at the current state of GAP for GIMP-1.3, it seems that we can
 already provide quite a few of the features that film people keep
 asking for.

As to the latter, I don't think so, or there wouldn't be a Film GIMP. 
Cinepaint exists, because it fulfils a clear need. 

Yes, there is a difference between what people need and what they 
think they need. 

An example would be resolution: a completely useless measurement of 
scale, yet all the people in the print graphics business swear by it. 
I won't tell you how often art directors have asked me what the 
resolution should be for the web site designs they are making. I 
always try to educate them, tell them that only the pixels count, but 
it would probably be much easier if I told them 74 dpi or some such 
number.

Similarly, working in CMYK is not a technical necessity: it's a 
market space demand (although I personally would not mind having 
blackness as separate channel, but then preferably in a RGBK format).

So you have to ask yourself: who am I selling to? Graphics artists? 
Geeks? Buyers for large firms? Reporters? The Slashdot crowd? 
Governments? They all have different needs, and these needs may not 
be fulfilled by a pretty version number, or by features, or by 
technical prowess and progress.

If you're trying to sell GIMP progress by organising a meaningful 
GIMPcon, perhaps asking for money on Slashdot would be more useful 
than talking to one or two journalists. I don't know. What are your 
expectations? Does your experience tell you they will come true?

-- 
branko collin
[EMAIL PROTECTED]
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


[Gimp-developer] Re: What's new in GIMP-1.3 so far

2003-06-19 Thread Carol Spears
On 2003-06-19 at 1504.01 +0200, Henrik Brix Andersen typed this:
 On Thu, 2003-06-19 at 12:14, David Neary wrote:
  Sven Neumann wrote:
   Yes, please. But we probably need to get to a point here.
   GIMP-something.0 sounds pretty weird for a stable release...
  
  I say it's time for a show of hands. My vote is for 2.0, because
  there are likely to be lots of new bugs and 1.4 makes it sould
  like a really stable release.
 
 I couldn't have said it any better. A new road map (or release plan)
 will have to be written no matter if we call the next release 1.4 or 2.0
 - and changing a three year old release plan is something that most
 people involved with software will understand.
 
 I say we go for 2.0 - and, as mentioned elsewhere on this list, plan for
 a quick 2.2 bug-fix release later this year.
 
is this you volunteering to fix the wiki?

http://wiki.gimp.org/gimp/

carol

___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Re: What's new in GIMP-1.3 so far

2003-06-19 Thread pcg
On Thu, Jun 19, 2003 at 02:03:50PM +0200, Branko Collin [EMAIL PROTECTED] wrote:
 So you have to ask yourself: who am I selling to? Graphics artists? 

(off-topic philosophical rant, not meant as an answer to you!)

Personally, I didn't write gimp-perl (the only major contribution of mine
to gimp) to sell it to anybody.

I wrote it to fulfill a need. My need. This need can either be practical
(as was in this case), or philosophical (I wrote a zipcracker once simply
because I couldn't find a fere one), or being asked by people (I can do
it, and so many people want it). Another way to describe that as the
need for personal pleasure or masturbation or whatever you want to call
it.

Some people might want to sell. I don't. And everybody who tells me
marc, you have to sell it to the people will get my sincerest flame,
since I write it, you either take it, or leave it. You can comment, or
help, or criticise. But if somebody tells me that you have to xxx I cna
get rather angry, as all this you want to sell just presumes what I want
or even tries to order me around.

I know not everybody thinks that way. Alan Cox probably thinks similarly,
Linus doesn't. There are all sorts of people.

And not all of them feel that selling something they wrote is a must, or
a need, or even useful.

-- 
  -==- |
  ==-- _   |
  ---==---(_)__  __   __   Marc Lehmann  +--
  --==---/ / _ \/ // /\ \/ /   [EMAIL PROTECTED]  |e|
  -=/_/_//_/\_,_/ /_/\_\   XX11-RIPE --+
The choice of a GNU generation   |
 |
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer