Hi,
On Mon, 2007-11-05 at 22:34 -0800, Valerie VK wrote:
Are there any plans for a Future feature page on the GIMP
website?
You obviously completely missed that we are currently discussing the
roadmap for 2.6 on this mailing-list. The goal is to get this task list
published by the end of
I wrote:
I do take the hart of the matter [...] serious.
really, I did not mean an adult male deer,
I meant 'the heart of the matter...'
--ps
founder + principal interaction architect
man + machine interface works
http://mmiworks.net/blog : on interaction
Sven wrote:
So could we please stop talking about
some completely irrelevant article and instead deal with the actual
problem? Thank you.
since I am responsible for this 'department', I do want to say
something, but I'll keep it short.
I do take the hart of the matter, which is behind that
Alexandre Prokoudine alexandre.prokoudine at gmail.com writes:
Solve the transparency problem, and the criticism will go away.
You say what to do, but you don't say how.
Very simple: Peter has a blog, right? and very occasionaly, he posts something
relevant to the Gimp UI, such as the
Michael Grosberg wrote:
Very simple: Peter has a blog, right? and very occasionaly, he
posts something
relevant to the Gimp UI, such as the post about the print dialog.
uhm, the print dialog stuff is for openPrinting. That project plots
the future of printing for all linux desktop systems.
On Tue, 06 Nov 2007 22:47:12 +0100, peter sikking [EMAIL PROTECTED]
wrote:
I wrote:
I do take the hart of the matter [...] serious.
really, I did not mean an adult male deer,
I meant 'the heart of the matter...'
you probably also meant seriously. I'm surprised an intelligent dutchman
On 11/5/07, Valerie VK wrote:
This is why I suspect it to be a transparency problem and not really
a process problem. People actually Won't criticize a process if they
think it is doing a good job. In the case of the GUI team, we don't
know if it's doing a good job. In fact, we don't see a
2007/11/5, Alexandre Prokoudine [EMAIL PROTECTED]:
Solve the transparency problem, and the criticism will go away.
You say what to do, but you don't say how.
allowing comments (with moderation... like most blogs) on
http://gimp-brainstorm.blogspot.com/ will be a good start.
the wiki of the
As an example of why a GIMP.UI mailing list (or changes in the blog) is
necessary
Send your image to us [EMAIL PROTECTED], put the word 'GIMP' in
the title of your email (to avoid spam, emails without GIMP in the title
or without an image attachment will not be opened).
So, if I have a
Esteban Barahona wrote:
allowing comments (with moderation... like most blogs) on
http://gimp-brainstorm.blogspot.com/ will be a good start.
The idea is that comments are done by images - if you do like something,
you can add more suggestions based on it. If you don't like
something, you
On 11/5/07, Esteban Barahona wrote:
You say what to do, but you don't say how.
allowing comments (with moderation... like most blogs) on
http://gimp-brainstorm.blogspot.com/ will be a good start.
That won't work. Brainstorm means no discussion. Otherwise it's not a
brainstorm.
See, I do
This is why I suspect it to be a transparency problem and not really
a process problem. People actually Won't criticize a process if they
think it is doing a good job. In the case of the GUI team, we don't
know if it's doing a good job. In fact, we don't see a job being done
at all.
I suspect the true problem isn't one about the process, but one
about the perceived results. When you think about it, people rarely
criticize a project Just for the process. People criticize MS
Windows for being closed-source and thus full of bugs and
functionality problems, but nobody criticizes
On Sun, 04 Nov 2007 02:26:30 +0100, Tim Jedlicka [EMAIL PROTECTED]
wrote:
Contrast the GIMP UI redesign with the GIMP project as a whole, which
invites and receives patches, bug reports, and ideas from scores of
outsiders.
The focus was on the UI redesign, not GIMP. In fact the quote
gg at catking.net writes:
I dont think Nathan's analysis is that far off the mark. The interaction
with the UI team is very one way and definately gives the impression of
please go away , we're busy.
The so called brainstorm blog is more like a super market's suggestion box
than a
Well, I agree with the gist of your message... but one thing needs to be
said:
Designing a good UI doesn't require the same amount of people that
implementing
it in code does.
This is why I suspect it to be a transparency problem and not really
a process problem. People actually Won't
GIMP just got some negative press at linux.com. What are y'alls opinions on it?
http://www.linux.com/feature/120635
Loo
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
On 11/3/07, Barry Loo wrote:
GIMP just got some negative press at linux.com. What are y'alls opinions on
it?
http://www.linux.com/feature/120635
This is quite unusual for Nathan to miss the point *that* much.
Alexandre
___
Gimp-developer mailing
Barry Loo wrote:
GIMP just got some negative press at linux.com. What are y'alls opinions on
it?
http://www.linux.com/feature/120635
As far as GIMP is concerned,
http://www.linux.com/?module=commentsfunc=displaycid=1169329
and
http://www.linux.com/?module=commentsfunc=displaycid=1169345
Date: Sat, 3 Nov 2007 14:47:18 -0400
From: Barry Loo [EMAIL PROTECTED]
GIMP just got some negative press at linux.com. What are y'alls
opinions on it?
http://www.linux.com/feature/120635
I've had my share of issues with the GIMP UI (and I've been vocal
about it at times), but I
Contrast the GIMP UI redesign with the GIMP project as a whole, which
invites and receives patches, bug reports, and ideas from scores of
outsiders.
The focus was on the UI redesign, not GIMP. In fact the quote above
compliments GIMP (but at the UI redesign's expense).
--
Tim Jedlicka,
21 matches
Mail list logo
