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
On Thu, 14 Dec 2000, [EMAIL PROTECTED] wrote:
This one covers a lot of things I previous mentioned in a bit better tone.
Quoting comes from Raphael Quinet's post #12115.
Wow, finally a person who understands my concerns, and is actually an
active gimp developer, so that things could really
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
Marc wrote on Mittwoch, 13. Dezember 2000 21:21:
On Wed, Dec 13, 2000 at 04:36:16PM +0100, Tino Schwarze
[EMAIL PROTECTED] wrote:
There is _no_ Unix way.
Yes, there is:
Look at Netscape's shortcuts, e.g. "Close Window".
They are all configurable ;) I, for example, press alt-f4
"Garry R. Osgood" wrote:
Here is what I propose:
1. There is now a "latency" bug where, when the curve tool is brought up
with a non-identity transform, it is not immediately applied
(when preview is on) - yes, this is indeed easily fixable. Although if
we reset, it doesn't matter ...
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
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
