Hi Sven and tiff maintainer,
Am 28.11.03, 15:00 +0100 schrieb Sven Neumann:
> I agree that it makes sense to make the code for the two plug-ins more
> common since it will make it easier to merge changes between the two
> but I am not going to accept any ifdef's in GIMP CVS that aren't
> strictly
Hi Sven and tiff maintainer,
Am 28.11.03, 15:00 +0100 schrieb Sven Neumann:
> I agree that it makes sense to make the code for the two plug-ins more
> common since it will make it easier to merge changes between the two
> but I am not going to accept any ifdef's in GIMP CVS that aren't
> strictly
Hi Sven and tiff maintainer,
Am 28.11.03, 15:00 +0100 schrieb Sven Neumann:
> I agree that it makes sense to make the code for the two plug-ins more
> common since it will make it easier to merge changes between the two
> but I am not going to accept any ifdef's in GIMP CVS that aren't
> strictly
Hi,
Kai-Uwe Behrmann <[EMAIL PROTECTED]> writes:
> Robin Rowe installed an compatibility layer so nearly all gimp-1.2
> plug-ins can compile. I think this is an essential step to make the
> distance of both applications smaller not greater. As long as we talk
> about plug-ins, why not use the com
Hello,
Am 28.11.03, 01:07 +0100 schrieb Sven Neumann:
> Daniel Rogers <[EMAIL PROTECTED]> writes:
>
> > Sven, I think what he was saying (and please speak up if I
> > misinterpreted your english) that he would like to become the
> > current maintainer of the current tiff plugin.
>
> That is somet
Hi,
Daniel Rogers <[EMAIL PROTECTED]> writes:
> Sven, I think what he was saying (and please speak up if I
> misinterpreted your english) that he would like to become the
> current maintainer of the current tiff plugin.
That is something the current maintainer of the plug-in has to decide.
> I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kai-Uwe Behrmann wrote:
| Hi,
|
| Am 27.11.03, 13:42 +0100 schrieb Sven Neumann:
|
|
|>There is no way a GIMP plug-in can support multiple versions and even
|>a completely different app and at the same time be readable and
|>maintainable code. In my opi
Hi,
Am 27.11.03, 13:42 +0100 schrieb Sven Neumann:
> There is no way a GIMP plug-in can support multiple versions and even
> a completely different app and at the same time be readable and
> maintainable code. In my opinion the version included with GIMP-2.0
> should be a plug-in for GIMP-2.0 and
Hi,
Kai-Uwe Behrmann <[EMAIL PROTECTED]> writes:
> > don't want to include a plug-in that will double the amount of #if and
> > #ifdef statements in the GIMP source tree.
>
> As I like to continue to develop this tiffreader, what would You think is
> appropriate to let the #if / #ifdef macros fa
Am 26.11.03, 22:53 +0100 schrieb Sven Neumann:
> Non-gzipped would certainly have been preferred since it allows to
> comment on the code more easily.
It would become ~140kB so I avoided unzipping for the list readers.
> > the patch for 97352 TIFF plugin shows progress bar when run
>
> That bug
Hi,
Kai-Uwe Behrmann <[EMAIL PROTECTED]> writes:
> So here comes the gzipped code.
Non-gzipped would certainly have been preferred since it allows to
comment on the code more easily.
> The old bugs I had visited and all but one checked. I could not see
> the patch for 97352 TIFF plugin shows pr
Am 26.11.03, 14:38 +0100 schrieb Sven Neumann:
> > Loading it up with my login failed. Are there other ways to send it?
>
> Patches can be send to the gimp-developer mailing-list.
So here comes the gzipped code.
The old bugs I had visited and all but one checked. I could not
see the patch for
97
12 matches
Mail list logo
