I wrote the Script File Migration Program.
It was used by MS Visual Studio C#.
The target is to migrate the simple and basic scripts to the new API 3 in
GIMP 2.99 (GIMP 3).
Yes, Scheme and Python, both.
It is still Draft level yet.
Scheme file was almost done, but, Python file is not complete yet.
Dear Jehan Pagès
Thanks a lot. Your detailed answers help me. :)
Q1.
> It looks like a limitation of this __gproperties__ syntax, but maybe I
> missed something in how this syntax works.
> And this is all why it's such a mess. Of course, maybe a best way might be
> to define all properties with
Derailment...
Only by seeing the code... (Not try yet)
In Foggify.py, a variable name "name" conflict with the "name" of the
property registration?
This is probably because the label string 'name' no longer appears in the
dialog.
(Only showing the TextBox default-valued "clouds".)
If so, in that
t;
> On 24/08/2021 17:31, ShiroYuki Mot via gimp-developer-list wrote:
> > I wrote the Script File Migration Program.
> > It was used by MS Visual Studio C#.
> > The target is to migrate the simple and basic scripts to the new API 3 in
> > GIMP 2.99 (GIMP 3).
> > Yes,
On my previous post, the following blocks is wrong.
>
(First, Can we replace 'pdb.' to 'null'?.)
Please forget it. And Please remove it.
PS;
When I tried from The Console, The applied last result from the Procedure
Browser shows '[ ]'.
It's not user friendly, a bit.
At the white space place, we
Sometimes we can get the value as ResultTuple in GIMP 2.99.
When we write a Python Script, Is it OK using a hard cording '[1]' after
the function in order to get the real value?
(ex. col_1=Gimp.context_get_foreground()[1] )
(If in GIMP 2.10, col_0=gimp.context_get_foreground() )
Perhaps,
including many wrong points. UTF-8 CrLf)
2021年8月2日(月) 19:08 Jehan Pagès :
> Hi!
>
> On Mon, Aug 2, 2021 at 9:38 AM ShiroYuki Mot via gimp-developer-list <
> gimp-developer-list@gnome.org> wrote:
>
>> It is the Question (same as
>> https://gitlab.gnome.org/GNOME/g
cause
>>> everyone wrote a bit of what they wanted, but with time and more people
>>> giving time into it, the documentation will organize itself.
>>>
>>
>> Let's port! Thanks.
>>
> Cool!
>
> Jehan
>
>>
>> PS;
>> I tri
write docs. Sure there will be changes, and
>>>>> sure it means some of the docs will be wrong and need to be changed before
>>>>> release. But better start early and fix as we go than write dozens of
>>>>> pages
>>>>> of documentation a
It is the Question (same as
https://gitlab.gnome.org/GNOME/gimp/-/issues/7114)
Please teach me.
At the next coming 2.99.8, the Python script will avoid the crash. (See
#7106 (closed))
(https://gitlab.gnome.org/GNOME/gimp/-/issues/7106)
So, One question I have. It is not the issue!.
Can I rewrite
Maybe not a high priority.
After Script-Fu called (ex. guides-new.scm), Verbose Output said,
> procedure_commands_get_display_args: plug-in procedures expecting a single
> drawable are deprecated!
The result of the script is quite normal.
I suspect the procedure (gimp-displays-flush), but I
In the official page at
https://www.gimp.org/news/2022/08/27/gimp-2-99-12-released/,
You say that "with all gettext catalogs under the locale/ folder of the
plug-in directory, and named the same way as the plug-in itself".
Please teach me 'How TO do that'.
On OS, Windows, If I placed my script
└── LC_MESSAGES
> │ └── ofn-guides-presets.mo # messages for French
> └── ofn-guides-presets.py # plugin code
>
> And yes, using 'gimp30-python' in your own scripts doesn't make much
> sense (it does for scripts delivered with Gimp, that share the message
> base with other co
>> │ └── LC_MESSAGES
>> │ └── ofn-guides-presets.mo # messages for French
>> └── ofn-guides-presets.py # plugin code
>>
>> And yes, using 'gimp30-python' in your own scripts doesn't make much
>> sense (it does for scripts delivered wit
itself, and as I understand it, if the I18N domain is the same
> >> name as the plugin file, you don't even need to define this
> >> method,
> >> because it's the default behavior.
> >>
> >> Then you create the .mo file(s
15 matches
Mail list logo
