On Tuesday 23 November 2004 23:44, Sven Neumann wrote:
> Hi,
>
> "Joao S. O. Bueno Calligaris" <[EMAIL PROTECTED]> writes:
> > So the suggestion taht arised is to have a paint tool that reads
> > what it will do from plain text files. These plain text files
> > will be stored in a collection in the
Hi,
"William Skaggs" <[EMAIL PROTECTED]> writes:
> I'm not just making this up, I'm reporting my own repeated
> experiences. I feel ten times as productive working on plug-ins as
> working on the core. This isn't because plug-ins are intrinsically
> easier, it's because the api docs are so wond
Hi,
"Joao S. O. Bueno Calligaris" <[EMAIL PROTECTED]> writes:
> When I first reported I was thinking of being able to write such
> callbacks in Python language, so that changes on the paint behavior
> would not require any compiling at all. Moreover, parameters for a
> painting tool would be adde
Sven wrote:
> Well, that is, please excuse me, very stupid. We aren't putting our
> free time into cleaning up the code for ourselves only. We would love
> to see more people working on the core and I would very much
> appreciate if you could stop spreading this FUD that hacking the core
> would b
Hi,
"William Skaggs" <[EMAIL PROTECTED]> writes:
> Well, I think I have demonstrated that I need to create or modify at
> least 10 files to produce a new paint tool, and I have probably
> missed something along the way. But I will admit that the danger of
> code collision does not seem all that
Ok, for those who are wondering,
this is discussion is tied with what I've requested in
[Bug 140165] A Paint Tool that allows stroke events to callback
plug-in procedures
My initial wriitng in there was:
"Hi,
I know it had been thought before, but anyway could not find it in
bugzilla. So here it
Sven wrote:
> If you had a look at the Ink tool you would have noticed that all
> paint tools are extraordinarily simple. I agree that other tools
> (those that draw to the display) are a lot more complex but all paint
> tools are identical except that they register different GimpPaintCore
> objec
Sven Neumann wrote:
[...]
Also, it is my impression that coders are often reluctant to ask what
seems like very basic questions, because they know how much effort you
and Mitch are already putting into GIMP devlopment, and know that basic
questions are often the kind that take the most effort to an
Hi,
"William Skaggs" <[EMAIL PROTECTED]> writes:
> Let me give a specific example. I know by this time, having worked with
> GIMP for months, that "drawing tools" are tools that make temporary marks
> on the image display (as opposed to the image itself), and that all such
> drawing is done in X
Sven wrote:
> You obviously didn't understand me. Adding such an API would be a
> major undertaking and we are not going to add such a framework for
> anyone unless that someone has at least built a prototype in the
> core. I do simply not believe that there is serious interest for
> developing o
Hi,
"Joao S. O. Bueno Calligaris" <[EMAIL PROTECTED]> writes:
> My idea of asking the possibility of a callback brush is that any
> such impelementation would take lots of parameters. And Huge amounts
> of trial and error before good results are achieved.
> And even them, if someone would like
On Tuesday 23 November 2004 05:41, Laxminarayan Kamath wrote:
> -- Forwarded message --
> From: Laxminarayan Kamath <[EMAIL PROTECTED]>
> Date: Mon, 22 Nov 2004 23:41:01 -0800
> Subject: Re: [Gimp-developer] Re: whishes for Gimp
> To: Sven Neumann <[EMAIL PR
-- Forwarded message --
From: Laxminarayan Kamath <[EMAIL PROTECTED]>
Date: Mon, 22 Nov 2004 23:41:01 -0800
Subject: Re: [Gimp-developer] Re: whishes for Gimp
To: Sven Neumann <[EMAIL PROTECTED]>
On Tue, 23 Nov 2004 00:32:23 +0100, Sven Neumann <[EMAIL PROTECTE
Hi,
"Joao S. O. Bueno Calligaris" <[EMAIL PROTECTED]> writes:
> I have openned bug 140165 to track such idea and help develop it,
> hopefully over the next development cycle.
> ( http://bugzilla.gnome.org/show_bug.cgi?id=140165 )
I have added some comments to that bug report that you and every
On Sunday 21 November 2004 09:29, Juhana Sadeharju wrote:
> >From:Alan Horkan <[EMAIL PROTECTED]>
> >
> >Sven's point still stands though, adding more tools to the default
> > toolbox is not a great idea.
>
> I agree completely, because I did not suggest that.
>
> We still need a system whi
>From: Alan Horkan <[EMAIL PROTECTED]>
>
>Sven's point still stands though, adding more tools to the default toolbox
>is not a great idea.
I agree completely, because I did not suggest that.
We still need a system which allows us to add as many tools as
needed to the tool pucket --- a tool plugi
On Thu, 18 Nov 2004, Juhana Sadeharju wrote:
> Date: Thu, 18 Nov 2004 13:21:49 +0200
> From: Juhana Sadeharju <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Gimp-developer] Re: whishes for Gimp
>
> >From: Sven Neumann <[EMAIL PROTECTED]>
> >
>
>From: Sven Neumann <[EMAIL PROTECTED]>
>
>Adding more tools has the disadvantage of cluttering the toolbox.
Just suggestions:
Solution 1: everything goes to menu (tree) and each non-default
menu item would have toggle which would append it to the toolbox.
Solution 2: toolbox (and menues) could
Hi,
Juhana Sadeharju <[EMAIL PROTECTED]> writes:
> It would be a good idea to have specialized crop tools.
> Alternatives are always good. Doing the thing with separate
> tools is just a waste of time and is not ergonomic at all.
Adding more tools has the disadvantage of cluttering the toolbox.
>From:
>3-To be able to change perspective with crop tool.
>In fotoshop you may make selection with the crop tool, and then rotate
>that selection before cropping.
It would be a good idea to have specialized crop tools.
Alternatives are always good. Doing the thing with separate
tools is just a w
20 matches
Mail list logo