Re: [Gimp-developer] error help

2021-11-13 Thread Alexandre Prokoudine via gimp-developer-list
Hi Jane,

Screenshots as attaches don't work in this mailing list. Please upload to
e.g.  imgur.com.

Alex

сб, 13 нояб. 2021 г., 11:49 Jane Smith :

> I received the following message while installing GIMP.  I 'tried again' to
> no avail so used the skip (not recommended) option.
>
> Will there be a glitch in using or is there a fix you can offer?
>
>
>
> Thank you in advance for your time.
>
>
>
> Jane B Smith
>
>
>
>
>
> ___
> 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] Need help for the macOS package?

2021-10-10 Thread Alexandre Prokoudine via gimp-developer-list
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 :)

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] Downloading GIMP on my iMac

2021-08-17 Thread Alexandre Prokoudine via gimp-developer-list
Hi,

All attachments are stripped from emails, so we don't know what
message you got. Please elaborate?

Alex

On Tue, Aug 17, 2021 at 11:29 AM Curt Kimmel via gimp-developer-list
 wrote:
>
> I have an iMac which has just been updated to Big Sur. I attempted to
> download your GIMP program but received a message that it could not be
> done. How can I download your program?[image: GIMP_-_Downloads.jpg]
>
> Curt
> ___
> 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 development process

2021-06-02 Thread 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] Information request.

2021-05-25 Thread Alexandre Prokoudine via gimp-developer-list
On Tue, May 25, 2021 at 11:30 AM OOrtiz@certitude.london
 wrote:
>
> Hi Development Team,
>
> I will be installing the application on some of our machines and would like 
> to know more about the application. If possible, could you please answer the 
> following:
>
>
> 1.Does the software require admin rights? If yes please instruct reasons for 
> admin rights

You can install it without admin rights, if my memory serves me well.

> 2.Can we have source files of the software (Installation files )

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

> 3. Is there any instructions or documentation how to support his application ?

There is an online user manual. There are tons of videos on YouTube.
There are paid-for courses on various platforms such as Udemy. Please
elaborate.

> 4.Does it require any special ports towards network config behind firewalls?

GIMP does three things with network (that I recall):

1. It can access any remote file storage that you configured in your
system, like a corporate network file server.
2. If the user manual isn't installed locally, GIMP will prompt the
user to open the online version from within its own user interface.
3. Every time (not sure about every time though) GIMP starts, it
queries gimp.org for the number of the latest version available, and
if there's a new release, it will tell you so. You can disable this
feature in preferences on per-user basis.

So I'm guessing you need to have 443 port open for HTTPS requests.

> 5.Does the software use any authentication ?

None whatsoever.

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-2.10 and GIMP2.99 are still sRGB-only image editors

2021-02-04 Thread 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] deriving transform by comparing image before/after edit

2020-12-27 Thread Alexandre Prokoudine via gimp-developer-list
Hi Bill,

I don't know of plugins that would calculate a matrix in GIMP. There's
a plugin called GetCurves by Elsamuko [1] that calculates a rough
approximation of a color transform between two layers and creates an
RGB curves preset.

Due to its nature, the plugin has obvious issues treating different
hue ranges differently [2] but maybe it's a motivation for someone to
come up with a better tool. Although I'd be damned if I knew how you
would then apply a generated 3x3 matrix to a different image :)

I recently looked at free/libre options to create 3D LUT files, and
the existing options like Harlequin [3] are not very encouraging yet.

[1] 
https://github.com/elsamuko/gimp-elsamuko/tree/master/plugins/elsamuko-get-curves
[2] https://twitter.com/lgworld/status/1338597821881192448
[3] https://github.com/dunkyp/harlequin/

Alex

On Sun, Dec 27, 2020 at 2:47 PM Bill Ross via gimp-developer-list
 wrote:
>
> Given a pair of before/after jpeg photos edited with global-effect
> commands (vs. operations on selected areas), is it possible to derive
> transformation matrix/matrices that reproduce the result from the
> original? Presumably by iterating over all the pixels in a 1:1 mapping.
>
> My hope is to train neural nets to predict the matrix operation(s)
> required. Example:
>
> http://phobrain.com/pr/home/gallery/pair_vert_manual_9_2845x2.jpg
>
> Thanks,
>
> Bill
>
>
> --
> 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] Touchpad gestures for zooming

2020-12-02 Thread Alexandre Prokoudine via gimp-developer-list
On Wed, Dec 2, 2020 at 1:55 AM Povilas Kanapickas wrote:
>
> Hello,
>
> I would like to implement touchpad gesture support in GIMP. Perhaps the
> most useful use case is the ability to do pinch gesture to zoom the
> currently opened image in and out. I would like to focus on just this
> use case initially.
>
> Is this something the team sees as an useful feature?

Hello!

Yes, Jehan Pages experimented with that a few years back but switched
to other tasks. So that would be a very much welcome feature :)

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] Bug

2020-11-27 Thread Alexandre Prokoudine via gimp-developer-list
On Fri, Nov 27, 2020 at 6:44 PM Gregory Reshetniak wrote:

> No Alex, every communication channel reposting GIMP news is full of your
> comments like "piss off or make pull requests" and it's ing tiresome to
> be observing for years on end.
> You want to be a spokesperson? Well then behave like one.
>

I'm not sure what caused this continuous urge to look for offense where no
offense was meant, and I'd rather not speculate. But I'm afraid I have to
point out that you are balancing right on the edge of violating our code
of conduct: https://www.gimp.org/mail_lists.html#code-of-conduct

Please adhere to it.

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] Bug

2020-11-27 Thread Alexandre Prokoudine via gimp-developer-list
On Fri, Nov 27, 2020 at 6:28 PM Gregory Reshetniak wrote:

> "Dear Albert Einstein, unfortunately there hasn't been a MacOS expert to
> help us fix the release process yet. Hopefully someone will appear soon -
> we'd really want to continue releasing for Macs again. Perhaps you might
> help us with it? Here are the tasks that need to be done
> https://gitlab.gnome.org/GNOME/gimp/-/issues/4504;
>
> See Alex, it's possible to reply to completely innocent questions without
> full force of your passive aggressive ego scaring away users and even
> possible contributors. Try it, we believe in you.
>

You replied with aggression to a short, concise reply that implied no
aggression whatsoever, passive or otherwise.

Do I need to point out that this sort of behavior is not appreciated here?

Please do not do that again. Thank you.

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] Bug

2020-11-27 Thread Alexandre Prokoudine via gimp-developer-list
On Fri, Nov 27, 2020 at 4:27 PM Albert Einstein via
gimp-developer-list  wrote:
>
> Are there any news about the release of the new and fixed version for MacOS ?

There will be once someone joins the team to work on macOS builds.

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] GIMP is 25 yo

2020-11-21 Thread 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


Re: [Gimp-developer] how should I read this string (translation related)

2020-11-09 Thread Alexandre Prokoudine via gimp-developer-list
Precision refers to 8-bit per channel, 16-bit per channel, 32-bit per channel.

Images can be converted between e.g. 8-bit and 32-bit. That's the
precision conversion.

Alex

On Mon, Nov 9, 2020 at 5:20 PM Cristian Secară  wrote:
>
>  about this string:
>
> #. Convert Precision Dialog
> #: ../app/dialogs/preferences-dialog.c:2264
> msgid "Precision Conversion Dialog"
>
> 1. The precision degree of a conversion
> or
> 2. The conversion of a precision factor
>
> ??
>
> Cristi
>
> --
> Cristian Secară
> https://www.secarica.ro
> ___
> 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] where can I see this string in action (translation related)

2020-10-15 Thread Alexandre Prokoudine via gimp-developer-list
On Thu, Oct 15, 2020 at 2:13 PM Cristian Secară  wrote:
>
> În data de Thu, 15 Oct 2020 13:48:31 +0300, Alexandre Prokoudine a scris:
>
> > TIFF exporting, I think
> >
> > > Where or how can I see this string in action:
> > >
> > > #: ../libgimp/gimpexport.c:444
> > > msgid "%s plug-in needs to crop the layers to the image bounds"
> > >
>
> Not quite: the TIFF export dialog has another sting
>
> #: ../plug-ins/ui/plug-in-file-tiff.ui.h:2
> msgid "Cr_op layers to image bounds"

I'm not sure if it really matters. The translation is straightforward,
and the %s variable is just the name of the file plugin like TIFF or
PNG or whatever.

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] where can I see this string in action (translation related)

2020-10-15 Thread Alexandre Prokoudine via gimp-developer-list
TIFF exporting, I think

чт, 15 окт. 2020 г., 13:37 Cristian Secară :

> Where or how can I see this string in action:
>
> #: ../libgimp/gimpexport.c:444
> #, c-format
> msgid "%s plug-in needs to crop the layers to the image bounds"
>
> ?
>
> --
> Cristian Secară
> https://www.secarica.ro
> ___
> 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] how should I read this string (translation related)

2020-10-10 Thread Alexandre Prokoudine via gimp-developer-list
1

сб, 10 окт. 2020 г., 21:14 Cristian Secară :

>  about this string:
>
> #: ../app/widgets/gimpcontrollerinfo.c:119
> msgid "Debug events"
>
> 1. debug [the] events
> or
> 2. view the events of a debugging action (or when debugging something)
>
> ??
>
> --
> Cristian Secară
> https://www.secarica.ro
> ___
> 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] Offering help

2020-10-09 Thread Alexandre Prokoudine via gimp-developer-list
Hello Vrok!

Our onboarding procedure could do with some improvement indeed :)

I guess the first step would be building GIMP from source code. We
typically do it n Linux with Mingw, but I know there's some work going
on to try doing this with MSYS2. At least that's my impression from
quick glances on our IRC channel.

As for actual development, we usually recommend accomplishing a simple
task that really excites you, something you want to see fixed in GIMP.
If all else fails, there's a 'Newcomers' label for issues that are
simple enough to get started contributing:

https://gitlab.gnome.org/GNOME/gimp/-/issues?label_name%5B%5D=4.+Newcomers

Please don't hesitate asking questions :)

Alex

On Fri, Oct 9, 2020 at 1:26 PM Tan Vrok Fei via gimp-developer-list
 wrote:
>
> Hello,
>
> I’m Vrok, and I would like to help out with developing and introducing new 
> features to GIMP. However, I don’t know where to start.
>
> Any guidance on where to begin is welcome. Thank you.
>
> Regards,
> Vrok
>
> Sent from Mail for Windows 10
>
> ___
> 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] [ANNOUNCE] GIMP 2.10.22

2020-10-08 Thread Alexandre Prokoudine via gimp-developer-list
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

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-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] VPAT request

2020-09-04 Thread Alexandre Prokoudine via gimp-developer-list
https://www.gimp.org/about/ITI-VPAT.pdf

On Fri, Sep 4, 2020 at 6:18 PM Godswill Peter via gimp-developer-list
 wrote:
>
> Good afternoon;
>
> My name is Godswill Peter and I work for the Texas A University
> Engineering and Experiment Station as a student assistant, I hope this
> email finds you well. I am emailing you to request the VPAT for your
> software (GIMP 2.10.20 (Latest) version), as it is required that all
> software we use here at Texas A University has their own VPAT. Please get
> back to me as soon as possible.
>
>
>
> Cheers,
>
> Godswill Peter
>
> Student Assistant
>
> Texas A University Engineering and Experiment Station
>
> Suite 102
> ___
> 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] Dog-bone

2020-08-19 Thread Alexandre Prokoudine via gimp-developer-list
Hello,

This is GIMP's devel list, not Inkscape's :)

Anyway,
https://gitlab.com/inkscape/inkscape/-/blob/master/src/live_effects/lpe-fillet-chamfer.cpp

Alex

ср, 19 авг. 2020 г., 11:04 John Tapsell via gimp-developer-list <
gimp-developer-list@gnome.org>:

> I love the path effects, and there's a particularly useful path effect that
> I use all the time:
>
> Corners (Fillet/Chamfer)
>
> I'd love for it to have one extra feature - a dog-bone effect.  This is
> essential when laser cutting slots in acrylic, because acrylic doesn't like
> sharp 90 degree corners.
>
> Also for wood CNC, when you literally can't cut a 90 degree corner:
>
> https://fablab.ruc.dk/content/images/2017/03/dogbones.jpg
>
> I'm happy to code this myself, but I want to check:
>
> 1. Where is the code for this?  Are these in the main git repo?
> 2. Would a contribution for this feature be accepted? (Assuming sufficient
> code quality of course)
>
> Thank you,
>
> John
> ___
> 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] Suggestd enhancement

2020-07-24 Thread Alexandre Prokoudine via gimp-developer-list
On Fri, Jul 24, 2020 at 12:53 PM Ofnuts wrote:

> I would also recommend Klipper, but the version in my Kubuntu 19.10
> (5.16.5) makes Gimp crash when it copies image to the clipboard (if I
> set Klipper to watch for images).

It happens with pretty much any clipboard manager running on Linux.
Annoys the hell out of quite a few people out there, I'm told. We have
a bug report for that, but no fixes whatsoever.

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] [ANNOUNCE] GIMP 2.10.20, babl 0.1.78, GEGL 0.4.24

2020-06-11 Thread Alexandre Prokoudine via gimp-developer-list
Hello,

We've just released GIMP 2.10.20 with usability improvements, new
features, and bug fixes. Just like always, the release is accompanied
by new releases of babl and GEGL libraries.

Here's release notes with screenshots and whatnot :)

https://www.gimp.org/news/2020/06/11/gimp-2-10-20-released/

For a full list of changes, please see the respective NEWS files.

https://gitlab.gnome.org/GNOME/gimp/-/blob/master/NEWS
https://gitlab.gnome.org/GNOME/babl/-/blob/master/NEWS
https://gitlab.gnome.org/GNOME/gegl/-/blob/master/docs/NEWS.txt

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] Interview with Ell

2020-05-04 Thread Alexandre Prokoudine via gimp-developer-list
Hello,

A few days ago, I published an interview with Ell, one of the most
active GIMP developers. We talked about things like beginning to
contribute to a software project like GIMP, i.e. old large codebase,
and also about some of his further plans for the project.

Enjoy :)

http://libregraphicsworld.org/blog/entry/you-d-have-to-be-crazy-to-rewrite-gimp-in-anything-interview-with-ell

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] file permission issue

2020-04-27 Thread Alexandre Prokoudine via gimp-developer-list
On Tue, Apr 28, 2020 at 3:08 AM Scott Goldie via gimp-developer-list wrote:

> I have a laptop called Apple MacBook Pro with os is Catalina.
> Anyway, I download this GIMP 2.10.18 and It’s a appears to be a problem
> with file permission issue.  My question is Are you guys are going to fix it 
> soon?

You mean Catalina asks you to grant GIMP permission to access folders?
That's not an issue. This is how Catalina works, nothing to fix on our
end. This is your life now :)

https://nektony.com/duplicate-finder-free/folders-permission

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] Latest version 2.10

2020-04-07 Thread Alexandre Prokoudine via gimp-developer-list
On Wed, Apr 8, 2020 at 12:22 AM Tom D via gimp-developer-list wrote:
>
> I have been an avid user of version 2.8 for a long time. I tried 2.10
> but quickly switched back to 2.8.  The new version doesn't have the
> color tool icons 2.8 does.  Plus the display is all gray, including
> the icons, making them harder to distinguish. I could not find any
> option to change these colors.  The tool icons in 2.8 are easier to
> see and the white display provides better contrast.  Perhaps there
> could be a "use prior interface" option of some type.

There is.

Edit > Preferences > Interface > Theme (System) / Icon Theme (Legacy).

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] GEGL-OpenCL

2020-04-01 Thread Alexandre Prokoudine via gimp-developer-list
On Wed, Apr 1, 2020 at 4:18 AM Massimo Fidanza wrote:
>
> Hi,
>
> I found this repository https://github.com/OpenCL/GEGL-OpenCL on GitHub
> which is sadly stopped in May 2017. Can I ask if this code has ever been
> merged?

Yes, you can, and yes, it was merged :)

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] 30 days ago ...

2020-03-22 Thread Alexandre Prokoudine via gimp-developer-list
вс, 22 мар. 2020 г., 10:34 Maurizio Loreti via gimp-developer-list <
gimp-developer-list@gnome.org>:

> 30 days ago GIMP 2.10.18 has been released for GNU/Linux and Windows. And,
> after a whole month, has not been released for MacOS, a platform used by
> several professional photographers, and where 2.10.14 only is available for
> download.
>
> I would like to know if there are still plans to support MacOS, and when
> the MacOS distribution will be available.
>

Please do not rush to conclusions. Our macOS packager has been sick.

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] Naive/Native

2020-03-07 Thread Alexandre Prokoudine via gimp-developer-list
On Sat, Mar 7, 2020 at 1:20 PM Rodrigo Lledó Milanca via
gimp-developer-list  wrote:

> Hello,
>
> I'm trying to translate GIMP into spanish. This string caught my attention:
>
> GIMP 2.10.18 fixes some critical bugs, introduces naive support for
> CMYK PSD files,
> and adds a higher-contrast variation of the symbolic icon theme.
>
> Did you mean native support?


Nope

or it's more like an
> early/unpolished/primitive support?
>

Yep :)

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] GIMP 2.10.18 released

2020-02-24 Thread Alexandre Prokoudine via gimp-developer-list
Hello,

A new version of GIMP is out. Release highlights:

- Tools are now grouped in the toolbox by default
- Sliders now use a compact style with improved user interaction
- Dockable areas now highlighted when a dockable dialog is being dragged
- Vastly improved user experience for the transformation preview
- New 3D Transform tool to rotate and pan items
- Much smoother brush outline preview motion on the canvas
- Symmetry painting enhancements
- Faster loading of ABR brushes
- PSD support improvements
- Consolidated user interface for merging down and anchoring layers
- Update check to notify users of new releases available

For more information, please see
https://www.gimp.org/news/2020/02/24/gimp-2-10-18-released/.

Flatpak and the build for macOS are late arrivals and will be
announced separately.

Best regards,
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] gimpfu port to Gimp 3

2020-01-11 Thread Alexandre Prokoudine via gimp-developer-list
On Sat, Jan 11, 2020 at 1:55 PM Lloyd Konneker via gimp-developer-list wrote:
>
> Alexandre: Yes, that code, in master (2.99, the “dev” branch for Gimp 3)
>
> In that branch, the Makefile.am has commented out the pygimp sub directory,
> and the meson script does not subdir the pygimp directory (doesn’t try to 
> build it.)
>
> So an onlooker like myself wonders whether it is abandoned, or just waiting 
> for someone to work on it.
> Maybe there was a prior discussion about it, maybe a private discussion?

Around autumn 2019, GIMP in the master branch was ported to use
GObject introspection (https://gi.readthedocs.io/en/latest/) and
Python 3 (Lua and JavaScript plugins also possible now). My
understanding from talking to Jehan is that he ported some of the
existing plug-ins to Python 3 and moved them to
https://gitlab.gnome.org/GNOME/gimp/tree/master/plug-ins/python. The
rest was disabled from building/installing. According to Jehan, Elad
looked into other Python plugins and found out only two of them make
sense to be ported (I don't know which ones exactly, Elad will
probably elaborate).

Of course, there are also 3rd party Python plugins like the one you
ship with Resynthesizer.

I hope things are a bit clearer now :)

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] gimpfu port to Gimp 3

2020-01-10 Thread Alexandre Prokoudine via gimp-developer-list
On Fri, Jan 3, 2020 at 5:09 PM Lloyd Konneker via gimp-developer-list wrote:
>
> I started porting gimpfu.py to Gimp 3, Python 3.
>
> Is there any reason not to?  Am I duplicating effort?

Hello Lloyd!

Are you talking about the contents of
https://gitlab.gnome.org/GNOME/gimp/tree/master/plug-ins/pygimp?

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] New asset / extension manager

2020-01-08 Thread Alexandre Prokoudine via gimp-developer-list
On Wed, Jan 8, 2020 at 7:17 PM Michal Vašut wrote:

>
> By priority I meant that Gimp team is pushing new features (that don't look
> like prerequisites for that manager)


Over the years, I've heard a lot of interesting ideas that suggest that
GIMP team members can replace each other or work on each other's tasks.

You seem to be under the same kind of impression. Perhaps we should
communicate our roles and interests better.

- Mitch knows GIMP in and out, can hack both back-end and front-end code,
but currently focuses on refactoring, all things color management, and
reviewing patches coming from other people.

- Jehan has a wide range of interests mostly stemming from stuff his wife
needs for their animation project. He does both back-end and front-end work
related to painting and animation. But since plugins management is pain,
that's also among things he wants to improve. While he has a long history
of fixing bugs, he mostly works on new features.

- Ell focuses on performance and new features that involve interaction on
the canvas. He understands the back-end very well and contributes to GEGL
as well.

- Pippin has a comparatively light footprint in GIMP's source code, GEGL
and babl are the libraries where his contributions mostly go. Hence his
work directly affects how GIMP pushes pixels around and whether pixels get
pushed where they ought to be.

- Thomas Manni works mostly on GEGL operations and also has a light
footprint in GIMP's code. But his work helps GIMP provide sensible, useful,
and fast filters for end-users.

That's 5 top contributors in terms of code. Every one of them has his own
interests and specialization — an area where they shine.

There are more contributors, like Massimo and Elle. Maybe they are supposed
to work towards plugin management. Well, nope. Let me tell you about them.

Massimo is a prolific contributor of small sane patches that apply cleanly
and work very well. He mastered this art, and we treasure him for sticking
around and doing just that. We'd never expect him to do some massive work
involving redesigning GIMP, because, as far as I can tell, he's not exactly
interested in big stuff.

Elle is amazing at what she understands very well — color science. Color
space converison, LAB/xyY/etc. spaces support in the color picker and
sample points — that's the kind of work she does.

So when you are looking at Ell adding a 3D Transform tool or Thomas adding
a new GEGL filter, or Elle adding Yu'v' (CIE 1976 UCS) support to GIMP
color picker, please do not expect them to drop everything and start
hacking on something that is out of scope of their interest. This is not
how it works.

I hoped I cleared this up a little. If you have more questions, shoot :)

P.S. You did not say anything of the kind, but since this is related and
still preying on my mind, to everyone who thinks contributors should have
worked on CMYK support or non-destructive image editing instead of
designing the greyscale icon theme I'll just say this: P :)

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] 2019 project report

2020-01-05 Thread Alexandre Prokoudine via gimp-developer-list
On Sun, Jan 5, 2020 at 7:22 PM Christopher Curtis wrote:

> In that thread from 2012 I proposed a 3-month release cycle. This is, and was,
> a slightly slower pace than that used by the Linux kernel. The number is 
> arbitrary
> but I still think the results will be worthwhile. With 3 releases in 2019, a 
> 4-month
> process may be a good place to start.

Personally, I can see this happening for the stable series, i.e. what
is now the 2.10.x branch. Our build process is now more or less
automated for flatpak (Linux) and dmg (macOS), and we think we can do
that for WIndows eventually. That simplifies quite a lot of work,
although the last few Win/Mac updates required manual intervention. In
fact, we recently put two updated Windows installers — one because of
an important fix in GEGL, and one because of a fix for a broken 3rd
party component.

As for the release frequency, we try to make a release around LGM
time, which is usually April-May, we did 2.10.6 and 2.10.12 in the
summer time, and we did 2.10.8 and 2.10.14 in late autumn before the
Xmas madness. That already sounds like a plan.

That said, I don't think it's entirely possible for the unstable
branch. Mitch keeps uncovering bad code all the time, and once you
start pulling a funny-smelling rope, there's always a chance there's a
rotting corpse on the other end of it, if you pardon my analogy :)

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] 2019 project report

2020-01-05 Thread Alexandre Prokoudine via gimp-developer-list
Hello,

Our annual GIMP/GEGL report is out:

https://www.gimp.org/news/2020/01/04/gimp-and-gegl-in-2019/

Enjoy :)

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] About N-Point Deformation.

2019-12-18 Thread Alexandre Prokoudine via gimp-developer-list
Hi Mario,

I'm sorry to say that, but this tool is more or less abandoned and
waiting for someone to pick it up and clean it up and complete it.

Until then, it won't get any better than what you experience.

Alex

On Wed, Dec 18, 2019 at 2:44 PM Mario Mey via gimp-developer-list
 wrote:
>
> [UPDATE]
>
> I tried several (not all) commits of GIMP and tested N-Point Deformation
> tool. As I said before, about half of commits, this tool works very slow.
> The other half, it crashes GIMP.
>
> QUESTION: Can I upload GIMP with flatpak to a version previous to the last
> in the commit list? It is from 2018-10-27.
>
> Note: I'm on Debian 9 and the last version I tried (crash) is from
> 2019-10-30. I also have another partition with Debian 10 with last version,
> but I didn't test this tool there. If the tool crashes or not in actual
> version is another issue. If it does, I'll report the bug, but for the
> moment, I only need a version where I can use this tool fast and it doesn't
> crash!
>
> El mar., 17 dic. 2019 a las 10:10, Mario Mey ()
> escribió:
>
> > Hello there. I need to run GIMP in Debian 9 and I need N-Point Deformation
> > tool. I installed from flatpak 2.10.14, but that tool crashes GIMP. So, I
> > installed an old version, 2.10.0 RC2 (48MB flatpak file, from
> > https://download.gimp.org/mirror/pub/gimp/v2.10/linux/). It works... but
> > I saw that is an old version... and I don't really trust in this
> > installation.
> >
> > Then, I learnt how to install a commit with flatpak. I tried to install a
> > version from 2019/Jan. And it works... but N-Point Def tool works veeerryyy
> > sloooww
> >
> > Does anybody knows if that tool is working well in a particular commit? I
> > don't want to try eeeverryy commit.
> >
> > This is the list of commits:
> >
> > $ flatpak remote-info --log flathub org.gimp.GIMP
> > GNU Image Manipulation Program - Create images and
> > edit photographsID: org.gimp.GIMP
> >Ref:
> > app/org.gimp.GIMP/x86_64/stable
> > Arch: x86_64
> > Branch: stable
> >  Version: 2.10.14
> >
> >License: GPL-3.0+ AND LGPL-3.0+
> >   Collection: org.flathub.Stable
> >   Download: 108.9 MB
> >
> > Installed: 308.1 MB
> >  Runtime: org.gnome.Platform/x86_64/3.32
> >
> >Sdk: org.gnome.Sdk/x86_64/3.32
> > Commit:
> > 8003d469b2224a1abe54b45793c9692e822cacee860d94861f5fc5e43111a689
> > Parent:
> > 3fdfdf0963ba67629f287092229d9f5659bc9a2eeb1158c060b09d8a603acbcf
> >Subject: Fix CPU detection on GEGL build. (3b047adf)
> >   Date: 2019-10-30 00:56:11 +
> >History:
> >
> > Commit:
> > 3fdfdf0963ba67629f287092229d9f5659bc9a2eeb1158c060b09d8a603acbcf
> >Subject: Fix typo! (a752f7df)
> >   Date: 2019-09-02 20:28:05 +
> >
> > Commit:
> > 798d8cd8a6a2ccf1bf21c0f5e9749dd4d97ecd511a3af1922d6fedf6c26e3a7c
> >Subject: Release GIMP 2.10.12! (1366fa63)
> >   Date: 2019-06-13 02:25:52 +
> >
> > Commit:
> > 451758521226112dd7d4e2c4ce7fadaa93f69ce58c2f1afb70fb057db81f5e57
> >Subject: Update to GEGL 0.4.16. (1d8cb1dd)
> >   Date: 2019-05-09 05:02:52 +
> >
> > Commit:
> > 5c8a3dc204a12d4695c5bb7e98ea3b3862d78e52c1cf0f9b021c1dae836ecc95
> >Subject: Build GTK+2 with more patches. (d7578706)
> >   Date: 2019-04-25 16:46:42 +
> >
> > Commit:
> > fdbcfcbb8e5a4a6f484674208c6bbdf96c6e37fe2df21983a444069e5949276f
> >Subject: Release GIMP 2.10.10! (781c0f7c)
> >   Date: 2019-04-07 21:40:06 +
> >
> > Commit:
> > 81dc4a6595d81ef6fe7b563dc046cf6dec2856a9628c1b8ff3178bf0547e6490
> >Subject: Update some dependencies. (8cef7f17)
> >   Date: 2019-04-04 18:14:23 +
> >
> > Commit:
> > d0d12223774157ce64690d7096624741bdadc9490ac730ee2aa752eabf2ce0b1
> >Subject: Downgrade ibus from shared-modules (d5d82037)
> >   Date: 2019-04-03 20:07:35 +
> >
> > Commit:
> > 1c130cbfaec924ee87a98f541b451f8e527599b2efda3add51cb0f57b3806ac5
> >Subject: Add "org.freedesktop.FileManager1" bus access. (bbf1f104)
> >   Date: 2019-01-08 19:51:49 +
> >
> > Commit:
> > 1fcb2c783cf61e22ca6ed03df9f95d59785d5cbd668b50f9765693956f1eedeb
> >Subject: Update babl dependency. (e7b662db)
> >   Date: 2018-11-16 22:41:23 +
> >
> > Commit:
> > b6186ed16c732603f5c317bbc42717e500c0077251f9e8035a3266924b9cd55b
> >Subject: Release GIMP 2.10.8. (34b1d53c)
> >   Date: 2018-11-09 13:49:13 +
> >
> > Commit:
> > 0edfacfb334969b2fd5dc8d02cb1f0a5a98a833b24fdc6bb25ba3fb042df08a9
> >Subject: Update babl and GEGL. (efaecfbb)
> >   Date: 2018-10-27 23:52:37 +
> >
> > Thanks everyone.
> >
> ___
> 

Re: [Gimp-developer] Participation to GameDev room at FOSDEM

2019-11-30 Thread Alexandre Prokoudine via gimp-developer-list
Hello Julian!

It took a while to ask everyone, sorry about that :)

Unfortunately, none of us is going to be at FOSDEM in 2020.

However, we are up for a meeting in late May during Libre Graphics
Meeting, in Rennes, France:

https://libregraphicsmeeting.org/2020/en/index.html

How does it sound for you?

Alex

On Mon, Nov 25, 2019 at 4:14 PM Julian Murgia  wrote:
>
>  Hello,
>
> First of all I'm sorry if this was not the right place to send this email,
> even though I believe it is addressed mostly to GIMP developers.
>
> I am a member of Godot Engine's organization team for FOSDEM. We have been
> granted with a "Game Developers" room at FOSDEM, taking place in Brussels,
> Belgium, on February 1st and 2nd 2020.
> Even though we proposed this developers room, it will be about "*Free and
> Open Source Game Development"* at large and not focused on Godot Engine.
>
> Thus, we are calling for participations aimed at Free Softwares projects,
> involved closely or less closely in game development. These participations
> would consist in technical-oriented presentations during the GameDev room:
> game developers, game engine developers, tools developers are very welcome.
>
> GIMP is the most used image processing Free Software for almost all usages.
> Our lead developer Juan Linietsky presented a nice tutorial for creating
> graphics and textures using GIMP last year during our Godot Engine annual
> convention (
> https://www.youtube.com/watch?v=wrGLIt322jM=PLeG_dAglpVo5XPsWqBiXXg6wvee11yDeS).
> GIMP is one mandatory tool in game developers toolbox. We'd also be happy
> to discuss your plans and your needs for GIMP development, and discuss
> assets workflow and integration into game and game engines.
>
> You'll find some details on our past news post:
> https://godotengine.org/article/cfp-game-development-room-fosdem-2020. If
> you wish, you can of course respond to this mail for more precisions before
> applying on FOSDEM's Pentabarf.
>
> Waiting for your reply,
>
> Best regards,
> Julian Murgia - Godot Engine
> ___
> 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 Workshop, Denmark 2020, GG Festival

2019-11-06 Thread 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] How do I register for https://gitlab.gnome.org/GNOME/gimp/issues?label_name%5B%5D=OS%3A+Linux

2019-10-22 Thread Alexandre Prokoudine via gimp-developer-list
Hello Adlabert,

You can add this URL to your RSS feed:

https://gitlab.gnome.org/GNOME/gimp/issues.atom?feed_token=PypNNB512dsgs3NBA7BJ_name%5B%5D=OS%3A+Linux=opened

Alex

On Tue, Oct 22, 2019 at 2:08 PM Adalbert Hanßen  wrote:
>
> I have a bug report for Gimp which I want to post to 
> https://gitlab.gnome.org/GNOME/gimp/issues?label_name%5B%5D=OS%3A+Linux. 
> Apparently I have to sign in into https://gitlab.gnome.org/users/sign_in 
> since this forum uses the same log in as several others.
>
> However I don't understand how to first register for this forum. I have no 
> idea what the terms LDAP means.  I stumbled about $userid on the explanatory 
> page
>
> https://wiki.gnome.org/AccountsTeam/RetrieveYourGNOMEAccountPassword
>
> I tried the shown ssh command, but that returned me just the usage of ssh. 
> echo $userid returned just an empty line. probably something which I do not 
> know has to be substituted for it. But what the hell is sit?
>
> Kind regards
>
> Adalbert Hanßen
>
> ___
> 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] New Features: full screen crosshair pointer , customizable window/toolbar-dialog

2019-10-08 Thread Alexandre Prokoudine via gimp-developer-list
Is this a feature request? :)

Alex

вт, 8 окт. 2019 г., 20:56 Anonymousemail via gimp-developer-list <
gimp-developer-list@gnome.org>:

>
> 2 New Features
>
>
> 1) Full screen crosshair mouse pointer
>
> - additional feature full screen crosshair, working like on
> Metatrader 4 trading platform extending lines up to edges (rulers)
>
> - Option for switch mouse pointers settings directly from right mouse
> click menu View on a sub-menu, and/or key shortcut
>
> - Full screen crosshair lines selectable color: black, middle gray,
> automatic or segmented (auto select color for make it more visible
> depending on background image colors), customizable color value
>
> - Setting option for change pointers from center mouse click and/or space
> bar or other key
>
>
> 2) Additional Customizable toolbox/dialog window with custom added icons,
> where user can add standard filters/settings from menus and also
> preferences, using drag and drop or other method for add/replicate wanted
> feature to new custom icon bar that work similar to shortcut
>
> 
> ___
> 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] (no subject)

2019-08-27 Thread Alexandre Prokoudine via gimp-developer-list
On Tue, Aug 27, 2019 at 11:34 AM Bekzod Kobilov via gimp-developer-list wrote:
>
> Hi GIMP Team,
>
> I am going through the documentation of GIMP to find out if any software
> components or sub-components (libraries, source codes, any extensions) from
> third parties are used in GIMP? Or are all of the source code solely
> written by developer team? I have looked for the type of diagram that gives
> an overview of GIMP's software architechture in GIMP documentation, but i
> could not find one. Thanks in advance.

$ apt-cache show gimp | grep Depends
Depends: libgimp2.0 (>= 2.10.8), libgimp2.0 (<= 2.10.8-z), gimp-data
(>= 2.10.8), gimp-data (<= 2.10.8-z), libgdk-pixbuf2.0-0 (>= 2.30.8),
xdg-utils, libaa1 (>= 1.4p5), libbabl-0.1-0 (>= 0.1.10), libbz2-1.0,
libc6 (>= 2.27), libcairo2 (>= 1.12.2), libfontconfig1 (>= 2.12.6),
libfreetype6 (>= 2.2.1), libgcc1 (>= 1:3.0), libgegl-0.4-0 (>=
0.4.12), libgexiv2-2 (>= 0.10.6), libglib2.0-0 (>= 2.54.2), libgs9 (>=
8.61.dfsg.1), libgtk2.0-0 (>= 2.24.10), libgudev-1.0-0 (>= 167),
libharfbuzz0b (>= 0.6.0), libheif1 (>= 1.1.0), libilmbase23 (>=
2.2.0), libjpeg8 (>= 8c), liblcms2-2 (>= 2.9), liblzma5 (>=
5.1.1alpha+20120614), libmng2 (>= 1.0.10), libmypaint-1.3-0 (>=
1.3.0), libopenexr23, libopenjp2-7 (>= 2.0.0), libpango-1.0-0 (>=
1.29.4), libpangocairo-1.0-0 (>= 1.29.4), libpangoft2-1.0-0 (>=
1.29.4), libpng16-16 (>= 1.6.2-1), libpoppler-glib8 (>= 0.44.0),
librsvg2-2 (>= 2.14.4), libstdc++6 (>= 5.2), libtiff5 (>= 4.0.3),
libwebp6 (>= 0.5.1), libwebpdemux2 (>= 0.5.1), libwebpmux3 (>=
0.6.1-2), libwmf0.2-7 (>= 0.2.8.4), libx11-6, libxcursor1 (>> 1.1.2),
libxext6, libxfixes3, libxmu6, libxpm4, zlib1g (>= 1:1.1.4)

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] [Crédit Agricole] Windows 10 - Migration

2019-08-18 Thread Alexandre Prokoudine via gimp-developer-list
It works, but we recommend upgrading your version of GIMP, it's out of date.

Alex

вс, 18 авг. 2019 г., 17:12 GIEBG Coordination Etude W10 <
coordination.etude@ca-ts.fr>:

> Hello,
>
> As part of migration of Windows 10 version 1709 to 1809, we ask you as
> software publisher to know:
> 1. The adhesions between your software(s) below and the Windows OS?
> 2. Are the version(s) of your software(s) compatible with version 1809 of
> Windows 10?
>
> We thank you in advance for your quick return ideally by 30th of August,
> please.
>
> GIMP - 2.10.8
>
> Cordialement, Regards,
>
> Pôle Produit Entreprise Numérique
> Tribu Environnement de travail & Outils collaboratifs
>
> Alexandre BORJA
> Sarah CANELLAS-GUILLE
> Florent JULLIEN
> Sébastien MOTTE
> Elodie PACAUD
> Petra SIVERBRANT
> Rémi VOYANT
>
> @: coordination.etude@ca-ts.fr
>
> Ce message et toutes les pieces jointes (ci-apres le "message") sont
> etablis a l'attention exclusive de ses destinataires.
> Si vous recevez ce message par erreur, merci de le detruire et d'en
> avertir immediatement l'expediteur par e-mail.
> Toute utilisation de ce message non conforme a sa destination, toute
> diffusion ou toute publication, totale ou partielle, est interdite, sauf
> autorisation expresse.
> Les communications sur Internet n'etant pas securisees, l'expediteur
> informe qu'il ne peut accepter aucune responsabilite quant au contenu de ce
> message.
>
> This mail message and attachments (the "message") are solely intended for
> the addressees.
> It is confidential in nature .
> If you receive this message in error, please delete it and immediately
> notify the sender by e-mail.
> Any use other than its intended purpose, dissemination or disclosure,
> either whole or partial, is prohibited except if formal approval is granted.
> As communication on the Internet is not secure, the sender does not accept
> responsibility for the content of this message.
> ___
> 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] help compiling babl

2019-08-12 Thread Alexandre Prokoudine via gimp-developer-list
Hello,

You should be using the Meson build system now.

Alex

On Mon, Aug 12, 2019 at 8:36 PM Marco Ciampa via gimp-developer-list
 wrote:
>
> Hi devs, I have a prolem compiling babl...
>
> from master git I do:
>
> ./configure
> make
> make: *** No rule to make target 'Makefile.am', needed by 'Makefile.in'.  
> Stop.
>
> but with a:
>
> git checkout BABL_0_1_68
>
> it works...
>
> what's going on here?
>
> TIA
>
> --
>
>
> 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
___
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] I NEED Gimp for Android!!

2019-07-14 Thread Alexandre Prokoudine via gimp-developer-list
Hello,

Please read 
https://www.gimp.org/docs/userfaq.html#will-you-release-gimp-for-android-or-ios-devices

Alex

On Sun, Jul 14, 2019 at 11:49 AM Dj via gimp-developer-list
 wrote:
>
> Could you PLEASE make a full featured Android version of Gimp that can be 
> downloaded on Google Play Store, and automatically resize to fit on any 
> Android phone or tablet, but still be usable on the device? Two apps on 
> Google Play have attempted it,  but on one (Androports) it's too big for my 
> phone and I'm not able to scroll to be able to view my files and add an image 
> as a layer. And the other app (XGimp Image Editor) works great except it 
> won't let me save files to my phone's storage (my files would have to be 
> public and I want to keep them private).
> ___
> 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] developers communication

2019-03-15 Thread Alexandre Prokoudine via gimp-developer-list
On Fri, Mar 15, 2019 at 10:46 AM Marco Ciampa wrote:
>
> Hi devs,
>
> I would like to know where the devs ml/channel/comunication/whatever
> really is,

On IRC: #gimp channel at irc.gimp.org.

> One question for all: is it just my impression or the 2.10 dev branch is
> slowing down and the master branch accelerating?

The master branch gets all the new stuff, the gimp-2-10 branch gets
only the safe part of that -- both bugfixes and new features.

> Are we next to a GIMP 3.x version?

Absolutely not.

> For this reason, is it better that I less and less dedicate
> my time on the 2.10 branch and start focusing on the master branch?

As a translator, you shouldn't bother about the master branch right now.

Also, there is not much difference between the two branches, because
most new features end up in 2.10.x anyway.

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] Gtk4

2019-02-13 Thread Alexandre Prokoudine via gimp-developer-list
On Wed, Feb 13, 2019 at 2:46 PM Elle Stone wrote:

> Will the port from GTK3 to GTK4 be as onerous as the port from GTK2 to GTK3?

https://blog.gtk.org/2019/02/08/report-from-the-gtk-hackfest-in-brussels/
appears to outline a number of changes that will absolutely affect
GIMP. E.g. I'm unsure if the proposed constraint -based layout system
will replace the old boxes or be available next to it. But if it will,
updating the UI will take quite a while.

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] AI algorithms in GIMP

2019-01-17 Thread Alexandre Prokoudine via gimp-developer-list
On Thu, Jan 17, 2019 at 2:14 PM Maitraya Bhattacharyya wrote:
>
> Dear devs,
>
> I have recently joined the mailing list because I wanted to contribute my
> two pennies to GIMP development (since I use it for my work). I had a look
> at the proposed plan for GIMP and wondered if people would be interested in
> including some popular AI algorithms for several image processing tasks.
>
> I would be interested in writing implementations of some of these
> algorithms into gimp if someone can commit to writing a frontend/GUI for it.
>
> It would be great if we can make a list of these algorithms to implement
> and rank them according to priority.
>
> As for my background, I am a theoretical physicist making simulations for
> HPCs (in C/C++) and interpreting their data (in Python). I have a
> reasonable workstation to train neural nets, if necessary. Be warned that I
> have never written a GUI software in my life and I don't know the GIMP
> codebase at all. I envision these to be standalone scripts which can be
> called in from the GIMP interface.
>
> Please let me know what you think.

Hello and welcome :)

What algorithms in particular are you thinking of?

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] UV mapping of OBJ???

2019-01-11 Thread Alexandre Prokoudine via gimp-developer-list
On Thu, Jan 10, 2019 at 7:40 PM Michal Vašut wrote:
>
> Hello, I've just read an article at Gimp site (
> https://www.gimp.org/news/2019/01/02/gimp-and-gegl-in-2018/ )  and here is
> proposal of possible new feature mentioned there:
>
> "There are all sorts of other interesting ideas for plug-ins, like UV
> unwrapping
> from OBJ files for texturing."
>
> Is that really necessary in 2D editor? Let the 3D artist export UV
> wireframe in 3D software of his / her choice into some 2D format and then
> he / she can work on texture even with current version of Gimp. 3D software
> suites today already have functionality for UV mapping and even painting
> directly on the surface of model (resp. on mapped texture).
> What would be benefits of such thing in Gimp?

The important word there is "ideas". Ideas are not endorsements or plans.

So you don't like the idea. That's perfectly OK. There are more ideas
in the bug tracker, some of which you might like.

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-web] Alexandre Prokoudine attacks on GIMP critics around the Web

2019-01-09 Thread Alexandre Prokoudine via gimp-developer-list
ср, 9 янв. 2019 г., 7:24 Ryan Stark efflux...@googlemail.com:

> Ardour is poor and there were lots of DAWs being developed on Linux
> (probably still are but I don't look into it any more).
>

How many is "lots"? 10? 20? 30? :)))

Ardour (and one or two its dead forks), Ecasound, Protux/Traverso. That is
pretty much it.

Paul at Ardour is arrogant.
>

You keep making these unsubstantiated claims, but just like the original
topicstarter, you'll find it to be a hard sell on this list.

It doesn't matter if he is funded. That doesn't make Ardour a success in
> terms of how it works.
>

Since he is funded by the community, it means Ardour is a success for its
user base. And most of those people are on Windows, where they have a much
wider choice of applications to run.

If you install Reaper on Linux there is absolutely no comparison whatsoever
> and Reaper can be run free or a small licence charge. Ardour tried to be
> Protools. This is what not to do if you develop open source software. It
> has to have something unique about it.
>

I guess you didn't pay much attention then. Back when Ardour started,
unlimited tracks and buses, as well as anything-to-anything routing were
unheard of.

They can rightly claim that they have something better than what commercial
> software provides.
>

Pretty much every Reddit thread on GIMP has people who say GIMP is better
for them. They might have funny reasons to say so, but it's their opinion.
You seem to be pretending that these people don't exist. I suggest you
reconsider your existential statement.

If you look at what they are doing in the Mypaint brush engine. It is also
> unique. The new features in the brush engine can create results that are
> amazing and unlike any other program yet the basic concept is quite simple.
>

Every unique feature of MyPaint's brush engine stops being unique for just
MyPaint the moment it's out. Would you hazard a guess why? (Hint: see my
previous email)

However, the brush engine is painfully slow so what is the point.
>

You still haven't given us any details about that.

So there will never be a method to simply draw individual straight lines on
> the canvas without unnecessary tools appearing on the canvas?
>

I don't know how you arrive to these funny conclusions.

I'm afraid, unless you begin substantiating any of your claims, I will have
to bow out of this conversation. You are welcome to post your bug reports
to the tracker.

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-web] Alexandre Prokoudine attacks on GIMP critics around the Web

2019-01-08 Thread Alexandre Prokoudine via gimp-developer-list
On Wed, Jan 9, 2019 at 5:42 AM Ryan Stark via gimp-developer-list wrote:
>

You know, I started having my suspicions while reading your first
email where you complained that GIMP tries to do everything, then
proceeded complaining it is focused on photo editing rather than doing
other things (mutually exclusive statements).

> Mypaint is different from Gimp because obviously the brush engine is unique

It's not unique. Several applications now use MyPaint's brush engine,
including GIMP. And that isn't even the only "difference" between
MyPaint and GIMP. They are conceptually different applications. Surely
I don't need to tell you about things like the infinite canvas?

> but if Gimp was better Krita would not be needed in my opinion.

People have always scratched their itches. What's the shocking news?

> This is how audio programs gotdamaged on Linux. Several competing projects.

There is virtually zero competition among free/libre DAWs on Linux,
because there is just one functional DAW, which is Ardour.

Everything else with the sole exception for Qtractor does MIDI
sequencing and some score editing, with overly simplistic audio
editing, because everything else is stuck in the early 2000s when the
Linux crowd thought that separating MIDI from audio was the real deal,
and JACK would rule them all (it didn't).

Paul recognized the problem relatively early on, that's why MIDI
started being worked on around 2007.

If you think there is any competition, try recording multiple audio
inputs into MusE or Rosegarden using external control surfaces, with
VCA for track groups, do quick fades and crossfades, then tell me how
it worked for you.

> Ardour should have been the open source DAW but will never ever compete now 
> partly due to the arrogant style of development ethos.

What are you even talking about? :)))

> Open source audio is now completely dead because vastly superior commercial 
> apps moved onto Linux.
> There is absolutely no way now for an open source project to compete with
> running for example Reaper on Linux.

Open source audio is so dead that Paul's development efforts are fully
funded every month long before the month is over, and he gives the
spare funds to other contributors. Robin is paid by Harrison to work
on both Mixbus and Ardour. And original MIxbus team contribute to
Ardour on regular basis. That's how dead it is.

> Gimp tries to be Photoshop

It does not. I don't know where you are getting all these funny ideas from :)

> Saying that a bezier tool is somehow a step further than a simple tool to
> draw straight lines is the sort of crazy idea that is exactly the problem
> with Gimp. In Photoshop and other apps you click a key command and draw a
> single line or lots of lines anywhere without even seeing any tool on the
> canvas.

You mean the latest Photoshop CC still has no clue how to show people
what they are drawing on the canvas? And that's great why, exactly?

> It seems that in Gimp such a simple idea wasn't thought of. The
> shift command for drawing straight lines in Gimp doesn't achieve the same
> very simple task.

Yeah, better drawing tools are definitely in the plans. But If you
want us to show people blank canvas while they draw, then no, not
gonna happen.

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-web] Alexandre Prokoudine attacks on GIMP critics around the Web

2019-01-08 Thread Alexandre Prokoudine via gimp-developer-list
On Wed, Jan 9, 2019 at 2:09 AM Ryan Stark wrote:

> Gimp should be usable as a painting program just like Photoshop is.

We can have a nice long argument about that, because I can show you
artwork made with GIMP, and you wouldn't be able to tell if it was
done with GIMP, Krita, Painter, or Photoshop :)

> So many of Gimp's features seem unfinished. For example, look at the guides. 
> There are horizontal and vertical guides similar to Inkscape in operation yet 
> no diagonal guides which would be an obvious addition.

It's on the roadmap. This is simply the question of having the manpower.

> Applying any dynamics to a brush causes Gimp to go at an absolute snail's 
> pace. Why?

What brush size?

> And why on earth are all those hideous brushes, patterns etc still included 
> in Gimp when there are other better and free ones available?

Some of the "hideous brushes" come from the GIMP Paint Studio project
which people used to love with a capital L :) The others (from G-P-S)
haven't been merged, because the only person who decided to spend time
on this hasn't yet finished what he started -- for reasons I'm not
aware of (probably just busy).

This is really simple. If you want something improved, there are
basically three options: wait till someone does it, hire someone to do
it, or do it yourself.

Every single person in this project (including me) got involved with
GIMP in their respective roles because we wanted something that GIMP
didn't have, and waiting wasn't an option.

If you are interested in updating the default assets like patterns
(with free-as-in-speech licensed content), you are welcome to do
exactly that. We'll insist on keeping the bell pepper though, for
hysterical raisins :)

> You can't go from from single window mode to multiple without your layout 
> being messed up.

I've just done exactly that to verify your statement, and nothing
broke. I'm on Ubuntu 18.10 and GNOME/Wayland, with GIMP from
up-to-date 'gimp-2-10' git branch (haven't seen anything like what you
described for as long as I can remember though). More details (with
screenshots) would be helpful, and possibly in the bug tracker.

> For example there is some kind of problem where certain actions with a mouse 
> or pen causes docked tabs to constantly break free without reason.

If this can be reproduced, it should be reported.

> The problem is that some people may be prepared for a few problems, report a 
> few bugs etc but then it just gets tedious and they move to another app. I 
> believe many will do this with Gimp.

Yes, but we can't fix bugs we aren't told about.

> What are the solutions to these problems? I don't really know but i think 
> once some bad design decisions are made with an app it is very hard to fix 
> things.

Undoing bad design decision was a major part of 2.10 development cycle
and continues to be in the master branch leading up to v3.0.

> The developers or at least some developer who has a vision on how to improve 
> things is the most crucial component. I think the problem with a lot of 
> software is that the developers do not use the software extensively or study 
> how other programs do things.

End-users tend to expect developers to do all sorts of things, from
writing user manuals to making builds for every single possible Linux
flavor out there. While developers tend to lack the time to do actual
programming, let alone all those nice things you are talking about.
This is why we treasure good, sensible bug reports and feature
requests explaining why something is wrong and what are the options of
improving on that.

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-web] Alexandre Prokoudine attacks on GIMP critics around the Web

2019-01-08 Thread Alexandre Prokoudine via gimp-developer-list
On Tue, Jan 8, 2019 at 8:27 PM Ryan Stark wrote:
>
> I appreciate that the app is free open source and developers are working for 
> free but it seems they are cut off from most users.

What would you suggest to do that we don't already do?

> Virtually every feature has some kind of usability bad design

And you are welcome to report issues and propose specific changes.

> and Gimp is not as stable and reliable as it used to be

Yes, the side effect of releasing a huge amount of changes you've seen
in 2.10 is less stability.

> Most people are not going to bother going on mailing lists. There doesn't 
> seem to be any decent forum that everyone uses like there is for Blender as 
> in Blenderartists

There is discuss.pixls.us. It's decent and everyone (but you?) uses
it. I also regularly answer questions on Twitter, Reddit, Facebook
etc. Places that noone uses :)

> and there is no Gimp manual for the latest version.

Yes. It's being worked on by a single person. Would you be interested
to help Julien?

> Gimp appears to be a jack of all trades and master of none so there is no 
> passionate community.

That is quite the opposite of what I see. Darn, I have to stop some
users from being too passionate :)

> A sign of the problems is that on Linux we have Krita and Mypaint. If Gimp's 
> tools had been better for painting and manipulating things on the canvas we 
> would not have needed those apps.

Krita is almost 20 years old. You might want revisiting your argument.

MyPaint's development is, sadly, on the declining side. Personally, I
hope that Briend will merge all his changes from 2017-2018 and
stimulate a new, long overdue release.

I don't think we as a community need just GIMP. I love what Martin et
al. did with MyPaint, there absolutely is enough room for applications
like MyPaint and Krita streamlined for particular demographics or use
cases.

> Most people edit photos in a RAW editors now so these more comprehensive 2D 
> image editors should not be centred around just editing photos.

GIMP 2.10.x features MyPaint Brush tool, canvas rotating/flipping, and
other painting-specific things. Some features like layer group masks
are useful for a variety of use cases. Upcoming v2.10.10 is also
featuring smart colorization for painters and comic artists, as well
as a DDS plug-in for game designers.

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] GEGL Drop Shadow filter not working

2019-01-05 Thread Alexandre Prokoudine via gimp-developer-list
пт, 4 янв. 2019 г., 19:36 Marco Ciampa:

> On Fri, Jan 04, 2019 at 03:09:21PM +0300, Alexandre Prokoudine via
> gimp-developer-list wrote:
> > https://i.imgur.com/TciFDZy.png
>
> Sorry, no:
>
> https://imgur.com/a/8OepPGF


I really have no idea what's going on in your case.

I'm on Ubuntu 18.10 and GIMP from gimp-2-10 master branch, although it
doesn't change a thing -- it's been working for me since the beginning.

1. New image
2. New layer
3. Select, fill with color
4. Crop to content
5. Enlarge layer boundary
6. Launch the GEGL op in question.

Or even simpler, with a text layer:

1. New image
2. New text layer with some text
3. Layer to image size
4. Launch the GEGL op in question.

In both scenarios, the GEGL-based filter works just like on my screenshot.

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] Adding feature!!

2019-01-05 Thread Alexandre Prokoudine via gimp-developer-list
On Sat, Jan 5, 2019 at 5:24 AM tosan uçbağa wrote:
>
> Can you add a auto resizer?

What does it do?

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] GEGL Drop Shadow filter not working

2019-01-04 Thread Alexandre Prokoudine via gimp-developer-list
https://i.imgur.com/TciFDZy.png

On Thu, Jan 3, 2019 at 10:57 AM Julien Hardelin  wrote:
>
> I tried this before posting, using Layer Boundary Size to make the layer size 
> bigger : it doesn't work.
>
> Le 02/01/2019 à 22:38, Alexandre Prokoudine a écrit :
>
> The layer has to be the size of the canvas or at least somewhat larger than 
> its contents
>
> Alex
>
> ср, 2 янв. 2019 г., 20:39 Julien Hardelin jm.h...@wanadoo.fr:
>>
>> Hi devs,
>>
>> With Gimp-2.10.8 and Gimp-2.99, under different systems and computers,
>> the Drop Shadow filter doesn't work: nothing happens when I use it.
>> (Drop Shadow (legacy) works perfectly)
>>
>> Is this due to work in progress or to something I don't understand in
>> using it?
>>
>> Julien
>>
>> ___
>> 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] GEGL Drop Shadow filter not working

2019-01-02 Thread Alexandre Prokoudine via gimp-developer-list
The layer has to be the size of the canvas or at least somewhat larger than
its contents

Alex

ср, 2 янв. 2019 г., 20:39 Julien Hardelin jm.h...@wanadoo.fr:

> Hi devs,
>
> With Gimp-2.10.8 and Gimp-2.99, under different systems and computers,
> the Drop Shadow filter doesn't work: nothing happens when I use it.
> (Drop Shadow (legacy) works perfectly)
>
> Is this due to work in progress or to something I don't understand in
> using it?
>
> Julien
>
> ___
> 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] Please Help

2018-12-12 Thread Alexandre Prokoudine via gimp-developer-list
On Wed, Dec 12, 2018 at 4:59 PM Elle Stone wrote:
>
> On 12/12/2018 07:28 AM, C R via gimp-developer-list wrote:
> > Maybe. The eyes flash red under certain circumstances. It's quite creepy...
> > Though this is not a new thing in GIMP.:)
>
> If this is an actual fact - that sometimes Wilbur's eyes flash a color -
>   then here is a request that this very odd "feature" be considered a
> bug and removed.

Easter eggs that only show up on April 1 are that bad?

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] Please Help

2018-12-12 Thread Alexandre Prokoudine via gimp-developer-list
On Wed, Dec 12, 2018 at 2:20 PM Göran Persson via gimp-developer-list wrote:
>
> Hello.
>
> Please, I am very pleased with GIMP.
> Very nice and good program.
> but now a virus has appeared.
>
> See attached file.
> I don’t like this cow.
>
> How do I get rid of it?

There are no cows on the GIMP farm, only five-legged goats. They are
yours forever.

Please upload the screenshot. There are no attaches 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] FW: different Vignette parameters 2.8 vs 2.10

2018-12-06 Thread Alexandre Prokoudine via gimp-developer-list
пт, 7 дек. 2018 г., 5:50 Owen erote:

> Hi,
>
>
> Not a developer, but I note that in 2.10.6  it is described as a gegl
> operation. I cannot find Vignette in 2.8.22


Tools > GEGL tool

Choose Vignette in the drop-down list.

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] PSD support in GIMP

2018-11-17 Thread Alexandre Prokoudine via gimp-developer-list
Hi,

One of the common topics regarding GIMP is its support for PSD files,
both importing and exporting.

There is now a wiki page that lists unsupported PSD features and explains:

- what features are not supported
- whether these features can be hacked on immediately or do they
require prior work
- what kind of prior work is required
- whether this prior work is mapped to any milestones in the official
roadmap, and thus certain features can only be expected after a
certain major update of GIMP

https://wiki.gimp.org/wiki/PSD_support

Obviously, it's a work in progress. If you don't see something covered
there, please tell us or, better yet, please file a bug report and
submit a sample file -- we miss such files for a few existing bug
reports regarding PSD:

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

Thank to an anonymous user on opennet.ru who politely nudged us in the
direction of creating this page :)

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-web] Alexandre Prokoudine attacks on GIMP critics around the Web

2018-11-16 Thread Alexandre Prokoudine via gimp-developer-list
пт, 16 нояб. 2018 г., 23:19 Simone Karin Lehmann sim...@lisanet.de:

> …
>
> "We don't do "release dates" :) We release when it's ready.“
>
> Niccolo still answers, IMO, very politely

and explains why, in his opinion, he thinks planned release dates are
> better than solely saying "we don't do release dates“ and explains how a
> smiley at the end of this sentence sounds to him and finally admitting that
> he might be wrong, though.
>

The problem here is that you are reading a reply that he later edited to
look nicer, after I replied to him.

The original comment suggested that by refusing to set dates to releases we
tell users to f*** off (I'm redacting this here, he didn't). And there was
no admission that he could be wrong.

Look, Simone, there are not many active contributors to GIMP, but those who
are, me including, spend upwards of 20 hours a week on this project (maybe
even more for some). It's like having another job (or another family).

And since my job is pretty much about communication between users and
developers, I find his repeated suggestion that we don't care about users
incredibly offensive, which I told him about several times, and he never
had the dignity to apologize (which would resolve the conflict completely).
On the contrary, instead of apologizing, he did his best to discredit my
involvement, not to mention all the expletives.

It's your choice to protect an abusive person though.

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-web] Alexandre Prokoudine attacks on GIMP critics around the Web

2018-11-16 Thread Alexandre Prokoudine via gimp-developer-list
On Fri, Nov 16, 2018 at 2:47 PM C R  wrote:

> Well clearly he was harassing you with his facts and sarcasm.
>
> You'll pull through though. I believe in you!
> I've got to go now though. Have fun with whatever this is.
>

I'm afraid I've been giving a bad example how to deal with abusive users.
Let's not repeat my mistakes.

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-web] Alexandre Prokoudine attacks on GIMP critics around the Web

2018-11-16 Thread Alexandre Prokoudine via gimp-developer-list
пт, 16 нояб. 2018 г., 6:40 Trevor Rose tarose.tre...@gmail.com:

>
> 3 — the solution to the problem is to tighten up your communications
> channels, and to use some other technology rather than just an email group,
> and in which alternative system a person must be logged in, and each post,
> thread and comment/reply is not only better organised, but can be
> identified as per user ID, GROUP, and ROLE ... PLUS AND MOST IMPORTANTLY
> you can constrain each unit of communication by using mandatory fields and
> filters, in order to force clearer communication and remove some amount of
> abuse, while also being able to ban anyone who takes their passion beyond
> an accepted threshold/limit.
>

Hi Trevor,

I'm afraid I'm not a big believer in technical constraints as means to
manage a community. We have a history of making it difficult for people to
contribute to GIMP in any way. I would hesitate to make it even harder.

Your suggestion boils down to making initial communication more complicated
while, indeed, more structured. It also seems to suggest some sort of
pre-moderation which puts a heavier burden on those of us involved with
moderation.

So mailing lists are a tool that keeps communication open enough and takes
just about the right amount of time to keep our sanity at the cost of rare
outbursts like this one.

Having said all that, I would still appreciate examples of what you
consider superior communication channels.

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] Alexandre Prokoudine attacks on GIMP critics around the Web

2018-11-15 Thread Alexandre Prokoudine via gimp-developer-list
On Thu, Nov 15, 2018 at 7:35 PM Niccolo Brogi  wrote:

> Not so, I listened to what you said. Like I said many times, I change my
> mind like a flag in the middle of the storm, and you do have a positive
> attitude to not stop this natural process of mine.
>
> You ended your reply with "you were a dick",
>

1. He didn't end his reply with that. The word was in the middle of his
email.

2. He said "it was a dick move", he didn't call you one.

If you continue this well established pattern of knowingly misrepresenting
what people tell you, I'm afraid we will have to force-end this
conversation.

Alex

I said that I have 3 more. It's 4 or us so far, then.
>
___
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] Alexandre Prokoudine attacks on GIMP critics around the Web

2018-11-15 Thread Alexandre Prokoudine via gimp-developer-list
On Thu, Nov 15, 2018 at 6:25 PM Niccolo Brogi  wrote:

> Nope.
>
> Everything started because I was called a "backseat viewer", and therefore
> not allowed to say that scheduled releases are good. After that I was
> replying to that attitude, and not about whether rolling releases are
> better (which I had an extremely open mind about).
>

I'm afraid you are conflating "criticism" with "purposedly being a true
pain in the neck".

If people are not happy with unsheduled releases, I would (naively?) expect
them to begin with stating that they think this is wrong and then, politely
or not so much, asking why that is the case and what is the reason for not
switching to rolling. You never really asked. You started the conversation
with a claim that we should pay attention to users (like we don't, contrary
to a mountain of evidence) and that we tell them to f*** off. What did you
expect to happen next?

(For the record, I personally would prefer the rolling model for GIMP, but
it is currently not quite realistic. Besides, so far, most people who spoke
up seem to be happy with the new release model where new things get ported
to the stable branch and then released every month or two.)

In almost a week of this ongoing "conversation" you still haven't asked why
we don't do rolling and scheduled releases. This is exactly how much
constructive your "criticism" is. And I'm still willing to explain why,
publicly.

I'm only replying to this, because here you are again pretending that we
(or me personally) attack critics. We don't. All that happened here is that
I was sarcastic over yet another case of someone being unnecessarily nasty
to the point of insult.

I don't know how many times I have to repeat it: criticism is welcome and
studied, but insults, shouting, and use of expletives aren't. Please learn
the difference. We cannot have a constructive conversation until you do.

Alex


>
> The message you quoted is way after things started going bad.
>
> As for your comparison with Starbucks, I don't abuse Starbucks employees
> and neither I abuse GIMP's staff.
>
> I also don't care about harsh words, I'm not a little snowflake. I just
> want to know if GIMP is represented by Alexandre like he implies, and if
> the GIMP team is OK with attacking newbies and critics of GIMP saying
> they're backseat drivers that are not worth listening to and not worth
> explaining things.
>
> I'm not the only one who shares the view that in GIMP there is this
> attitude of "if you didn't make it, you're not allowed to talk bad about
> it".
>
> If that's the culture at GIMP, I'm not gonna cry. Just say it.
>
> On Thu, Nov 15, 2018, 16:00 C R  wrote:
>
___
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] Alexandre Prokoudine attacks on GIMP critics around the Web

2018-11-15 Thread Alexandre Prokoudine via gimp-developer-list
On Thu, Nov 15, 2018 at 4:48 PM Niccolo Brogi  wrote:

> Regarding CCing people, my thread hasn't been approved, so I don't know if
> people can read it.
>
> Regarding the rest, you don't have to present exhibits, we're not in
> court. I'm giving you feedback about your behavior as someone who
> represents the whole team (unless I got your pronuons wrong, you keep
> saying "we"--possibly to give authority to your arguments--and you
> misrepresent yourself as a developer of GIMP).
>

I have never claimed to be developer of GIMP, publicly or privately -- you
have zero proof of your claim. I actually correct people when they call me
a developer, and I have enough verifiable proof of that.

If you think that continuos piling of factually wrong statements will help
your cause, I suggest you rethink your stategy.


> Take this feedback however you want. So can the rest of the team, but
> considering you've been speaking on their behalf it's important that they
> know what you're doing and that people aren't happy. If your behavior is
> appropriate for someone who represents the team, good to know. If it's not,
> don't speak on behalf of everyone else and at that point you can be as much
> of an asshole as you want with both newbies and people who disagree with
> you.
>

I will have to point out that name-calling, which you once again went for,
is not welcome on our mailing lists as per code of conduct:

https://www.gimp.org/mail_lists.html

"Please make sure that you add value to the discussion, avoid repetitive
arguments, flamewars, trolling, and personal attacks."

Please consider rethinking your interaction here.

Good day to you.

Alex


>
> On Thu, Nov 15, 2018, 14:28 Alexandre Prokoudine <
> alexandre.prokoud...@gmail.com> wrote:
>
>>
>>
>> On Thu, Nov 15, 2018 at 3:46 PM Niccolo Brogi  wrote:
>>
>>> OK. If you're bad at talking to people (since people come with
>>> misconceptions although you could easily change that), as someone who
>>> doesn't only speak for himself, you should just not talk to people.
>>>
>>> It's also not just me,  many people have the same problem with you. I
>>> guess it's you against the world.
>>>
>>> Let's see if the rest of the team is aware of your behavior, and --in
>>> case they have the courage to approve my message or at least reply--if they
>>> approve of it (BTW, why don't you CC them, if you are so sure your behavior
>>> is OK?).
>>>
>>
>> I don't need to CC people who are already subscribed to the mailing lists
>> you posted to. This is how mailing lists essentially work: people get
>> emails sent to those list.
>>
>>
>>> I have thick skin (mind you, some people that have messeged me don't as
>>> much, and are still upset about your attacks and were in tears),
>>>
>>
>> Oh yes, about that. The allegations. Since there have been only two other
>> problematic cases with users in the past week, I'm confident I can pinpoint
>> the relevant threads.
>>
>> Exhibit A:
>>
>> >>> A day or two ago I dared criticize GIMP [...] and that alexlg guy
>> came off the ropes so hard I was literally in tears over it. Just wanted to
>> tell you how validating it was to see you jousting over the exact same
>> ground with him just a few days earlier.
>>
>> This is this very thread:
>>
>> https://www.reddit.com/r/linux/comments/9vneh8/gimp_2108_released/e9ex8sl/
>>
>> There was a quite justified complaint that text layers are hard to use in
>> GIMP, which I readily agreed with. Nevertheless, this user came to say that
>> lack of maturity of that feature is present because of GIMP team's "mindset
>> of "you don't need it" and "we don't like it"". The harshest thing I said
>> in response was point out evidence of the contrary, then saying "Facts...
>> Always such an inconvenient thing, isn't it? :)".
>>
>> I'd love to see here the cause of alleged tears or coming hard off the
>> ropes.
>>
>> And Exhibit B:
>>
>> >>> [...] He even went so far as to mention me by name in another thread
>> entirely, basically calling me a whiny baby, once enough people had
>> dogpiled that he was forced to slightly change his stance on something.
>> Even if you win, you lose...
>>
>> This is this very thread:
>> https://www.reddit.com/r/GIMP/comments/9wrgwp/whats_new_in_gimp_2108_by_davis_media_design_this/
>>
>> Essentially, someone got steamed up because of having to spend shocking 3
>> minutes on "wading through a sea of jargon, buzz

Re: [Gimp-developer] Alexandre Prokoudine attacks on GIMP critics around the Web

2018-11-15 Thread Alexandre Prokoudine via gimp-developer-list
On Thu, Nov 15, 2018 at 3:46 PM Niccolo Brogi  wrote:

> OK. If you're bad at talking to people (since people come with
> misconceptions although you could easily change that), as someone who
> doesn't only speak for himself, you should just not talk to people.
>
> It's also not just me,  many people have the same problem with you. I
> guess it's you against the world.
>
> Let's see if the rest of the team is aware of your behavior, and --in case
> they have the courage to approve my message or at least reply--if they
> approve of it (BTW, why don't you CC them, if you are so sure your behavior
> is OK?).
>

I don't need to CC people who are already subscribed to the mailing lists
you posted to. This is how mailing lists essentially work: people get
emails sent to those list.


> I have thick skin (mind you, some people that have messeged me don't as
> much, and are still upset about your attacks and were in tears),
>

Oh yes, about that. The allegations. Since there have been only two other
problematic cases with users in the past week, I'm confident I can pinpoint
the relevant threads.

Exhibit A:

>>> A day or two ago I dared criticize GIMP [...] and that alexlg guy came
off the ropes so hard I was literally in tears over it. Just wanted to tell
you how validating it was to see you jousting over the exact same ground
with him just a few days earlier.

This is this very thread:

https://www.reddit.com/r/linux/comments/9vneh8/gimp_2108_released/e9ex8sl/

There was a quite justified complaint that text layers are hard to use in
GIMP, which I readily agreed with. Nevertheless, this user came to say that
lack of maturity of that feature is present because of GIMP team's "mindset
of "you don't need it" and "we don't like it"". The harshest thing I said
in response was point out evidence of the contrary, then saying "Facts...
Always such an inconvenient thing, isn't it? :)".

I'd love to see here the cause of alleged tears or coming hard off the
ropes.

And Exhibit B:

>>> [...] He even went so far as to mention me by name in another thread
entirely, basically calling me a whiny baby, once enough people had
dogpiled that he was forced to slightly change his stance on something.
Even if you win, you lose...

This is this very thread:
https://www.reddit.com/r/GIMP/comments/9wrgwp/whats_new_in_gimp_2108_by_davis_media_design_this/

Essentially, someone got steamed up because of having to spend shocking 3
minutes on "wading through a sea of jargon, buzzwords, mansplaining, and
patting yourselves on the back" which is how this person characterized the
official 2.10.8 announcement.

"mention me by name in another thread entirely" is actually about the very
same thread --
https://www.reddit.com/r/GIMP/comments/9wrgwp/whats_new_in_gimp_2108_by_davis_media_design_this/e9oe05x/
-- about the very same topic: providing a shorter list of changes between
versions.

And here is the "basically calling me a whiny baby" quote:

"I don't see any way in Gitlab to view all files at the time of tagging a
release, but I'm not sure if having to scroll through changes for the next
version first [in an updated NEWS file] would give anyone a heart attack,
save for our friend /u/Unchayned <https://www.reddit.com/u/Unchayned> here."

There are facts, and then there are interpretations. I don't think our
interpretations will ever match, but I'd be happy to be proven wrong.

Alex


> and I don't care what you say and do if you take responsibility for your
> actions-- which you have to do since you not only speak for yourself only,
> but for other people as well.
>
> On Thu, Nov 15, 2018, 13:22 Alexandre Prokoudine <
> alexandre.prokoud...@gmail.com> wrote:
>
>> Hi Niccolo,
>>
>> There is a certain thing I'm rather horrible at - trying to a have a
>> conversation with people who come with preconceptions about something they
>> are not qualified to make judgments of and unwilling to learn before
>> drawing conclusions.
>>
>> When stumbling upon your message that by not setting dates to releases we
>> tell users to "f*** off" (which you later edited away), I should have kept
>> my mouth shut. Nor should I have replied to your continuos verbal abuse
>> containing expletives.
>>
>> I am truly and genuinely sorry about that.
>>
>> Alexandre
>>
>> чт, 15 нояб. 2018 г., 14:48 Niccolo Brogi :
>>
>>> Hello.
>>>
>>> TLDR:
>>> Alexandre attacks GIMP critics around the internet implying that he's a
>>> developer of GIMP and represents GIMP, using language and doing things that
>>> are completely inappropriate for his (self-proclaimed?) role, which makes
>>> the whole GIMP team look like crap for no

Re: [Gimp-developer] Alexandre Prokoudine attacks on GIMP critics around the Web

2018-11-15 Thread Alexandre Prokoudine via gimp-developer-list
Hi Niccolo,

There is a certain thing I'm rather horrible at - trying to a have a
conversation with people who come with preconceptions about something they
are not qualified to make judgments of and unwilling to learn before
drawing conclusions.

When stumbling upon your message that by not setting dates to releases we
tell users to "f*** off" (which you later edited away), I should have kept
my mouth shut. Nor should I have replied to your continuos verbal abuse
containing expletives.

I am truly and genuinely sorry about that.

Alexandre

чт, 15 нояб. 2018 г., 14:48 Niccolo Brogi :

> Hello.
>
> TLDR:
> Alexandre attacks GIMP critics around the internet implying that he's a
> developer of GIMP and represents GIMP, using language and doing things that
> are completely inappropriate for his (self-proclaimed?) role, which makes
> the whole GIMP team look like crap for no reason.
>
> FULL:
>
> A little bit of a backstory (which you can skip if in a hurry): I've had a
> couple of unpleasant exchanges with Alexandre. Our latest exchange is
> https://www.reddit.com/r/linux/comments/9vneh8/gimp_2108_released/e9doqjq
> from the Reddit thread at
> https://www.reddit.com/r/linux/comments/9vneh8/gimp_2108_released/. While
> it started innocently enough, it quickly turned nasty. What triggered
> Alexandre was my opinion that scheduled releases are better than random
> ones, because people like IT administrators might have to upgrade hundreds
> of computers, and being able to plan for that is nice. I think he
> understood I claimed the GIMP development team could and should refactor
> GIMP to GTK3 and release in 6 months (which I never said). Regardless,
> instead of saying "ah, no GIMP is better with rolling release because, bla
> bla bla..." he started attacking me personally--basically saying that I had
> no right to say that because I'm not a GIMP developer (but neither is he
> more on that later). A missed opportunity to learn something: just because
> of his tone, the discussion deviated from that and got uncivil, which is
> what I observed always happens with him when he exchanges ideas with people
> that have unapproved opinions.
>
> I tend to be blunt and ignore political correctness. Add that to perhaps
> getting passionate or even emotional about stuff, and to be honest
> sometimes I do get harsh replies and have to rephrase things I didn't say
> nicely enough. However, exchanges with Alexandre are a totally different
> beast.
>
> Why? A while after posting the comments I talked about above I started
> getting PMs of "solidarity" from other users that Alexandre attacked around
> Reddit. For instance, I was given permission to include:
>
> >>> A day or two ago I dared criticize GIMP [...] and that alexlg guy came
> off the ropes so hard I was literally in tears over it. Just wanted to tell
> you how validating it was to see you jousting over the exact same ground
> with him just a few days earlier.
>
> Another message:
> >>> [...] He even went so far as to mention me by name in another thread
> entirely, basically calling me a whiny baby, once enough people had
> dogpiled that he was forced to slightly change his stance on something.
> Even if you win, you lose...
>
> Because he implies that he's a GIMP developer--by saying stuff like "oh,
> you don't develop GIMP, you can't say anything bad about it", or using "we"
> in connection with the GIMP dev team (with the word "dev" being important
> here)--he seems to get some sympathy from fellow users, because what kind
> of piece of shit attacks volunteers that create awesome free stuff for
> people (which I agree with). It really upset me when I found out that he's
> not at developer at all, but contributes in non-technical ways. This is bad
> not only because I can excuse his attitude from a developer but not from
> someone that writes articles on Facebook while pretending to be a developer
> to please his ego, but because he doesn't get banned from communities just
> because he implies that he's in the dev team.
>
> I think that if Alexandre's job is to "market" GIMP, not only he's doing a
> horrible job, but he's being detrimental to the project. It's easy to
> relate to people that agree with you, they're already passionate GIMP
> users! Those that have some kind of issues are the ones to really talk to,
> because you can explain things to them and since GIMP is an awesome project
> you can change their mind or make them more informed, and turn a critic
> into a passionate GIMP user (or even evangelist). In addition, pretending
> to be in the dev team is good for his ego, but really bad for the dev team,
> since it just gives the impression that GIMP devs are entitiled assholes.
>
> I'm aware that this email might not only fail to help stop Alexandre from
> attacking people, but also cause more attacks towards me since I would
> assume you sympathize with him, but so be it. Maybe (just maybe) you guys
> are not aware of what's going on and don't actually 

Re: [Gimp-developer] GIMP Hacking:TODO page is not updated

2018-11-14 Thread Alexandre Prokoudine via gimp-developer-list
On Wed, Nov 14, 2018 at 4:02 AM Massimo Fidanza via gimp-developer-list <
gimp-developer-list@gnome.org> wrote:

> Hi, the wiki page https://wiki.gimp.org/wiki/Hacking:TODO is not updated,
> I
> see some of the bugs are now closed. I would like to update the page and
> report the current situation, how can I help?
>

Hi, thanks for reminding, totally overlooked this. Fixed.

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] usability: 72 year old has trouble with dark padding

2018-08-28 Thread Alexandre Prokoudine via gimp-developer-list
On Tue, Aug 28, 2018 at 12:09 PM, Laxminarayan Kamath via
gimp-developer-list  wrote:
> Hi,
> To those studying/working on the usability aspect of GIMP, here is an
> interesting case:
>
> https://m.facebook.com/groups/1921288214858432?view=permalink=2119666095020642

"The page you requested cannot be displayed right now. It may be
temporarily unavailable, the link you clicked on may be broken or
expired, or you may not have permission to view this page."

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] no recent macOS builds

2018-08-22 Thread Alexandre Prokoudine via gimp-developer-list
On Tue, Aug 21, 2018 at 9:39 PM, Yurii Kolesnykov via gimp-developer-list wrote:
> Hi, Developers!
>
> I had spotted a lack of recent macOS builds.

There is a mostly untested build of 2.10.6. We shall probably upload it soonish.

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] Dependency gtk-encode-symbolic-svg

2018-08-21 Thread Alexandre Prokoudine via gimp-developer-list
On Tue, Aug 21, 2018 at 1:22 PM, Owen wrote:
> Hi,
>
> Today (after a week or so break) this new dependency, gtk-encode-symbolic-svg 
> was needed for the Git version.

It's the gtk-3-examples package in Debian.

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] Update RoadMap page

2018-07-03 Thread Alexandre Prokoudine via gimp-developer-list
On Mon, Jul 2, 2018 at 11:03 PM, Andrew Pullins wrote:

> And to people who will file bug reports against issues in, say, upcoming in
>> 2.10.4 and hope to see that fixed in 2.10.6 this would be helpful how,
>> exactly?
>>
>
> Ok I guess that makes sense, but what does not make sense is to keep
> issues labeled as for 2.8.X,
>


You are welcome to join the team, test every 2.8.x bug report in 2.10.x,
and update milestones.


> If it is not crucial to that point release and no one goes to work on the
> issue than why is it labeled as being for the point release?
>

Because we don't always know if we work on a 2.10.x issue or feature
request while 2.10.x development is still ongoing.


> Kinda makes the release look half backed if there are still issues for the
> release not finished. That is my point.
>

It looks like you want to move things around solely for the purpose of the
milestones completion chart look cool and be a lie :)

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] Update RoadMap page

2018-07-01 Thread Alexandre Prokoudine via gimp-developer-list
вс, 1 июл. 2018 г., 16:44 Andrew Pullins:

> Sounds like these issues need to be recategorized then. All the 2.8.X and
> 2.10.X might need to be moved to the 3.0 release or perhaps removed from
> milestones.
>

And to people who will file bug reports against issues in, say, upcoming in
2.10.4 and hope to see that fixed in 2.10.6 this would be helpful how,
exactly?

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] Update RoadMap page

2018-06-30 Thread Alexandre Prokoudine via gimp-developer-list
сб, 30 июн. 2018 г., 15:33 Andrew Pullins :

> There is no duplicate management of milestones. The Roadmap page is mostly
>> a PR thing, nothing else. No developers use it. There is no milestone
>> management there.
>
>
> One thing that always frustrated me about the roadmap as a person who
> occasionally wondered how things were going. Was that some of the roadmap
> points would have bug reports hyperlinked while the features I was most
> interested in or did not understand did not. With milestones, every issue
> that would be attached to that milestone would be displayed. I would say
> that half the interest in the roadmap is to see how far along development
> is and the other half is to find out what will be in the next release/to
> see what the developers are working on.
>

https://gitlab.gnome.org/GNOME/gimp/milestones

That makes 2.10 only 37% ready (while released), the now obsolete 2.8 only
8% ready, and doesn't even begin to cover the amount of work on 3.0 that is
untracked, because mitch et al. keep discovering ugly code as they go.

Given that, all estimations would be a lie.

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] Update RoadMap page

2018-06-29 Thread Alexandre Prokoudine via gimp-developer-list
On Fri, Jun 29, 2018 at 4:46 PM, Andrew Pullins wrote:

> Would it be possible to move the roadmap to the Gnome GitLab milestones?
>

I don't understand how this would be done, exactly.


> This way the issues on GitLab link to milestones and the progress of that
> milestone would automatically be updated when issues are updated.
>

The whole point of the Roadmap page is to tell people we know and care
about the most important issues. It isn't meant to have every single issue
listed.

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] Update RoadMap page

2018-06-29 Thread Alexandre Prokoudine via gimp-developer-list
On Fri, Jun 29, 2018 at 3:54 PM, Massimo Fidanza wrote:
> Hi Alex,
>
> thank you for updating this. I noticed that others pages on the wiki are
> outdated.I want to help fix them, but I need to ask information to someone,
> which one is the best communication channel?

We usually use IRC for instant messaging, with a caveat that a person
you need might not be online at the moment you join the channel.

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] Update RoadMap page

2018-06-28 Thread Alexandre Prokoudine via gimp-developer-list
Yes, thanks for reminding :)

Alex

чт, 28 июн. 2018 г., 2:54 Massimo Fidanza via gimp-developer-list <
gimp-developer-list@gnome.org>:

> Hi,
>
> Can roadmap page https://wiki.gimp.org/wiki/Roadmap be updated with
> current
> project status and references to Gitlab?
>
> Il mer 27 giu 2018, 23:12 Ofnuts  ha scritto:
>
> > This seems due to the script importing another module:
> >
> > Traceback (most recent call last):
> >File "E:\Gimp\Arakne\arakne-path-shape-creator8.py", line 35, in
> > 
> >  import gtk, gimpui, pnt2d, drawUI
> > ImportError: No module named pnt2d
> >
> > In other words, the plugin main module is making the assumption that it
> > is in the python path, so any module in the same directory can be
> > imported. This doesn't seem to be true for the Windows version (the
> > plugin works OK in Linux 2.10). This is possibly a bug in the Windows
> > version.
> >
> > On 06/25/18 07:26, Paco Garcia via gimp-developer-list wrote:
> > > ​The scripts are working fine until ​the last gimp release, two of the
> > > scripts failing are:
> > >
> http://www.arakne.es/en/dessign/gimp-guideslab-edit-guides-numerically/
> > > and
> > >
> http://www.arakne.es/en/programming/python/gimp-plugin-shape-creator-v8/
> > >
> > > Calling gimp with the verbose option don't give more clues about the
> > error:
> > >
> > > Querying plug-in: 'C:\Users\yo\Desktop\gimp_plugins\pnt2d.py'
> > > gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error
> > > Querying plug-in: 'C:\Users\yo\Desktop\gimp_plugins\drawUI.py'
> > > gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error
> > > Querying plug-in:
> > > 'C:\Users\yo\Desktop\gimp_plugins\araknepathshapecreatorshapes.py'
> > > gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error
> > > Querying plug-in: 'C:\Users\yo\Desktop\gimp_plugins\arakne-stitch3b.py'
> > > Querying plug-in:
> > > 'C:\Users\yo\Desktop\gimp_plugins\arakne-path-shape-creator8.py'
> > > gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error
> > > Querying plug-in:
> 'C:\Users\yo\Desktop\gimp_plugins\arakne-guide-lab.py'
> > > gimp-2.10: LibGimpBase-ADVERTENCIA: gimp-2.10: gimp_wire_read(): error
> > > Querying plug-in: 'C:\Program Files\GIMP
> > 2\lib\gimp\2.0\plug-ins\gimpfu3.py'
> > > Any help is welcome
> > >
> > > 2018-06-23 18:29 GMT+02:00 Carol Spears via gimp-developer-list <
> > > gimp-developer-list@gnome.org>:
> > >
> > >> On Sat, Jun 23, 2018 at 10:23 AM, Carol Spears <
> carol.spe...@gmail.com>
> > >> wrote:
> > >>
> > >>>
> > >>> On Sat, Jun 23, 2018 at 8:25 AM, Ofnuts  wrote:
> > >>>
> >  On 06/19/18 21:43, Paco Garcia via gimp-developer-list wrote:
> > 
> > > Is there any way to get more information about the gimp_wire_read
> ()
> > > error
> > > that occurs when loading python scripts? Many scripts that worked
> in
> > > previous versions of gimp fail in the new one without apparent
> cause.
> > > Spanish version:
> > > ¿Hay alguna forma de obtener mas información sobre el error
> > > gimp_wire_read() que se produce al cargar scripts de python?.
> Muchos
> > > scripts que funcionaban en versiones anteriores de gimp fallan en
> la
> > > nueva
> > > sin causa aparente.
> > > ___
> > >
> >  I have seen plenty of such errors and they don't make the
> registration
> >  fail. In 2.10 for Windows, scripts that import pygtk can have
> problems
> > >> (you
> >  have to make sure you import gimpfu first). Would you have the URL
> to
> > >> such
> >  a script?
> > 
> > 
> > >>> That's right.  I've seen that error before though, but I write crappy
> > >>> python also.  Maybe it is missing its beginning:
> > >>>
> > >>> #!/usr/bin/env python
> > >>> # -*- coding: utf-8 -*-
> > >>>
> > >>> or pygtk is not installed.  Or maybe the script is a template and
> > broken
> > >>> from the fill ins.
> > >>>
> > >>> My earlier suggestion to poke around with it was not wrong, however.
> > >>>
> > >> Maybe the file is base64 or whatever that format was for mail in the
> > 1980s.
> > >>
> > >> 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
> > >>
> > > ___
> > > 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:
> > 

Re: [Gimp-developer] Learning about GIMP

2018-06-19 Thread Alexandre Prokoudine
On Mon, Jun 18, 2018 at 4:18 PM, jonathan henrick wrote:

> Hello guys im doing a univeristy work and i need that you guys describe the 
> process about changes at GIMP

That sounds kike a very inspecific request to do your homework :)

What do you need to know _exactly_?

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] ANNOUNCE: gimp-data-extras 2.0.4 released

2018-06-14 Thread Alexandre Prokoudine
Hi,

While working on v2.10, we removed scripts that used to be available
via 'File > Create' and 'Filters > Alpha to Logo' submenus. This is
because the scripts generated rather dated-looking graphics mostly of
subpar quality.

However it turns out that some users still want them and ask how they
can get them back. So we moved them to a package we used to maintain,
called gimp-data-extras. It used to contain just brushes and patterns,
now it also contains scripts.

The new release is available from
https://download.gimp.org/mirror/pub/gimp/extras/.

The Git repository is here: https://gitlab.gnome.org/GNOME/gimp-data-extras/

Changes in v2.0.4:

- Updated license to GPLv3+
- Moved brushes to dedicated folders to enable tags
- Moved all patterns to the Legacy folder to tag them accordingly
- Added scripts obsoleted in GIMP 2.10
  ('File > Create' and 'Filters > Alpha to Logo'
  and update some PDB use to match changes in 2.10
- Modernized automake
- Switched to minor/micro versioning

If you are a Linux user, you should be able to install the package
following the usual ./configure && make && make install routine (you
can also ping gimp-data-extras packager of your Linux distribution to
update it). Windows users can simply unpack the archive and copy
scripts to their local GIMP folder.

Please note that while the package is called gimp-data-extras, you
should really treat it as gimp-data-legacy.

Additionally, please note that some of the plug-ins we disabled in
2.10 don't quite belong there for a variety of reasons.

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] Participation at Apple Developer Program

2018-06-14 Thread Alexandre Prokoudine
On Mon, Mar 26, 2018 at 1:45 AM,   wrote:
> I've invited you to fill out the following form:
> Participation at Apple Developer Program
>
> To fill it out, visit:
> https://docs.google.com/forms/d/e/1FAIpQLSdRepYcE1dLD0342FaVGenU0Nr519SyK-MYzdGylmNXYq5rUQ/viewform?c=0w=1usp=mail_form_link
>
> Hi.
>
> Wed like to know opinions of all developers and contributors of GIMP,
> but not everyone is on IRC. Please vote :)
>
> P.S. Collecting emails in this form is disabled. Its safe to vote.
>
> Alex

Jehan reminded me of this, so I looked up the results:

https://imgur.com/a/R5euq4F

I find this so terribly irresponsible that I will donate the annual
membership to whoever is our next official macOS packager.

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] gimptool with 2.99

2018-05-25 Thread Alexandre Prokoudine
пт, 25 мая 2018 г., 21:53 Jean-Luc Coulon (f5ibh):

> Hi,
>
> When I issue "gimptool-2.99 --libs" (from git master), I get:
>
> Package gimpui-2.0 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `gimpui-2.0.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'gimpui-2.0' found
> No output from 'pkg-config --libs gimpui-2.0'
>
> Of course, I dont have gimpui-2.0 but 3.0.
>
> Did I do something wrong?
>

Apart from trying to build and use something currently not intended to be
used at 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


Re: [Gimp-developer] GIMP branched: new stable branch gimp-2-10

2018-05-22 Thread Alexandre Prokoudine
On Tue, May 22, 2018 at 2:04 PM, Elle Stone wrote:

> Will the port to GTK+3 be finished before the apparently planned initial
> release of GTK+4 later this year
> (https://blogs.gnome.org/mclasen/2018/02/03/gtk-hackfests-day-2/)?

How can one possibly provide a realistic estimation of that? :)

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] Missing tools in new Toolbox

2018-05-15 Thread Alexandre Prokoudine
вт, 15 мая 2018 г., 20:16 jEsuSdA 8) :

> Hi!
>
> Could someone tell me how to add extra tools into the toolbox?
>
> I mean: in Gimp 2.8 I was able to insert "desaturate", "colorize", etc.
> tools via Preferences, but in 2.10 there is only a few tools allowed to
> be included.
>
>
> I use some color tools as much as the default one and it was very useful
> to me (and I suppose to other people) add some of them into the toolbox.
>
> Is there any way to add other but the listed ones?
>

Nope. Not without patching GIMP. You can assign custom keyboard shortcuts
though.

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] Participation at Apple Developer Program

2018-03-25 Thread alexandre . prokoudine

I've invited you to fill out the following form:
Participation at Apple Developer Program

To fill it out, visit:
https://docs.google.com/forms/d/e/1FAIpQLSdRepYcE1dLD0342FaVGenU0Nr519SyK-MYzdGylmNXYq5rUQ/viewform?c=0w=1usp=mail_form_link

Hi.

Wed like to know opinions of all developers and contributors of GIMP,  
but not everyone is on IRC. Please vote :)


P.S. Collecting emails in this form is disabled. Its safe to vote.

Alex

Google Forms: Create and analyze surveys.
___
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] GEGL

2018-03-13 Thread Alexandre Prokoudine
On Tue, Mar 13, 2018 at 7:18 PM, Michal Vašut wrote:
> Is GEGL comparable with Blender's node editor

This is a technically incorrect question.

GEGL is an image processing engine. It isn't UI.

It does have a UI which is available optionally, and unlike Blender's
node editor, very few people have used it so far. There also was a
GSoC project to build a conventional node-based editor with GTK+ UI
for GEGL, but it didn't exactly succeed.

> or could it be visualised this way?

It can be, see above.

> Another one: Does Gimp use GEGL localisations (there are some in GEGL
> repository), or it's own?

If GEGL operations are translated into your native language, and GIMP
uses that language in UI, you will see options of those operations in
your native language.

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] Starting contributing slowly

2018-03-07 Thread Alexandre Prokoudine
On Tue, Mar 6, 2018 at 2:22 AM, Kevin Pellet wrote:
> Hi everyone!
>
> I am following this list sincewell, quite a bunch of months now. I
> am a french student in computer science, and for once I am both in a
> mood of being productive and I have some time. So I'd like to help
> contributing to GIMP, and I am emailing the list because I am not sure
> where to start.
>
> I started working on a bug a long time ago, but there was a few points
> that were needed to be discussed so it was kind of blocked (And I lost
> which bug it was). I love to code, I know more about web development
> (JavaScript stuff to be precise), but I already coded in C, C++, Python,
> and even tried Rust! And I am very interested in ux/ui design, even
> though I have no practical knowledges in it or even some degreed.
>
> So, where do I have to start? :p More seriously, I'd like get my hand
> dirty to make GIMP an even more cool software. I know there is a lot of
> work to get 2.10 finished, is there anything I can do to help about this?
>
> Thanks for reading! Have a nice day everyone _o/

Hello and welcome, Kevin :)

Here is the list of all bugs that block the v2.10 release:

https://bugzilla.gnome.org/buglist.cgi?quicksearch=product%3A%22gimp%22%20severity%3Ablocker%20target%3A2.10_id=294963

It looks like #792141 (replacing jasper with openjpeg lib for JPEG2000
support) is now being taken care of by Darshan, our intern from FSF,
and #589371 (improving default set of brushes etc.) is being done by
Americo. The rest is probably free to be worked on.

There is also a bunch of bugs with "normal" and "minor" severity.
Here's the full list:

https://bugzilla.gnome.org/buglist.cgi?bug_status=UNCONFIRMED_status=NEW_status=ASSIGNED_status=REOPENED_id=294966=GIMP_milestone=2.10

What picks your interest there?

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] GSoC project query

2018-03-05 Thread Alexandre Prokoudine
On Tue, Mar 6, 2018 at 2:04 AM, Kevin Cozens wrote:

> Having read the above I had the idea that it could be worth having a student
> work on one or more of the previous GSoC projects

Google is usually extremely unhappy with this.

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] GSoC project query

2018-03-04 Thread Alexandre Prokoudine
On Sun, Mar 4, 2018 at 1:37 PM, Darshan  kadu wrote:
> Hello,
>
> I am Darshan Kadu Intern at FSF working on GNU GIMP as the task of the
> internship.
>
> I would like to contribute to the GNU GIMP as part of GSoC also, as GNU is
> participating too.
>
> But I don't see the page giving any description of the project.
> So does that means I cant contribute to GIMP for GSoC?
> If yes how to proceed further?

Hi Darshan,

We are not participating at GSoC as a standalone organisation, and we
haven't discussed doing it under any umbrella project with any
umbrella project.

P.S. We are GIMP, not GNU GIMP :)

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] 2017 report

2018-01-02 Thread Alexandre Prokoudine
Hi,

Dec 31 was a bit of a busy day, so mentioning the 2017 report here on
the lists was completely forgotten. And yet, here it is:

https://www.gimp.org/news/2017/12/31/gimp-and-gegl-in-2017/

Happy 2018 :)

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] Compiling GIMP-2.9 with the new mypaint requirements

2018-01-02 Thread Alexandre Prokoudine
On Tue, Jan 2, 2018 at 7:42 PM, Alexandre Prokoudine wrote:
> On Tue, Jan 2, 2018 at 4:48 PM, Jehan Pagès wrote:
>
>> Why it worked inside /usr is because this is already in the defaults
>> path of pkg-config for the /usr/ or /usr/local/ prefixes but you have
>> to take care of it for any custom prefix.
>
> Um, I built with --prefix=/usr and GIMP still fails to find it.

OK, so I'm being Mr. Silly, switched to the 1.3 branch, it worked.

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] fix gimp

2017-12-27 Thread Alexandre Prokoudine
On Thu, Dec 28, 2017 at 1:42 AM Boudewijn Rempt wrote:

>
> This, actually, is also how Photoshop works: one Krita developer spoke to
> a Photoshop developer during a recent conference and picked his brain...
> Photoshop makes a copy of the image for _every_ state. Any undo state is a
> shallow copy of the document.


Even for gigapixel panoramas?

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] [FYI] Filter layer implementation in gimp-2.8+

2017-08-07 Thread Alexandre Prokoudine
On Mon, Aug 7, 2017 at 8:09 PM, sigetch wrote:

> As for road-map, it depends on the project's development policy.
> Personally, I think "non-destructive" and "filter layer" is not the same
> thing, because painting tool, transform tool, or other functions also have
> to be "non-destructive" at gimp 3.2.

To the best of my knowledge, we haven't actually discussed how much
exactly would be done in 3.2. We know we want some sort of adjustment
layers for sure.

= snip=

> - Filter should be layer ? or attributes of the layer? I chose filter as
> layer design. GimpFilterStack seems to choose latter one.

IMO, both layer filters and filter layers have their use.

Also, to quote mitch from today's IRC discussion:

"it's a medium joke to implement "adjustment layers" is the generally
used term... in fact a layer *is* a filter on the stack below, just
need to replace gegl:buffer-source by another op, in simple terms"

> -  What kind of filter functions should be applied. In my work, PDB or
> plug-in function is applied. Alternative candidates is to use Gegl
> operations for filter.

GEGL filters are the way to go :)

= snip=

> - What kind of GUI should be provided for filter configuration? PDB
> functions have good configuration dialog, but it is hard to use that kind
> of dialog from outside of PDB process.

GEGL filters can have either automatically generated or custom UIs.
There even is some metadata to help build more sensible UIs, from
using custom widgets instead of regular spinboxes to "adaptive"
layouts. E.g.: https://streamable.com/ajbi4 (available in upcoming
2.9.6).

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] [FYI] Filter layer implementation in gimp-2.8+

2017-08-07 Thread Alexandre Prokoudine
Hello,

I've been wondering when you'd announce that :)

As is usual with your fork, it's impressive work. I definitely like
some of the implementation specifics, although I can see that certain
things could be improved (I can elaborate on that, if you wish).

Unfortunately, this cannot be backported to mainstream GIMP 'as is'.
Off top of my head:

- It's based on GIMP 2.8 that uses obsolete tech.
- Your implementation doesn't use the "new" GimpFilterStack class
(available in git master since 2013) for stacking filters on a layer.
- XCF version in upstream's git master is already 10 now, while you
use v4, so that would make mainstream GIMP and your fork (even more?)
incompatible.

Personally, I'm not sure what is the best approach here.

On one hand, this is something users have been requesting for ages,
and I can already here crowds screaming, how dare I criticize your
work :)). On the other hand, certain changes would need to happen for
this to be merged. On yet another hand, I don't know how this will
play with proposed release order where non-destructive editing is
scheduled for 3.2.

More opinions, please?

Alex


On Mon, Aug 7, 2017 at 5:13 PM, sigetch  wrote:
> Hello all,
> I recently added filter layer (or adjustment layer in other words) in my
> gimp-painter 2.8 branch. You can see how it works at following demo movie.
> https://www.youtube.com/watch?v=ddzAqrppHnk
>
> If you are interested in filter layer, please visit
> https://github.com/seagetch/gimp-painter to see details.
>
> Thanks,
> --
> seagetch
> ___
> 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] 404 on registry.gimp.org reset password page

2017-08-02 Thread Alexandre Prokoudine
On Wed, Aug 2, 2017 at 3:23 PM, Andrew Pullins wrote:
> So I am unable to login post new plugins or comment on others?

Yes.

? Why? Is it a maintenance issue?

Yes, the site was full of spam, and existing anti-spam solutions didn't work.

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] 404 on registry.gimp.org reset password page

2017-08-01 Thread Alexandre Prokoudine
On Tue, Aug 1, 2017 at 11:17 AM, Andrew Pullins wrote:
> I am trying to reset my password but get a 404 error. Bellow is the error I
> am getting.
>
> "404 -- URL not found.
>
> If you came here through a link on the site, we're sorry, but we only
> mirrored the plugin-pages when we went all-static. All other content (e.g.,
> forum posts) is unavailable right now."
>
> Sorry if this is not the place for this.

Translation of the text above into plain English: the site doesn't
work as expected intentionally, you can only download stuff.

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] New metadata editor

2017-07-08 Thread Alexandre Prokoudine
On Sat, Jul 8, 2017 at 10:29 PM, Ben wrote:
> Hello Alex,
>
> For #1 the issue seems to be that once edited in the editor, the new updates
> aren't read by the viewer. If you save and reload the image
> then you get the saved tags. Not sure what's going on there yet but
> that's the gist of it.
>
> Also i fixed a possible crash issue this morning when saving back the
> metadata from the editor which may have affected you with #1.

Well, I was referring to the fact that I expected a DICOM tab in the
viewer and didn't expect the data to show up in the XMP tab.

> For #2 i took a look at it again today and not sure how easily
> i can fix this. What exactly would need for this to work?

I tried placing N_() around messages in metadata-tags.h and adding
metadata-tags.h to POTFILES.in, but that just doesn't cut it. Perhaps
the .ui file needs tweaking as well.

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] New metadata editor

2017-07-08 Thread Alexandre Prokoudine
On Sat, Jun 17, 2017 at 6:00 PM, Ben wrote:
> I've updated the patches for a new metadata editor plugin. It adds support
> for the fields supported by Photoshop/Bridge/Lightroom, and GPS location
> data as well as keeping support for the original GIMP IPTC fields. Now the
> same metadata can be handle between GIMP and Adobe products.

Hello Ben,

I have two questions:

1. The metadata editor seems to provide UI to enter DICOM metadata,
but the viewer doesn't seem to support viewing DICOM metadata. Is that
temporary?

2. Only labels in the editor dialog are translatable. All the
user-visible strings that are in combo boxes etc. are not. Is that
intentional?

Thanks!

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] plugin development on a mac

2017-06-24 Thread Alexandre Prokoudine
24 июня 2017 г. 11:03 PM пользователь "Jason Scherer" <
jason.sche...@gmail.com> написал:

I'm emailing the list to ask: is there anyone else building plugins on a
mac?  Did you have issues getting set up?  Is there really no way to build
plugins other than by building all of gimp from source?


We briefly discussed this a while ago. Ideally, we should provide some sort
of SDK package for macOS. But our .dmg maintainer is a busy dude with not
much spare time.

I'm sure that Partha will share some knowledge on building plug-ins for
macOS. He's been doing that for quite a while.

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] request

2017-06-24 Thread Alexandre Prokoudine
24 июня 2017 г. 8:40 PM пользователь "Ofnuts"  написал:

What Gimp could have is either a counter of the number of times a warning
has been issued (and stop issuing it after a while) or a "Don't tell me
again" checkbox.


So that people treat it like something annoying and disable it, then still
run into the issue?

Personally, I'd rather see a combobox in JOEG exporting options to select
background color, with these options: Black, White, Current Background
Color, Cyrrent Foreground Color.

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] Trouble with building Gimp 2.9.5 against libmypaint

2017-06-24 Thread Alexandre Prokoudine
24 июня 2017 г. 2:27 PM пользователь "Thorsten Stettin" <
thorsten.stet...@gmail.com> написал:


libmypaint: 2.0.0


https://github.com/mypaint/libmypaint/commit/aace2b9bdfb944d40360506d76cb36ae046f0076


https://github.com/mypaint/libmypaint/issues/92

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


  1   2   3   4   5   6   7   >