Re: [Gimp-user] Announcement: this mailing list will be retired by the end of Oct 2022

[Jehan Pagès via gimp-user-list]

Hi!

On Thu, Oct 20, 2022 at 5:42 PM  wrote:

> From:   Andrea Veri 
> Subject:[Gimp-user] Announcement: this mailing list will be
> retired by the end of Oct 2022
> > ... GNOME's Mailman platform is being decommissioned ...
> > ...
> > [1] https://discourse.gnome.org
>
> > Jehan (from the GIMP Team) kindly provided some instructions ...
>
> I created an account, found the list of tags, switched order from
> "count" to "name" and found gimp.  Whew!  Conclusion: more complex
> than necessary but it works.
>
> Haven't found a logout.  Does Discourse have logout?
>

Yeah, it's a bit hidden, I agree.

1) On the top-right, there is an icon representing your account (it's
either a profile picture if you set one, or I believe by default, it's the
first letter of your account name). Click it.
2) It pops up some popover dialog, with 4 top icons. The rightest icon is
like some kind of "person". Click the person icon.
3) The menu shown below will have a "Log Out" item.

Jehan


> Thanks,   ... P.
>
>
>
>
> mobile: +1 778 951 5147
>   VoIP: +1 604 670 0140
> https://en.wikibooks.org/wiki/User:PeterEasthope
>
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Discontinuation of mailing lists and moving to Discourse

[Jehan Pagès via gimp-user-list]

Hi!

On Wed, Oct 19, 2022 at 11:20 AM Marco Ciampa via gimp-user-list <
gimp-user-list@gnome.org> wrote:

> On Wed, Oct 19, 2022 at 02:43:53PM +0900, Joel Rees via gimp-user-list
> wrote:
> > I'm not an active user of the lists, haven't posted in ages. so I was
> just
> > considering ignoring this thread and when the list disappears
> disappearing
> > from the community myself.
> >
> > But I decided to investigate discourse to see if I would be installing a
> > client or whatever, and I find the project pages really don't tell me
> what
> > I want to know before I install something new. (That other thing,
> Discord,
> > for instance, does not seem to be surviving the move to the new phone.
> I'm
> > getting pickier.)
> >
> > So I went to Wikipedia for a better overview and I noticed something
> > disconcerting on the Wikipedia page –
> >
> > Paraphrased: This reads like advertising material. And, ... nine years
> > later it still reads like advertising material.
> >
> > Not a confidence builder. Which means, yeah, lurkers like me will likely
> > disappear from the community.
> >
> > FWIW.
> >
> > Joel Rees
>
> Exactly my same feeling. I wonder: since the very low traffic of these
> lists, was it so hard to keep them alive? Why not ask for a hand before
> deciding to migrate?
>

I can't talk for the GNOME Infra team, but I know that the problem is often
the small things adding up. So even if it's probably not too hard, there is
this + that + this. 路

As for providing a hand, you can always propose. Maybe it's not too late
since they are still here. I believe the Infrastructure tracker would be a
good place to start (https://gitlab.gnome.org/Infrastructure/Infrastructure/)
or maybe #sysadmin channel on GIMPNet (looking for AndreaVeri/av). We would
just follow and if the mailing lists stayed around, we'll happily continue
using them.

Jehan
GIMP team


> --
>
> Amike,
> Marco Ciampa
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] [Gimp-developer] Discontinuation of mailing lists and moving to Discourse

[Jehan Pagès via gimp-user-list]

Hi!

On Tue, Oct 18, 2022 at 3:25 AM Ken Moffat  wrote:

> On Mon, Oct 17, 2022 at 10:00:24PM +0200, Jehan Pagès via
> gimp-developer-list wrote:
> > Hi!
> >
> > On Mon, Oct 17, 2022 at 9:48 PM Rick Strong  wrote:
> >
> > > So if I want to ask a question about using GIMP, or respond to a
> question,
> > > how do I do it?
> > >
> >
> > Well basically same as you always did, except that now it will be on one
> of
> > the Discourse instances, such as the pixls.us one or the GNOME one.
> Instead
> > of being subscribed to a mailing list, it's on Discourse (which is
> > basically a modern-time forum, as I see it), on which you'd have a
> > login/account. :-)
> >
> > Jehan
> >
>
> As a linux user, this feels like a retrograde step (there are ways
> of running mailing lists without python2, such as sympa, although
> they tend to work sub-optimally).  But it is outside my, and your,
> control so thanks for the forewarning.
>
> I guess that if I have any questions in the future I'll use
> https://discuss.pixls.us in the hope that I might get indications of
> how to do something (I'm logged in there on one of my machines, I
> get mails every week or so with topics since I last visited - most
> of which seem to be about non-interesting *to me* software).
>
> This might be my last post here, so I'll say thanks to the people
> who have helped me on -user over the years, and to the devs who have
> made 2.10 what it is - yes, I'd like to use 2.99 but I also want
> script-fu and g'mic plugins so I guess I'll be staying on 2.10 for a
> while.
>

Script-fu is still available in 2.99 and nowadays we get a very active
contributor for it. So it's even improving. :-)

As for G'MIC, it is available for GIMP 2.99 too, though maybe not on all
platforms, and it probably "breaks" at nearly every dev release (as we
progressively change the API here and there). So there is indeed often a
short span of time where it's non-available. Of course, not advising you to
use 2.99 either as it's still marked as "unstable" releases (so to be used
carefully), but just saying that these 2 points are not hugely broken and
there is no doubt to me that they will will be available with GIMP 3.0 (and
no API break for a long time then!). :-)

Jehan


> ĸen
> --
> Greater love hath no woman for the premiership than to lay down the
> life of her bosom friend in an attempt to save her own skin.
>  -- Andrew Rawnsley
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Discontinuation of mailing lists and moving to Discourse

[Jehan Pagès via gimp-user-list]

Hi!

On Tue, Oct 18, 2022 at 4:43 AM Rick Strong  wrote:

> Gee, Jehan I'm really sorry I was so involved in getting photographs ready
> for print tomorrow morning that I overlooked the possibility that YOU might
> also be stressed out. I’m going blind in one eye, had a heart attack in
> August and I’ve been going for over 12 hours now, but that’s no excuse. You
> have my sympathy. [image: Crying face]
>

Hey no problem don't worry. Neither your email nor the one from the other
person were rude or anything. I was just annoyed by the fact they were sent
privately and it's true I'm quite tired these days.
Anyway thanks for understanding and sorry to read about your health issues.
I hope these will get better soon! 

Jehan


> Rick
>
>
> -Original Message-
> From: Jehan Pagès via gimp-user-list
> Sent: Monday, October 17, 2022 8:29 PM
> To: gimp-web-list ; GIMP User List ; gimp-gui-l...@gnome.org ; GIMP Docs
> ; gimp-developer ; gegl-developer-list
> Subject: Re: [Gimp-user] Discontinuation of mailing lists and moving to
> Discourse
>
> Hi everyone!
>
> I received 2 off-list emails. Please do not send me off-list emails. I am
> exhausted  and cannot do private support in addition to public support,
> code development, news writing, website making and everything else in GIMP.
> 
>
> This is even more true as I don't really see anything private/sensitive in
> the 2 emails I received. Really no need to make them private, except for
> making me work double (whereas as public emails, someone else could have
> answered). I generally advise contributors to preserve themselves from
> overworking by not answering to private messages.
>
> Anyway, regarding unhappiness about the new platform, I will mainly answer
> that there is not much we can do. We are heavily relying on GNOME
> Infrastructure (which we thank for this) and they have their own reasons
> (one of them is that mailing lists are apparently one of the elements in
> their stack which prevent them from dropping Python 2; we can relate!). Cf.
> the link in my original email.
>
> Now we could always try to fight against the current and persuade GNOME
> infrastructure team, but we made a small opinion tour among the current
> core team and nobody really had particular love or use of our mailing
> lists. Also we realize it's very low volume these days (barely a few
> threads per month, counting all mailing lists together). Myself I barely
> look at mailing lists every once in a while and make a random answer
> sometimes. And there were several mailing lists I was not even subscribed
> to (I did for the sake of this announcement). So that's probably why none
> from the core team is really trying to fight this change.
>
> There is one more thing to take into consideration: more infrastructure
> means more work. I said it above, I am exhausted by this all. I was only
> managing one of the mailing lists so far (the gimp-gui one, the most
> recent) and still had to regularly handle spams. I am personally thankful
> that this work goes to GNOME admins now. Moreover I would not try to find
> alternative mailing list providers either. Now, same as hundreds of
> third-party forums discuss GIMP out there, people are welcome to create
> third-party mailing lists to discuss GIMP if that's really what you are
> into. I won't be such a person; and apparently it looks like nobody else
> from the core team is so far.
>
> One last thing: I am aware that Discourse is not perfect. I also spent some
> time today to try and understand how to efficiently transform it into a
> mailing list equivalent.
>
> For questions about only receiving emails for the "gimp" tag, I think that
> you should not try to use the "Enable mailing list mode" option. Instead
> just go to the "gimp" tag page (https://discourse.gnome.org/tag/gimp),
> click the bell icon on the top-right and set to "Watching" mode. This way,
> you will be notified of absolutely all messages for this tag. Then in your
> "Emails" preferences, set "Email me when I am quoted, replied to, my
> @username is mentioned, or when there is new activity in my watched
> categories, tags or topics" to "always". This should transform every
> notification into emails, in other words you will receive an email for
> every message added in the "gimp" tag. You can even directly reply to a
> notification email from your mail client without going to Discourse.
> At least, so far it worked for me (I tried today, and I only received
> emails for the 2 messages which came in with the "gimp" tag, no other
> emails). So it's probably the right setting.
>
> Anyway please understand that it's really not about comparing the

Re: [Gimp-user] Discontinuation of mailing lists and moving to Discourse

[Jehan Pagès via gimp-user-list]

ill receiving uncountable numbers of
emails daily.
And now you'll understand why I am doing a single and hopefully last answer
on this topic. I'm just tired and don't want to paste the same email twice
(or more).

Actually sending private emails, you kind of made a counter-argument
against mailing lists where it is indeed quite common that people feel they
can just continue discussions in private. But there is a reason why it's
public: anyone can join in, help and contribute to the discussion. No need
to involve a single person only (forbidding others to help by going
private). In GIMP, we work in full transparency, with public
infrastructure. We don't want private discussions, and unfortunately as you
showed, this is often what some people believe they can afford to do with
emails. So you both shot your opinion in the foot by telling me that
mailing lists are better while deciding not to use these to tell me this. 藍

So yes, bottom line: mailing lists will be gone. It's not a private
decision from anyone in GIMP team (I got notified today myself of the
end-of-month deadline), though clearly nobody fought against it either.
It's not really something we can or want to control so there is really no
need to give counter-arguments here. If you really wish to do so, you are
welcome to ask the GNOME Infrastructure team. If they back down from their
decision, we'll happily comply and keep the mailing lists.

Jehan
GIMP team


On Mon, Oct 17, 2022 at 10:00 PM Jehan Pagès 
wrote:

> Hi!
>
> On Mon, Oct 17, 2022 at 9:48 PM Rick Strong  wrote:
>
>> So if I want to ask a question about using GIMP, or respond to a
>> question,
>> how do I do it?
>>
>
> Well basically same as you always did, except that now it will be on one
> of the Discourse instances, such as the pixls.us one or the GNOME one.
> Instead of being subscribed to a mailing list, it's on Discourse (which is
> basically a modern-time forum, as I see it), on which you'd have a
> login/account. :-)
>
> Jehan
>
> Rick
>>
>> -Original Message-
>> From: Jehan Pagès via gimp-user-list
>> Sent: Monday, October 17, 2022 12:38 PM
>> To: gimp-web-list ; gimp-developer ; GIMP User List ;
>> gimp-gui-l...@gnome.org ; gegl-developer-list ; GIMP Docs
>> Subject: [Gimp-user] Discontinuation of mailing lists and moving to
>> Discourse
>>
>> Hello everyone!
>>
>> The GNOME Foundation has been moving all its discussions to a Discourse
>> forum, progressively:
>>
>> https://mail.gnome.org/archives/desktop-devel-list/2022-September/msg00018.html
>>
>> We were informed today that they are on the last stage of this migration
>> and that all the mailing lists will be fully retired by the end of
>> October.
>> This implies also all of GIMP and GEGL mailing lists.
>>
>> Instead, people wishing to discuss about GIMP are expected to use GNOME's
>> Discourse instance. In particular 2 tags were created for us:
>>
>> * "gimp" tag for GIMP-related discussions:
>> https://discourse.gnome.org/tag/gimp
>> * "gegl" tag for GEGL-related discussions:
>> https://discourse.gnome.org/tag/gegl
>>
>> We don't have as many tags as we used to have mailing lists, just these 2,
>> but since all our lists are quite low volume these days, I didn't think it
>> was worth asking, at least for now. GNOME admins confirmed that it would
>> not be a problem to add new tags in the future if we ever decided we
>> needed
>> more (e.g. having a "gimp-dev" tag or whatnot).
>>
>> By the way, noteworthy information: GIMP has had already an official
>> presence on pixls.us Discourse: https://discuss.pixls.us/gimp/
>> We discussed among the team if it was worth having presence on both
>> pixls.us
>> and GNOME discourse and we came to the conclusion that the audience is
>> different, therefore it is interesting to stay on both communities. For
>> discussion with existing GNOME contributors, translators and various GNOME
>> users for instance, they might be already on the GNOME Discourse. On the
>> other hand, pixls.us is a much more specialized forum/community on
>> Photography in particular, and is also probably more platform-independent
>> too.
>>
>> Last but not least, as I expect that some people might prefer interacting
>> by email, I tried to look up what are the possibilities. This thread
>> "Interacting with Discourse via email" is of interest:
>> https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
>>
>> It didn't have the ability to create new threads easily, especially tagged
>> with the "gimp" keyword. Discourse has a way to create a topic on a
&

Re: [Gimp-user] Discontinuation of mailing lists and moving to Discourse

[Jehan Pagès via gimp-user-list]

Hi!

On Mon, Oct 17, 2022 at 9:48 PM Rick Strong  wrote:

> So if I want to ask a question about using GIMP, or respond to a question,
> how do I do it?
>

Well basically same as you always did, except that now it will be on one of
the Discourse instances, such as the pixls.us one or the GNOME one. Instead
of being subscribed to a mailing list, it's on Discourse (which is
basically a modern-time forum, as I see it), on which you'd have a
login/account. :-)

Jehan

Rick
>
> -Original Message-
> From: Jehan Pagès via gimp-user-list
> Sent: Monday, October 17, 2022 12:38 PM
> To: gimp-web-list ; gimp-developer ; GIMP User List ;
> gimp-gui-l...@gnome.org ; gegl-developer-list ; GIMP Docs
> Subject: [Gimp-user] Discontinuation of mailing lists and moving to
> Discourse
>
> Hello everyone!
>
> The GNOME Foundation has been moving all its discussions to a Discourse
> forum, progressively:
>
> https://mail.gnome.org/archives/desktop-devel-list/2022-September/msg00018.html
>
> We were informed today that they are on the last stage of this migration
> and that all the mailing lists will be fully retired by the end of October.
> This implies also all of GIMP and GEGL mailing lists.
>
> Instead, people wishing to discuss about GIMP are expected to use GNOME's
> Discourse instance. In particular 2 tags were created for us:
>
> * "gimp" tag for GIMP-related discussions:
> https://discourse.gnome.org/tag/gimp
> * "gegl" tag for GEGL-related discussions:
> https://discourse.gnome.org/tag/gegl
>
> We don't have as many tags as we used to have mailing lists, just these 2,
> but since all our lists are quite low volume these days, I didn't think it
> was worth asking, at least for now. GNOME admins confirmed that it would
> not be a problem to add new tags in the future if we ever decided we needed
> more (e.g. having a "gimp-dev" tag or whatnot).
>
> By the way, noteworthy information: GIMP has had already an official
> presence on pixls.us Discourse: https://discuss.pixls.us/gimp/
> We discussed among the team if it was worth having presence on both
> pixls.us
> and GNOME discourse and we came to the conclusion that the audience is
> different, therefore it is interesting to stay on both communities. For
> discussion with existing GNOME contributors, translators and various GNOME
> users for instance, they might be already on the GNOME Discourse. On the
> other hand, pixls.us is a much more specialized forum/community on
> Photography in particular, and is also probably more platform-independent
> too.
>
> Last but not least, as I expect that some people might prefer interacting
> by email, I tried to look up what are the possibilities. This thread
> "Interacting with Discourse via email" is of interest:
> https://discourse.gnome.org/t/interacting-with-discourse-via-email/46
>
> It didn't have the ability to create new threads easily, especially tagged
> with the "gimp" keyword. Discourse has a way to create a topic on a
> specific category but we couldn't find for tags, for instance you can send
> an email to community @ discourse.gnome.org (note that it doesn't work for
> every category, e.g. it didn't work for infrastructure; I haven't tested
> others). With Andrea Veri, GNOME Infrastructure admin, we came up with a
> special email hook: any email with "[GIMP]" in the subject will be tagged
> "gimp".
> Nevertheless you need to have level 1 trust level for this to work. We
> aren't sure exactly what it means other than having participated enough
> (whatever "enough" is) to the Discourse first. 路
>
> See:
>
> https://discourse.gnome.org/t/gimp-how-to-send-emails-to-discourse-tagged-for-gimp-forum/11535
>
> So I guess, let's continue discussing there everyone! 珞
>
> Jehan
> GIMP maintainer
>
> --
> ZeMarmot open animation film
> http://film.zemarmot.net
> Liberapay: https://liberapay.com/ZeMarmot/
> Patreon: https://patreon.com/zemarmot
> Tipeee: https://www.tipeee.com/zemarmot
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>
>

-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

[Gimp-user] Discontinuation of mailing lists and moving to Discourse

[Jehan Pagès via gimp-user-list]

Hello everyone!

The GNOME Foundation has been moving all its discussions to a Discourse
forum, progressively:
https://mail.gnome.org/archives/desktop-devel-list/2022-September/msg00018.html

We were informed today that they are on the last stage of this migration
and that all the mailing lists will be fully retired by the end of October.
This implies also all of GIMP and GEGL mailing lists.

Instead, people wishing to discuss about GIMP are expected to use GNOME's
Discourse instance. In particular 2 tags were created for us:

* "gimp" tag for GIMP-related discussions:
https://discourse.gnome.org/tag/gimp
* "gegl" tag for GEGL-related discussions:
https://discourse.gnome.org/tag/gegl

We don't have as many tags as we used to have mailing lists, just these 2,
but since all our lists are quite low volume these days, I didn't think it
was worth asking, at least for now. GNOME admins confirmed that it would
not be a problem to add new tags in the future if we ever decided we needed
more (e.g. having a "gimp-dev" tag or whatnot).

By the way, noteworthy information: GIMP has had already an official
presence on pixls.us Discourse: https://discuss.pixls.us/gimp/
We discussed among the team if it was worth having presence on both pixls.us
and GNOME discourse and we came to the conclusion that the audience is
different, therefore it is interesting to stay on both communities. For
discussion with existing GNOME contributors, translators and various GNOME
users for instance, they might be already on the GNOME Discourse. On the
other hand, pixls.us is a much more specialized forum/community on
Photography in particular, and is also probably more platform-independent
too.

Last but not least, as I expect that some people might prefer interacting
by email, I tried to look up what are the possibilities. This thread
"Interacting with Discourse via email" is of interest:
https://discourse.gnome.org/t/interacting-with-discourse-via-email/46

It didn't have the ability to create new threads easily, especially tagged
with the "gimp" keyword. Discourse has a way to create a topic on a
specific category but we couldn't find for tags, for instance you can send
an email to community @ discourse.gnome.org (note that it doesn't work for
every category, e.g. it didn't work for infrastructure; I haven't tested
others). With Andrea Veri, GNOME Infrastructure admin, we came up with a
special email hook: any email with "[GIMP]" in the subject will be tagged
"gimp".
Nevertheless you need to have level 1 trust level for this to work. We
aren't sure exactly what it means other than having participated enough
(whatever "enough" is) to the Discourse first. 路

See:
https://discourse.gnome.org/t/gimp-how-to-send-emails-to-discourse-tagged-for-gimp-forum/11535

So I guess, let's continue discussing there everyone! 珞

Jehan
GIMP maintainer

-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] update

[Jehan Pagès via gimp-user-list]

Hello,

On Thu, Sep 1, 2022 at 9:50 AM Jennifer Smith via gimp-user-list <
gimp-user-list@gnome.org> wrote:

> Hi
>
> When trying to click the update button in the about window of gimp,
> nothing happens.
> Is this the behavior when no update is available or did I find a bug?
>

I guess, you mean the "Check for updates" button (we don't have an update
button because GIMP is not able to update itself at this point), and yes if
there are no new releases, then it's normal that nothing happens. It will
only change to a button (which would send you to our download page if you
click it) if there is a new version.

Actually when I say "nothing happens", it's wrong. A small label just below
the button says "Last checked on ". It should appear (if it was
not present) or the date should be updated each time you click the button.
If this doesn't happen, it means GIMP was not able to verify the release
listing (no internet? Something else?).

I guess we could add an error label (or small icon with tooltip showing the
network error) saying that the update check failed, when this happens.

Jehan


> I use windows 10 and latest official gimp
>
> Sent with [Proton Mail](https://proton.me/) secure email.
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

[Gimp-user] ANNOUNCE: GIMP 2.99.6 released

[Jehan Pagès via gimp-user-list]

Hello everyone!

We have not been very good with announcing releases on the mailing list
lately, so let's fix this! In particular, we have never announced here any
of the development releases of the 2.99 series (the unstable versions meant
to become GIMP 3 later on) even though this is actually the third one!

* GIMP 2.99.2 (2020-11-06):
https://www.gimp.org/news/2020/11/06/gimp-2-99-2-released/
* GIMP 2.99.4 (2020-12-25):
https://www.gimp.org/news/2020/12/25/gimp-2-99-4-released/
* GIMP 2.99.6 (today):
https://www.gimp.org/news/2021/05/08/gimp-2-99-6-released/

Note about the release dates: some people may have noticed that versions
are tagged earlier in the git repository, because we now wait for at least
the Windows installer or macOS DMG before announcing a new version, and for
mirrors to sync up. In GIMP 2.99.6 case, we are even 11 days late, but such
is life! It is nicer not to announce something most people cannot test.
Though our flatpak (Linux) package is always timely distributed a few hours
after version tagging.

For a list of the changes, with nice text and screenshots, please refer to
the relevant news link above, on our website. For a more complete list of
changes since GIMP 2.99.6, please see the "Changes" section below.

Happy GIMPing,

Jehan and the GIMP team!

Download


  GIMP 2.99.6 is available from:

  https://download.gimp.org/mirror/pub/gimp/v2.99/

  and from the mirrors listed at:

  https://www.gimp.org/downloads/devel/#mirrors

  The sha256 and sha512 checksums of the tarball are:

8d264b28445a3df2b940f30ee0b89b469255e975e8563b889fd57fb2f58f66a0
 gimp-2.99.6.tar.bz2

51ada696693ac51624ba222d1fff54d39bdc72a06de54f7c244b89740b77f7205aab44f1cec90785ca4196cab32f817e7390b4287a30f5024606163f24222961
 gimp-2.99.6.tar.bz2

Overview of Changes from GIMP 2.99.4 to GIMP 2.99.6
===

Core:

  - Various fixes for Wayland support.
  - Canvas Size dialog now displays a template selector to simply
resize the canvas to a known template. When the image's and
template's pixel density don't match, a choice will be proposed to
set the image's PPI to the template's one or to scale the template's
pixel size with the image's pixel density.
  - Off-canvas guides are now allowed. Guides are not deleted anymore
when dropped off-canvas, but when dropped off-viewport.
  - Pinch gesture is now possible on canvas for zooming in/out (works on
Wayland, not on X11; untested yet on *BSD, macOS, Windows and
others).
  - GimpAction core class now stores a reason for explaining being
disabled. This can be used later for giving better hints on why some
effects or plug-ins are not usable in some situations. We already
had this feature, but by tweaking the action's tooltip, which
prevented this to have proper styling on GUIs and disrupted action
search (as the reason text was searched, hence may return actions it
should not).
  - Copy|Cut-Paste could already operate on multiple layers, by merging
the result into a single layer. It will still do this when a
selection exists, yet will paste layers as-is otherwise. This makes
an alternative way to move layers, which is sometimes easier than
drag'n dropping (especially between separate images).

Tools:

  - Paint Select tool got various improvements:
* apply a threshold on the image mask before triggering the
  automatic expansion to simplify mask handling in the gegl
  paint-select operation.
* enable viewport-based local selection.
  - GEGL Operation tool is now moved into Filters > Generic menu because
it behaves more like a generic filter conceptually. As other
filters, the GEGL Operation action is now only active when there are
opened images.

API:

  - The generate "Metadata" frame layout in a GimpSaveProcedureDialog
has been improved to always show the same number of columns to avoid
ugly layout with options on 3 columns, then 2 columns on the next
line (for instance).
  - The "Reset" button in GimpProcedureDialog shows a down arrow to show
this is actually a button menu.
  - "Save|Load Defaults" in GimpProcedureDialog are renamed as "Save
Settings" and "Load Saved Settings". The term "defaults" was not
very clear and could be confused with "factory defaults". Moreover
tooltips were added and the "Load Defaults" button is now only
sensitive if "Save Defaults" buttion has been hit at least once.
  - Annotations improved.
  - Drop g_object_notify() in favor of g_object_notify_by_pspec() in
various implementations to avoid a slight performance hit because of
a global lock.
  - New function gimp_parasite_get_data() replacing gimp_parasite_data()
and gimp_parasite_data_size() in a GObject Introspection friendly
way.
  - gimp_procedure_dialog_new() now allows a NULL title if a menu label
was set on the GimpProcedure with gimp_procedure_set_menu_label().
  - 

Re: [Gimp-user] [Gimp-developer] GIMP-2.10 and GIMP2.99 are still sRGB-only image editors

[Jehan Pagès via gimp-user-list]

Hi!

On Fri, Feb 5, 2021 at 1:00 AM Elle Stone 
wrote:

> A misconception I keep seeing on various forums needs to be corrected:
>
> GIMP-2.10 does *NOT* produce correct editing results in color spaces
> other than sRGB. Neither does GIMP-2.99.
>
> Editing in AdobeRGB, ProPhotoRGB, Rec2020, etc WILL produce *wrong*
> results for many operations, and unless you are thoroughly conversant
> with the underlying code, or else have a way to compare results with a
> properly color-managed editing application, you don't have any way to
> know what's right and what's wrong. It's best to stick with editing only
> in GIMP's built-in sRGB color spaces.
>
> The same is true if you are using GIMP-2.99: Some things that don't work
> in GIMP-2.10, do work in GIMP-2.99. Other things that actually do work
> in GIMP-2.10, don't work in GIMP-2.99.
>
> About two years ago major changes were made in babl and additional
> changes were made in GIMP-2.99, messing up stuff that still works in
> GIMP-2.10. For awhile progress was being made in GIMP-2.99 on extending
> the arena of "what actually works", some of which progress is from bug
> reports I filed and in some cases helped to fix - it seems nobody else
> was testing the new code to see what actually did work.
>
> I was able to write code that fixed some of the bugs I reported for
> GIMP-2.99 color management. But once I reached the point where further
> coding requirements exceeded my coding ability, progress simply stopped,
> with everyone else saying "some day" proper color management for GIMP
> would be a priority. I began to feel like the best way to make sure a
> bug would never get fixed, was to have the dreaded "Concepts: Color
> Science" tag attached to it.
>
> Since autumm of 2013 I've been participating in GIMP development, mostly
> in the area of color management (editing in color spaces other than
> sRGB) and color science (making sure GIMP code produces correct results
> for things like layer blend modes, Curves and Levels, AutoStretch,
> Luminance, and so on; and adding code for things like LCh color pickers
> and blend modes).
>
> Participating in GIMP development used to be challenging and enjoyable.
> But over the last couple of years my interest in and patience with the
> slow pace of progress regarding GIMP color management have dwindled to
> the point of disappearing altogether.
>
> If someone else feels like helping with GIMP color management and color
> science, here's a list of still-open bug reports that I reported after
> the migration to gitlab, most of which have to do with color
> management/color science:
>
>
> https://gitlab.gnome.org/GNOME/gimp/-/issues?scope=all=%E2%9C%93=opened_username=ellestone
>
> Here are bugs that I opened before the migration to gitlab:
>
> https://gitlab.gnome.org/GNOME/gimp/-/issues?scope=all=%E2%9C%93=opened_username=bugzilla-migration=ellestone
>
> The most important color management bugs still open from before the
> migration to gitlab are these:
>
> * Replace hard-coded sRGB parameters to allow editing in other RGB
> working spaces (opened 6 years ago):
> https://gitlab.gnome.org/GNOME/gimp/-/issues/594 - in some ways this bug
> is obsolete as current GIMP color management issues are less about
> actual hard-coded values and more about a lack of any way to convey the
> required "not sRGB" color space information to various sections of code
> that need this information.
>
> * Decomposed to LAB images have the wrong ICC profile assigned (opened 4
> years ago): https://gitlab.gnome.org/GNOME/gimp/-/issues/883
>
> * Address various limitations of LCMS soft proofing (opened 4 years
> ago): https://gitlab.gnome.org/GNOME/gimp/-/issues/976
> the
> and hoping very much that GIMP will find new developers that them a lot
> of energy and some interest and expertise in color management and color
> science.
> * Support for high bit depth RGB (and LCH?) color palettes for painting
> (opened 2 years ago): https://gitlab.gnome.org/GNOME/gimp/-/issues/1328
>
> Similar searchs in https://gitlab.gnome.org/GNOME/gegl/ and
> https://gitlab.gnome.org/GNOME/babl/ will turn up a few additional color
> management issues.
>
> Best of luck to all,
>

So it feels like you are saying goodbye.
If so I hope it's only a temporary one and you'd be back if we get more
active on the color management side. We will, we definitely will, because
it's a major part of what GIMP 3 is supposed to be about anyway.

I personally have a high theoretical interest on this topic, but not a
practical one unfortunately (because we work in sRGB), which is why it is
both high in priority for me (because we need it for GIMP 3) and low
(compared to what we actually do day to day with GIMP). I have always been
hoping that Mitch and Ell would be back soon as they are much better suited
than me to decide on these topics anyway IMO. These are actually very
intimidating topics. I do understand them (or so I believe), when
scratching the head very hard, but I feel much 

Re: [Gimp-user] GIMP *super* slow on new iMac

[Jehan Pagès via gimp-user-list]

Hi!

On Sat, Jan 30, 2021 at 12:44 AM Liam R E Quin  wrote:

> On Fri, 2021-01-29 at 04:41 -0800, Lani P. Richards via gimp-user-list
> wrote:
> > I just bought a 27” 2020 iMac with full SSD (not fusion), 8GB memory,
> > AMD Radeon Pro 5300 4 GB, 3.1 GHz 6-Core Intel Core i5.
> >
> > Just drawing with the pen tool has a bunch of lag. This baby can do
> > 5120x2880. Still, I cannot smoothly draw in GIMP because of extreme
> > lag. What’s going on?
>
> We have a problem with GIMP on the Big Sur release of the Apple
> operating system. We do not have a timeline for a fix - we have a
> volunteer who dropped by and said he might look at it less than a month
> ago, but i odon't think we've heard back since;


We have heard from him and he is quite active, but not so much on the IRC
channel, which may be why you get this impression. 
Actually he just released a revision 3 of the DMG (like barely 2 days ago
and it was uploaded on download servers yesterday but not on the website
yet as we need to wait for mirrors to pick it up). I suggest to anyone with
issues to test it (gimp-2.10.22-x86_64-3.dmg):
https://download.gimp.org/mirror/pub/gimp/v2.10/macos/

For the record, from feedbacks so far, the revision 2 DMG was already much
better on Big Sur, but it turned out it was slower for macOS before Big Sur
(for this, the revision 1 was better). Our new macOS contributor thinks
that this last revision should be better for everyone. We welcome feedbacks
to confirm (or oppositely to refute).


> none of the core GIMP
> developers are Mac programmers and we rely on volunteers.
>

Indeed as a general rule, GIMP is fully community-developed and relies on
volunteers (whichever the platform even).

And more particularly macOS has always been the platform with lowest
contributors (even since I started to contribute, this is the only platform
where we never managed to get more than 1 active and regular contributor in
the same time as I recall).
So we really encourage people who like GIMP on macOS to actually
participate. This is the only way for support to be actually reliable.

Jehan

>
>
> --
> Liam Quin - web slave for https://www.fromoldbooks.org/
>
>
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] GIMP Version 2.8.16

[Jehan Pagès via gimp-user-list]

Hello Kenny,

First of all, I am sorry to hear about your condition.

Unfortunately we don't store any compiled package for GIMP on Linux (unlike
Windows/macOS packages). Even our flatpak is quite new (since late GIMP 2.8
releases, if not mistaken). The Flathub repository actually stores an
history of former builds, so it is actually possible to install older
builds (this is quite a hidden feature of Flatpak, very useful for
debugging), but I just checked and the 2.8 builds are long gone because
Flathub only stores up to 25 builds (which makes me think that maybe we
should store standalone Flatpak builds on our download server, but someone
would have to do the work to automatize this as much as possible). So you
are out of luck here.

Maybe you should be able to get older .deb packages of Linux Mint. Normally
distributions also keep their older packages and there are also some
websites which keep archives of all packages made for various
distributions. So I'm sure GIMP 2.8.x packages for Mint can be found. And
if you are lucky, these older packages can still be installed manually and
work on a newer distribution. You should ask about this on Linux Mint
forums.

As for the remark of overlooking legacy, I believe GIMP to be quite good on
this actually. We take a lot of care to not break too much older usage, and
rarely remove a feature without implementing first a better alternative,
nor do we change things on a whim without thinking hard about it. Now we
still have to evolve. Caring about compatibility is important, but it
should not mean being stuck in the past. Still I am sorry to read about
such a neurological disorder and I do wish you all the best. If finding an
older GIMP is the best for you, I hope you'll find an older version and
continue doing more of the nice photography artworks you linked earlier. 
Regards,

Jehan


On Wed, Sep 16, 2020 at 9:17 PM Kenny Mann via gimp-user-list <
gimp-user-list@gnome.org> wrote:

> I just discovered that tools can be ungrouped in GIMP 2.10
> (Sure, I can hold onto the concept that a tool is made visible by looking
> inside the group of related tools, but with my particular cognitive
> disorder, things that aren't visible tend to not exist in any functional
> sense. Imagine if the location of absolutely everything in the world were
> like the last time you lost your keys -- everything, all day, every day,
> your whole life.)
>
> Ungrouping the tools I use regularly makes it possible to have the toolbox
> in 2.10 appear as it always has in GIMP 2 -- a major cognitive help.
>
> Oh And: Now I see that the layers tab can be dragged to the set at the top
> of the column and the brushes can be dragged to the set at the bottom. It's
> nice not having the layers panel disappear until I look where the brushes
> always were and then keep finding the brushes have disappeared until I
> glance upward.
>
> Yes, having things only truly functionally exist when they're in view is
> weird. Be very glad you can take it for granted that things exist in
> locations on routes that you can keep track of without applying total
> conscious effort every single time.
>
> Picture GIMP in your mind's eye. I can't. If you were to ask me where
> things are in GIMP when I don't have the app open, I couldn't tell you,
> even if you offered me an all-expenses-paid trip to Mars.
>
> On Fri, Sep 4, 2020 at 2:50 PM Kenny Mann 
> wrote:
>
> > Why is GIMP 2.8.16 not available?
> >
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Missing files

[Jehan Pagès via gimp-user-list]

Hi!

For the record, the official Flatpak build has a few extension flatpaks for
plug-ins. And resynthesizer is one of them! This way, even if you use a
distribution where pygtk2 got removed (as is your case on Debian testing),
you can still run GIMP with python plug-ins.

I explain the command lines to install the Flatpak resynthesizer plug-in on
this post: https://www.patreon.com/posts/39631718

Jehan


On Wed, Jul 29, 2020 at 2:18 PM Frank McCormick  wrote:

>   Thanks for those links. It appears it's a widespread problem with no
> real solution, until Gimp 3.0 is out. We'll see how it works out.
>
> Thanks
>
> On 7/28/20 10:46 AM, Daniel Smith wrote:
> > I think it’s because when they moved onto newer versions of Linux they
> > drop the support for certain packages I looked it up and saw this link
> > it’ll probably be useful for you. And then the other link is the general
> > search that I did to find that link
> >
> > https://bbs.archlinux.org/viewtopic.php?id=253710
> >
> >
> https://www.google.com/search?q=gimpfu+lost+debian+update=UTF-8=UTF-8=en-us=safari
> >
> > Dan 
> >
> > On Tue, Jul 28, 2020 at 9:35 AM Frank McCormick  > > wrote:
> >
> >
> >
> > On 7/27/20 9:53 PM, Liam R E Quin wrote:
> >  > On Mon, 2020-07-27 at 20:43 -0400, Frank McCormick wrote:
> >  >> I am using Debian Bullseye and gimp 2.10. Sometime in the distant
> >  >> past
> >  >> the resynthesizer plugin stopped loading and working because of
> the
> >  >> absence of a library called gimpfu.
> >  >
> >  > This is probably from the Python plug-in for GIMP so installing
> that
> >  > might help.
> >  >
> >  > slave liam
> >  >
> >
> >
> >  As far as I know there is no python plugin for GIMP, at least
> > not in
> > the Debian repositories.
> >
> > ___
> > gimp-user-list mailing list
> > List address: gimp-user-list@gnome.org  gimp-user-list@gnome.org>
> > List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-user-list
> > List archives: https://mail.gnome.org/archives/gimp-user-list
> >
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] MacOS

[Jehan Pagès via gimp-user-list]

t;>>>>
>>>>>>> I'm the macOS packager for LMMS.  I might be able to help out in his
>>>>>>> absence.  LMMS is written in Qt, so the dependency stack is much
>>>>>>> different than Gimp which is Gtk, but if there's a documented build 
>>>>>>> process
>>>>>>> via MacPorts or Homebrew, I can take a swing at it.
>>>>>>>
>>>>>>
>>>>>> I know there are non-official MacPorts and Homebrew because it's
>>>>>> written on our website. So these can be good references indeed.
>>>>>>
>>>>>> Ideally we want the build scripts to be public and the build itself
>>>>>> to also be public (not happen on someone's computer for obvious reasons).
>>>>>> This is why Alex (our macOS contributor) has done a lot of work on the
>>>>>> build repository:
>>>>>> https://gitlab.gnome.org/Infrastructure/gimp-macos-build
>>>>>> It would be nice if continuing work were to happen on this same
>>>>>> repository.
>>>>>>
>>>>>> As for the build itself, it was happening on some CI service called
>>>>>> CircleCI (because macOS builds can be done there, unlike the GNOME Gitlab
>>>>>> CI machines). Builds are there:
>>>>>> https://circleci.com/gh/GNOME/gimp-macos-build
>>>>>>
>>>>>> Note: you'll notice that there are builds for GIMP 2.10.18 there,
>>>>>> which was from last time Alex was working on it. We don't really know the
>>>>>> state and in particular if these builds done 2 months ago work well and
>>>>>> safely, since none of us (but Alex) even has an Apple machine so we 
>>>>>> cannot
>>>>>> test and won't recklessly make public completely untested DMG packages.
>>>>>>
>>>>>> Last we heard from Alex, he had issues with the new "hardening" rules
>>>>>> of macOS. Basically it made it impossible to run a debugger (lldb), which
>>>>>> is what GIMP tries to do to self-debug when it crashes or encounter
>>>>>> critical errors (a debug feature introduced in GIMP 2.10).
>>>>>> I'm not sure he actually fixed it before going off-radar. If he
>>>>>> didn't and the solution is too complicated, a possibility is to not care
>>>>>> about this self-debugging feature of course. It's annoying if it doesn't
>>>>>> work (because it makes reporting/fixing bugs easier), but it is better to
>>>>>> have a package without the feature than none obviously. :-)
>>>>>>
>>>>>> In any case, we will definitely welcome the help. Feel free to look
>>>>>> at the scripts and propose patches/merge requests. I'm not sure if an
>>>>>> access is needed to CircleCI project to see the build details (artifacts,
>>>>>> logs and whatnot). Maybe just connecting with a github account is enough.
>>>>>> If not, we'll try to figure this out.
>>>>>>
>>>>>> Oh and last thing, if you have questions, the #gimp IRC channel on
>>>>>> irc.gimp.org is a good place where you can find most developers.
>>>>>> Thanks!
>>>>>>
>>>>>> Jehan
>>>>>>
>>>>>> Credentials: https://github.com/LMMS/lmms/pull/2271
>>>>>>>
>>>>>>>
>>>>>>> -Tres
>>>>>>>
>>>>>>> - tres.finocchi...@gmail.com
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Apr 24, 2020 at 1:11 PM Jehan Pagès via gimp-user-list <
>>>>>>> gimp-user-list@gnome.org> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> On Fri, Apr 24, 2020 at 8:16 AM Maurizio Loreti via gimp-user-list <
>>>>>>>> gimp-user-list@gnome.org> wrote:
>>>>>>>>
>>>>>>>> > Any foresight for an implementation of GIMP 2.10.18 for MacOS?
>>>>>>>> [I mean
>>>>>>>> > official, not MacPorts (that uses XQuartz) nor Partha's].
>>>>>>>> >
>>>>>>>>
>>>>>>>> Isn't it you who already asked at least twice the same thing? The
>>>>>>>> answer is

Re: [Gimp-user] MacOS

[Jehan Pagès via gimp-user-list]

the CI logs.
>>>
>>
>> I indeed know the DMG is made available on CircleCI and can be downloaded
>> in the "Artifacts" tab of builds. Maybe you'd need an account to see this,
>> no idea. Do you see the DMG link?
>>
>>
>>> I'm only a casual Gimp user though, so I'd be weary of passing a build
>>> as good on instinct alone.  Do you have a QC spreadsheet or is it more of a
>>> best-effort basis?
>>>
>>
>> To be clear, we have no idea. If this is not in the repository, it means
>> that either Alex had not documented it (yet?) or it was just in his head.
>> He has been the only one working on GIMP on macOS for like the last 2 years
>> (and before him, we had another contributor who was also alone for many
>> years; it seems we never manage to get more than 1 macOS dev at a time! ).
>>
>> I guess you could start creating a QC steps howto and contribute it to
>> the repo once you are done. :-)
>>
>> Sorry to not be of much help, but this is just how much we know nothing
>> macOS-related.
>>
>> Alex's notes are stellar btw.
>>>
>>
>> Nice to read. He did put a lot of time and effort on this. We are
>> extremely thankful to him (and to any contributor for that matter!).
>>
>> Note, I use Gimp on macOS Catalina Developer Beta so I'll know right away
>>> if the app or a particular feature is blocked and I'm more likely to have
>>> stricter (beta) hardening as Apple makes changes to the OS.
>>>
>>
>> Cool. :-)
>>
>> Jehan
>>
>>
>>> -Tres
>>>
>>> - tres.finocchi...@gmail.com
>>>
>>>
>>> On Fri, Apr 24, 2020 at 2:55 PM Jehan Pagès 
>>> wrote:
>>>
>>>> Hi Tres,
>>>>
>>>> On Fri, Apr 24, 2020 at 7:34 PM Tres Finocchiaro <
>>>> tres.finocchi...@gmail.com> wrote:
>>>>
>>>>> Jehan,
>>>>>
>>>>> I'm the macOS packager for LMMS.  I might be able to help out in his
>>>>> absence.  LMMS is written in Qt, so the dependency stack is much
>>>>> different than Gimp which is Gtk, but if there's a documented build 
>>>>> process
>>>>> via MacPorts or Homebrew, I can take a swing at it.
>>>>>
>>>>
>>>> I know there are non-official MacPorts and Homebrew because it's
>>>> written on our website. So these can be good references indeed.
>>>>
>>>> Ideally we want the build scripts to be public and the build itself to
>>>> also be public (not happen on someone's computer for obvious reasons). This
>>>> is why Alex (our macOS contributor) has done a lot of work on the build
>>>> repository: https://gitlab.gnome.org/Infrastructure/gimp-macos-build
>>>> It would be nice if continuing work were to happen on this same
>>>> repository.
>>>>
>>>> As for the build itself, it was happening on some CI service called
>>>> CircleCI (because macOS builds can be done there, unlike the GNOME Gitlab
>>>> CI machines). Builds are there:
>>>> https://circleci.com/gh/GNOME/gimp-macos-build
>>>>
>>>> Note: you'll notice that there are builds for GIMP 2.10.18 there, which
>>>> was from last time Alex was working on it. We don't really know the state
>>>> and in particular if these builds done 2 months ago work well and safely,
>>>> since none of us (but Alex) even has an Apple machine so we cannot test and
>>>> won't recklessly make public completely untested DMG packages.
>>>>
>>>> Last we heard from Alex, he had issues with the new "hardening" rules
>>>> of macOS. Basically it made it impossible to run a debugger (lldb), which
>>>> is what GIMP tries to do to self-debug when it crashes or encounter
>>>> critical errors (a debug feature introduced in GIMP 2.10).
>>>> I'm not sure he actually fixed it before going off-radar. If he didn't
>>>> and the solution is too complicated, a possibility is to not care about
>>>> this self-debugging feature of course. It's annoying if it doesn't work
>>>> (because it makes reporting/fixing bugs easier), but it is better to have a
>>>> package without the feature than none obviously. :-)
>>>>
>>>> In any case, we will definitely welcome the help. Feel free to look at
>>>> the scripts and propose patches/merge requests. I'm not sure if an access
>>>> is needed to CircleCI pr

Re: [Gimp-user] MacOS

[Jehan Pagès via gimp-user-list]

 swing at it.
>>>
>>
>> I know there are non-official MacPorts and Homebrew because it's written
>> on our website. So these can be good references indeed.
>>
>> Ideally we want the build scripts to be public and the build itself to
>> also be public (not happen on someone's computer for obvious reasons). This
>> is why Alex (our macOS contributor) has done a lot of work on the build
>> repository: https://gitlab.gnome.org/Infrastructure/gimp-macos-build
>> It would be nice if continuing work were to happen on this same
>> repository.
>>
>> As for the build itself, it was happening on some CI service called
>> CircleCI (because macOS builds can be done there, unlike the GNOME Gitlab
>> CI machines). Builds are there:
>> https://circleci.com/gh/GNOME/gimp-macos-build
>>
>> Note: you'll notice that there are builds for GIMP 2.10.18 there, which
>> was from last time Alex was working on it. We don't really know the state
>> and in particular if these builds done 2 months ago work well and safely,
>> since none of us (but Alex) even has an Apple machine so we cannot test and
>> won't recklessly make public completely untested DMG packages.
>>
>> Last we heard from Alex, he had issues with the new "hardening" rules of
>> macOS. Basically it made it impossible to run a debugger (lldb), which is
>> what GIMP tries to do to self-debug when it crashes or encounter critical
>> errors (a debug feature introduced in GIMP 2.10).
>> I'm not sure he actually fixed it before going off-radar. If he didn't
>> and the solution is too complicated, a possibility is to not care about
>> this self-debugging feature of course. It's annoying if it doesn't work
>> (because it makes reporting/fixing bugs easier), but it is better to have a
>> package without the feature than none obviously. :-)
>>
>> In any case, we will definitely welcome the help. Feel free to look at
>> the scripts and propose patches/merge requests. I'm not sure if an access
>> is needed to CircleCI project to see the build details (artifacts, logs and
>> whatnot). Maybe just connecting with a github account is enough. If not,
>> we'll try to figure this out.
>>
>> Oh and last thing, if you have questions, the #gimp IRC channel on
>> irc.gimp.org is a good place where you can find most developers.
>> Thanks!
>>
>> Jehan
>>
>> Credentials: https://github.com/LMMS/lmms/pull/2271
>>>
>>>
>>> -Tres
>>>
>>> - tres.finocchi...@gmail.com
>>>
>>>
>>> On Fri, Apr 24, 2020 at 1:11 PM Jehan Pagès via gimp-user-list <
>>> gimp-user-list@gnome.org> wrote:
>>>
>>>> Hello,
>>>>
>>>> On Fri, Apr 24, 2020 at 8:16 AM Maurizio Loreti via gimp-user-list <
>>>> gimp-user-list@gnome.org> wrote:
>>>>
>>>> > Any foresight for an implementation of GIMP 2.10.18 for MacOS?  [I
>>>> mean
>>>> > official, not MacPorts (that uses XQuartz) nor Partha's].
>>>> >
>>>>
>>>> Isn't it you who already asked at least twice the same thing? The
>>>> answer is
>>>> still the same as we told you several times already. Our (unique!) macOS
>>>> contributor has not been available for like more than a month. And to be
>>>> fair, I don't care as much about the macOS version of GIMP as I am
>>>> worried
>>>> about this contributor and hoping he (and his family) is still fine as
>>>> we
>>>> get no news.
>>>>
>>>> Since you knew already about the situation, a bit of compassion would
>>>> not
>>>> be a bad thing.
>>>>
>>>>
>>>> > If GIMP has problems with MacOS, what are these problems?
>>>> >
>>>>
>>>> Isn't *no contributor* enough of a problem by itself? The problem is
>>>> that
>>>> nobody seem to care enough to help this package happen (only enough to
>>>> **ask** for it apparently). We have called for contributors so many
>>>> times
>>>> over the years (and again recently, so much there has even been a French
>>>> specialized mac-news website who relayed the call a few weeks ago!).
>>>> This contributor could be you if you want to help packaging!
>>>> The current version of scripts are there:
>>>> https://gitlab.gnome.org/Infrastructure/gimp-macos-build
>>>>
>>>> There are only 3 possible outcomes:
>>>> 1/ This con

Re: [Gimp-user] MacOS

[Jehan Pagès via gimp-user-list]

Hi Tres,

On Fri, Apr 24, 2020 at 7:34 PM Tres Finocchiaro 
wrote:

> Jehan,
>
> I'm the macOS packager for LMMS.  I might be able to help out in his
> absence.  LMMS is written in Qt, so the dependency stack is much
> different than Gimp which is Gtk, but if there's a documented build process
> via MacPorts or Homebrew, I can take a swing at it.
>

I know there are non-official MacPorts and Homebrew because it's written on
our website. So these can be good references indeed.

Ideally we want the build scripts to be public and the build itself to also
be public (not happen on someone's computer for obvious reasons). This is
why Alex (our macOS contributor) has done a lot of work on the build
repository: https://gitlab.gnome.org/Infrastructure/gimp-macos-build
It would be nice if continuing work were to happen on this same repository.

As for the build itself, it was happening on some CI service called
CircleCI (because macOS builds can be done there, unlike the GNOME Gitlab
CI machines). Builds are there:
https://circleci.com/gh/GNOME/gimp-macos-build

Note: you'll notice that there are builds for GIMP 2.10.18 there, which was
from last time Alex was working on it. We don't really know the state and
in particular if these builds done 2 months ago work well and safely, since
none of us (but Alex) even has an Apple machine so we cannot test and won't
recklessly make public completely untested DMG packages.

Last we heard from Alex, he had issues with the new "hardening" rules of
macOS. Basically it made it impossible to run a debugger (lldb), which is
what GIMP tries to do to self-debug when it crashes or encounter critical
errors (a debug feature introduced in GIMP 2.10).
I'm not sure he actually fixed it before going off-radar. If he didn't and
the solution is too complicated, a possibility is to not care about this
self-debugging feature of course. It's annoying if it doesn't work (because
it makes reporting/fixing bugs easier), but it is better to have a package
without the feature than none obviously. :-)

In any case, we will definitely welcome the help. Feel free to look at the
scripts and propose patches/merge requests. I'm not sure if an access is
needed to CircleCI project to see the build details (artifacts, logs and
whatnot). Maybe just connecting with a github account is enough. If not,
we'll try to figure this out.

Oh and last thing, if you have questions, the #gimp IRC channel on
irc.gimp.org is a good place where you can find most developers.
Thanks!

Jehan

Credentials: https://github.com/LMMS/lmms/pull/2271
>
>
> -Tres
>
> - tres.finocchi...@gmail.com
>
>
> On Fri, Apr 24, 2020 at 1:11 PM Jehan Pagès via gimp-user-list <
> gimp-user-list@gnome.org> wrote:
>
>> Hello,
>>
>> On Fri, Apr 24, 2020 at 8:16 AM Maurizio Loreti via gimp-user-list <
>> gimp-user-list@gnome.org> wrote:
>>
>> > Any foresight for an implementation of GIMP 2.10.18 for MacOS?  [I mean
>> > official, not MacPorts (that uses XQuartz) nor Partha's].
>> >
>>
>> Isn't it you who already asked at least twice the same thing? The answer
>> is
>> still the same as we told you several times already. Our (unique!) macOS
>> contributor has not been available for like more than a month. And to be
>> fair, I don't care as much about the macOS version of GIMP as I am worried
>> about this contributor and hoping he (and his family) is still fine as we
>> get no news.
>>
>> Since you knew already about the situation, a bit of compassion would not
>> be a bad thing.
>>
>>
>> > If GIMP has problems with MacOS, what are these problems?
>> >
>>
>> Isn't *no contributor* enough of a problem by itself? The problem is that
>> nobody seem to care enough to help this package happen (only enough to
>> **ask** for it apparently). We have called for contributors so many times
>> over the years (and again recently, so much there has even been a French
>> specialized mac-news website who relayed the call a few weeks ago!).
>> This contributor could be you if you want to help packaging!
>> The current version of scripts are there:
>> https://gitlab.gnome.org/Infrastructure/gimp-macos-build
>>
>> There are only 3 possible outcomes:
>> 1/ This contributor finally comes back and he continues *alone*  to do
>> all the mac packaging.
>> 2/ Other people finally show they care by contributing.
>> 3/ A mix of 1/ and 2/ which is the best outcome!
>>
>> In none of these scenarios just asking without contributing helps in any
>> way.
>> Thanks for either helping or understanding. 
>>
>> Jehan
>>
>>
>> > --
>> > Maurizio Loreti  --  maurizio.lor...@gmail.com
>> > 

Re: [Gimp-user] MacOS

[Jehan Pagès via gimp-user-list]

Hello,

On Fri, Apr 24, 2020 at 8:16 AM Maurizio Loreti via gimp-user-list <
gimp-user-list@gnome.org> wrote:

> Any foresight for an implementation of GIMP 2.10.18 for MacOS?  [I mean
> official, not MacPorts (that uses XQuartz) nor Partha's].
>

Isn't it you who already asked at least twice the same thing? The answer is
still the same as we told you several times already. Our (unique!) macOS
contributor has not been available for like more than a month. And to be
fair, I don't care as much about the macOS version of GIMP as I am worried
about this contributor and hoping he (and his family) is still fine as we
get no news.

Since you knew already about the situation, a bit of compassion would not
be a bad thing.


> If GIMP has problems with MacOS, what are these problems?
>

Isn't *no contributor* enough of a problem by itself? The problem is that
nobody seem to care enough to help this package happen (only enough to
**ask** for it apparently). We have called for contributors so many times
over the years (and again recently, so much there has even been a French
specialized mac-news website who relayed the call a few weeks ago!).
This contributor could be you if you want to help packaging!
The current version of scripts are there:
https://gitlab.gnome.org/Infrastructure/gimp-macos-build

There are only 3 possible outcomes:
1/ This contributor finally comes back and he continues *alone*  to do
all the mac packaging.
2/ Other people finally show they care by contributing.
3/ A mix of 1/ and 2/ which is the best outcome!

In none of these scenarios just asking without contributing helps in any
way.
Thanks for either helping or understanding. 

Jehan


> --
> Maurizio Loreti  --  maurizio.lor...@gmail.com
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Export to pdf

[Jehan Pagès via gimp-user-list]

Hi!

On Fri, May 3, 2019 at 10:07 PM Uwe Sassnowski  wrote:

> Hello,
>
> I designed a brochure in gimp with several picture and text levels /
> layers. Then I combined all pictures and texts to one layer and exported it
> to pdf. I sent the pdf to the printing company for printing. The print was
> not in a perfect quality. The printing company told us that they normally
> get pdf's from their clients where they can make changes to improve the
> quality. I tried to export to pdf without combining all layers. But then
> all texts are changed in format. I can create pictures from the text
> layers. But then I and the printing company cannot go into the text
> anymore. Is there a way to export to pdf all single pictures and texts
> without combining all layers so that the printing company can touch all
> pictures and texts and to reach a higher quality print?
>

I can't remember if our implementation for PDF export rasterize text or
not. In any case, if you want to lay out various items and similar
activities common for printed objects, I would suggest to use Inkscape
and/or Scribus. I mean: you can still use GIMP for obviously raster parts
(drawing, photographs, etc.). But when it comes to complex designs,
Inkscape may be the most appropriate tool. And if you have objects to set
precisely on your page, Scribus may be better suited (it won't do that much
more than what Inkscape does, simply it's rather *how* it does it which may
make it much more straightforward when you think in term of print).

Now GIMP can also work very fine, even if you have texts. But then you have
to understand well the printing process to provide a perfect raster object
to the printshop and not expect them to edit it (we certainly don't want
printshops to edit our designs in fact!).

Jehan


>
> With best regards,
> Uwe
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list



-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Rights

[Jehan Pagès via gimp-user-list]

Hi!

Yes it's not a problem. Anything which came with GIMP (core version) can be
used to do whatever you want. This includes the tool, but also data such as
brushes, patterns, etc.
We don't control licensing of data from third-party (for instance if you
downloaded some pattern from some random website). But core data and core
features are not a problem for commercial work.

See also our FAQ:
https://www.gimp.org/docs/userfaq.html#can-i-use-gimp-commercially

Jehan

On Tue, Apr 9, 2019 at 11:07 PM Voltane 17 via gimp-user-list <
gimp-user-list@gnome.org> wrote:

> Hello,
>
> I decided to use Gimp in order to make a game for Android. But i would like
> to sell it. Can i use all the software's functions ? Like the elliptic
> selection or rectangular selection to create graphics, with the rights to
> sell the game with the graphics created with the software?
>
>   Thank you for advance
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Surface pro 4 pressure sensitivity

[Jehan Pagès via gimp-user-list]

Hi!

On Wed, Dec 5, 2018 at 6:40 PM jason kolano via gimp-user-list <
gimp-user-list@gnome.org> wrote:

> Hi.  I can't get pressure sensitivity with my pen on my surface pro using
> gimp.  Does anyone have experience with this?
>

I am guessing it may work if you install the optional Wintab drivers from
there: https://www.microsoft.com/en-us/download/details.aspx?id=49498

Basically GIMP only has support for Wintab drivers (and in particular not
the new Ink API which Microsoft is now pushing forward; though we'd love to
have support but that would require someone to step up and implement this
in GTK+).

Note that some people (on bug reports) have problems with higher versions
of the Surface Pro and Microsoft does not mention anymore optional Wintab
drivers from v5 and above. Therefore it is possible that GIMP may not work
on recent versions, but you may still be fine with the version 4 which you
have.

Of course this is all just a lot of assumptions from what I could gather
from the web, since I have not such a device (and I think none of other
GIMP developers have one either).

If you manage to get GIMP working on the surface pro 4, please tell us.
This will be an interesting input.
Also you may want to try with the version GIMP 2.10.6, and not the latest
2.10.8, as there is a bug which affected some tablets on Windows (no idea
if it would affect this one too, but no harm on being double sure).

Jehan


> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Why 2.10.4 not 2.10.6 at my Debian

[Jehan Pagès via gimp-user-list]

On Tue, Oct 2, 2018 at 5:21 AM sebul  wrote:

> Thank. But...
>
> I run
> flatpak update
> and
> flatpak run org.gimp.GIMP -n
> and
> I get
> GIMP 2.10.2
> Neither 2.10.6 nor 2.10.4
>
> How can I get 2.10.6 ?
>

Well that's the way.
Is something happening when running `flatpak update`? (like do you see
anything updating?)
Maybe you installed as user, in which case, you need to run: flatpak update
--user

Jehan


> 2018년 9월 30일 (일) 오전 12:21, Jehan Pagès 님이 작성:
>
>> Hi!
>>
>> On Fri, Sep 28, 2018 at 11:54 PM sebul via gimp-user-list <
>> gimp-user-list@gnome.org> wrote:
>>
>>> Hello. I use Debian 9.5
>>>
>>> https://www.gimp.org/news/2018/08/19/gimp-2-10-6-released/
>>> says gimp 2.10.6
>>> But
>>>
>>> flatpak install
>>> https://flathub.org/repo/appstream/org.gimp.GIMP.flatpakref
>>> says
>>> error: App org.gimp.GIMP, branch stable is already installed
>>>
>>> flatpak run org.gimp.GIMP -n &
>>> runs GIMP but this gimp version is 2.10.4 not 2.10.6
>>>
>>>
>> Flatpak has the last version, which is indeed 2.10.6. But maybe you
>> installed it when it was 2.10.4 and have not updated it yourself since.
>> Please run `flatpak update` to do so (if you have some desktop with
>> deeper flatpak support, like a recent GNOME, it could even propose you to
>> update by itself) and you should get GIMP 2.10.6.
>>
>>
>>> apt-get install gimp
>>> installs gimp 2.8 not 2.10
>>>
>>
>> As many distributions, they are late in updating packages, and in
>> particular keep older versions for stability reasons (even though we think
>> GIMP 2.10 is stabler, sometimes "stable" means not breaking habits).
>> In any case, we don't maintain distribution packages. We don't know when
>> they will update.
>>
>>>
>>> How can I run GIMP 2.10.6 ?
>>>
>>
>> As explained above. :-)
>> Have fun!
>>
>> Jehan
>>
>>
>>> --
>>> 세벌식 http://sebul.sarang.net 
>>> ___
>>> gimp-user-list mailing list
>>> List address:gimp-user-list@gnome.org
>>> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
>>> List archives:   https://mail.gnome.org/archives/gimp-user-list
>>
>>
>>
>> --
>> ZeMarmot open animation film
>> http://film.zemarmot.net
>> Liberapay: https://liberapay.com/ZeMarmot/
>> Patreon: https://patreon.com/zemarmot
>> Tipeee: https://www.tipeee.com/zemarmot
>>
>
>
> --
> 세벌식 http://sebul.sarang.net 
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] Why 2.10.4 not 2.10.6 at my Debian

[Jehan Pagès via gimp-user-list]

Hi!

On Fri, Sep 28, 2018 at 11:54 PM sebul via gimp-user-list <
gimp-user-list@gnome.org> wrote:

> Hello. I use Debian 9.5
>
> https://www.gimp.org/news/2018/08/19/gimp-2-10-6-released/
> says gimp 2.10.6
> But
>
> flatpak install
> https://flathub.org/repo/appstream/org.gimp.GIMP.flatpakref
> says
> error: App org.gimp.GIMP, branch stable is already installed
>
> flatpak run org.gimp.GIMP -n &
> runs GIMP but this gimp version is 2.10.4 not 2.10.6
>
>
Flatpak has the last version, which is indeed 2.10.6. But maybe you
installed it when it was 2.10.4 and have not updated it yourself since.
Please run `flatpak update` to do so (if you have some desktop with deeper
flatpak support, like a recent GNOME, it could even propose you to update
by itself) and you should get GIMP 2.10.6.


> apt-get install gimp
> installs gimp 2.8 not 2.10
>

As many distributions, they are late in updating packages, and in
particular keep older versions for stability reasons (even though we think
GIMP 2.10 is stabler, sometimes "stable" means not breaking habits).
In any case, we don't maintain distribution packages. We don't know when
they will update.

>
> How can I run GIMP 2.10.6 ?
>

As explained above. :-)
Have fun!

Jehan


> --
> 세벌식 http://sebul.sarang.net 
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list



-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] GIMP SWAP Folder not honored

[Jehan Pagès via gimp-user-list]

Hi!

On Tue, Sep 18, 2018 at 11:33 AM stormy  wrote:

> >Hi,
> >Do you have any link for developers so that we know where to look for
> >regarding this SWAP settings?
>
> I'm not sure what you mean by "link", the "SWAP Folder" is a GIMP feature,
> it is
> located in EDIT->Preferences, then scroll down to FOLDERS, there are two
> options
> one "Temporary folder" and other is "Swap folder".
>
>
Oh sorry. I thought this was some OS settings where you could configure
where programs should cache their data by default.

Anyway I opened a bug report on our side:
https://gitlab.gnome.org/GNOME/gimp/issues/2224

Jehan


> >Does it go to one or the other? I'm sure it does the right thing, but
> >I
> >doubt that it randomly use one folder or another at different runs,
> >right?
>
> It never went to the location I set in the actual preferences dialog,
> instead it
> went into one or the other locations , that depended on the
> cleanup/reinstall
> sequence i took (did this many times), but once it chose a location , it
> kept
> using it for the duration of that install cycle.. if i were to cleanup and
> reinstall, it might choose the other location, but, never the one
> specified in
> the prefs.
>
>
> >special case the cache directory for this OS. If you tell us more
> >about
> >this SWAP settings on Windows (and in particular what we have to look
> >for?
>
> I'm talking about GIMP's internal swap, not windows swap.  I'm just an
> end-user,
> do not know how gimp uses this 'swap' :)
>
> >Is there an API to know this folder? An env variable), this would
> >help.
>
> Maybe there is an env var, I just used the GUI interface to try and
> relocate the
> swap to a drive with more space.
>
> >Also what is the proper default cache folder expected on Windows if
> >none
> >were explicitly set?
>
> I guess this is OK:
>
> c:\Users\myuser\AppData\Local\Microsoft\Windows\INetCache\gegl-0.4
>
> as for a default, or leave it like today, to choose based on some other
> window's
> specific logic.
>
> >Please when you answer, mention me explicitly (I have filters) so that
> >I
> >don't miss your answer.
> >Thanks.
> >
> >Jehan
>
> hopefully you see this Jehan :)
>
> --
> stormy (via www.gimpusers.com/forums)
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] GIMP SWAP Folder not honored

[Jehan Pagès via gimp-user-list]

Hi,

On Fri, Sep 14, 2018 at 12:22 AM stormy  wrote:

> On Windows 10, uninstalled 2.8.18, and reinstalled 2.10.6, however, the
> SWAP &
> Temporary folders, in Edit-Properties->Folders, do not appear to be
> honored.
>

Do you have any link for developers so that we know where to look for
regarding this SWAP settings?
Keep in mind all the core devs do not use Windows, so do not hesitate to be
accurate and consider we don't know much about Windows.


> Set the Temporary folder to F:\tmp and Swap folder to F:\swp, restarted
> GIMP,
> and PC...
>
> however, no matter what, GIMP still goes to either:
>
> c:\Users\myuser\.cache\gegl-0.4\12056-shared.swap
>
>
> c:\Users\myuser\AppData\Local\Microsoft\Windows\INetCache\gegl-0.4\12056-shared.swap
>

Does it go to one or the other? I'm sure it does the right thing, but I
doubt that it randomly use one folder or another at different runs, right?
:-)


> That "C:" drive is low on space, only few GB, and drive F has a TB free :)
>
> I've reinstalled many times, and removed all possible files from
> directories,
> and registry as per various urls online, however, no matter what, each new
> re-install, gimp ignores the folders settings, and writes directly to the
> above
> locations... any ideas?
>

Yeah it obviously follows XDG folder (which is a spec for Linux
distributions), and that is obviously not right for Windows. We should
special case the cache directory for this OS. If you tell us more about
this SWAP settings on Windows (and in particular what we have to look for?
Is there an API to know this folder? An env variable), this would help.
Also what is the proper default cache folder expected on Windows if none
were explicitly set?

Please when you answer, mention me explicitly (I have filters) so that I
don't miss your answer.
Thanks.

Jehan


> Stormy.
>
> --
> stormy (via www.gimpusers.com/forums)
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] gimp 2.10.4 midi not working

[Jehan Pagès via gimp-user-list]

Hi!

On Tue, Aug 14, 2018 at 5:09 AM patrick via gimp-user-list <
gimp-user-list@gnome.org> wrote:

> When trying to compile on Raspbian (debian) Stretch, I am not able to
> install all the deps:
>
> - Error: missing dependency babl >= 0.1.52
>   - Error: missing dependency gegl-0.4 >= 0.4.4
>   - Error: missing dependency glib >= 2.54.2
>   *** Test for GLIB failed
>   - Error: missing dependency gegl
>   *** Could not find native gegl executable in your PATH.
>   - Error: missing dependency fontconfig >= 2.12.4
>   - Error: missing dependency gexiv2 >= 0.10.6
>   - Error: missing dependency poppler-glib >= 0.44.0
>
> glib >= 2.54.2 is really a show stopper on this distribution afaik.
>
> I would indeed not install a glib different from the distribution one
system-wide (on any distribution), since it is low level and widely used
(and could break other programs), but it is easy to install it in a custom
prefix and have GIMP only use this version.

Unless you mean that it is impossible to build glib 2.54.2 on Raspbian. In
this case, I have no idea (but this may be the occasion to fix whatever
needs to be).


>
> About the midi problem with the flatpak, it is kind of documented
> here, so it doesn't look too good for me:
> https://github.com/flatpak/flatpak/issues/12
>
>
Yes the MIDI support is not built in GIMP on Flatpak. And you should not
expect this to work any time soon (I mean, it may happen any day, who
knows?! But it is quite some work and it doesn't look like anyone is really
interested into this).

I did not answer on this in my first email as I was unsure you were really
asking about this specific feature (you did not ask about this in the body
of the email, only as a short mention in the title). :-)


> Not an expert on the subject, but when using snap you can add
> permission using interfaces:
> https://docs.snapcraft.io/reference/interfaces
>
> This is the same thing for Flatpak, but someone needs to implement the
said permission first.
In the case of this specific feature, it would require someone to implement
the said portal (possibly several times, as it may depend on the desktop
for instance; don't know if this is the case here), then someone to
re-implement the feature in GIMP instead of using libudev (which is how we
currently implement this feature, but this won't ever work; libudev won't
likely ever be usable in a Flatpak sandbox).


> So the question is: anyone using gimp 2.10.4 with midi support on rpi3?
>

You won't find anyone, this is currently not possible.

If having this feature is a blocker to you, then yes, you have to install
GIMP some other way, either by building it yourself or waiting for the
distribution to get a GIMP 2.10 package; I saw that Debian Testing just got
GIMP 2.10.2. This should reach Raspbian at some point. :-)

Jehan


> Thanks
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] gimp 2.10.4 midi not working

[Jehan Pagès via gimp-user-list]

Hi!

On Sun, Aug 12, 2018 at 5:57 PM patrick via gimp-user-list <
gimp-user-list@gnome.org> wrote:

> No, only gimp 2.8 something is available (I want mypaint's brushes
> only available in 2.10.4). Also it looks like I cannot compile from
>

Could you be more explicit on what you are trying to do and why you say
GIMP 2.10.4 is not available? Do you mean in a particular distribution? If
so, you should ask the distribution packagers, not us.


> source on RPI / raspbian (debian optimized for rpi). Any advice?
>

We provide a flatpak of GIMP, which builds on 4 architectures: x86, x86_64,
arm and aarch64.
So that means that installing GIMP on a RPI should be a matter of one
command line.
Please see for details: https://www.gimp.org/downloads/

Once you installed GIMP on Raspberry Pi with flatpak, I'd be interested to
get a feedback to know how it went (it should work, but I never tried
myself).

Jehan


> Thanks
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list