Hi,
Nathan Carl Summers [EMAIL PROTECTED] writes:
I took a look at the new image dialogs on the list today, and I made
a few improvements. I've posted them at
http://wilber.gimp.org/~rock/NewDialogSimple.png and
http://wilber.gimp.org/~rock/NewDialogExpanded.png
Sorry, but I fail to see
Austin Donnelly [EMAIL PROTECTED] writes:
- Add an easy way to change the image's unit. It's quite well hidden
in the Image Scale dialog right now. With the changes proposed
above, changing the image unit could become a more frequent task, so
it should be easily accessible.
I just got rebuked by Sven for reporting bugs that are strictly
related to Jernej Simoncic's MS Windows builds of the GIMP.
Apparently, Bugzilla is only there for reporting bugs on the stuff
that WGO distributes.
In a way, that definitely makes sense.
However, anyone who uses a pre-compiled
Juhana Sadeharju ([EMAIL PROTECTED]) wrote:
But maybe they are not that easy to code? Adding a vector layer to
the images should be easy if the image object is good, but the vector
manipulations can be difficult. Typically each plugin has its own
kludge way to manipulate vector objects
Hi,
Branko Collin wrote:
However, anyone who uses a pre-compiled build cannot know beforehand
what part of the bugs are build related, and what part GIMP related.
Especially MS Windows users, who may not (and should not!) have a
concept of build versus source distribution to begin with, may
Dave Neary ([EMAIL PROTECTED]) wrote:
Jernej's installers are a great service, and if we don't want him to stop
(and I know I don't), and bit more tolerance is called for. Currently, we
don't even tell people how they should report bugs against the installer,
the bugs are just closed
Hi,
Branko Collin [EMAIL PROTECTED] writes:
Of course, this would put the burden of triage on the GIMP developers
who are currently doing that, but it might avoid reporters being
scared away by curt WONTFIX replies.
The reply is NOTGNOME and we usually ask the bug reporter to get in
Hi,
Simon Budig wrote:
What about a component installers or binary packages where we
can put the bugs that are related to a certain gimp distribution?
Sure, I could do this. I'll wait to see what the feedback on this thread is first.
Dave.
--
Dave Neary
[EMAIL PROTECTED]
Hi,
Sven Neumann wrote:
Branko Collin [EMAIL PROTECTED] writes:
Of course, this would put the burden of triage on the GIMP developers
who are currently doing that, but it might avoid reporters being
scared away by curt WONTFIX replies.
The reply is NOTGNOME and we usually ask the bug reporter
Hi,
Dave Neary [EMAIL PROTECTED] writes:
By we, you mean I, don't you? And today that hasn't happened at
least once, the reply was simply Your bug report is about the
installer then and thus does not belong into this bug-tracker.
Well, I knew that I was dealing with Branko, who should know
On 7 May 2004, at 17:50, Sven Neumann wrote:
Dave Neary [EMAIL PROTECTED] writes:
By we, you mean I, don't you? And today that hasn't happened at
least once, the reply was simply Your bug report is about the
installer then and thus does not belong into this bug-tracker.
Well, I knew
Dave Neary wrote:
Sven Neumann wrote:
Branko Collin [EMAIL PROTECTED] writes:
Of course, this would put the burden of triage on the GIMP developers
who are currently doing that, but it might avoid reporters being
scared away by curt WONTFIX replies.
The reply is NOTGNOME and we
On Friday, May 7, 2004, 17:50:13, Sven Neumann wrote:
Because we can't do anything about the bugs. Nobody but the packager
can. The situation would be different if the tools used to build the
binary packages would be in GNOME CVS. That would certainly qualify
the project for also using the
Hi Jernej,
Jernej Simon?i? wrote:
Not sure about what kind of proprietary scripts are you talking about - the
installer scripts were always available...
I'm glad you joined the thread, because there's one question that
hasn't been answered yet.
Would you like to have your installer's problems
On Friday, May 7, 2004, 20:59:14, David Neary wrote:
I'm glad you joined the thread, because there's one question that
hasn't been answered yet.
I've been subscribed for a while, but haven't really posted much (and I
just noticed that the last 2 messages I did send never arrived to the list
Hi,
=?Windows-1250?Q?Jernej_Simon=E8i=E8?= [EMAIL PROTECTED] writes:
Because we can't do anything about the bugs. Nobody but the packager
can. The situation would be different if the tools used to build the
binary packages would be in GNOME CVS. That would certainly qualify
the project
On Friday, May 7, 2004, 22:59:14, Sven Neumann wrote:
I was under the impression that building a GIMP installer involved
some black magic. After all there don't seem to be many people able to
build GIMP from source on win32.
Once you have the mingw+MSys environment set up, building Gimp is
Hi Michael,
You might want to have a look at XNest, or the following GIMP plug-in if
you are working on Win32: http://registry.gimp.org/plugin?id=3892
I don't know if there is an equivalent for Mac OS X, though.
Thanks for the link. This is great, it's got a lot of what I was
interested in. If
Hi,
as you might (or might not) have noticed, the wiki at
http://wiki.gimp.org is becoming a really useful resource for The GIMP.
There are, however, a few problems that should be looked at.
In short words, these are look, content and configuration.
Look
The wiki just doesn't look like a
Hi,
Simon Budig [EMAIL PROTECTED] writes:
Dave Neary ([EMAIL PROTECTED]) wrote:
Jernej's installers are a great service, and if we don't want him to stop
(and I know I don't), and bit more tolerance is called for. Currently, we
don't even tell people how they should report bugs against
On 7 May 2004, Sven Neumann wrote:
Hi,
Nathan Carl Summers [EMAIL PROTECTED] writes:
I took a look at the new image dialogs on the list today, and I made
a few improvements. I've posted them at
http://wilber.gimp.org/~rock/NewDialogSimple.png and
21 matches
Mail list logo
