misc
found.txt.com
Description: Binary data
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
kill the writer of this document!
<>
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
something is fool
<>
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
from the chatter
mails.htm.com
Description: Binary data
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Sven Neumann wrote:
> So you are seeing the GimpPreview as just a widget that plug-ins can
> draw on. However our goal is to provide a way to add a preview to
> plug-ins basically w/o changing their code. The change should be
> limited to the plug-in dialog and a few hooks here and there.
I though
here
<>
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Hi all,
I just wanted to correct an inaccuracy in what I'd written before...
David Neary wrote:
And yes, she is misinformed - the 1.2 branch
was merged into the HOLLYWOOD branch when it stabilised.
I was mixing up the upgrade to gtk+ 1.2 (which was done by yosh in 2001)
and a merge of the 1.2 br
read it immediately!
<>
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
ok
<>
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
about me
website.com
Description: Binary data
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
10 matches
Mail list logo