On Sun, Mar 11, 2012 at 2:21 PM, grafxuser wrote:
Hi,
I'm a bit confused about this answer. Was it meant sarcastic or is there no
planning at all in GIMP development?
Could it be both? :)
Planning with the current amount of active developers would be rather pointless.
Alexandre Prokoudine
Hi
here are some thoughts from me to the topic and postings before:
1. Solve the real problems:
Full acknowledgement with Alexia and Alexandre to first solve the real
problems that caused the delay. I like the proposal for the further Git
branching and the proposal to iteratively check-in in
Hi,
currently I see the gimp.org news page updated round about one time per
month.
Why not tell the readers more often about GIMP's progress? Look at
digikam.org. Nearly every week there comes a message, showing what's
possible with Digikam and that the project is still alive.
To show this
Hi,
it was easier for new developers to contribute, if they had a
ready-to-use development environment.
Not everybody wanting to help, is a born Linux administrator by himself
to setup a suitable programming environment. There are many Windows or
Mac users, who'd like to help, but are
I'm a bit confused about this answer. Was it meant sarcastic or is
there no planning at all in GIMP development?
Could it be both? :)
Planning with the current amount of active developers would be rather
pointless.
Hi Alexandre,
I understand this and your sarcasm and have a few thoughts
On Sun, Mar 11, 2012 at 11:23 PM, grafxuser wrote:
I'm software developer, too, and would support GIMP when I have more time.
Reading various postings I'm convinced I'm not the only one with this
approach. For outsiders the decision to contribute would be easier, if they
knew the project is
On Sun, Mar 11, 2012 at 11:17 PM, grafxuser wrote:
Hi,
currently I see the gimp.org news page updated round about one time per
month.
Why not tell the readers more often about GIMP's progress? Look at
digikam.org. Nearly every week there comes a message, showing what's
possible with
Maybe you could put a link to gimpusers.com on the front page.
Why?
- because it will not hurt
- because it's somewhat logic (why not keeping a link to a community of
users ?)
2012/3/12 Alexandre Prokoudine alexandre.prokoud...@gmail.com
On Sun, Mar 11, 2012 at 11:17 PM, grafxuser wrote:
On Sun, Mar 11, 2012 at 5:45 PM, SorinN nemes.so...@gmail.com wrote:
Maybe you could put a link to gimpusers.com on the front page.
Why?
- because it will not hurt
- because it's somewhat logic (why not keeping a link to a community of
users ?)
I would think this is the other way around?
On Sunday, March 11, 2012, 22:37:24, Partha Bagchi wrote:
Finally, Ender, can you help or are you aware of this issue?
I didn't see any replies from him here. So perhaps he is busy.
I haven't tried building with ghostscript yet.
I wonder why tiff 4.0.1 is failing on my builds. Has anyone
2012/3/11 Jernej Simončič jer...@ena.si:
On Sunday, March 11, 2012, 22:37:24, Partha Bagchi wrote:
Finally, Ender, can you help or are you aware of this issue?
I didn't see any replies from him here. So perhaps he is busy.
I haven't tried building with ghostscript yet.
I wonder why tiff
that's not mean that you are right.
please think from the user perspective
indeed you don't expect them to link to your builds
that's does not mean that they should not do that.
from a developer point of view they have some reasons for that - connected
with the credibility of the GIMP stable
Great! At the very bottom, there is one with a typo... (web is
included in the href link, if we remove that part it should end right
after the forward slash.
Thanks!
On Sat, 10 Mar 2012 16:20:07 +0100, Martin Nordholts wrote:
Den 7 mars 2012 23:43 skrev Nils Philippsen n...@redhat.com:
And now, the rest of the story. I've completed this project, and
everything worked out. Turns out that my perceived memory leak was
nothing more than normal growth of the undo stack; disable undos, and
the problem goes completely away. As for gimp_image_delete(), it occurs
as part of deleting
On Sun, Mar 11, 2012 at 8:12 PM, Tom Vrankar t...@cox.net wrote:
...[deleted]
The
only problems that remained were with the API. I guess there's a lot of
history there, but inconsistencies in it make it a chore to learn. And when
you call a function potentially thousands of times, you can't
On 12-03-11 08:12 PM, Tom Vrankar wrote:
only problems that remained were with the API. I guess there's a lot of
history there, but inconsistencies in it make it a chore to learn. And when
you call a function potentially thousands of times, you can't tolerate the
pointlessly repeating deprecated
16 matches
Mail list logo
