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

[James Cloos via gimp-developer-list]

i forgot to mention that the one reasonable alternative to smtp lists is nntp.

it is ok to configure the all to "moderated" so that submission is via smtp.

or code the server to accept via nntp but hold for approval.

if that is desired.

but everything is floss.
and people can have a local copy if they want.
or not if they do not want.

push is still best, but nntp is at least an ethical alternative.

http browser junk is not.

-JimC
-- 
James Cloos  OpenPGP: 0x997A9F17ED7DAEA6
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[Mukund Sivaraman]

Hey Kevin :)

I hope you're keeping well.

On Fri, Oct 21, 2022 at 11:46:12AM -0400, Kevin Cozens wrote:
> On 2022-10-17 12:38, Jehan Pagès via gegl-developer-list wrote:
> > The GNOME Foundation has been moving all its discussions to a Discourse
> > forum, progressively:
> 
> I misread the above and thought it referred to the live chat system called
> Discord. I wondered how that could possibly replace an email system.
> 
> I found a message from GNOME about the change and found it is due to mailman
> still needing Python 2. I'm a little surprised that no one has volunteered
> to update it to work with Python 3.

There is a Mailman 3 which is a rewrite of Mailman and uses Python 3 as
the language. Some operators of Mailman 2 lists moved to Mailman 3. It
is not quite the same system, but depending on whether one wants to have
mailing lists, it can be used. An example is the Fedora mailing lists
that use Mailman 3.

An alternate that is also popular these days is mlmmj (mailing list
manager) + public-inbox (archive). An example is kernel.org which has
been switching lists to it.

email has its problems, and mailing lists have their issues with message
authentication schemes like DKIM, but an experienced person can make it
work well.

Mukund


signature.asc
Description: PGP signature
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[James Cloos via gimp-developer-list]

PD> It's worth noting that in general, you can use a Discourse forum _entirely_
PD> in mailing-list mode if you want to.  That is, you'll still see emails
PD> coming in from the system and can reply to them in your mail client of
PD> choice.


really?  last i saw it blocked new $subject threads and only permitted
replies to existing threads.

and screws up threading when $subject changes.

very much not _entirely_ in mailing-list mode.

plus you still have to screw around with tortuous ecmascript to subscribe.

now if they have fixed those fatal flaws, 

but otherwise the change is harm w/o value.

-JimC
-- 
James Cloos  OpenPGP: 0x997A9F17ED7DAEA6
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[GSR - FR]

Hi,
gimp-developer-list@gnome.org (2022-10-22 at 0839.17 -0500):
> > While wandering around the new site, yes, it shows "This topic will
> > close 14 days after the last reply." near the bottom of threads.
> 
> This is entirely a site setting that can be changed by the admins of the
> site.
> I believe the Gnome administrator considered it here:
> https://discourse.gnome.org/t/longer-auto-lock-timeout-for-topic-threads/7233/4

Interesting that the reason for so short open time is lack of
moderators, then say that moderators can be contacted to reopen
threads.

Couple of posts there reasoned that some months would be more useful.

> The point is to avoid bumping necro-threads - it's easy enough to start a
> new topic and link/reference the previous topic (or individual posts) as
> needed.

Do posters remember to make the proper reference? Do people involved
in the closed thread get notified in that case? Or in the case that
the message is edited later to add the reference (or tags that were
not added properly at creation time)? Is the world moving so fast that
14-30 days are necro now? Hey, look, a squirrel!!!

Last post in thread mentioned an idea to smooth all this a bit (add
"New Linked Topic"). Page says closed while showing Reply button, so
it got implemented but forgot to label it properly, or there is
another kind of bug.

Cheers,
GSR
 
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[Marco Ciampa via gimp-developer-list]

On Mon, Oct 24, 2022 at 01:17:50PM +0300, Cristian Secară wrote:
> În data de Fri, 21 Oct 2022 11:25:05 -0500, Pat David via gimp-developer-list 
> a scris:
> > Change sucks.  I understand.  
> 
> When things gets complicated instead of getting simplified, that sucks for 
> sure.

Yeah!

-- 

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

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

[Pat David via gimp-developer-list]

> While wandering around the new site, yes, it shows "This topic will
> close 14 days after the last reply." near the bottom of threads.

This is entirely a site setting that can be changed by the admins of the
site.
I believe the Gnome administrator considered it here:
https://discourse.gnome.org/t/longer-auto-lock-timeout-for-topic-threads/7233/4

The point is to avoid bumping necro-threads - it's easy enough to start a
new topic and link/reference the previous topic (or individual posts) as
needed.

On Fri, Oct 21, 2022 at 5:38 PM GSR - FR 
wrote:

> Hi,
> gimp-developer-list@gnome.org (2022-10-21 at 2237.14 +0200):
> > Is it true that topics get auto-locked after few weeks? That doesn't
> > seem pretty smart in terms of software development or user support at
> > all, if it's true.
>
> While wandering around the new site, yes, it shows "This topic will
> close 14 days after the last reply." near the bottom of threads. If
> you visit any index, threads showing 16d e.g. in the right side have
> lock icon in the left side.
>
> Cheers,
> GSR
>
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>


-- 
https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[GSR - FR]

Hi,
gimp-developer-list@gnome.org (2022-10-21 at 2237.14 +0200):
> Is it true that topics get auto-locked after few weeks? That doesn't
> seem pretty smart in terms of software development or user support at
> all, if it's true.

While wandering around the new site, yes, it shows "This topic will
close 14 days after the last reply." near the bottom of threads. If
you visit any index, threads showing 16d e.g. in the right side have
lock icon in the left side.

Cheers,
GSR
 
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[wwp via gimp-developer-list]

Hello,


On Fri, 21 Oct 2022 11:25:05 -0500 Pat David via gimp-developer-list 
 wrote:

> It's worth noting that in general, you can use a Discourse forum _entirely_
> in mailing-list mode if you want to.  That is, you'll still see emails
> coming in from the system and can reply to them in your mail client of
> choice.
> On the backend, this translates into emails from you becoming forum posts
> on discourse, and new posts showing up as new messages in your inbox.
> 
> We've got a bunch of users at pixls using it in mailing-list mode (myself
> included for a while initially).
> 
> The caveat, of course, is that you'll still need to register for an account
> on the forum in the first place (to provide your email address and set up
> any settings you want initially).
> Another caveat is that the forum administrators need to enable this as an
> option - particularly for mailing *into* the forum to start a new topic (I
> have this turned off be default on pixls but will enable it shortly for
> y'all).
[snip]

Is it true that topics get auto-locked after few weeks? That doesn't
seem pretty smart in terms of software development or user support at
all, if it's true.
The same topic is discussed here and there, it's interesting (and a bit
scary) to see feedback coming from discourse users - currently I'm
following the midnight commander ML as well, hosted at gnome.org for
historical reasons but definitely independent nowadays.


Regards,

-- 
wwp
https://useplaintext.email/


pgpOjab4tQpsz.pgp
Description: OpenPGP digital signature
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[Pat David via gimp-developer-list]

Hi all!

It's worth noting that in general, you can use a Discourse forum _entirely_
in mailing-list mode if you want to.  That is, you'll still see emails
coming in from the system and can reply to them in your mail client of
choice.
On the backend, this translates into emails from you becoming forum posts
on discourse, and new posts showing up as new messages in your inbox.

We've got a bunch of users at pixls using it in mailing-list mode (myself
included for a while initially).

The caveat, of course, is that you'll still need to register for an account
on the forum in the first place (to provide your email address and set up
any settings you want initially).
Another caveat is that the forum administrators need to enable this as an
option - particularly for mailing *into* the forum to start a new topic (I
have this turned off be default on pixls but will enable it shortly for
y'all).

With that being said, if your primary view of internet forums is from
previous software stacks (simple machines, phpBB, etc.) I would *strongly*
suggest you give Discourse a fair shake.  It is light-years beyond any
forum software I've ever seen and the developers are focused on advancing
meaningful interactions and discussions.

Change sucks.  I understand.  Sometimes it's for a good reason and might
surprise you with its utility and features.

pat

On Fri, Oct 21, 2022 at 10:46 AM Kevin Cozens  wrote:

> On 2022-10-17 12:38, Jehan Pagès via gegl-developer-list wrote:
> > The GNOME Foundation has been moving all its discussions to a Discourse
> > forum, progressively:
>
> I misread the above and thought it referred to the live chat system called
> Discord. I wondered how that could possibly replace an email system.
>
> I found a message from GNOME about the change and found it is due to
> mailman
> still needing Python 2. I'm a little surprised that no one has volunteered
> to update it to work with Python 3.
>
> > Instead, people wishing to discuss about GIMP are expected to use
> GNOME's
> > Discourse instance. In particular 2 tags were created for us:
>
> The replacement to the mailing list is a forum based site. I don't like
> forums. I find it hard to follow the thread of a discussion. The use of a
> forum also means I have to go to the site, login, then search for messages
> that might be of interest to me. I don't see myself using the forum site.
>
> Once the mailing list goes away I will feel rather detached from the GIMP
> community and thus it will feel like the end of an almost 30 year
> involvement with the project. For now I will stay connected to the gimp
> IRC
> channel.
>
> --
> Cheers!
>
> Kevin.
>
> http://www.ve3syb.ca/   | "Nerds make the shiny things that
> https://www.patreon.com/KevinCozens | distract the mouth-breathers, and
>  | that's why we're powerful"
> Owner of Elecraft K2 #2172  |
> #include  | --Chris Hardwick
>
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>


-- 
https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[Kevin Cozens]

On 2022-10-17 12:38, Jehan Pagès via gegl-developer-list wrote:
The GNOME Foundation has been moving all its discussions to a Discourse 
forum, progressively: 


I misread the above and thought it referred to the live chat system called 
Discord. I wondered how that could possibly replace an email system.


I found a message from GNOME about the change and found it is due to mailman 
still needing Python 2. I'm a little surprised that no one has volunteered 
to update it to work with Python 3.


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


The replacement to the mailing list is a forum based site. I don't like 
forums. I find it hard to follow the thread of a discussion. The use of a 
forum also means I have to go to the site, login, then search for messages 
that might be of interest to me. I don't see myself using the forum site.


Once the mailing list goes away I will feel rather detached from the GIMP 
community and thus it will feel like the end of an almost 30 year 
involvement with the project. For now I will stay connected to the gimp IRC 
channel.


--
Cheers!

Kevin.

http://www.ve3syb.ca/   | "Nerds make the shiny things that
https://www.patreon.com/KevinCozens | distract the mouth-breathers, and
| that's why we're powerful"
Owner of Elecraft K2 #2172  |
#include  | --Chris Hardwick

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

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

[Paka via gimp-developer-list]

* Michael Schumacher via gimp-developer-list  
[10-19-22 06:18]:
> 
> Am 19.10.22 um 07:43 schrieb Joel Rees via gimp-developer-list
> > Not a confidence builder. Which means, yeah, lurkers like me will likely
> > disappear from the community.
> 
> Lurking is comparatively easy, though - if you are on
> https://discourse.gnome.org/tag/gimp and logged in (this isn't really a
> different requirement to being subscribed to a mailing list), you have
> the notifications bell icon on that site, and can select there what kind
> of notification mails you are receiving for this tag. I've set this to
> "Watching", for example - this should allow me to follow the discussions
> just like on an existing list.
> 
> One downside is that you can't really determine from the notification
> mails that they are for the gimp tag, but their List-ID header tells you
> that they are from GNOME discourse, at least.
> 
> What can be expected is a much higher volume than on the lists, though -
> so taking care of the notifications with mail client rules is likely a
> necessity.

that is: If one prefers forums which have always appeared to me as a bowl
of spaghetti soup, "Not a Good Thing!"


-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet oftc
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[Michael Schumacher via gimp-developer-list]

Am 19.10.22 um 07:43 schrieb Joel Rees via gimp-developer-list

Not a confidence builder. Which means, yeah, lurkers like me will likely
disappear from the community.


Lurking is comparatively easy, though - if you are on
https://discourse.gnome.org/tag/gimp and logged in (this isn't really a
different requirement to being subscribed to a mailing list), you have
the notifications bell icon on that site, and can select there what kind
of notification mails you are receiving for this tag. I've set this to
"Watching", for example - this should allow me to follow the discussions
just like on an existing list.

One downside is that you can't really determine from the notification
mails that they are for the gimp tag, but their List-ID header tells you
that they are from GNOME discourse, at least.

What can be expected is a much higher volume than on the lists, though -
so taking care of the notifications with mail client rules is likely a
necessity.

--
Regards,
Michael



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

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

[Joel Rees via gimp-developer-list]

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
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[Jehan Pagès via gimp-developer-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-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[Jehan Pagès via gimp-developer-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 Discourse
> and mailing list technologies. GIMP is not a discussion platform, we only
> provide these channels on the side because it's a cool community tool, but
> we cannot spend all our time managing these. This is why we need to go with
> the flow of what GNOME is proposing (as long as it's not completely wrong;
> e.g. if

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

[Rick Strong]

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. 

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 Discourse
and mailing list technologies. GIMP is not a discussion platform, we only
provide these channels on the side because it's a cool community tool, but
we cannot spend all our time managing these. This is why we need to go with
the flow of what GNOME is proposing (as long as it's not completely wrong;
e.g. if they had proposed to go for some walled garden proprietary network
for the main discussion channels, I would have questioned the choice). I am
not into gamification, infinite scrolls or such things either. Us accepting
this platform is not about us wanting these. It's really about having a
limited core team and nobody highly interested into maintaining complicated
infrastructure for a different system than what GNOME does. That's about it.

Also for the 2 people who sent private emails, forgive me for not answering
directly and privately to

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

[Rick Strong]

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

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-l...@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list 


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

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

[Ken Moffat via gimp-developer-list]

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.

ĸ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
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

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

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 Discourse
and mailing list technologies. GIMP is not a discussion platform, we only
provide these channels on the side because it's a cool community tool, but
we cannot spend all our time managing these. This is why we need to go with
the flow of what GNOME is proposing (as long as it's not completely wrong;
e.g. if they had proposed to go for some walled garden proprietary network
for the main discussion channels, I would have questioned the choice). I am
not into gamification, infinite scrolls or such things either. Us accepting
this platform is not about us wanting these. It's really about having a
limited core team and nobody highly interested into maintaining complicated
infrastructure for a different system than what GNOME does. That's about it.

Also for the 2 people who sent private emails, forgive me for not answering
directly and privately to you. It's not against you, I just hope you will
understand I am trying to preserve my mental sanity here. Someone was even
apparently "shocked" that I used a gmail account. The reason is actually
exactly the same (avoiding private emails): historically I wanted to avoid
spreading my main email address too much (even though I now realize it was
a vain wish, I was young back then! 😜) so I created this account as a
trash email, maybe 15 years ago, and that's the address I historically used
to subscribe to mailing lists. I am still receiving uncountable numbers of
emails daily.
And now you'll understand why I am doing a single an

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

[Jehan Pagès via gimp-developer-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-l...@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-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] GIMP 2.99.12 Python User Script's Localization

[ShiroYuki Mot via gimp-developer-list]

Dear Ofnuts, Thanks for your reply.

In my environment, the results are a little different.
Are these useful?

GIMP 2.99.12 Python Console
Python 3.10.6 (main, Aug 12 2022, 18:00:29)  [GCC 12.1.0 64 bit (AMD64)]
>>> import os
>>> os.environ['LANG']
Traceback (most recent call last):
  File "", line 1, in 
  File "C:\Program Files\GIMP 2.99\lib\python3.10\os.py", line 679, in
__getitem__
raise KeyError(key) from None
KeyError: 'LANG'
>>> os.environ['LANGUAGE']
'ja'
>>>
>>> import sys
>>> sys.platform
'win32'
>>> sys.getwindowsversion()
sys.getwindowsversion(major=10, minor=0, build=19044, platform=2,
service_pack='')

2022年8月31日(水) 22:00 Ofnuts via gimp-developer-list <
gimp-developer-list@gnome.org>:

> PS: of course your Gimp should be working in Japanese (which it will be
> if these environment variables are set when you start Gimp)
>
> On 31/08/2022 14:45, Ofnuts via gimp-developer-list wrote:
> > Just re-checked, works for me. What are the environment values in the
> > Python console?
> >
> > >>> os.environ['LANG']
> > 'fr_FR.UTF-8'
> > >>> os.environ['LANGUAGE']
> > 'fr_FR'
> >
> > 'fr_FR' should be 'ja_JP' for you (and possibly only one of these is
> > necessary)
> >
> >
> > On 31/08/2022 10:58, ShiroYuki Mot wrote:
> >> Not localized!
> >> Am I doing something wrong?
> >>
> >> (I've tried replacing '_' with '-' or renaming the .mo file, but the
> >> result was the same.)
> >>
> >> cmd.exe Tree View
> >>
> >> Microsoft Windows [Version 10.0.19044.1889]
> >> (c) Microsoft Corporation. All rights reserved.
> >>
> >> C:\Users\UserA>tree C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins /F
> >>
> >> C:\USERS\USERA\APPDATA\ROAMING\GIMP\2.99\PLUG-INS
> >> └─Shiro_Dialog_Args6_Test_API3
> >> │  Shiro_Dialog_Args6_Test_API3.py
> >> │
> >> ├─locale
> >> │  └─ja
> >> │  └─LC_MESSAGES
> >> │  Shiro_Dialog_Args6_Test_API3.mo
> >> │
> >> └─work
> >> Shiro_Dialog_Args6_Test_API3.mo
> >> Shiro_Dialog_Args6_Test_API3.po
> >> Test.pot
> >>
> >>  Notice: .pot = Shift-JIS(cp932) ANSI / .po = UTF-8 / UTF-8 (NoBOM)
> >>: OS = Windows 10 Japanese Edition
> >>
> >> Code
> >>
> >> ## GimpPlugIn virtual methods ##
> >> def do_set_i18n(self, procname):
> >> return True, 'Shiro_Dialog_Args6_Test_API3', None
> >> def do_query_procedures(self):
> >> return [ 'python-fu-shiro-dialog-args6-test-api3' ]
> >>
> >> Zipped File  Shiro_Dialog_Args6_Test_API3.zip
> >>
> >> 2022年8月30日(火) 19:37 ShiroYuki Mot :
> >>
> >> Dear Ofnuts.
> >>
> >> Thanks for presenting the solution.
> >> It was detailed and easy to understand.
> >> I'm glad that this clears up my questions. :)
> >> I'll try this tonight.
> >>
> >> 2022年8月30日(火) 18:40 Ofnuts via gimp-developer-list
> >> :
> >>
> >> My own plugin does:
> >>
> >>  def do_set_i18n(self, *args):
> >>  print(f'do_set_i18n({args})')
> >>  return True, 'ofn-guides-presets',None
> >>
> >> (where 'ofn-guides-presets' is the same same as the plugin
> >> python file
> >> itself, and as I understand it, if the I18N domain is the same
> >> name as the plugin file, you don't even need to define this
> >> method,
> >> because it's the default behavior.
> >>
> >> Then you create the .mo file(s)  and put them in a
> >> locale/{language
> >> code}/LC_MESSAGES subdirectory of your plugin directory.
> >> ofn-guides-presets/
> >> ├── locale
> >> │   └── fr
> >> │   └── LC_MESSAGES
> >> │   └── ofn-guides-presets.mo # messages for French
> >> └── ofn-guides-presets.py   # plugin code
> >>
> >> And yes, using 'gimp30-python' in your own scripts doesn't
> >> make much
> >> sense (it does for scripts delivered with Gimp, that share the
> >> message
> >> base with other code).
> >>
> >>
> >> On 29/08/2022 10:20, ShiroYuki Mot via gimp-developer-list
> >> wrote:
> >> > In the official page at
> >> > https://www.gimp.org/news/2022/08/27/gimp-2-99-12-released/,
> >> > You say that "with all gettext catalogs under the locale/
> >> folder of the
> >> > plug-in directory, and named the same way as the plug-in
> >> itself".
> >> >
> >> > Please teach me 'How TO do that'.
> >> >
> >> > On OS, Windows, If I placed my script file
> >> > (Shiro_Dialog_Args6_Test_API3.py) at
> >> >
> >>
> C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3,
> >> > Where do I deploy .mo file?
> >> > Is it at
> >> >
> >>
> 'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3\locale'?
> >> > Or at
> >> 'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\locale'?
> >> > And one more question.
>

Re: [Gimp-developer] GIMP 2.99.12 Python User Script's Localization

[Ofnuts via gimp-developer-list]

PS: of course your Gimp should be working in Japanese (which it will be 
if these environment variables are set when you start Gimp)


On 31/08/2022 14:45, Ofnuts via gimp-developer-list wrote:

Just re-checked, works for me. What are the environment values in the
Python console?

>>> os.environ['LANG']
'fr_FR.UTF-8'
>>> os.environ['LANGUAGE']
'fr_FR'

'fr_FR' should be 'ja_JP' for you (and possibly only one of these is
necessary)


On 31/08/2022 10:58, ShiroYuki Mot wrote:

Not localized!
Am I doing something wrong?

(I've tried replacing '_' with '-' or renaming the .mo file, but the
result was the same.)

cmd.exe Tree View

Microsoft Windows [Version 10.0.19044.1889]
(c) Microsoft Corporation. All rights reserved.

C:\Users\UserA>tree C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins /F

C:\USERS\USERA\APPDATA\ROAMING\GIMP\2.99\PLUG-INS
└─Shiro_Dialog_Args6_Test_API3
    │  Shiro_Dialog_Args6_Test_API3.py
    │
    ├─locale
    │  └─ja
    │      └─LC_MESSAGES
    │              Shiro_Dialog_Args6_Test_API3.mo
    │
    └─work
            Shiro_Dialog_Args6_Test_API3.mo
            Shiro_Dialog_Args6_Test_API3.po
            Test.pot

 Notice: .pot = Shift-JIS(cp932) ANSI / .po = UTF-8 / UTF-8 (NoBOM)
       : OS = Windows 10 Japanese Edition

Code

    ## GimpPlugIn virtual methods ##
    def do_set_i18n(self, procname):
        return True, 'Shiro_Dialog_Args6_Test_API3', None
    def do_query_procedures(self):
        return [ 'python-fu-shiro-dialog-args6-test-api3' ]

Zipped File  Shiro_Dialog_Args6_Test_API3.zip

2022年8月30日(火) 19:37 ShiroYuki Mot :

    Dear Ofnuts.

    Thanks for presenting the solution.
    It was detailed and easy to understand.
    I'm glad that this clears up my questions. :)
    I'll try this tonight.

    2022年8月30日(火) 18:40 Ofnuts via gimp-developer-list
:

    My own plugin does:

     def do_set_i18n(self, *args):
     print(f'do_set_i18n({args})')
     return True, 'ofn-guides-presets',None

    (where 'ofn-guides-presets' is the same same as the plugin
    python file
    itself, and as I understand it, if the I18N domain is the same
    name as the plugin file, you don't even need to define this
    method,
    because it's the default behavior.

    Then you create the .mo file(s)  and put them in a
    locale/{language
    code}/LC_MESSAGES subdirectory of your plugin directory.
    ofn-guides-presets/
    ├── locale
    │   └── fr
    │   └── LC_MESSAGES
    │   └── ofn-guides-presets.mo # messages for French
    └── ofn-guides-presets.py   # plugin code

    And yes, using 'gimp30-python' in your own scripts doesn't
    make much
    sense (it does for scripts delivered with Gimp, that share the
    message
    base with other code).


    On 29/08/2022 10:20, ShiroYuki Mot via gimp-developer-list 
wrote:

    > In the official page at
    > https://www.gimp.org/news/2022/08/27/gimp-2-99-12-released/,
    > You say that "with all gettext catalogs under the locale/
    folder of the
    > plug-in directory, and named the same way as the plug-in
    itself".
    >
    > Please teach me 'How TO do that'.
    >
    > On OS, Windows, If I placed my script file
    > (Shiro_Dialog_Args6_Test_API3.py) at
    >
C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3,
    > Where do I deploy .mo file?
    > Is it at
    >
'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3\locale'?
    > Or at
'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\locale'?
    > And one more question.
    > How do I write the following parts?
    > def do_set_i18n(self, procname):
    >     return True, 'gimp30-python', None
    > (Maybe, That code means calling the official 
gimp30-python.mo.)

    > ___
    > gimp-developer-list mailing list
    > List address:gimp-developer-list@gnome.org

    > List
membership:https://mail.gnome.org/mailman/listinfo/gimp-developer-list
    > List
archives:https://mail.gnome.org/archives/gimp-developer-list

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



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

List archives: https://mail.gnome.org/archives/gimp-developer-list


___
gimp-developer-list mailing list
List address:gimp-

Re: [Gimp-developer] GIMP 2.99.12 Python User Script's Localization

[Ofnuts via gimp-developer-list]

Just re-checked, works for me. What are the environment values in the
Python console?

>>> os.environ['LANG']
'fr_FR.UTF-8'
>>> os.environ['LANGUAGE']
'fr_FR'

'fr_FR' should be 'ja_JP' for you (and possibly only one of these is
necessary)


On 31/08/2022 10:58, ShiroYuki Mot wrote:

Not localized!
Am I doing something wrong?

(I've tried replacing '_' with '-' or renaming the .mo file, but the
result was the same.)

cmd.exe Tree View

Microsoft Windows [Version 10.0.19044.1889]
(c) Microsoft Corporation. All rights reserved.

C:\Users\UserA>tree C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins /F

C:\USERS\USERA\APPDATA\ROAMING\GIMP\2.99\PLUG-INS
└─Shiro_Dialog_Args6_Test_API3
    │  Shiro_Dialog_Args6_Test_API3.py
    │
    ├─locale
    │  └─ja
    │      └─LC_MESSAGES
    │              Shiro_Dialog_Args6_Test_API3.mo
    │
    └─work
            Shiro_Dialog_Args6_Test_API3.mo
            Shiro_Dialog_Args6_Test_API3.po
            Test.pot

 Notice: .pot = Shift-JIS(cp932) ANSI / .po = UTF-8 / UTF-8 (NoBOM)
       : OS = Windows 10 Japanese Edition

Code

    ## GimpPlugIn virtual methods ##
    def do_set_i18n(self, procname):
        return True, 'Shiro_Dialog_Args6_Test_API3', None
    def do_query_procedures(self):
        return [ 'python-fu-shiro-dialog-args6-test-api3' ]

Zipped File  Shiro_Dialog_Args6_Test_API3.zip

2022年8月30日(火) 19:37 ShiroYuki Mot :

Dear Ofnuts.

Thanks for presenting the solution.
It was detailed and easy to understand.
I'm glad that this clears up my questions. :)
I'll try this tonight.

2022年8月30日(火) 18:40 Ofnuts via gimp-developer-list
:

My own plugin does:

 def do_set_i18n(self, *args):
 print(f'do_set_i18n({args})')
 return True, 'ofn-guides-presets',None

(where 'ofn-guides-presets' is the same same as the plugin
python file
itself, and as I understand it, if the I18N domain is the same
name as the plugin file, you don't even need to define this
method,
because it's the default behavior.

Then you create the .mo file(s)  and put them in a
locale/{language
code}/LC_MESSAGES subdirectory of your plugin directory.
ofn-guides-presets/
├── locale
│   └── fr
│   └── LC_MESSAGES
│   └── ofn-guides-presets.mo # messages for French
└── ofn-guides-presets.py   # plugin code

And yes, using 'gimp30-python' in your own scripts doesn't
make much
sense (it does for scripts delivered with Gimp, that share the
message
base with other code).


On 29/08/2022 10:20, ShiroYuki Mot via gimp-developer-list wrote:
> In the official page at
> https://www.gimp.org/news/2022/08/27/gimp-2-99-12-released/,
> You say that "with all gettext catalogs under the locale/
folder of the
> plug-in directory, and named the same way as the plug-in
itself".
>
> Please teach me 'How TO do that'.
>
> On OS, Windows, If I placed my script file
> (Shiro_Dialog_Args6_Test_API3.py) at
>

C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3,
> Where do I deploy .mo file?
> Is it at
>

'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3\locale'?
> Or at
'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\locale'?
> And one more question.
> How do I write the following parts?
> def do_set_i18n(self, procname):
>     return True, 'gimp30-python', None
> (Maybe, That code means calling the official gimp30-python.mo.)
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org

> List
membership:https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List
archives:https://mail.gnome.org/archives/gimp-developer-list

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


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

Re: [Gimp-developer] GIMP 2.99.12 Python User Script's Localization

[ShiroYuki Mot via gimp-developer-list]

Not localized!
Am I doing something wrong?

(I've tried replacing '_' with '-' or renaming the .mo file, but the result
was the same.)

cmd.exe Tree View

Microsoft Windows [Version 10.0.19044.1889]
(c) Microsoft Corporation. All rights reserved.

C:\Users\UserA>tree C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins /F

C:\USERS\USERA\APPDATA\ROAMING\GIMP\2.99\PLUG-INS
└─Shiro_Dialog_Args6_Test_API3
│  Shiro_Dialog_Args6_Test_API3.py
│
├─locale
│  └─ja
│  └─LC_MESSAGES
│  Shiro_Dialog_Args6_Test_API3.mo
│
└─work
Shiro_Dialog_Args6_Test_API3.mo
Shiro_Dialog_Args6_Test_API3.po
Test.pot

 Notice: .pot = Shift-JIS(cp932) ANSI / .po = UTF-8 / UTF-8 (NoBOM)
   : OS = Windows 10 Japanese Edition

Code

## GimpPlugIn virtual methods ##
def do_set_i18n(self, procname):
return True, 'Shiro_Dialog_Args6_Test_API3', None
def do_query_procedures(self):
return [ 'python-fu-shiro-dialog-args6-test-api3' ]

Zipped File  Shiro_Dialog_Args6_Test_API3.zip

2022年8月30日(火) 19:37 ShiroYuki Mot :

> Dear Ofnuts.
>
> Thanks for presenting the solution.
> It was detailed and easy to understand.
> I'm glad that this clears up my questions. :)
> I'll try this tonight.
>
> 2022年8月30日(火) 18:40 Ofnuts via gimp-developer-list <
> gimp-developer-list@gnome.org>:
>
>> My own plugin does:
>>
>>  def do_set_i18n(self, *args):
>>  print(f'do_set_i18n({args})')
>>  return True, 'ofn-guides-presets',None
>>
>> (where 'ofn-guides-presets' is the same same as the plugin python file
>> itself, and as I understand it, if the I18N domain is the same
>> name as the plugin file, you don't even need to define this method,
>> because it's the default behavior.
>>
>> Then you create the .mo file(s)  and put them in a locale/{language
>> code}/LC_MESSAGES subdirectory of your plugin directory.
>> ofn-guides-presets/
>> ├── locale
>> │   └── fr
>> │   └── LC_MESSAGES
>> │   └── ofn-guides-presets.mo # messages for French
>> └── ofn-guides-presets.py   # plugin code
>>
>> And yes, using 'gimp30-python' in your own scripts doesn't make much
>> sense (it does for scripts delivered with Gimp, that share the message
>> base with other code).
>>
>>
>> On 29/08/2022 10:20, ShiroYuki Mot via gimp-developer-list wrote:
>> > In the official page at
>> > https://www.gimp.org/news/2022/08/27/gimp-2-99-12-released/,
>> > You say that "with all gettext catalogs under the locale/ folder of the
>> > plug-in directory, and named the same way as the plug-in itself".
>> >
>> > Please teach me 'How TO do that'.
>> >
>> > On OS, Windows, If I placed my script file
>> > (Shiro_Dialog_Args6_Test_API3.py) at
>> >
>> C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3,
>> > Where do I deploy .mo file?
>> > Is it at
>> >
>> 'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3\locale'?
>> > Or at 'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\locale'?
>> > And one more question.
>> > How do I write the following parts?
>> > def do_set_i18n(self, procname):
>> > return True, 'gimp30-python', None
>> > (Maybe, That code means calling the official gimp30-python.mo.)
>> > ___
>> > gimp-developer-list mailing list
>> > List address:gimp-developer-list@gnome.org
>> > List membership:
>> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
>> > List archives:https://mail.gnome.org/archives/gimp-developer-list
>>
>> ___
>> gimp-developer-list mailing list
>> List address:gimp-developer-list@gnome.org
>> List membership:
>> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
>> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>>
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] GIMP 2.99.12 Python User Script's Localization

[ShiroYuki Mot via gimp-developer-list]

Dear Ofnuts.

Thanks for presenting the solution.
It was detailed and easy to understand.
I'm glad that this clears up my questions. :)
I'll try this tonight.

2022年8月30日(火) 18:40 Ofnuts via gimp-developer-list <
gimp-developer-list@gnome.org>:

> My own plugin does:
>
>  def do_set_i18n(self, *args):
>  print(f'do_set_i18n({args})')
>  return True, 'ofn-guides-presets',None
>
> (where 'ofn-guides-presets' is the same same as the plugin python file
> itself, and as I understand it, if the I18N domain is the same
> name as the plugin file, you don't even need to define this method,
> because it's the default behavior.
>
> Then you create the .mo file(s)  and put them in a locale/{language
> code}/LC_MESSAGES subdirectory of your plugin directory.
> ofn-guides-presets/
> ├── locale
> │   └── fr
> │   └── LC_MESSAGES
> │   └── ofn-guides-presets.mo # messages for French
> └── ofn-guides-presets.py   # plugin code
>
> And yes, using 'gimp30-python' in your own scripts doesn't make much
> sense (it does for scripts delivered with Gimp, that share the message
> base with other code).
>
>
> On 29/08/2022 10:20, ShiroYuki Mot via gimp-developer-list wrote:
> > In the official page at
> > https://www.gimp.org/news/2022/08/27/gimp-2-99-12-released/,
> > You say that "with all gettext catalogs under the locale/ folder of the
> > plug-in directory, and named the same way as the plug-in itself".
> >
> > Please teach me 'How TO do that'.
> >
> > On OS, Windows, If I placed my script file
> > (Shiro_Dialog_Args6_Test_API3.py) at
> >
> C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3,
> > Where do I deploy .mo file?
> > Is it at
> >
> 'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3\locale'?
> > Or at 'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\locale'?
> > And one more question.
> > How do I write the following parts?
> > def do_set_i18n(self, procname):
> > return True, 'gimp30-python', None
> > (Maybe, That code means calling the official gimp30-python.mo.)
> > ___
> > gimp-developer-list mailing list
> > List address:gimp-developer-list@gnome.org
> > List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> > List archives:https://mail.gnome.org/archives/gimp-developer-list
>
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] GIMP 2.99.12 Python User Script's Localization

[Ofnuts via gimp-developer-list]

My own plugin does:

    def do_set_i18n(self, *args):
    print(f'do_set_i18n({args})')
    return True, 'ofn-guides-presets',None

(where 'ofn-guides-presets' is the same same as the plugin python file
itself, and as I understand it, if the I18N domain is the same
name as the plugin file, you don't even need to define this method,
because it's the default behavior.

Then you create the .mo file(s)  and put them in a locale/{language
code}/LC_MESSAGES subdirectory of your plugin directory.
ofn-guides-presets/
├── locale
│   └── fr
│   └── LC_MESSAGES
│   └── ofn-guides-presets.mo # messages for French
└── ofn-guides-presets.py   # plugin code

And yes, using 'gimp30-python' in your own scripts doesn't make much
sense (it does for scripts delivered with Gimp, that share the message
base with other code).


On 29/08/2022 10:20, ShiroYuki Mot via gimp-developer-list wrote:

In the official page at
https://www.gimp.org/news/2022/08/27/gimp-2-99-12-released/,
You say that "with all gettext catalogs under the locale/ folder of the
plug-in directory, and named the same way as the plug-in itself".

Please teach me 'How TO do that'.

On OS, Windows, If I placed my script file
(Shiro_Dialog_Args6_Test_API3.py) at
C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3,
Where do I deploy .mo file?
Is it at
'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\Shiro_Dialog_Args6_Test_API3\locale'?
Or at 'C:\Users\UserA\AppData\Roaming\GIMP\2.99\plug-ins\locale'?
And one more question.
How do I write the following parts?
def do_set_i18n(self, procname):
return True, 'gimp30-python', None
(Maybe, That code means calling the official gimp30-python.mo.)
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership:https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:https://mail.gnome.org/archives/gimp-developer-list


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

Re: [Gimp-developer] #gimp from Element (Re: Need help for the macOS package?)

[Ludovic Rousseau via gimp-developer-list]

Hello,

Le mar. 12 oct. 2021 à 00:13, Pat David  a écrit :
>
> Actually, to use Element as an IRC client to the gimp channel on gimpnet the 
> room address is: #_gimpnet_#gimp:gnome.org

I think I am in the room now.
I could not find how to enter the room #_gimpnet_#gimp:gnome.org from Element.
But it worked using another client https://fluffychat.im/

Thanks

-- 
 Dr. Ludovic Rousseau
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] #gimp from Element (Re: Need help for the macOS package?)

[Pat David via gimp-developer-list]

Actually, to use Element as an IRC client to the gimp channel on gimpnet
the room address is: #_gimpnet_#gimp:gnome.org


On Sun, Oct 10, 2021 at 7:09 AM Ludovic Rousseau via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> Le dim. 10 oct. 2021 à 10:06, Alexandre Prokoudine via
> gimp-developer-list  a écrit :
> >
> > On Fri, Oct 8, 2021 at 10:43 PM Ludovic Rousseau wrote:
> >
> > > I do not use IRC. Sorry.
> >
> > Personally, I use Matrix (via Element web UI and its mobile app) to
> > access IRC. It's quite bearable :)
>
> Very interesting. I also use Element.
> I did not know Element was also an IRC client.
>
> I searched for gimp in Element public Rooms.
> I found:
> #gimp
> GIMP - GNU Image Manipulation Program dicussion channel.
> https://www.gimp.org/ - State your OS/Gimp version. |
> https://www.gimp.org/tutorials/ | Development version: GIMP 2.99.6
> Released: https://www.gimp.org/news/2021/05/08/gimp-2-99-6-released/
> #freenode_#gimp:matrix.org
> 
>
> Is it this room?
> Do I need to add a server in Element?
>
> Maybe https://www.gimp.org/irc.html could document the use of Element? :-)
>
> Bye
>
> --
>  Dr. Ludovic Rousseau
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>


-- 
https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp export to function

[Ofnuts via gimp-developer-list]

What OS/Version? It is possibly some security setting that prevents
unrecognized apps from accessing external drives.

On 02/10/2021 20:04, Ken Masters via gimp-developer-list wrote:

I downloaded GIMP and so far I think most everything is fine except “when I use 
the export function it won’t show the external drive in the list of possible 
functions.


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

Re: [Gimp-developer] Gimp export to function

[Jacob Boerema via gimp-developer-list]

On 2 Oct 2021 at 15:34, Ken Masters via gimp-develope wrote:

> I downloaded GIMP and so far I think most everything is fine except
> “when I use the export function it won’t show the external drive in
> the list of possible functions. 

This sounds like a bug, which is best reported in our issue tracker:

https://gitlab.gnome.org/GNOME/gimp/-/issues

Please search first if this issue is already known. If it is add your 
information 
there.

If not make a new issue and please don't forget to fill in all required 
information in the template.

--

Jacob Boerema
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp export to function

[Asalle via gimp-developer-list]

Hi Ken,
please redirect questions regarding usage of gimp to the GIMP user list:
gimp-user-l...@gnome.org, you can also try the irc channel (
https://www.gimp.org/irc.html).
This mailing list is for software development.

Best,
Asa

On Thu, 7 Oct 2021 at 00:26, Ken Masters via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> I downloaded GIMP and so far I think most everything is fine except “when
> I use the export function it won’t show the external drive in the list of
> possible functions.
>
> Please help
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>


-- 
Best regards,
Asalle
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] GIMP development process

[Shlomi Fish]

Hi Alex and all!

On Wed, 2 Jun 2021 11:48:30 +0300
Alexandre Prokoudine via gimp-developer-list 
wrote:

> On Tue, Jun 1, 2021 at 2:59 PM Jack 04 via gimp-developer-list
>  wrote:
> >
> > Dear GIMP team,
> > I'm a software engineering student of University of Padova and I would like
> > to get some information about GIMP development process, in particular on
> > which methodology (i.e. waterfall model, v-shape model, agile methods,
> > SCRUM, XP, ...) you chose and why, finally how you have organized it and
> > implemented in the team.
> > Thank you in advance for your attention, I will wait for your answer.  
> 
> Hello,
> 
> Simply put, we don't do any of that.
> 
> We are not a company, we don't have any kind of a contract or boss,
> and only some of us receive humble donations.
> 
> We have only rough planning of major releases. We usually set one or
> two major goals for every major release (e.g. 2.6, 2.8, 2.10, 3.0) and
> then work towards those goals. As there are many, many requests made
> by users, we end up with features that can be severely out of scope of
> major goals. Moreover, some features are contributed by new people who
> are not necessarily a part of what I might flamboyantly call the core
> team :)
> 
> We don't set particular goals for minor releases (e.g. 2.10.22 or
> 2.99.4). It's typically a mix of some work towards a major goal, minor
> or major new features, UX/UI improvements, bug fixes etc.
> 
> Please let me know if you need to know more.
> 
> Alex

Thanks for replying so well. In addition, I and others have written:

* https://www.shlomifish.org/philosophy/computers/software-management/

* http://programming-motherfucker.com/

*
https://www.shlomifish.org/philosophy/philosophy/putting-cards-on-the-table-2019-2020/putting-cards-on-the-table-2019-2020/big-minded-vs-small-minded.xhtml

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



-- 

Shlomi Fish   https://www.shlomifish.org/
Freecell Solver - https://fc-solve.shlomifish.org/

If Chuck Norris is disappointed by you not following his advice, he’ll survive.
On the other hand, you will not.
— https://www.shlomifish.org/humour/bits/facts/Chuck-Norris/

Please reply to list if it's a mailing list post - https://shlom.in/reply .
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] GIMP development process

[Alexandre Prokoudine via gimp-developer-list]

On Tue, Jun 1, 2021 at 2:59 PM Jack 04 via gimp-developer-list
 wrote:
>
> Dear GIMP team,
> I'm a software engineering student of University of Padova and I would like
> to get some information about GIMP development process, in particular on
> which methodology (i.e. waterfall model, v-shape model, agile methods,
> SCRUM, XP, ...) you chose and why, finally how you have organized it and
> implemented in the team.
> Thank you in advance for your attention, I will wait for your answer.

Hello,

Simply put, we don't do any of that.

We are not a company, we don't have any kind of a contract or boss,
and only some of us receive humble donations.

We have only rough planning of major releases. We usually set one or
two major goals for every major release (e.g. 2.6, 2.8, 2.10, 3.0) and
then work towards those goals. As there are many, many requests made
by users, we end up with features that can be severely out of scope of
major goals. Moreover, some features are contributed by new people who
are not necessarily a part of what I might flamboyantly call the core
team :)

We don't set particular goals for minor releases (e.g. 2.10.22 or
2.99.4). It's typically a mix of some work towards a major goal, minor
or major new features, UX/UI improvements, bug fixes etc.

Please let me know if you need to know more.

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

Re: [Gimp-developer] gimp on Windows slow to install

[Jernej Simončič via gimp-developer-list]

On Friday, February 12, 2021, 11:11:25, Marco Ciampa via gimp-developer-list 
wrote:

> I noticed that GIMP is, by far, the slowest app to install on Windows.
> _Much_ slower than, for instance, LibreOffice that is about 1/3 bigger.
> Why is it so? Perhaps a too aggressive compression of the package?

Very aggressive compression, and GIMP's install size is almost twice as large 
as that of LibreOffice. Probably the biggest reason for slow install is because 
both 32 and 64-bit versions are in the same installer, and when doing a 64-bit 
install, a lot of 32-bit version is also installed; I've been meaning to look 
into optimizing this, but haven't gotten around to do it yet.

-- 
< Jernej Simončič ><><><><>< https://eternallybored.org/ >

Trust only those who stand to lose as much as you when things go wrong.
   -- Chase's Rule For Success

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

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

[JonnyRobbie via gimp-developer-list]

"I general we're not likely to move to anything that isn't libre"
 

I would suggest the Matrix protocol. It has a fully open api standard and 
reference server implementation with gpl compatible license. https://matrix.
org/discover/
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

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

[Jehan Pagès via gimp-developer-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&utf8=%E2%9C%93&state=opened&author_username=ellestone
>
> Here are bugs that I opened before the migration to gitlab:
>
> https://gitlab.gnome.org/GNOME/gimp/-/issues?scope=all&utf8=%E2%9C%93&state=opened&author_username=bugzilla-migration&search=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
scratchin

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

[Liam R E Quin]

On Sat, 2021-02-06 at 18:35 -0500, Christopher Curtis via gimp-
developer-list wrote:
> On Thu, Feb 4, 2021 at 7:17 PM Liam Quin  wrote:
> 
> Maybe the right conversation to have is, how can we get some more
> > programmers to spend their free time on GIMP.
> 
> And I'm not astroturfing Discord: there are free software
> alternatives that
> can be self-hosted.

I general we're not likely to move to anything that isn't libre (and
not just open source for that matter).

But the days of IRC are probably numbered, XKCD notwithstanding :)


-- 
ankh - web slave for https://www.fromoldbooks.org/


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

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

[Christopher Curtis via gimp-developer-list]

On Thu, Feb 4, 2021 at 7:17 PM Liam Quin  wrote:

Maybe the right conversation to have is, how can we get some more
> programmers to spend their free time on GIMP.
>

On this topic, I would like to suggest that people consider using a tool
like Discord. It is reasonably popular (ie: easy to use) and has plugins
that can connect to the current IRC channels.

Where I think it provides more value (besides not requiring an IRC client
or archie server), is its support for voice channels, and limited
(low-quality) screen/video sharing. It is far, far, simpler at times to hop
onto an audio channel and explain ideas or share a screen to see what
people are talking about than to try to turn that into prose.

GIMP is complex and its development requires study. Reducing this friction
can only make things easier. Often, the hardest part is just getting
started and building a base of "functional newbies" through easy on-ramping
can kick off blog posts and all that other good developer supporting
material.

And I'm not astroturfing Discord: there are free software alternatives that
can be self-hosted. I've found it to be a useful tool when text chat keeps
missing the point and pastebin is just too much to bother with. It seems
like an easy thing to trial if people are willing to use it, but be under
no delusion that it is a panacea: I think it may just be a bit better.

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

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

[Elle Stone]

On 2/4/21 11:27 PM, Alexandre Prokoudine via gimp-user-list wrote:

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


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.


Two years ago we had three active developers hacking on GIMP like
there was no tomorrow.

We lost one of them entirely, it seems, and another one is mostly
preoccupied with family business, so we are down to one active
developer and a few new active contributors. We are also approaching
the end of very long and tiresome work on refactoring which is not
done yet. Also, a lot of time of that one active developer was spent
figuring out ways to make development of GIMP sustainable (no details
at this point in time, sorry). So yes, there are several critical
areas where help is needed. Color management is clearly one of them.

I guess if you adjust your expectations accordingly, you will see that
there is no acting in bad faith here.


Alexandre, I'm not sure why you felt obligated to introduce the idea of 
"acting in bad faith". It has not escaped my notice that various 
developers have cut back or ceased altogether from participating in GIMP 
development. I'm not even completely unaware of some of the reasons.


Life happens, sometimes good, sometimes not good. Speaking for myself, I 
knew two years ago that I had a limited timeframe in which to hopefully 
help bring GIMP color management to the state of being reliable for 
color spaces other than sRGB. My family is dealing with some serious 
problems, has been for a long time now and will be for the foreseeable 
future.


It's good to hear that someone on the team is trying to figure out how 
to make GIMP development sustainable. Hopefully that effort includes 
figuring out how to prioritize goals based on the editing needs of 
potential and actual users.


To the members of the GIMP team who've worked with me over the years on 
various color-management/color-science topics - you know who you are, so 
I won't name any names - you went out of your way to help with my coding 
efforts and you made me feel like a part of the team - that meant a lot. 
Thank you.


Speaking of "thank you", Michael Schumacher's "Concepts: Color Science" 
tag will be a big help to whichever current or future devs turn their 
attention to making GIMP finally be fully and reliably color-managed. 
One of the first things I did when starting to work on GIMP color 
management, was to compile a list for all open and closed GIMP bug 
reports having to do with color management, then read through and 
categorize all the bugs, to get an idea of what was already done, what 
was left to do, and most importantly to figure out what concerns 
motivated the users who filed the bug reports. A "Concepts: Color 
Science" tag would have been a big help.


GIMP is important in the free-libre universe of image-editing programs. 
But without good color management GIMP is seriously flawed as a 
professional-level editing program.


Best wishes to GIMP team members past, present, and future.
Elle

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

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

[Alexandre Prokoudine via gimp-developer-list]

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

> 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.

Two years ago we had three active developers hacking on GIMP like
there was no tomorrow.

We lost one of them entirely, it seems, and another one is mostly
preoccupied with family business, so we are down to one active
developer and a few new active contributors. We are also approaching
the end of very long and tiresome work on refactoring which is not
done yet. Also, a lot of time of that one active developer was spent
figuring out ways to make development of GIMP sustainable (no details
at this point in time, sorry). So yes, there are several critical
areas where help is needed. Color management is clearly one of them.

I guess if you adjust your expectations accordingly, you will see that
there is no acting in bad faith here.

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

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

[Elle Stone]

On 2/4/21 7:14 PM, Michael Schumacher via gimp-user-list wrote:



On February 5, 2021 12:59:50 AM GMT+01:00, Elle Stone 
 wrote:


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.


You make it sound like introducing this tag was a wrong decision. As I 
introduced it as a way to group thhese issues together, did I do something 
wrong there?



Of course you didn't do anything wrong. It's an excellent tag to let 
people know what the topic is.


It's been stated over and over again by a particular GIMP dev that GIMP 
development works best if people do what they are interested in doing. 
The question is which current GIMP devs other than myself have an 
*interest* in dealing bugs tagged with "Concept: Color Science"?


It would be great if you could find the time to go through the links I 
provided in my post and add the tag as appropriate to any relevant bug 
reports that don't yet have the tag. Someday when GIMP has found another 
developer with an interest in color management and color science, that 
person will find the "Concepts: Color Science" tag very useful.


Best,
Elle

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

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

[Liam Quin]

On Thu, 2021-02-04 at 18:59 -0500, Elle Stone wrote:
> 
> GIMP-2.10 does *NOT* produce correct editing results in color spaces 
> other than sRGB. Neither does GIMP-2.99.

For sure you also get a dramatically bad result if you export as png of
jpeg from 32-bit images. But convert to 8-bit first and it's OK. So
clearly there's work to be done.

It might be that the attention Web browser makers are currently giving
to other colourspaces, wider gamut, and higher bit depth, will drive
demand - and, we can hope, lead to increased resources for GIMP too.

There are other areas where GIMP needs work, too - one of my own
interests is in text and better openType support for example - so we
are both in the same position in that that's more we'd like to see than
we can do. In my case i'm slowly doing experiments, but no patches
(yet?). In your case you're well ahead of me but the patches are very
hard to review, because colour management is so specialized.

Maybe the right conversation to have is, how can we get some more
programmers to spend their free time on GIMP.

[replying only to gimp-developer list, not user list as well]

-- 
Liam Quin - web slave for https://www.fromoldbooks.org/

Full-time  slave in voluntary servitude

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

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

[Michael Schumacher via gimp-developer-list]

On February 5, 2021 12:59:50 AM GMT+01:00, Elle Stone 
 wrote:

>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.

You make it sound like introducing this tag was a wrong decision. As I 
introduced it as a way to group thhese issues together, did I do something 
wrong there?

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] [Gimp-user] How to compile a vala GIMP plugin on Windows pc?

[Bill Ross via gimp-developer-list]

To be clear, I don't speak for gimp, haven't worked on it even, but did look 
into Windows programming for a possible job during a dry spell, and I'd rather 
code in COBOL with vi. So, sorry the intent was wasted. 
:-)BillAI:http://phobrain.com/pr/home/view.html
 Original message From: Christopher Curtis via 
gimp-developer-list  Date: 1/3/21  6:48 PM  
(GMT-08:00) To: gimp-developer  Subject: Re: 
[Gimp-developer] [Gimp-user] How to compile a vala GIMP plugin
  on Windows pc? These are incredibly unhelpful responses.It is fine to 
evangelize if you are also providing useful information, butone cannot 
simultaneously bemoan the lack of developers for a particularplatform and also 
chastise those developing on that platform.To the original questioner, I would 
suggest following Jernej's advice. I,unfortunately, don't regularly use Windows 
or Vala, but there are claims ofVala support in 2.99.4 so someone must have had 
some success. I do have aWindows 10 machine that I installed Debian on using 
WSL2 (I may have eveninstalled it from the Microsoft Store) - that may be an 
easier solutionthan installing MSys2, but I cannot say authoritatively. If 
nothing else,it may be a better first step to ensure you can build the plugin 
onGIMP's primary development environment, then try it with MSys2.If you can 
document your Windows Vala Plugin build process in the Wiki thatwould be even 
better. This may be useful to get 
started:https://wiki.gimp.org/wiki/Hacking:Building/WindowsIdeally, GIMP would 
provide a Windows SDK that plugins could be builtagainst, but I don't know if 
anyone has considered that. It's quitepossible that with GObject introspection 
simply installing the GIMPexecutable provides that function and you only need a 
Vala compiler tocompile the Vala code (I don't know how linking works in that 
case, but itsounds nice).ChrisOn Sun, Jan 3, 2021 at 5:52 PM Bill Ross via 
gimp-developer-list  wrote:> If you can find any 
online docs on Windows programming, that should> finish convincing you.>> 
Bill>> On 1/3/21 12:36 PM, Ruben Safir wrote:> > Save yourself a life time of 
trouble and switch ovr the a GNU system now> --> Phobrain.com> 
___> gimp-developer-list mailing 
list> List address:    gimp-developer-list@gnome.org> List membership:> 
https://mail.gnome.org/mailman/listinfo/gimp-developer-list> List archives:   
https://mail.gnome.org/archives/gimp-developer-list>___gimp-developer-list
 mailing listList address:    gimp-developer-list@gnome.orgList membership: 
https://mail.gnome.org/mailman/listinfo/gimp-developer-listList archives:   
https://mail.gnome.org/archives/gimp-developer-list
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] [Gimp-user] How to compile a vala GIMP plugin on Windows pc?

[Christopher Curtis via gimp-developer-list]

These are incredibly unhelpful responses.

It is fine to evangelize if you are also providing useful information, but
one cannot simultaneously bemoan the lack of developers for a particular
platform and also chastise those developing on that platform.

To the original questioner, I would suggest following Jernej's advice. I,
unfortunately, don't regularly use Windows or Vala, but there are claims of
Vala support in 2.99.4 so someone must have had some success. I do have a
Windows 10 machine that I installed Debian on using WSL2 (I may have even
installed it from the Microsoft Store) - that may be an easier solution
than installing MSys2, but I cannot say authoritatively. If nothing else,
it may be a better first step to ensure you can build the plugin on
GIMP's primary development environment, then try it with MSys2.

If you can document your Windows Vala Plugin build process in the Wiki that
would be even better. This may be useful to get started:
https://wiki.gimp.org/wiki/Hacking:Building/Windows

Ideally, GIMP would provide a Windows SDK that plugins could be built
against, but I don't know if anyone has considered that. It's quite
possible that with GObject introspection simply installing the GIMP
executable provides that function and you only need a Vala compiler to
compile the Vala code (I don't know how linking works in that case, but it
sounds nice).

Chris


On Sun, Jan 3, 2021 at 5:52 PM Bill Ross via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> If you can find any online docs on Windows programming, that should
> finish convincing you.
>
> Bill
>
> On 1/3/21 12:36 PM, Ruben Safir wrote:
> > Save yourself a life time of trouble and switch ovr the a GNU system now
> --
> Phobrain.com
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] [Gimp-user] How to compile a vala GIMP plugin on Windows pc?

[Bill Ross via gimp-developer-list]

If you can find any online docs on Windows programming, that should 
finish convincing you.


Bill

On 1/3/21 12:36 PM, Ruben Safir wrote:

Save yourself a life time of trouble and switch ovr the a GNU system now

--
Phobrain.com
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] [Gimp-user] How to compile a vala GIMP plugin on Windows pc?

[Ruben Safir]

We got it and heard you.  The easist way to do it is the use linux.

There might be someone who compiles on WIndows, but MS removed all the
compilers from its commericial OS and explaining how to install an
entire compiler and make environment on a stripped down commerical
windows box is a long and drawn out discussion.

Save yourself a life time of trouble and switch ovr the a GNU system now



On Sun, Dec 27, 2020 at 09:50:54PM -0800, Pen Guin via gimp-user-list wrote:
> Hi,
> 
> I have downloaded GIMP 2.99.4 on my Windows 8 pc.
> 
> I want to compile the goat-exercise vala plugin shipped with GIMP.  Can
> anyone please tell me how can I compile a vala plugin on my pc? What other
> softwares AND/OR dependent-files do I need to download? What command and
> attributes do I need to pass to the vala compiler to get a working exe
> without any errors?
> 
>  Thanks.
> ___
> gimp-user-list mailing list
> List address:gimp-user-l...@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list

-- 
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
http://www.mrbrklyn.com 

DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
http://www.nylxs.com - Leadership Development in Free Software
http://www2.mrbrklyn.com/resources - Unpublished Archive 
http://www.coinhangout.com - coins!
http://www.brooklyn-living.com 

Being so tracked is for FARM ANIMALS and extermination camps, 
but incompatible with living as a free human being. -RI Safir 2013

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

Re: [Gimp-developer] [Gimp-user] How to compile a vala GIMP plugin on Windows pc?

[Liam R E Quin]

On Sun, 2020-12-27 at 21:50 -0800, Pen Guin via gimp-user-list wrote:
> Hi,
> 
> I have downloaded GIMP 2.99.4 on my Windows 8 pc.
> I want to compile the goat-exercise vala plugin shipped with GIMP.

What are you trying to do exactly?

Are you familiar with C programming?


-- 
ankh - full time slave in voluntary servitude

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

Re: [Gimp-developer] GIMP is 25 yo

[Shlomi Fish]

On Sun, 22 Nov 2020 05:13:09 +0300
Alexandre Prokoudine via gimp-developer-list 
wrote:

> Hello!
> 
> GIMP turns 25 years old on November 21. We wrote something about it :)
> 
> https://www.gimp.org/news/2020/11/21/25-years-of-gimp/
> 
> Many thanks to everyone involved in any role imaginable!
> 

Mazal Tov! And thanks all.

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



-- 

Shlomi Fish   https://www.shlomifish.org/
Chuck Norris/etc. Facts - https://www.shlomifish.org/humour/bits/facts/

I have a brilliant idea: a distributed, NoSQL, Webscale™ /dev/null alternative.
I’m going to patent it. (Inspired by arubin on ##programming.)

Please reply to list if it's a mailing list post - https://shlom.in/reply .
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] GIMP is 25 yo

[Gimp-Werkstatt]

Herzlichen Glückwunsch GIMP!

und herzlichen Dank allen Entwicklern für die tolle Arbeit, die ihr
geleistet habt.

Viele Grüße

Die GIMP-Werkstatt

Am 22.11.20 um 03:13 schrieb Alexandre Prokoudine via gimp-developer-list:

Hello!

GIMP turns 25 years old on November 21. We wrote something about it :)

https://www.gimp.org/news/2020/11/21/25-years-of-gimp/

Many thanks to everyone involved in any role imaginable!

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


--
---
http://www.gimp-werkstatt.de
http://www.kompozer-web.de
http://www.kreativ-workshops.net

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

Re: [Gimp-developer] GIMP is 25 yo

[Akash Rao via gimp-developer-list]

happy birthday!

akash

On Sun, 22 Nov 2020 at 07:43, Alexandre Prokoudine via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> Hello!
>
> GIMP turns 25 years old on November 21. We wrote something about it :)
>
> https://www.gimp.org/news/2020/11/21/25-years-of-gimp/
>
> Many thanks to everyone involved in any role imaginable!
>
> Alex
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp 2.99: script-fu, gimp-file-load and GFile

[Lloyd Konneker via gimp-developer-list]

I think issue #5402 is relevant, and includes a patch to ScriptFu code for
2.99.

A script still uses string filenames.  ScriptFu the interpreter sees that
the signature of a PDB procedure requires a GFile and marshalls the string
into a GFile.

But the patch has not been applied yet.  Kevin, are you a maintainer who
can review and apply the patch?
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp 2.99: script-fu, gimp-file-load and GFile

[Kevin Cozens]

On 2020-10-14 8:07 a.m., Gottfried Müller wrote:

In the developer version the same procedure uses 2 arguments "run-mode,
file". The file has the format "GFile". The filename I get with the
SF-FILENAME parameter in the script-fu definition. The parameter "file"
in "gimp-file-load" does not accept a string parameter. How can I
convert the string of a filename in the GFile format?


I haven't seen any discussion about the change to using GFile in the mailing 
list messages. I don't know why that change was made or whether the side 
effects of making the change where fully explored. It breaks just about all 
of the third party plug-ins and scripts that need to do file I/O.


I don't know of any available API function that can take a filename and 
generate a GFile object that would be needed by Scheme, Perl, Python, or 
Ruby scripts. One will need to be made available or the API may need to be 
changed to continue allowing the use of functions that can take a filename 
as a string.


--
Cheers!

Kevin.

http://www.ve3syb.ca/   | "Nerds make the shiny things that
https://www.patreon.com/KevinCozens | distract the mouth-breathers, and
| that's why we're powerful"
Owner of Elecraft K2 #2172  |
#include  | --Chris Hardwick
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] [Gimp-user] [ANNOUNCE] GIMP 2.10.22

[Ruben Safir]

On Thu, Oct 08, 2020 at 11:57:16PM +0300, Alexandre Prokoudine via 
gimp-user-list wrote:
> Hi,
> 
> GIMP 2.10.22 is out. Release highlights:
> 
> - Improved HEIC and newly added AVIF support
> - Numerous improvements in the PSP file format support
> - Improved multi-layer TIFF exporting
> - Better handling of the Exif “Orientation” metadata
> - New “Sample merged” option in the GEGL operation tool
> 


I am impressed and anxious to see it work

> Details: https://www.gimp.org/news/2020/10/07/gimp-2-10-22-released/
> 
> Windows installer is available, so is the flatpak for Linux.
> Unfortunately, we won't have a build for macOS until someone steps up
> and contributes it.
> 
> Alex
> ___
> gimp-user-list mailing list
> List address:gimp-user-l...@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list

-- 
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
http://www.mrbrklyn.com 

DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
http://www.nylxs.com - Leadership Development in Free Software
http://www2.mrbrklyn.com/resources - Unpublished Archive 
http://www.coinhangout.com - coins!
http://www.brooklyn-living.com 

Being so tracked is for FARM ANIMALS and extermination camps, 
but incompatible with living as a free human being. -RI Safir 2013

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

Re: [Gimp-developer] [Gimp-user] [ANNOUNCE] GIMP 2.10.22

[Shlomi Fish]

On Thu, 8 Oct 2020 18:05:44 -0400
Partha Bagchi via gimp-user-list  wrote:

> I'm working on my McGimp build as we speak. So, it should be out soon.
> 

Thanks, Partha, Alexandre and all other gimp devs and contributors! I'll try to
get to preparing Mageia (linux) packages soon, but appreciate the availability
of packages for other OSes.

-- 

Shlomi Fish   https://www.shlomifish.org/
Interview with Ben Collins-Sussman - https://shlom.in/sussman

Microsoft — making it all make sense. Ours.
— https://www.shlomifish.org/humour.html
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp 3.0 advancement

[Shlomi Fish]

Hi Massimo,

On Wed, 22 Jul 2020 03:02:40 +0200
Massimo Fidanza via gimp-developer-list  wrote:

> I would like to contribute to the development, but I state that I know
> little of the C language, concretely in C I have exploited the code found
> on the internet to make the firmware of a pair of IoT relays that use the
> ESP8266. Instead I have experience with several languages including:
> Python, PHP, Pascal / Delphi, Java, Javascript, C #, PL / SQL (currently my
> daily bread). A few years ago I took a look at Go and now I'm interested in
> Rust.
> I took a look at the developer documentation
> https://wiki.gimp.org/wiki/Main_Page but it seems to me that many things
> are out of date. Give me a hint on what to start reading.
> 

It is not surprising that the documentation has become out of date - from my
experience, even inline comments do:

* https://blog.codinghorror.com/learn-to-read-the-source-luke/

*
https://www.shlomifish.org/humour/fortunes/show.cgi?id=sharp-perlcafe-trusting-the-docs

*
https://www.shlomifish.org/philosophy/computers/software-management/perfect-workplace/perfect-it-workplace.xhtml#soft-eng-methods-to-avoid

You can try learning C from these resources:

*
https://github.com/EbookFoundation/free-programming-books/blob/master/free-programming-books.md#c

*
https://github.com/shlomif/Freenode-programming-channel-FAQ/blob/master/FAQ_with_ToC__generated.md#i-want-to-learn-programming-which-language-should-i-start-with

It shouldn't be too much of a problem for you given your experience.

> Il giorno dom 19 lug 2020 alle ore 04:55 Massimo Fidanza 
> ha scritto:
> 
> > I built a docker image starting from a Ubuntu 20.04 and I have installed
> > all dependencies and compiled Babl, Gegl and Gimp from source, using Meson.
> > I have encountered the error
> > https://gitlab.gnome.org/GNOME/gimp/-/issues/5407, but I think that I
> > have found a solution. If you are interested I can share my image, but is
> > big 3.08GB
> >
> > Regards
> > Massimo
> >
> > Il giorno mer 15 lug 2020 alle ore 17:33 Liam R E Quin 
> > ha scritto:
> >  
> >> On Wed, 2020-07-15 at 12:21 +0200, Massimo Fidanza via gimp-developer-
> >> list wrote:  
> >> >
> >> > of the Gimp code to Python 3 and GTK 3 is finished  
> >>
> >> There's a major question about existing plugins- obviously they won't
> >> work, so maybe we should have a rewriting plugins wiki or something,
> >> and try to get some of the most popular ones updated.
> >>
> >>
> >> --
> >> Liam Quin - web slave for https://www.fromoldbooks.org/
> >>
> >> In 24/7 full-time voluntary servitude since 1998.
> >>
> >>  
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list



-- 

Shlomi Fish   https://www.shlomifish.org/
Parody of "The Fountainhead" - https://shlom.in/towtf

It does not mean what I think it means, but it means what *you* think it
means.
— https://www.shlomifish.org/humour.html

Please reply to list if it's a mailing list post - https://shlom.in/reply .
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp 3.0 advancement

[Massimo Fidanza via gimp-developer-list]

I would like to contribute to the development, but I state that I know
little of the C language, concretely in C I have exploited the code found
on the internet to make the firmware of a pair of IoT relays that use the
ESP8266. Instead I have experience with several languages including:
Python, PHP, Pascal / Delphi, Java, Javascript, C #, PL / SQL (currently my
daily bread). A few years ago I took a look at Go and now I'm interested in
Rust.
I took a look at the developer documentation
https://wiki.gimp.org/wiki/Main_Page but it seems to me that many things
are out of date. Give me a hint on what to start reading.

Il giorno dom 19 lug 2020 alle ore 04:55 Massimo Fidanza 
ha scritto:

> I built a docker image starting from a Ubuntu 20.04 and I have installed
> all dependencies and compiled Babl, Gegl and Gimp from source, using Meson. I
> have encountered the error
> https://gitlab.gnome.org/GNOME/gimp/-/issues/5407, but I think that I
> have found a solution. If you are interested I can share my image, but is
> big 3.08GB
>
> Regards
> Massimo
>
> Il giorno mer 15 lug 2020 alle ore 17:33 Liam R E Quin 
> ha scritto:
>
>> On Wed, 2020-07-15 at 12:21 +0200, Massimo Fidanza via gimp-developer-
>> list wrote:
>> >
>> > of the Gimp code to Python 3 and GTK 3 is finished
>>
>> There's a major question about existing plugins- obviously they won't
>> work, so maybe we should have a rewriting plugins wiki or something,
>> and try to get some of the most popular ones updated.
>>
>>
>> --
>> Liam Quin - web slave for https://www.fromoldbooks.org/
>>
>> In 24/7 full-time voluntary servitude since 1998.
>>
>>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp 3.0 advancement

[Massimo Fidanza via gimp-developer-list]

I built a docker image starting from a Ubuntu 20.04 and I have installed
all dependencies and compiled Babl, Gegl and Gimp from source, using Meson. I
have encountered the error https://gitlab.gnome.org/GNOME/gimp/-/issues/5407,
but I think that I have found a solution. If you are interested I can share
my image, but is big 3.08GB

Regards
Massimo

Il giorno mer 15 lug 2020 alle ore 17:33 Liam R E Quin 
ha scritto:

> On Wed, 2020-07-15 at 12:21 +0200, Massimo Fidanza via gimp-developer-
> list wrote:
> >
> > of the Gimp code to Python 3 and GTK 3 is finished
>
> There's a major question about existing plugins- obviously they won't
> work, so maybe we should have a rewriting plugins wiki or something,
> and try to get some of the most popular ones updated.
>
>
> --
> Liam Quin - web slave for https://www.fromoldbooks.org/
>
> In 24/7 full-time voluntary servitude since 1998.
>
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp 3.0 advancement

[Liam R E Quin]

On Wed, 2020-07-15 at 12:21 +0200, Massimo Fidanza via gimp-developer-
list wrote:
> 
> of the Gimp code to Python 3 and GTK 3 is finished 

There's a major question about existing plugins- obviously they won't
work, so maybe we should have a rewriting plugins wiki or something,
and try to get some of the most popular ones updated.


-- 
Liam Quin - web slave for https://www.fromoldbooks.org/

In 24/7 full-time voluntary servitude since 1998.

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

Re: [Gimp-developer] Gimp 3.0 advancement

[Shlomi Fish]

Hi Massimo!

On Wed, 15 Jul 2020 12:21:47 +0200
Massimo Fidanza via gimp-developer-list  wrote:

> Excuse me if I ask, I don't want to be petulant, I know that release will
> happen when the program is ready, but I just want to ask if the migration
> of the Gimp code to Python 3 and GTK 3 is finished or there are things that
> need to be completed?
> 

There may be still some rough spots, e.g: in the new meson build system (see:
https://gitlab.gnome.org/GNOME/gimp/-/issues/5407 ; autotools builds are
working better from my experience) or in script-fu (see:
https://gitlab.gnome.org/GNOME/gimp/-/issues/5402 ) and some other aspects.
Note that I may not be too major a contributor to GIMP.

I suppose we can use your help if you wish to contribute, and I maintain
https://metacpan.org/release/App-gimpgitbuild to (hopefully) facilitate
building testing and installing GIMP 2.99.x/git from source.

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



-- 

Shlomi Fish   https://www.shlomifish.org/
https://www.shlomifish.org/humour/bits/facts/Taylor-Swift/

There is no IGLU Cabal! Its members can be arranged in N! orders to form N!
different Cabals. The algorithm to find which order formulates the correct
IGLU Cabal is NP‐Complete.

Please reply to list if it's a mailing list post - https://shlom.in/reply .
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp 2.99 python3 plug-ins: writing a plugin to generate an image

[Lloyd Konneker via gimp-developer-list]

> is it possible writing a plug-in to generate an image without an opened
image?

Rephrasing the question: can you write a plugin whose menu item is always
enabled, even without an open image?  That used to be possible, by passing
an empty string for the "image types" registration data.   But your code
does not call procedure.set_image_types(""); Even so,  in my experience
that does not work (at least for an image type procedure) in 2.99.   I
don't know the answer for 2.99, maybe there is another way, or it is a
"feature" that fell by the wayside when much of the plugin capability was
migrated inside Gimp from PyGimp.  Maybe just create a Gimp.Procedure
instead of a Gimp.ImageProcedure?

> How to create a GFile in  scheme in 2.99?

I opened issue https://gitlab.gnome.org/GNOME/gimp/-/issues/5402 reporting
this.  And I am working on a patch to Gimp.  You don't need to change your
plugin, Gimp code needs fixing.
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp 2.99 python3 plug-ins: writing a plugin to generate an image

[Shlomi Fish]

Hi Gottfried!

On Mon, 13 Jul 2020 10:29:32 +0200
Gottfried Müller  wrote:

> Hello
> 
> is it possible writing a plug-in to generate an image without an opened
> image? I found no examples. As a test I tried to open a file image only.
> I've got the following message:
> 
> GIMP-Error: Procedure 'python-fu-openImageFile' has been called with an
> invalid ID for argument 'image'. Most likely a plug-in is trying to work
> on an image that doesn't exist any longer.
> 
> Here a code snippet:
> 
> def openImageFile(procedure, args, data):
>      print("start openImageFile")
>      return procedure.new_return_values(Gimp.PDBStatusType.SUCCESS,
> GLib.Error())
> 
> 
> class OpenImageFile(Gimp.PlugIn):
> 
>      def do_query_procedures(self):
>      return ["python-fu-openImageFile"]
> 
>      def do_create_procedure(self, name):
>      data = None
>      procedure = Gimp.ImageProcedure.new(
>      self, name, Gimp.PDBProcType.PLUGIN, openImageFile, data
>      )
>      procedure.set_documentation(DESCR_SHORT, DESCR_LONG, name)
>      procedure.set_attribution(AUTHOR, COPYRIGHT, DATE)
>      procedure.set_menu_label(MENU_LABEL)
>      procedure.add_menu_path(MENU_PATH)
>      return procedure
> 
> Gimp.main(OpenImageFile.__gtype__, sys.argv)
> 

Perhaps this will help:

https://github.com/shlomif/gimp-lepton-support-for-dropbox-jpeg-compression/blob/87fde8b6252f6f6694b8ef5b97d5727925d74a7e/gimp-lepton/gimp-2.99/file-lepton.py

(short URL: https://is.gd/TlTlIF )

It is a gimp-python extension to open dropbox lepton .lep files:

https://github.com/dropbox/lepton

It took me some experimentation to write as well.

> I tried also an scheme script using gimp-file-load. It is using a GFile
> argument now. In 2.10 I could use a filename. How to create a GFile in
> scheme in 2.99?
> 

Don't know about scheme.

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



-- 

Shlomi Fish   https://www.shlomifish.org/
Why I Love Perl - https://shlom.in/joy-of-perl

Larry Wall *does* know all of Perl. However, he pretends to be wrong
or misinformed, so people will underestimate him.
— https://www.shlomifish.org/humour/bits/facts/Larry-Wall/

Please reply to list if it's a mailing list post - https://shlom.in/reply .
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp "make install" fails with undefined references to fresh-built gegl

[Ken Moffat via gimp-developer-list]

On Wed, Jul 08, 2020 at 02:39:08PM -0700, Deft Developer wrote:
> I got all of the dependencies (except WebKit) and GIMP 2.10.20 to build on
> CentOS.
> To make a very long  story short, each dependency, and GIMP, is best built
> with no traces of previous builds or out-of-date dependencies. "make clean"
> and re-configuring  are inadequate. It's easiest just to re-clone each
> repository, or delete each extracted source directory.
> Each dependency needs to be installed into whatever build-prefix is
> configured, and then the next dependency may be built. Sometimes, Iterating
> over multiple versions of a dependency is required. In that case,
> delete/uninstall the older version after you have built what needed it, and
> then build the newer version.
> 
> I simply gave up for webkit. Webkit is gigantic, and has a wilderness of
> dependencies. It easier just to use an external browser to access GIMP help.
> 
First, I'm glad you fixed it.

Second, for webkit my impression is that gimp-2.10 looks for an
ancient version.  Certainly, using firefox to access the online help
has worked fine for me in the last couple of years.

ĸen
-- 
   He died at the console, of hunger and thirst.
   Next day he was buried, face-down, nine-edge first.
  - the perfect programmer
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp "make install" fails with undefined references to fresh-built gegl

[Deft Developer]

I got all of the dependencies (except WebKit) and GIMP 2.10.20 to build on
CentOS.
To make a very long  story short, each dependency, and GIMP, is best built
with no traces of previous builds or out-of-date dependencies. "make clean"
and re-configuring  are inadequate. It's easiest just to re-clone each
repository, or delete each extracted source directory.
Each dependency needs to be installed into whatever build-prefix is
configured, and then the next dependency may be built. Sometimes, Iterating
over multiple versions of a dependency is required. In that case,
delete/uninstall the older version after you have built what needed it, and
then build the newer version.

I simply gave up for webkit. Webkit is gigantic, and has a wilderness of
dependencies. It easier just to use an external browser to access GIMP help.

-Original Message-
From: gimp-developer-list [mailto:gimp-developer-list-boun...@gnome.org] On
Behalf Of Charles Hymes
Sent: Tuesday, June 16, 2020 3:53 PM
To: gimp-developer-list@gnome.org
Subject: [Gimp-developer] Gimp "make install" fails with undefined
references to fresh-built gegl

I built gimp 2.10.18 on CentOS 7 last year on another host, but on a new
host with gimp 2.10.20, I'm stuck with undefined reference errors for GEGL.
I'm not a c++ developer, so this is all a foreign language to me :(

 

CentOS 7 libraries are all very old, so I built them, including latest GEGL
(0.4_24) and configured it with -prefix=/opt/gimp2.10

I deleted all gegl files before rebuilding, and now when I look in the lib64
dir I see the new libs:

 

ls -1 /opt/gimp-2.10/lib64/libgegl-* 
/opt/gimp-2.10/lib64/libgegl-0.4.so
/opt/gimp-2.10/lib64/libgegl-0.4.so.0
/opt/gimp-2.10/lib64/libgegl-0.4.so.0.424.1
/opt/gimp-2.10/lib64/libgegl-npd-0.4.so
/opt/gimp-2.10/lib64/libgegl-sc-0.4.so

 

ls -1 /opt/gimp-2.10/lib64/pkgconfig/gegl-*
/opt/gimp-2.10/lib64/pkgconfig/gegl-0.4.pc
/opt/gimp-2.10/lib64/pkgconfig/gegl-sc-0.4.pc

 

I set LD_LIBRARY_PATH and PKG_CONFIG_PATH to include my fresh libraries:

 
LD_LIBRARY_PATH=/opt/gimp-2.10/lib64:/opt/gimp-2.10/lib:/usr/local/lib64:/us
r/local/lib:/usr/lib
 
PKG_CONFIG_PATH=/opt/gimp-2.10/lib64/pkgconfig:/opt/gimp-2.10/share/pkgconfi
g:/opt/gimp-2.10/lib/pkgconfig/pkgconfig:/usr/local/share/pkgconfig:/usr/loc
al/lib/pkgconfig

 

But when I try to build gimp, ld fails. The errors start with:

 

make[3]: Entering directory
'/usr/exports/projects/3rd_party/gimp-world/gimp/app'

CCLD gimp-2.10

display/libappdisplay.a(gimpdisplay.o): In function
`gimp_display_update_bounding_box':

gimpdisplay.c:(.text+0x130c): undefined reference to
`gegl_rectangle_subtract'

...

gimp-gegl-utils.c:(.text+0xc7e): undefined reference to
`gegl_rectangle_subtract'

collect2: error: ld returned 1 exit status

make[3]: *** [Makefile:1010: gimp-2.10] Error 1

...

 

Is this a gegl mis-configuration or a gimp one?

How should I fix?

 

Thanks!

 

Deft

 

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

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

Re: [Gimp-developer] Gimp "make install" fails with undefined references to fresh-built gegl

[Carol Spears via gimp-developer-list]

On Tuesday, June 16, 2020, Charles Hymes  wrote:

> I built gimp 2.10.18 on CentOS 7 last year on another host, but on a new
> host with gimp 2.10.20, I'm stuck with undefined reference errors for GEGL.
> I'm not a c++ developer, so this is all a foreign language
>


No promises but, pretend it is 15 years ago and as root type 'ldconfig'.

Then try building GIMP again.

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

Re: [Gimp-developer] Gimp "make install" fails with undefined references to fresh-built gegl

[wwp]

Hello Deft,


On Tue, 16 Jun 2020 18:37:09 -0700 "Deft Developer"  wrote:

> I built gimp 2.10.18 on CentOS 7 last year on another host, but on a new
> host with gimp 2.10.20, I'm stuck with undefined reference errors for GEGL.
> I'm not a c++ developer, so this is all a foreign language to me :(
> 
> CentOS 7 libraries are all very old, so I built them, including latest GEGL
> (0.4_24) and configured it with -prefix=/opt/gimp2.10
> 
> I deleted all gegl files before rebuilding, and now when I look in the lib64
> dir I see the new libs:
> 
> ls -1 /opt/gimp-2.10/lib64/libgegl-* 
> /opt/gimp-2.10/lib64/libgegl-0.4.so
> /opt/gimp-2.10/lib64/libgegl-0.4.so.0
> /opt/gimp-2.10/lib64/libgegl-0.4.so.0.424.1
> /opt/gimp-2.10/lib64/libgegl-npd-0.4.so
> /opt/gimp-2.10/lib64/libgegl-sc-0.4.so
> 
> ls -1 /opt/gimp-2.10/lib64/pkgconfig/gegl-*
> /opt/gimp-2.10/lib64/pkgconfig/gegl-0.4.pc
> /opt/gimp-2.10/lib64/pkgconfig/gegl-sc-0.4.pc
> 
> I set LD_LIBRARY_PATH and PKG_CONFIG_PATH to include my fresh libraries:
>  
> LD_LIBRARY_PATH=/opt/gimp-2.10/lib64:/opt/gimp-2.10/lib:/usr/local/lib64:/us
> r/local/lib:/usr/lib
>  
> PKG_CONFIG_PATH=/opt/gimp-2.10/lib64/pkgconfig:/opt/gimp-2.10/share/pkgconfi
> g:/opt/gimp-2.10/lib/pkgconfig/pkgconfig:/usr/local/share/pkgconfig:/usr/loc
> al/lib/pkgconfig
> 
> But when I try to build gimp, ld fails. The errors start with:
> 
> make[3]: Entering directory
> '/usr/exports/projects/3rd_party/gimp-world/gimp/app'
> 
> CCLD gimp-2.10
> 
> display/libappdisplay.a(gimpdisplay.o): In function
> `gimp_display_update_bounding_box':
> 
> gimpdisplay.c:(.text+0x130c): undefined reference to
> `gegl_rectangle_subtract'
> 
> ...
> 
> gimp-gegl-utils.c:(.text+0xc7e): undefined reference to
> `gegl_rectangle_subtract'
> 
> collect2: error: ld returned 1 exit status
> 
> make[3]: *** [Makefile:1010: gimp-2.10] Error 1
> 
> ...
> 
>  
> 
> Is this a gegl mis-configuration or a gimp one?
> 
> How should I fix?

I build Gimp 2.8.x and 2.10.x on CentOS 7 (with the almost complete set
of dependencies and dependencies of dependencies and the
cross-dependency hell) too, and didn't face this situation.

Did you build the 2.10.20 sources against the old gegl, then build the
new gegl and rebuild gimp without doing a `make clean`?


Regards,

-- 
wwp
https://useplaintext.email/


pgp5cmJb_ZP2z.pgp
Description: OpenPGP digital signature
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] gimp git master + python

[Lloyd Konneker via gimp-developer-list]

The official stance is that Python plugins in Gimp 3 will need to use
Python3 and GObject Introspection.  There are working examples in the
gimp/plug-ins/python directory and at gimp/plug-ins/goat-exercises/... .py
.  AFAIK there is little documentation for plugin authors.

IOW PyGimp and GimpFu will be obsolete, but you will still be able to write
plugins in Python, and many other languages.

Also, plugins in Gimp 3 are a work in progress.  I think features like
automatic GUI (plugin dialog) generation and saving of settings might still
be absent in Gimp itself,  possibly just in the working examples.

There is a discussion https://gitlab.gnome.org/GNOME/gimp/-/issues/4717 and
also earlier in this mailing list.

Note I am not a Gimp developer, just a plugin author.
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] gimp: GEGL-WARNING: ..[] EEEEeEeek! 1 GeglBuffers leaked

[Øyvind Kolås]

On Thu, May 14, 2020 at 5:12 PM Julien Michielsen  wrote:
> Julien Michielsen schreef op 07-05-2020 17:25:
> > I recently installed Ubuntu 20.4, which comes with 2.10.18.
> > I tried to edit a screenshot of a typescript I had made (a
> > png file).  I had made a rectangular selection of a part of
> > the screenshot, and when I wanted to save this selection of
> > the typescript I got the message:
> > gimp: GEGL-WARNING:
> > (../gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy:
> > runtime check failed:
> > (g_queue_is_empty (&cache_queue))
> > eEeek! 1 GeglBuffers leaked
> >
> > The error I experienced (and can reproduce as often as I
> > wish) looks like the one experienced by Elle Stone
> > "GeglBuffer leaks when using GIMP to cut a selection
> > Submitted by Elle Stone @ellestone
> >
> > Link to original bug (#770241)"
> >
> > It looks to me like if there is an error in gimp when making
> > rectangular selections and saving these to disk, and I report
> > this in the hope it helps to solve this.
>
> Today the same error happened again to me.  I had done the following,
> like previous time: opened a png-file with gimp (a snapshot of my
> screen,
> showing a graph I had found with firefox), made a rectangular selection
> of the graph, pasted the rectangular graph in a file I just created in
> gimp (file, new, giving a size just big enough to copy the graph into),
> subsequently I exported the file with the graph to a new png-file). Up
> till this moment everything went fine. Only my departure from Gimp is
> accompanied with the EEEeEEek! message. The last one I got:
> gimp: GEGL-WARNING:
> (../gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy:
> runtime check failed: (g_queue_is_empty (&cache_queue))
>
> So the problem seems to be linked to the departure and closure of
> gimp. I hope this can be usefull for diagnosing the problem.

The messages occur when closing GIMP, because internal book-keeping is
not adding up. Pixel data is what takes up the largest amount of
memory in GIMP and there is extra mechanisms reporting any suspicious
balances at shutdown, actual problem is related to the actions youv'e
taken during the session, repeatable steps are valuable. And if
repeating the steps you are able to make the count of leaked buffers
go higher we have a problematic memory leak.

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

Re: [Gimp-developer] gimp: GEGL-WARNING: ..[] EEEEeEeek! 1 GeglBuffers leaked

[Julien Michielsen]

Julien Michielsen schreef op 07-05-2020 17:25:

I recently installed Ubuntu 20.4, which comes with 2.10.18.
I tried to edit a screenshot of a typescript I had made (a
png file).  I had made a rectangular selection of a part of
the screenshot, and when I wanted to save this selection of
the typescript I got the message:
gimp: GEGL-WARNING:
(../gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy:
runtime check failed:
(g_queue_is_empty (&cache_queue))
eEeek! 1 GeglBuffers leaked

The error I experienced (and can reproduce as often as I
wish) looks like the one experienced by Elle Stone
"GeglBuffer leaks when using GIMP to cut a selection
Submitted by Elle Stone @ellestone

Link to original bug (#770241)"

It looks to me like if there is an error in gimp when making
rectangular selections and saving these to disk, and I report
this in the hope it helps to solve this.


Today the same error happened again to me.  I had done the following,
like previous time: opened a png-file with gimp (a snapshot of my 
screen,

showing a graph I had found with firefox), made a rectangular selection
of the graph, pasted the rectangular graph in a file I just created in
gimp (file, new, giving a size just big enough to copy the graph into),
subsequently I exported the file with the graph to a new png-file). Up
till this moment everything went fine. Only my departure from Gimp is
accompanied with the EEEeEEek! message. The last one I got:
gimp: GEGL-WARNING: 
(../gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy: 
runtime check failed: (g_queue_is_empty (&cache_queue))


So the problem seems to be linked to the departure and closure of
gimp. I hope this can be usefull for diagnosing the problem.

Julien Michielsen

--
Julien Michielsen
jul...@michkloo.xs4all.nl
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] GIMP 2.10.18 released

[Shlomi Fish]

On Tue, 25 Feb 2020 00:25:12 +0300
Alexandre Prokoudine via gimp-developer-list 
wrote:

> Hello,
> 
> A new version of GIMP is out. Release highlights:
> 

Thanks to all contributors! ♥


-- 

Shlomi Fish   https://www.shlomifish.org/
Apple Inc. is Evil - https://www.shlomifish.org/open-source/anti/apple/

Fortran - there isn’t a way to do it... oh wait! Now there is.
— http://www.shlomifish.org/humour/ways_to_do_it.html

Please reply to list if it's a mailing list post - http://shlom.in/reply .
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] GIMP 2.10.18? Yes, 2.10.18!

[Ell via gimp-developer-list]

On 2/21/20 8:57 PM, Ell via gimp-developer-list wrote:
> Hey, we're doing a ninja 2.10.18 release.  There was an ugly data
> corruption bug in 2.10.16
> (https://gitlab.gnome.org/GNOME/gimp/issues/4643) -- good thing we
> didn't announce it yet, huh? :)  We want to do it later today or
> tomorrow (more likely).  Just a heads up, if you have some last-minute
> fixes to push.

Well, this wasn't actually supposed to go to the list, but whatever.  If
anyone is already using 2.10.16, you might want to revert to 2.10.14 for
now.  There should be a new release soon.

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

Re: [Gimp-developer] GIMP 2,.8 Bug for function cancel - control+z

[Liam R E Quin]

On Sat, 2020-02-08 at 14:06 +, aertx0--- via gimp-developer-list
wrote:
> Does GIMP have a bug for version 2.8, with the button control  + z
> not working?

control-Z is Undo, not cancel. You can find it under the Edit menu.

The current GIMP version is 2.10, not 2.8, so you might want to update,
although i have not heard of undo not working at all. It might not work
if you have a very large image and are low on memory but i have not
seen that in many years.

slave liam




-- 
Liam Quin - web slave for https://www.fromoldbooks.org/
with fabulous vintage art and fascinating texts to read.
Click here to have the slave chained up.

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

Re: [Gimp-developer] GIMP 2,.8 Bug for function cancel - control+z

[Ofnuts]

On 2/8/20 3:06 PM, aertx0--- via gimp-developer-list wrote:

Does GIMP have a bug for version 2.8, with the button control  + z not
working?
Platform: Win7 64 bit


Never heard of that one. Go to "Edit>Keyboard shortcuts", and enter
"undo" in the search bar. Is Ctrl-Z mapped to "edit-undo"?



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

Re: [Gimp-developer] GIMP Workshop, Denmark 2020, GG Festival

[Alexandre Prokoudine via gimp-developer-list]

On Wed, Nov 6, 2019 at 10:22 PM Merete Jensen via gimp-developer-list
 wrote:
>
> Hi!
>
> I talked to one of your "colleagues" on Facebook the other day and they
> sent me this email, since you were all a bit busy with the new release -
> Which is understandable :)
>
>  I was contacted by GG Festival who wants me to join them in February and
> setup a creative workshop, where I'll be using GIMP to teach the basics and
> help the interested guests to make art that they can later receive on a
> sticker or other, to bring home with them.
>
> Last year they sold around 640 weekend tickets for the event (Not including
> guest/one day tickets). The event is mainly targeted at kids from 8-15
> years old.
>
> The reason why I contacted you guys, was to make sure this was ok for me to
> do. According to the answer on Facebook it's was all good.

Absolutely :) Give us the URL for the event, and we'll do extra PR for
your workshop on the social media too :)

> I also wanted to know if there's a chance you guys would throw in some
> pins, stickers, keyhangers or other "merch" like it, to hand out to the
> guests at the event. All to make your name more visual. :) This is what I
> was asked to email you about. :)

We _probably_ have some stickers around. Simon Budig would be the best
guy to talk to about the merch.

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

Re: [Gimp-developer] GIMP accessability Voluntary Product Accessibility Template(R)

[Liam R E Quin]

On Tue, 2019-09-17 at 17:03 +0200, Bernard Swart via gimp-developer-
list wrote:
>  I cannot get GIMP to read the icons labels when hovering with a
> mouse over them. The screen reader also does not read the menu and
> its submenus and items.

Which Linux distribution are you using? Is this with the Orca screen
reader? Which version of GIMP?

When i used GIMP with orca, i found it useful to edit preferences and
get rid of most of the stuff in the title bar as every time it changes,
orca reads out the title again, and that can be very irritating e.g. if
you are using the paintbrush.

slave liam (ankh on IRC)


-- 
Liam Quin - web slave for https://www.fromoldbooks.org/
with fabulous vintage art and fascinating texts to read.
Click here to have the slave beaten.

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

Re: [Gimp-developer] GIMP Open Ports

[Simon Budig]

Hi Estefania.

Hernandez, Estefania [USA] via gimp-developer-list 
(gimp-developer-list@gnome.org) wrote:
> Good afternoon,
> 
> I recently scanned GIMP and noticed that GIMP uses TCP 2177.
> 
> I was wondering if I could get information on TCP 2177, such as, what is the 
> purpose of TCP 2177?

I am right now unaware of gimp opening a port.

Did you install Gimp from the official packages referenced at
https://www.gimp.org/downloads/ ?

In the past there have been instances of unofficial installers, which
bundled unwanted addons or even malware. Please make sure to only use
official installers.

Bye,
 Simon

-- 
  si...@budig.de  http://simon.budig.de/
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] GIMP not compiling... and it is putting the blame on me??

[Ell via gimp-developer-list]

On 9/14/19 6:59 PM, Marco Ciampa via gimp-developer-list wrote:
> Hi devs,
> I received this email telling me that last commit I did made the GIMP
> compilation stop.
> 
> I updated the po/it.po file and then the po-plugins/it.po file, and
> NOTHING ELSE.
> 
> 
> Looking into the GIMP compilation error messages, I see this:
> 
> [...]
> 
> Obviously this has nothing to do with the translation .po files...
> 
> What is going on here?

The 2.10 CI build is currently broken, it's not your doing :)  GitLab
sends this message whenever CI fails to build a commit you've pushed,
even if previous commits had already been failing the same way.

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

Re: [Gimp-developer] GIMP build: XDG_DATA_DIRS causing "Unrecognized image file format"

[Liam R. E. Quin]

On Tue, 2019-09-03 at 15:10 -0400, Elle Stone wrote:
> 
> What I do know is that building babl/GEGL/GIMP is getting
> increasingly 
> complicated. 

Yes - i think it now depends on whether you'r wearing shoes, and the
colour of your socks. That is, it depends on things most of us eouldn't
think were relevant; we have to learn about the new dependencies.


> In case anyone has an idea what went wrong, here's the terminal
> output for the failed GEGL build:

[...]

> Couldn't find include 'Babl-0.1.gir' (search path: '['gir-1.0', 
> '/usr/share/gir-1.0', '/usr/share/gir-1.0', '/usr/share/gir-1.0']')
> [223/750] Generating module_common_gpl3.c with a meson_exe.py custom 
> command.

XDG_DATA_DIRS is used to find this. So, i think what matters is having
XDG_DATA_DIRS set, but also the order of the entries within it when it
is set. You need $prefix first i think.

slave ankh


-- 
Liam Quin, https://www.delightfulcomputing.com/
Available for XML/Document/Information Architecture/XSLT/
XSL/XQuery/Web/Text Processing/A11Y training, work & consulting.
Web slave for vintage clipart http://www.fromoldbooks.org/

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

Re: [Gimp-developer] GIMP-2.99 terminal complaints: python3, not finding Gegl v0.4, exceptions/tracebacks, various plug-ins

[Elle Stone]

On 9/5/19 9:11 AM, Øyvind Kolås wrote:

At least there is problems related to python / gobject introspection
not finding the Gegl-0.4.typelib, on my system that file is in
$PREFIX/lib/x86_64-linux-gnu/girepository-1.0 and that path has to be
added to the little documented GI_TYPELIB_PATH. Gobject-introspection
seem to be refined for system installed libraries/scripts, but there
are more hoops we have to run through for people that are building and
installing in custom prefixes.




Hi Pippin, and thanks! for the typelib hints. Sadly that didn't fix the 
terminal complaints, so maybe I'm still doing something wrong, or maybe 
more paths are needed, or maybe the code itself has issues.


On Debian Sid in my GIMP-2.99 prefix, the babl/GEGL typelibs are here:

   $PREFIX/lib/x86_64-linux-gnu/girepository-1.0/

and the GIMP typelib is here:

   $PREFIX/lib/girepository-1.0

Unfortunately, setting up my prefix like this:

PREFIX=$HOME/code-install/gimp299/install
export SRC_DIR=/home/elle/code-build/gimp299/build
export PATH=$PREFIX/bin:$PATH
export ACLOCAL_FLAGS="-I $PREFIX/share/aclocal"
export LD_LIBRARY_PATH=$PREFIX/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH=$PREFIX/lib/x86_64-linux-gnu:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig:$PKG_CONFIG_PATH
export PKG_CONFIG_PATH=$PREFIX/lib/x86_64-linux-gnu:$PKG_CONFIG_PATH
export 
PKG_CONFIG_PATH=$PREFIX/lib/x86_64-linux-gnu/pkgconfig:$PKG_CONFIG_PATH

export PKG_CONFIG_PATH=$PREFIX/share/pkgconfig:$PKG_CONFIG_PATH
export 
GI_TYPELIB_PATH=$PREFIX/lib/x86_64-linux-gnu/girepository-1.0:$PKG_CONFIG_PATH

export GI_TYPELIB_PATH=$PREFIX/lib/girepository-1.0:$PKG_CONFIG_PATH
export 
XDG_DATA_DIRS="$XDG_DATA_DIRS:$PREFIX/share:/usr/local/share/:/usr/share/"


and then rebuilding/installing babl/GEGL/GIMP-2.99 from scratch,

and then running GIMP-2.99, still results in typelib errors printed to 
the terminal (the other errors disappeared after updating GIMP 
yesterday, so not related to these remaining errors). Any ideas on what 
still needs to be changed? Did I set up the prefix correctly? Anything 
else needed?


Maybe there's an issue in the plug-in code for the affected plug-ins?

Maybe the python-related errors mean something needs to be added for python?

Best,
Elle

Here's the terminal output on starting the rebuilt/installed 
babl/GEGL/GIMP-2.99


Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 138, in 
load_module

introspection_module = get_introspection_module(namespace)
  File "/usr/lib/python3/dist-packages/gi/module.py", line 265, in 
get_introspection_module

module = IntrospectionModule(namespace, version)
  File "/usr/lib/python3/dist-packages/gi/module.py", line 117, in __init__
repository.require(namespace, version)
gi.RepositoryError: Typelib file for namespace 'Gegl', version '0.4' not 
found


During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/home/elle/code-install/gimp299/install/lib/gimp/2.99/plug-ins/spyro-plus/spyro-plus.py", 
line 20, in 

from gi.repository import Gimp
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 140, in 
load_module

raise ImportError(e)
ImportError: Typelib file for namespace 'Gegl', version '0.4' not found
GIMP-WARNING: gimp-2.99: gimp_wire_read(): error

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 138, in 
load_module

introspection_module = get_introspection_module(namespace)
  File "/usr/lib/python3/dist-packages/gi/module.py", line 265, in 
get_introspection_module

module = IntrospectionModule(namespace, version)
  File "/usr/lib/python3/dist-packages/gi/module.py", line 117, in __init__
repository.require(namespace, version)
gi.RepositoryError: Typelib file for namespace 'Gegl', version '0.4' not 
found


During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/home/elle/code-install/gimp299/install/lib/gimp/2.99/plug-ins/py-slice/py-slice.py", 
line 30, in 

from gi.repository import Gimp
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 140, in 
load_module

raise ImportError(e)
ImportError: Typelib file for namespace 'Gegl', version '0.4' not found
GIMP-WARNING: gimp-2.99: gimp_wire_read(): error

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 138, in 
load_module

introspection_module = get_introspection_module(namespace)
  File "/usr/lib/python3/dist-packages/gi/module.py", line 265, in 
get_introspection_module

module = IntrospectionModule(namespace, version)
  File "/usr/lib/python3/dist-packages/gi/module.py", line 117, in __init__
repository.require(namespace, version)
gi.RepositoryError: Typelib file for namespace 'Gegl', version '0.4' not 
found


During handling of the above exception, another exception occurred:

Traceback (most recent call last)

Re: [Gimp-developer] GIMP-2.99 terminal complaints: python3, not finding Gegl v0.4, exceptions/tracebacks, various plug-ins

[Øyvind Kolås]

At least there is problems related to python / gobject introspection
not finding the Gegl-0.4.typelib, on my system that file is in
$PREFIX/lib/x86_64-linux-gnu/girepository-1.0 and that path has to be
added to the little documented GI_TYPELIB_PATH. Gobject-introspection
seem to be refined for system installed libraries/scripts, but there
are more hoops we have to run through for people that are building and
installing in custom prefixes.

On Wed, Sep 4, 2019 at 6:06 PM Elle Stone
 wrote:
>
> I just updated and recompiled babl/GEGL/GIMP-2.99 (through GIMP commit
> commit 7019eaa56bcd9fc77f215e36c280bf6daae641e5), with no errors during
> the build, but with a lot of terminal complaints upon starting GIMP.
>
> I'm guessing the code is still in a state of flux from all the recent
> activity regarding plug-ins, so filing a bug report seems a bit silly.
>
> GIMP did start and run without any problems or significant further
> terminal complaints.
>
> In case it's helpful, here's the terminal output:
>
> # First, several screen's worth of these error messages: ###
>
> _gimp_gp_param_def_to_param_spec: GParamSpec type 'GimpParamImageID' is
> not handled
> GIMP-CRITICAL: gimp_procedure_add_return_value: assertion
> 'G_IS_PARAM_SPEC (pspec)' failed
>
> _gimp_gp_param_def_to_param_spec: GParamSpec type 'GimpParamImageID' is
> not handled
> GIMP-CRITICAL: gimp_procedure_add_argument: assertion 'G_IS_PARAM_SPEC
> (pspec)' failed
>
> _gimp_gp_param_def_to_param_spec: GParamSpec type 'GimpParamDrawableID'
> is not handled
> GIMP-CRITICAL: gimp_procedure_add_argument: assertion 'G_IS_PARAM_SPEC
> (pspec)' failed
>
>
> # Followed by many complaints about python3, not finding Gegl v0.4,
> exceptions/tracebacks, and various plug-ins: ###
>
> Traceback (most recent call last):
>File "/usr/lib/python3/dist-packages/gi/importer.py", line 138, in
> load_module
>  introspection_module = get_introspection_module(namespace)
>File "/usr/lib/python3/dist-packages/gi/module.py", line 265, in
> get_introspection_module
>  module = IntrospectionModule(namespace, version)
>File "/usr/lib/python3/dist-packages/gi/module.py", line 117, in __init__
>  repository.require(namespace, version)
> gi.RepositoryError: Typelib file for namespace 'Gegl', version '0.4' not
> found
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>File
> "/home/elle/code-install/gimp299/install/lib/gimp/2.99/plug-ins/spyro-plus/spyro-plus.py",
> line 20, in 
>  from gi.repository import Gimp
>File "/usr/lib/python3/dist-packages/gi/importer.py", line 140, in
> load_module
>  raise ImportError(e)
> ImportError: Typelib file for namespace 'Gegl', version '0.4' not found
> GIMP-WARNING: gimp-2.99: gimp_wire_read(): error
>
> Traceback (most recent call last):
>File "/usr/lib/python3/dist-packages/gi/importer.py", line 138, in
> load_module
>  introspection_module = get_introspection_module(namespace)
>File "/usr/lib/python3/dist-packages/gi/module.py", line 265, in
> get_introspection_module
>  module = IntrospectionModule(namespace, version)
>File "/usr/lib/python3/dist-packages/gi/module.py", line 117, in __init__
>  repository.require(namespace, version)
> gi.RepositoryError: Typelib file for namespace 'Gegl', version '0.4' not
> found
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>File
> "/home/elle/code-install/gimp299/install/lib/gimp/2.99/plug-ins/py-slice/py-slice.py",
> line 30, in 
>  from gi.repository import Gimp
>File "/usr/lib/python3/dist-packages/gi/importer.py", line 140, in
> load_module
>  raise ImportError(e)
> ImportError: Typelib file for namespace 'Gegl', version '0.4' not found
> GIMP-WARNING: gimp-2.99: gimp_wire_read(): error
>
> Traceback (most recent call last):
>File "/usr/lib/python3/dist-packages/gi/importer.py", line 138, in
> load_module
>  introspection_module = get_introspection_module(namespace)
>File "/usr/lib/python3/dist-packages/gi/module.py", line 265, in
> get_introspection_module
>  module = IntrospectionModule(namespace, version)
>File "/usr/lib/python3/dist-packages/gi/module.py", line 117, in __init__
>  repository.require(namespace, version)
> gi.RepositoryError: Typelib file for namespace 'Gegl', version '0.4' not
> found
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>File
> "/home/elle/code-install/gimp299/install/lib/gimp/2.99/plug-ins/palette-to-gradient/palette-to-gradient.py",
> line 18, in 
>  from gi.repository import Gimp
>File "/usr/lib/python3/dist-packages/gi/importer.py", line 140, in
> load_module
>  raise ImportError(e)
> ImportError: Typelib file for namespace 'Gegl', version '0.4' not found
> GIMP-WARNING: gimp-2.99: gimp_wire_read(): error
>
> Traceback (most recent call last):
>File "/usr

Re: [Gimp-developer] GIMP build: XDG_DATA_DIRS causing "Unrecognized image file format"

[Elle Stone]

On 9/3/19 3:38 PM, Liam R. E. Quin wrote:

On Tue, 2019-09-03 at 15:10 -0400, Elle Stone wrote:

Couldn't find include 'Babl-0.1.gir' (search path: '['gir-1.0',
'/usr/share/gir-1.0', '/usr/share/gir-1.0', '/usr/share/gir-1.0']')
[223/750] Generating module_common_gpl3.c with a meson_exe.py custom
command.


XDG_DATA_DIRS is used to find this. So, i think what matters is having
XDG_DATA_DIRS set, but also the order of the entries within it when it
is set. You need $prefix first i think.


Thanks! So for current (as of last week) Debian Sid and current 
babl/GEGL/GIMP-2.99 (as of this morning), XDG_DATA_DIRS really does need 
to be set.


But for Debian Testing, it seems XDG_DATA_DIRS shouldn't be set. I 
wonder what has changed between Debian Testing and Sid.


Anyone know what an XDG_DATA_DIRS actually is? Also, what is this "gir" 
thing that GEGL was looking for?


Elle


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

Re: [Gimp-developer] GIMP build: XDG_DATA_DIRS causing "Unrecognized image file format"

[Elle Stone]

On 9/3/19 11:59 AM, Akkana Peck wrote:

Does setting
XDG_DATA_DIRS="$XDG_DATA_DIRS:$PREFIX/share:/usr/local/share/:/usr/share/"
actually work for you, and you don't see the "Unrecognized image
file format" problem any more?


Well, it did work exactly as I posted. FWIW, just now I tried rebuilding 
GIMP-2.99 from scratch, starting from an empty install folder, but with 
the line 
'XDG_DATA_DIRS="$XDG_DATA_DIRS:$PREFIX/share:/usr/local/share/:/usr/share/"' 
commented out. But the build failed at GEGL (terminal output is below). 
Whether this failure to build with the XDG line commented out is 
coincidence or not, I just don't know, haven't yet taken the time to 
figure it out.


What I do know is that building babl/GEGL/GIMP is getting increasingly 
complicated. It would be nice if the developers who are writing all this 
new code for GIMP-2.99 could provide up-to-date guidelines for building 
all this new code :) but I guess "how to build" varies a lot from one 
system (and day) to the next.


I do vaguely remember the issue you mentioned with not finding the image 
file formats. That was on Debian, but not the current version of Debian 
Sid. There was another issue? The same issue? - sorry, I don't remember 
- that I encountered recently on Debian Sid, where the advice from 
Hacking GIMP was contrary to what actually worked, though the Hacking 
GIMP advice had worked previously.



In case anyone has an idea what went wrong, here's the terminal output 
for the failed GEGL build:


elle@debian:~/code-build/gimp299/build/gegl/build$ ninja install
[214/750] Generating Gegl-0.4.gir with a custom command.
FAILED: gegl/Gegl-0.4.gir
/usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
--no-libtool --namespace=Gegl --nsversion=0.4 --warn-all --output 
gegl/Gegl-0.4.gir --c-include=gegl.h 
-I/media/data1/code-build/gimp299/build/gegl/gegl 
-I/media/data1/code-build/gimp299/build/gegl/build/gegl -I./. -I../. 
-I./gegl/. -I../gegl/. -I./gegl/buffer -I../gegl/buffer -I./gegl/graph 
-I../gegl/graph -I./gegl/module -I../gegl/module -I./gegl/opencl 
-I../gegl/opencl -I./gegl/operation -I../gegl/operation -I./gegl/process 
-I../gegl/process -I./gegl/property-types -I../gegl/property-types 
--filelist=/media/data1/code-build/gimp299/build/gegl/build/gegl/2cd4258@@gegl-0.4@sha/Gegl_0.4_gir_filelist 
--include=GLib-2.0 --include=GObject-2.0 --include=Babl-0.1 
--symbol-prefix=gegl --identifier-prefix=Gegl --cflags-begin 
-DHAVE_CONFIG_H -Winit-self -Wmissing-declarations -Wmissing-prototypes 
-Wold-style-definition -Wpointer-arith -Wno-deprecated-declarations 
-mfpmath=sse -mmmx -msse -msse2 -msse4.1 -I./. -I../. -I./gegl/. 
-I../gegl/. -I./gegl/buffer -I../gegl/buffer -I./gegl/graph 
-I../gegl/graph -I./gegl/module -I../gegl/module -I./gegl/opencl 
-I../gegl/opencl -I./gegl/operation -I../gegl/operation -I./gegl/process 
-I../gegl/process -I./gegl/property-types -I../gegl/property-types 
-I/home/elle/code-install/gimp299/install/include/babl-0.1 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gio-unix-2.0 
--cflags-end --library gegl-0.4 
-L/media/data1/code-build/gimp299/build/gegl/build/gegl 
-L/home/elle/code-install/gimp299/install/lib/x86_64-linux-gnu 
-L/home/elle/code-install/gimp299/install/lib/x86_64-linux-gnu 
--extra-library=babl-0.1 --extra-library=glib-2.0 
--extra-library=gio-2.0 --extra-library=gobject-2.0 --extra-library=m 
--extra-library=gmodule-2.0
Couldn't find include 'Babl-0.1.gir' (search path: '['gir-1.0', 
'/usr/share/gir-1.0', '/usr/share/gir-1.0', '/usr/share/gir-1.0']')
[223/750] Generating module_common_gpl3.c with a meson_exe.py custom 
command.

ninja: build stopped: subcommand failed.
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp logo

[Pat David via gimp-developer-list]

It would be nice to have an /about/logo page, I’ll see about getting one
made.

The Wilber in the webpage is also official, and I believe can be used for
your purposes?

On Wed, May 29, 2019 at 9:29 AM David  wrote:

> Thank you, looks great.
>
> What's the font used in 2.8 and on gimp.org?
>
>
> The file in source/docs doesn't seem to be right. That file is an
> 100x75px image.
>
> Same for the other xcf there and the svg is much outdated.
>
> (source from here: https://gitlab.gnome.org/GNOME/gimp/tree/master/docs)
>
>
> I think it would be useful if there was some info regarding the logo on
> the website.
>
> Here's some examples from other open projects for reference:
>
> https://www.blender.org/about/logo/
>
> https://kdenlive.org/en/logo/
>
>
> Regards,
>
> David
>
>
>
>
> On 2019-05-29 09:20, C R wrote:
> > I also made this vector one in svg format, if that suits better:
> > https://www.dropbox.com/s/ouqyez32cer1veq/gimp_2.8_logo.svg?dl=1
> >
> > -C
> >
> > On Wed, May 29, 2019 at 7:44 AM David  > > wrote:
> >
> > Hello,
> >
> > I'm looking for the Gimp logo for use in film credits.
> >
> > Where can I find it in high quality?
> >
> >
> > Regards,
> >
> > David Rylander,
> >
> > Sweden
> >
> > --
> > ***
> > David Rylander
> > Rylander animation
> > Bergsrådsvägen 102, bv
> > 12842 Bagarmossen
> >
> > tel: +46(0)708-461978
> > www.rylanderanimation.se 
> > instagram: davidrylander
> > twitter: RylanderAnim
> > g+: rylle...@gmail.com 
> > ***
> >
> > ___
> > gimp-developer-list mailing list
> > List address: gimp-developer-list@gnome.org
> > 
> > List membership:
> > https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> > List archives: https://mail.gnome.org/archives/gimp-developer-list
> >
> --
> ***
> David Rylander
> Rylander animation
> Bergsrådsvägen 102, bv
> 12842 Bagarmossen
>
> tel: +46(0)708-461978
> www.rylanderanimation.se
> instagram: davidrylander
> twitter: RylanderAnim
> g+: rylle...@gmail.com
> ***
>
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
-- 
https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] [Gimp-user] C2G

[Carol Spears via gimp-developer-list]

On Tuesday, June 25, 2019, Jack Ogden  wrote:

> Hi,
>
> I have been using the GEGL C2G a lot in Gimp 2.8. Now I have updated to
> 2.10 I find the parameters in Color to Grey very different and have been
> unable to get the same effects - they seem more washed out and with less
> contrast.
>
> Any thoughts?
>

I noticed this with linear desaturate and switched my scripts back to the
other sometime ago.

A better discussion of this might be found at the developer mail list where
the authors are more frequent.

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

Re: [Gimp-developer] Gimp Background Removal App

[Ofnuts]

On 6/9/19 6:05 AM, Sarey Savy via gimp-developer-list wrote:

Hello there!

I absolutely love the Gimp background removal app but I noticed it scales the 
image drastically to a smaller size...

Is there a way to remove the back ground but keep the original size width and 
height of the image?

Looking forward to hearing back soon,

Sarey



Uh? You mean the foreground selector? It doesn't scale things, normally.
Can you provide a sample image?

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

Re: [Gimp-developer] [Gimp-gui] Using GIMP in the textile industry

[Jehan]

On 2019-06-04 14:31, Tobias Ellinghaus wrote:

Am Dienstag, 28. Mai 2019, 13:30:08 CEST schrieb Simon Budig:

[...]


One thing which came up though (and which we already have discussed in
the past IIRC) is the need for a better support for multiple documents
in single window mode. The software they're using currently is using a
classic Windows Multiple Documents Interface (MDI) and they do in fact
make use of it. I tried to explain why I personally consider GIMPs
multiple window interface as quite good, but the not-so-great support
for multiple desktops in windows (and the bad window management) made
this a tough point to sell...  :)

I see two options here and I think we've been discussing these in the
past.
  a) create multiple side-by-side image views within the single window
 mode. We could allow for tiling the image area into multiple
 notebooks, each containing its own set of images, allowing for
 Drag'n'Drop between them etc. ppp. My gut feeling is that this
 should be quite doable. It might be a bit tricky to control the
 keyboard focus there and to make it clear to the user, which of 
the

 images will be affected by the next keystroke.

  b) (not necessary XOR) it might be feasible to allow for a kind of
 hybrid single/multiple window mode, where one can drag out
notebook-tabs into their own image view that then is managed by the 
window
 manager. So we would have one dedicated main window containing 
the
 toolbox and the notebook-area with image views as well as 
separate

 windows containing image views (or a notebook of image views?).


What about this:

The tabs in single image mode are not just for one image each but 
contain
"workspaces". By default an image is opened in a new workspace 
containing a
single image, so it's the same we currently have. It would however be 
possible
to split the image area to show more than one image or view. I somewhat 
like
the quick and easy way that's done in blender, however, one would need 
to
think about what to do when the last view of an image is closed. That 
way each

tab could contain a arbitrarily complex setup of image views with the
toolboxen staying the same for all of them. Having rip-off windows 
might be
nice, but I personally don't feel the need, and having both a single 
image

window mixed with some floating windows might be confusing.


How we handle images in single window mode is anyway a real pain to me. 
Splitting a single tab to show several views of the same image or even 
different images is indeed a great idea.
But also we should be able to detach image tabs (which is what you call 
rip-off windows, I guess?) into their own windows (same as we can detach 
dockables even when in single window mode). I personally don't believe 
this to be confusing. I mean detaching tabs is a common feature in many 
software (like web browsers!), and it allows to do much more than being 
limited by what the program will allow you. First of all, if you have 
several screens, you can leave some images on one screen (say your 
reference images) and others on another screen (the image(s) you are 
working on for instance). And more usage (you are then only limited by 
your window manager).


In other words, we should stop with the whole single vs multi window 
mode nonsense. We should simply have a single mode allowing all 
possibilities (attaching or detaching images, dockables, toolbox, etc.).


This is something which have been on my TODO-list for years, and I am 
never able to make the time to do this. I would support anyone wishing 
to work in such directions. :-)


I'm also CC'ing the gui list as that seems to be a better place for 
this part

of the discussion.


By the way, maybe you want to subscribe to the gui list. I had to 
manually approve this email. :-)


Jehan


[...]


Bye,
 Simon


Tobias

___
gimp-gui-list mailing list
gimp-gui-l...@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-gui-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-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp logo

[David]

Thank you, looks great.

What's the font used in 2.8 and on gimp.org?


The file in source/docs doesn't seem to be right. That file is an 
100x75px image.


Same for the other xcf there and the svg is much outdated.

(source from here: https://gitlab.gnome.org/GNOME/gimp/tree/master/docs)


I think it would be useful if there was some info regarding the logo on 
the website.


Here's some examples from other open projects for reference:

https://www.blender.org/about/logo/

https://kdenlive.org/en/logo/


Regards,

David




On 2019-05-29 09:20, C R wrote:

I also made this vector one in svg format, if that suits better:
https://www.dropbox.com/s/ouqyez32cer1veq/gimp_2.8_logo.svg?dl=1

-C

On Wed, May 29, 2019 at 7:44 AM David > wrote:


Hello,

I'm looking for the Gimp logo for use in film credits.

Where can I find it in high quality?


Regards,

David Rylander,

Sweden

-- 
***

David Rylander
Rylander animation
Bergsrådsvägen 102, bv
12842 Bagarmossen

tel: +46(0)708-461978
www.rylanderanimation.se 
instagram: davidrylander
twitter: RylanderAnim
g+: rylle...@gmail.com 
***

___
gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org

List membership:
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list


--
***
David Rylander
Rylander animation
Bergsrådsvägen 102, bv
12842 Bagarmossen

tel: +46(0)708-461978
www.rylanderanimation.se
instagram: davidrylander
twitter: RylanderAnim
g+: rylle...@gmail.com
***

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

Re: [Gimp-developer] Gimp logo

[C R via gimp-developer-list]

Ooops! Didn't see it was changed. Yes, mine is an older version, please go
with what Michael's version.

On Wed, May 29, 2019 at 9:11 AM Michael Natterer  wrote:

> On Tue, 2019-05-28 at 14:41 +0200, David wrote:
> > Hello,
> >
> > I'm looking for the Gimp logo for use in film credits.
> >
> > Where can I find it in high quality?
>
>
> https://gitlab.gnome.org/GNOME/gimp/blob/master/icons/Color/scalable/gimp-wilber.svg
>
> This is the current official logo. PLEASE don't use any of the
> other suggestions.
>
> Regards,
> Mitch
>
>
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp logo

[C R via gimp-developer-list]

Sure. Feel free to add it to the repo. That's what I made it for. :)

No credit needed.

-C

On Wed, 29 May 2019, 08:44 Shlomi Fish,  wrote:

> On Wed, 29 May 2019 08:20:28 +0100
> C R via gimp-developer-list  wrote:
>
> > I also made this vector one in svg format, if that suits better:
> > https://www.dropbox.com/s/ouqyez32cer1veq/gimp_2.8_logo.svg?dl=1
> >
> > -C
> >
>
> Thanks for sharing it. It looks great.
>
> > On Wed, May 29, 2019 at 7:44 AM David 
> wrote:
> >
> > > Hello,
> > >
> > > I'm looking for the Gimp logo for use in film credits.
> > >
> > > Where can I find it in high quality?
> > >
> > >
> > > Regards,
> > >
> > > David Rylander,
> > >
> > > Sweden
> > >
> > > --
> > > ***
> > > David Rylander
> > > Rylander animation
> > > Bergsrådsvägen 102, bv
> > > 12842 Bagarmossen
> > >
> > > tel: +46(0)708-461978
> > > www.rylanderanimation.se
> > > instagram: davidrylander
> > > twitter: RylanderAnim
> > > g+: rylle...@gmail.com
> > > ***
> > >
> > > ___
> > > gimp-developer-list mailing list
> > > List address:gimp-developer-list@gnome.org
> > > List membership:
> > > https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> > > List archives:   https://mail.gnome.org/archives/gimp-developer-list
> > >
> > ___
> > gimp-developer-list mailing list
> > List address:gimp-developer-list@gnome.org
> > List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> > List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
>
>
> --
> -
> Shlomi Fish   http://www.shlomifish.org/
> https://youtu.be/n6KAGqjdmsk - “Hurt Me Tomorrow”
>
> I hope that if it had not been clear before, it isn’t less clear now.
> — One of Shlomi Fish’s Technion Lecturers
>
> Please reply to list if it's a mailing list post - http://shlom.in/reply .
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp logo

[Shlomi Fish]

On Wed, 29 May 2019 08:20:28 +0100
C R via gimp-developer-list  wrote:

> I also made this vector one in svg format, if that suits better:
> https://www.dropbox.com/s/ouqyez32cer1veq/gimp_2.8_logo.svg?dl=1
> 
> -C
>

Thanks for sharing it. It looks great.
 
> On Wed, May 29, 2019 at 7:44 AM David  wrote:
> 
> > Hello,
> >
> > I'm looking for the Gimp logo for use in film credits.
> >
> > Where can I find it in high quality?
> >
> >
> > Regards,
> >
> > David Rylander,
> >
> > Sweden
> >
> > --
> > ***
> > David Rylander
> > Rylander animation
> > Bergsrådsvägen 102, bv
> > 12842 Bagarmossen
> >
> > tel: +46(0)708-461978
> > www.rylanderanimation.se
> > instagram: davidrylander
> > twitter: RylanderAnim
> > g+: rylle...@gmail.com
> > ***
> >
> > ___
> > gimp-developer-list mailing list
> > List address:gimp-developer-list@gnome.org
> > List membership:
> > https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> > List archives:   https://mail.gnome.org/archives/gimp-developer-list
> >  
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list



-- 
-
Shlomi Fish   http://www.shlomifish.org/
https://youtu.be/n6KAGqjdmsk - “Hurt Me Tomorrow”

I hope that if it had not been clear before, it isn’t less clear now.
— One of Shlomi Fish’s Technion Lecturers

Please reply to list if it's a mailing list post - http://shlom.in/reply .
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp logo

[Michael Natterer]

On Tue, 2019-05-28 at 14:41 +0200, David wrote:
> Hello,
> 
> I'm looking for the Gimp logo for use in film credits.
> 
> Where can I find it in high quality?

https://gitlab.gnome.org/GNOME/gimp/blob/master/icons/Color/scalable/gimp-wilber.svg

This is the current official logo. PLEASE don't use any of the
other suggestions.

Regards,
Mitch


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

Re: [Gimp-developer] Gimp logo

[C R via gimp-developer-list]

I also made this vector one in svg format, if that suits better:
https://www.dropbox.com/s/ouqyez32cer1veq/gimp_2.8_logo.svg?dl=1

-C

On Wed, May 29, 2019 at 7:44 AM David  wrote:

> Hello,
>
> I'm looking for the Gimp logo for use in film credits.
>
> Where can I find it in high quality?
>
>
> Regards,
>
> David Rylander,
>
> Sweden
>
> --
> ***
> David Rylander
> Rylander animation
> Bergsrådsvägen 102, bv
> 12842 Bagarmossen
>
> tel: +46(0)708-461978
> www.rylanderanimation.se
> instagram: davidrylander
> twitter: RylanderAnim
> g+: rylle...@gmail.com
> ***
>
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Gimp logo

[Owen]

If you dowload the source code, you will find it in;

./docs/Wilber_Construction_Kit.xcf.gz


A very large xcf file that will allow you to tailor your logo.





Owen


>
> I'm looking for the Gimp logo for use in film credits.
>
> Where can I find it in high quality?

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

Re: [Gimp-developer] GIMP in the textile industry: handling of indexed colors

[Simon Budig]

Hi all.

Please see my previous mail for more context of this problem.

So here we go about the handling of colors in indexed images:

In the current toolchain for the carpets the images are indexed, i.e.
instead of RGB data per pixel each pixel stores an index into a color
palette.

At the company it is important to have good tools to manipulate color
palettes and I think there definitely is room in GIMP for a plugin that
provides advanced control over the colors contained in a project
specific palette as well as tools to control names and order of the
color entries.

In GIMP color palettes are available and they also can carry names. But
while you can use these palettes to create indexed images, the indexed
image itself carries a "colormap" which does not provide named colors.
It would be necessary to extend the core to store names associated to
the indexed colors. A small sideproject then is to make sure that these
color names also end up in the final resulting image, one thought there
was to define and write a specific text chunk into a PNG file that
provides advanced information about the palette.

I personally think that this would be a welcome addtition to GIMP. It
also is a project that is not too huge and might be beneficial to other
usecases as well.

I'd welcome input on that topic.

Bye,
 Simon
-- 
  si...@budig.de  http://simon.budig.de/
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] [Gimp-docs] spyrogimp untranslated

[Marco Ciampa via gimp-developer-list]

On Wed, Apr 03, 2019 at 04:37:37AM -0400, Ell via gimp-developer-list wrote:
> 
> 
> On 4/3/19 2:04 AM, Marco Ciampa via gimp-developer-list wrote:
> > On Tue, Apr 02, 2019 at 05:51:14PM +0200, Marco Ciampa via gimp-docs-list 
> > wrote:
> >> Hi devs,
> >> for translating purpouses I use to compile GIMP from git.
> >> I do not see any translation strings for the spyrogimp plug-in and yet I 
> >> see it completely untranslated.
> >> What am I doing wrong here?
> >>
> > 
> > Sorry I was unclear, I meant the GIMP application, not the manual.
> > 
> > I was trying to update the translation of the manual when I realized that
> > the specific dialog window was completely untranslated, yet no strings
> > were untranslated or fuzzy in the app...
> > 
> > Presumably my fault but I have no clue on how to fix it...
> 
> Make sure to run intltool-update in the po-python/ directory -- that's
> where the spyrogimp translation lives.  It should all work normally.

Oh my... yes you are right, I always check also that dir but I missed it
this time and I was convinced it was a "plug-in" so checked only the
po-plugins dir ...

Thanks!

-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.



 GNU/Linux User #78271
 FSFE fellow #364



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

Re: [Gimp-developer] [Gimp-docs] spyrogimp untranslated

[Ell via gimp-developer-list]

On 4/3/19 2:04 AM, Marco Ciampa via gimp-developer-list wrote:
> On Tue, Apr 02, 2019 at 05:51:14PM +0200, Marco Ciampa via gimp-docs-list 
> wrote:
>> Hi devs,
>> for translating purpouses I use to compile GIMP from git.
>> I do not see any translation strings for the spyrogimp plug-in and yet I see 
>> it completely untranslated.
>> What am I doing wrong here?
>>
> 
> Sorry I was unclear, I meant the GIMP application, not the manual.
> 
> I was trying to update the translation of the manual when I realized that
> the specific dialog window was completely untranslated, yet no strings
> were untranslated or fuzzy in the app...
> 
> Presumably my fault but I have no clue on how to fix it...

Make sure to run intltool-update in the po-python/ directory -- that's
where the spyrogimp translation lives.  It should all work normally.

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

Re: [Gimp-developer] [Gimp-docs] spyrogimp untranslated

[Marco Ciampa via gimp-developer-list]

On Tue, Apr 02, 2019 at 05:51:14PM +0200, Marco Ciampa via gimp-docs-list wrote:
> Hi devs,
> for translating purpouses I use to compile GIMP from git.
> I do not see any translation strings for the spyrogimp plug-in and yet I see 
> it completely untranslated.
> What am I doing wrong here?
> 

Sorry I was unclear, I meant the GIMP application, not the manual.

I was trying to update the translation of the manual when I realized that
the specific dialog window was completely untranslated, yet no strings
were untranslated or fuzzy in the app...

Presumably my fault but I have no clue on how to fix it...

-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.



 GNU/Linux User #78271
 FSFE fellow #364



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

Re: [Gimp-developer] Gimp version 2.8.18

[Kolbjørn Stuestøl]

Yes, it is.
And easy to install too.
Kolbjørn

Den 26.03.2019 15:19, skreiv David DEPIERRE:

Hello,

Our PC scientists will migrate under Windows 10 and we are asked to contact the 
provider to find out if the software is compatible or not with Windows 10.
We have  GIMP version 2.8.18 and it is compatbile with Windows 10 or not?

thank you in advance
cordially


David DEPIERRE
Technicien R&D

  [cid:image003.png@01D28E6E.A825EC10]

MARKETING & SERVICES

Recherche Marketing & Services
Carburants Additifs Bitumes
Tel : +(33) 4 78 02 60 71
Email: david.depie...@total.com

TOTAL MARKETING SERVICES
24 cours Michelet.
92800 Puteaux -France

Centre de Recherche de Solaize
Chemin du Canal - BP 22
69360 Solaize - France


CONFIDENTIALITE. Ce courrier électronique (y compris ses éventuelles pièces 
jointes) peut contenir des informations susceptibles d'être confidentielles. Il 
ne peut être utilisé autrement que pour la finalité pour laquelle il a été 
envoyé. Au cas où il ne vous serait pas destiné, merci de le supprimer et d'en 
avertir immédiatement l'expéditeur.

CONFIDENTIALITY. This email (including any attachments) may containinformation 
which that be confidential. It may not be used other than for the purpose for 
which it has been sent. If you are not the intended recipient, please delete it 
and notify the sender immediately.



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




---
Denne e-posten har blitt sjekket for virus av antivirusprogramvare fra Avast
https://www.avast.com/antivirus

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

Re: [Gimp-developer] GIMP-2.99 "No rule to make target 'gimpoperationmaskcomponents.c'"

[Shlomi Fish]

On Sun, 17 Feb 2019 14:24:56 -0500
Elle Stone  wrote:

> When compiling GIMP-2.99 updated this morning, I got this error:
> 
> make[4]: *** No rule to make target 'gimpoperationmaskcomponents.c', 
> needed by 'gimpoperationmaskcomponents.o'.  Stop.
> make[4]: *** Waiting for unfinished jobs
> make[3]: *** [Makefile:984: all-recursive] Error 1
> make[2]: *** [Makefile:1266: all-recursive] Error 1
> make[1]: *** [Makefile:854: all-recursive] Error 1
> make: *** [Makefile:755: all] Error 2
> 
> In fact there doesn't seem to be "gimpoperationmaskcomponents.c", though 
> there is "gimpoperationmaskcomponents.cc".
> 
> Renaming the file and typing "make" to continue compiling results in a 
> bunch of other errors, and "make" doesn't finish.
> 

Hi Elle!

Try running "git clean -dxf" and then try a clean build.

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



-- 
-
Shlomi Fish   http://www.shlomifish.org/
List of Networking Clients - http://shlom.in/net-clients

Chuck Norris has 0 messages in his E-mail inbox. Including already read ones.
— http://www.shlomifish.org/humour/bits/facts/Chuck-Norris/

Please reply to list if it's a mailing list post - http://shlom.in/reply .
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] GIMP-2.99 "No rule to make target 'gimpoperationmaskcomponents.c'"

[Elle Stone]

On 2/17/19 2:46 PM, Ell via gimp-developer-list wrote:



On 2/17/19 2:24 PM, Elle Stone wrote:

When compiling GIMP-2.99 updated this morning, I got this error:

make[4]: *** No rule to make target 'gimpoperationmaskcomponents.c',
needed by 'gimpoperationmaskcomponents.o'.  Stop.
make[4]: *** Waiting for unfinished jobs
make[3]: *** [Makefile:984: all-recursive] Error 1
make[2]: *** [Makefile:1266: all-recursive] Error 1
make[1]: *** [Makefile:854: all-recursive] Error 1
make: *** [Makefile:755: all] Error 2



This happens each time we convert a C file to C++.  Since both the old
.c and new .cc files compile into the same .o file, autofoo is too dumb
to smoothly handle that for an existing build.  You need to either do
fresh build, or, in your build directory, edit
app/operations/.deps/gimpoperationmaskcomponents.Po, and change
"gimpoperationmaskcomponents.c" to "gimpoperationmaskcomponents.cc", on
the first or second line.

--
Ell


Ell, thanks! compiling from scratch worked.

Best,
Elle
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list