RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

Addressing one of the gimp vision items..."easy installation of plug-ins"

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

Rob Antonishen
2010-05-14 16:13:13 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

I was reading the gimp vision again, and two things jumped out:

- GIMP is easily user-extendable, by easy installation of plug-ins - GIMP should be easily extensible by the average user: one click-installation of plug-ins

and was wondering if this could be implemented within the current codebase as follows:

Pick a new extension .gegz that will mean a gimp extension (precompiled or python) plugin or script installation package.

This will just be a gz file with a new extension.

Write a file load handler to handle this extension that will:

Unzip the file to a temp directory.

Inside the zip file will be all the necessary files for the python/binary plugin or script as well as a file (xml?) that would provide information on the contents: - type (scm file, python extension, binary+platform) - registered name
- payload list

The file load handler could then check to see if the thing is already installed using the name
The file load handler could move the files to the appropriate loaction The file load handler could refresh scripts, if a scm script or provide a message that gimp needs to restart if a plugin/python.

Is there a roadmap for something like this already anywhere?

-Rob A>

Martin Nordholts
2010-05-14 17:17:00 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

On 05/14/2010 04:13 PM, Rob Antonishen wrote:

I was reading the gimp vision again, and two things jumped out:

- GIMP is easily user-extendable, by easy installation of plug-ins - GIMP should be easily extensible by the average user: one click-installation of plug-ins

and was wondering if this could be implemented within the current codebase as follows:

[...]

Is there a roadmap for something like this already anywhere?

I agree installation of plug-ins is a pain, but I'm not aware of anyone planning to work on improving the situation.

/ Martin

Akkana Peck
2010-05-14 23:00:46 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

Martin Nordholts writes:

On 05/14/2010 04:13 PM, Rob Antonishen wrote:

- GIMP should be easily extensible by the average user: one click-installation of plug-ins
[...]

I agree installation of plug-ins is a pain, but I'm not aware of anyone planning to work on improving the situation.

Writing a file handler like Rob describes sounds easy -- if all you care about is script-fu. The hard part would getting Python and C plug-ins installed for users (especially Windows users) who don't have Python, PyGTK or a C compiler.

...Akkana

Jernej Simon?i?
2010-05-14 23:07:33 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

On Friday, May 14, 2010, 23:00:46, Akkana Peck wrote:

Writing a file handler like Rob describes sounds easy -- if all you care about is script-fu. The hard part would getting Python and C plug-ins installed for users (especially Windows users) who don't have Python, PyGTK or a C compiler.

Python and PyGTK+ will be included with GIMP 2.8.

Michael Schumacher
2010-05-14 23:08:54 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

On 14.05.2010 23:00, Akkana Peck wrote:

Writing a file handler like Rob describes sounds easy -- if all you care about is script-fu. The hard part would getting Python and C plug-ins installed for users (especially Windows users) who don't have Python, PyGTK or a C compiler.

Getting Python plug-ins installed wouldn't be the problem, they just won't run if the requirements aren't met. But this is supposed to change with future installers...

Regards, Michael

Alexia Death
2010-05-14 23:16:01 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

On Sat, May 15, 2010 at 12:00 AM, Akkana Peck wrote:

Martin Nordholts writes:

On 05/14/2010 04:13 PM, Rob Antonishen wrote:

- GIMP should be easily extensible by the average user: one click-installation of plug-ins
[...]

I agree installation of plug-ins is a pain, but I'm not aware of anyone planning to work on improving the situation.

Writing a file handler like Rob describes sounds easy -- if all you care about is script-fu.  The hard part would getting Python and C plug-ins installed for users (especially Windows users) who don't have Python, PyGTK or a C compiler.

This file handler should also be able to handle all other resources gimp has like brushes, patterns, dynamcs, tool presets etc. Its been considered for a long time and If my time wasnt aready booked full I would look into it myself.

Rob Antonishen
2010-05-15 19:16:23 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

The biggest first step would be to define the package xml syntax. After that, resource types could be added. I agree that only scripts, binaries, and python plugins would make sense to package this way. Anything needing compiling would be out of scope.

-Rob A>

On 5/14/10, Alexia Death wrote:

On Sat, May 15, 2010 at 12:00 AM, Akkana Peck wrote:

Martin Nordholts writes:

On 05/14/2010 04:13 PM, Rob Antonishen wrote:

- GIMP should be easily extensible by the average user: one click-installation of plug-ins
[...]

I agree installation of plug-ins is a pain, but I'm not aware of anyone planning to work on improving the situation.

Writing a file handler like Rob describes sounds easy -- if all you care about is script-fu.  The hard part would getting Python and C plug-ins installed for users (especially Windows users) who don't have Python, PyGTK or a C compiler.

This file handler should also be able to handle all other resources gimp has like brushes, patterns, dynamcs, tool presets etc. Its been considered for a long time and If my time wasnt aready booked full I would look into it myself.

--
--Alexia
_______________________________________________ Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Martin Nordholts
2010-05-15 19:59:17 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

On 05/15/2010 07:16 PM, Rob Antonishen wrote:

The biggest first step would be to define the package xml syntax. After that, resource types could be added. I agree that only scripts, binaries, and python plugins would make sense to package this way. Anything needing compiling would be out of scope.

If you do that, please
1. Collaborate with other create.freedesktop.org programs on the format 2. Prefer existing package formats before custom ones

/ Martin

peter sikking
2010-05-15 20:35:36 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

Rob Antonishen wrote:

I was reading the gimp vision again, and two things jumped out:

- GIMP is easily user-extendable, by easy installation of plug-ins - GIMP should be easily extensible by the average user: one click-installation of plug-ins

and was wondering if this could be implemented within the current codebase

I thought I discussed this last year with somebody who really wanted to build us a repository...

there is two things I want to say that are requirements for this one.

one click _really_ means one click. this one click is either:

- in some website; - inside a plug-in browser within GIMP; or - on the desktop, but only when it was not received by the 2 methods above (e.g. from a friend on a USB stick).

the other thing that is important is that GIMP should not have to be restarted for the new plug-ins to appear and work.

my 2 cents,

--ps

founder + principal interaction architect man + machine interface works

http://mmiworks.net/blog : on interaction architecture

Liam R E Quin
2010-05-15 22:05:33 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

On Sat, 2010-05-15 at 20:35 +0200, peter sikking wrote:

one click _really_ means one click.

"Click here to install a virus?"

Martin Nordholts
2010-05-15 23:16:02 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

On 05/15/2010 10:05 PM, Liam R E Quin wrote:

On Sat, 2010-05-15 at 20:35 +0200, peter sikking wrote:

one click _really_ means one click.

"Click here to install a virus?"

So we should have an "Are you sure you want to install this plug-in?"-popup or what? :)

I don't think viruses will be a problem in practice if we host a user-moderated plug-in registry on www.gimp.org for example. We could also have support for digital signatures so users can verify that the claimed provider of a plug-in is genuine. That way they can restrict themselves to providers they trust.

https://addons.mozilla.org/ is a good source for inspiration here.

/ Martin

Liam R E Quin
2010-05-15 23:28:57 UTC (almost 15 years ago)

Addressing one of the gimp vision items..."easy installation of plug-ins"

On Sat, 2010-05-15 at 23:20 +0200, Martin Nordholts wrote:

On 05/15/2010 10:05 PM, Liam R E Quin wrote:

[...]

"Click here to install a virus?"

[...]

I don't think viruses will be a problem in practice if we host a user-moderated plug-in registry on www.gimp.org for example. We could also have support for digital signatures so users can verify that the claimed provider of a plug-in is genuine. That way they can restrict themselves to providers they trust.

Right, I agree, it just has to be thought about.

Liam