Re: RFC: The future of The GIMP

2000-12-18 Thread Fernando Herrera
Just one issue. This "Future of the GIMP" paper doesn't say anyting about GNOME integration. I think this is an important issue. I know that GIMP wants to be plataform independent (just now KDE/GNOME independent, because other Unix vendors as HP-UX, Solaris and AIX are dropping CDE

Re: RFC: The future of The GIMP

2000-12-18 Thread Marc Lehmann
On Mon, Dec 18, 2000 at 03:56:55PM +0100, Fernando Herrera [EMAIL PROTECTED] wrote: Unix vendors as HP-UX, Solaris and AIX are dropping CDE towards GNOME), but GNOME optional support will be very interesting. For example: It will be very easy to make a gnome-frontend for gimp-2.0, as it will

Re: RFC: The future of The GIMP

2000-12-17 Thread Carsten Hammer
Raphael Quinet wrote: I think that it is more important to standardize a method to build and install from source, because that will enable everybody to try the plug-ins as soon as they are released, and this will support many more platforms than the ones that are actively updated by a

Re: RFC: The future of The GIMP

2000-12-16 Thread egger
On 14 Dec, Sven Neumann wrote: Please keep in mind that the main intention of our proposal has been to better distribute work between core and plug-in developers by seperating the source trees during development. Perhaps this scheme could be translated to distribution too, but it does not

Re: RFC: The future of The GIMP

2000-12-14 Thread Rebecca J. Walter
sounds good to me. we do need to also worry about the cost of downloading from the web for european users who often have expensive slower connections. im lucky and have a unlimited usage so could use the convenient web idiot-proof method. Lourens Veen wrote: Jon Winters wrote: We

Re: RFC: The future of The GIMP

2000-12-14 Thread Lourens Veen
Sven Neumann wrote: Please keep in mind that the main intention of our proposal has been to better distribute work between core and plug-in developers by seperating the source trees during development. Perhaps this scheme could be translated to distribution too, but it does not have to. If we

Re: RFC: The future of The GIMP

2000-12-14 Thread Sven Neumann
Hi, Lourens Veen [EMAIL PROTECTED] writes: All true, but then the problem is that non-technical users have to wait for someone (or their favourite distribution) to package new plugins. IE, let's say I write a new plugin, put it on plugins.gimp.org in source form. Then Joe User can't use it

Re: RFC: The future of The GIMP

2000-12-14 Thread Raphael Quinet
Small addition to my previous message: Basically, what we need for distributing the source code of the plug-ins is a mechanism similar to CPAN, except that it should rely on a tool or plug-in distributed with the Gimp and not on Perl. It could also be extended for fetching binaries, but this

Re: RFC: The future of The GIMP

2000-12-13 Thread Sven Neumann
Hi, Tino Schwarze [EMAIL PROTECTED] writes: Why would you want to reinvent the wheel? Follow Unix philosophy: Use tools which are already there. I propose: 1. let the user use the package tool she wants 2. make plugins relocateable (I guess, not only RPM can do that) 3. provide easy

Re: RFC: The future of The GIMP

2000-12-13 Thread Jon Winters
We should keep in mind that the vast majority of Gimp users are not compiling from source. A shell script is not something those folks understand. Their reaction will be... Heh.. Where are all the plugins, this sucks! Then large numbers of them will post to the gimp-devel list wondering WTF

Re: RFC: The future of The GIMP

2000-12-13 Thread Jon Winters
Your last email looks good! Something for everyone! I should have added that the "craplet" that I described could have a "get plugins from CDROM" button that could facilitate installing plugins from CD. You are correct... it is hard to imagine a computer without an internet connection. ;-)

Re: RFC: The future of The GIMP

2000-12-13 Thread Sven Neumann
Hi, Jon Winters [EMAIL PROTECTED] writes: We should keep in mind that the vast majority of Gimp users are not compiling from source. A shell script is not something those folks understand. Their reaction will be... Heh.. Where are all the plugins, this sucks! Please keep in mind that the

RFC: The future of The GIMP

2000-12-12 Thread Michael Natterer
The future of The GIMP December 2000 by Sven Neumann Michael Natterer This document is meant to be a RFC (Request For Comments). Nothing described in here is a fixed decision, everything can and should be discussed. The reason for writing this

Re: RFC: The future of The GIMP

2000-12-12 Thread Lourens Veen
I realise that it's probably too late already, but dare I say C++? Did anyone ever even consider this? As for the plugin distribution, I think the nicest way would be to have a plugin manager that would enable you to download plugins from the web on the fly. Something Linux distributions have

Re: RFC: The future of The GIMP

2000-12-12 Thread Alan
On Tue, Dec 12, 2000 at 05:08:03PM +0100, Lourens Veen wrote: I realise that it's probably too late already, but dare I say C++? Did anyone ever even consider this? As for the plugin distribution, I think the nicest way would be to have a plugin manager that would enable you to download

Re: RFC: The future of The GIMP

2000-12-12 Thread Adrian Likins
On Tue, Dec 12, 2000 at 05:59:56PM +0100, Fernando Herrera wrote: Tue, Dec 12, 2000 at 04:40:54PM +0100, Michael Natterer escribió: o Think about a new way to handle plug-in distribution As more and more plug-ins go into the main gimp distribution (and a lot of plug-ins are wating

Re: RFC: The future of The GIMP

2000-12-12 Thread Jon Winters
Someone today mentioned something about a new way to manage plugins. I think the users would enjoy a plugin manager similar to the Helix Gnome Updater. Users could fire it up from time to time and be presented with a list of plugins to update or add. I think the Helix thing is open source.