Re: [Gimp-developer] What's new in GIMP-1.3 so far

2003-06-19 Thread David Necas (Yeti)
ht 2.0 would be GEGL based, support CMYK, 16bit channels, ... and when 2.0 is released I can't see any trace of these, I'm disappointed. - When I thought 1.4 would still be Gtk+1 based, and when it's released I see it's Gtk+2 based, I'm delighted. Regards, Yeti

Re: [Gimp-developer] Plug-in preview API proposal

2003-04-03 Thread David Necas (Yeti)
-keeping to preview, and it seems > to work. That's great. Then I can answer your original question, yes, as a below-average-plug-in-developer, I'd use it. Just please update the API reference, it still says the render function has to be reentran

Re: [Gimp-developer] Plug-in preview API proposal

2003-04-02 Thread David Necas (Yeti)
On Thu, Apr 03, 2003 at 01:15:31AM +0200, Ernst Lippe wrote: > P.S. I just modified my preview so that the re-entrancy problem has > been eliminated. Excuse me, but which reentrancy problem has been eliminated? Does it mean the render function no longer needs to be reentrant? Regards,

Re: [Gimp-developer] Plug-in preview API proposal

2003-04-01 Thread David Necas (Yeti)
ot; alone is strange It's quite easy to invent new words and phrases for me, thanks to my miserable English ;-) but "proof view" seems to be already invented, according to Google. Regards, Yeti ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Gimp 1.2.4 Final?

2003-03-20 Thread David Necas (Yeti)
s a conflicting additional restriction on further distribution and modification. A least this is how I understand it. Yeti ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Re: caching considerations in gegl

2003-03-11 Thread David Necas (Yeti)
7;t care about alpha, and what I really care about is transparency. So everything what was said can be repeated, only s/alpha/transparency/. My need for pixels retaining their properties even in invisible state didn't disappear. Yeti ___ Gimp-de

Re: [Gimp-developer] caching considerations in gegl

2003-03-11 Thread David Necas (Yeti)
Alpha = (Alpha1 + Alpha2)/2 PremulChannel = (PremulChannel1 + PremulChannel2)/2 on premultiplied alpha. Blurring with black only occurs when you don't combine pixels and just increase alpha of a pixel. Yeti ___ Gimp-developer mailing list [EMAIL P

Re: [Gimp-developer] Re: caching considerations in gegl

2003-03-11 Thread David Necas (Yeti)
more complex way than necessary? Or did I missed something? Yeti ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] caching considerations in gegl

2003-03-11 Thread David Necas (Yeti)
8 The tool will work along the same lines (there are matrices and such stuff, but the idea doesn't change). There are no doubts how pixels should be blended together (which is what blur does), the only source of controversy is handling of alpha of indi

Re: [Gimp-developer] caching considerations in gegl

2003-03-11 Thread David Necas (Yeti)
On Tue, Mar 11, 2003 at 07:15:16PM +0100, Raphaƫl Quinet wrote: > On Tue, 11 Mar 2003 18:55:33 +0100, "David Necas (Yeti)" <[EMAIL PROTECTED]> wrote: > > Your example is fine, except for the last step using Noisify on the > alpha channel. As Adam pointed out i

Re: [Gimp-developer] caching considerations in gegl

2003-03-11 Thread David Necas (Yeti)
ibed -- purely experimentally -- while they don't know there's anything like layer mask, and mabye will never find out. Yeti ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] caching considerations in gegl

2003-03-11 Thread David Necas (Yeti)
correct" in some sense and in some situations. However, Gimp uses separate alpha channel internally thus I see as illogical to force the other mental model. Yeti ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] tile row hints (was: caching considerations ingegl)

2003-03-11 Thread David Necas (Yeti)
rily make some area transparent just to give some its parts nonzero opacity later as a useful feature, the rest of world obviously thinks otherwise ;-( Yeti ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] gimp-perl moved into its own CVS module

2003-02-28 Thread David Necas (Yeti)
On Fri, Feb 28, 2003 at 10:07:30PM +0100, Marc A. Lehmann wrote: > On Fri, Feb 28, 2003 at 09:19:17PM +0100, "David Necas (Yeti)" <[EMAIL PROTECTED]> > wrote: > > You need cookies to log in, so you generally need cookies to > > change anything (what brower do y

Re: [Gimp-developer] gimp-perl moved into its own CVS module

2003-02-28 Thread David Necas (Yeti)
need JS (though it may improve user experience in a few places). You need cookies to log in, so you generally need cookies to change anything (what brower do you use? bugzilla works even in lynx). You don't need anything to search for bugs, wget is enough if you know what y

Re: [Gimp-developer] Re: http://developer.gimp.org/

2003-02-10 Thread David Necas (Yeti)
> and netscape will happily skip the second stylesheet. OK, and when one wants everything in one CSS file, he/she can make use of NN's inability to parse comments (so-called Caio's Hack), this is probably even better solution:

Re: [Gimp-developer] http://developer.gimp.org/

2003-02-10 Thread David Necas (Yeti)
rty trick http://centricle.com/ref/css/filters/ to make it see no/other/only part of the style sheet, e.g. @import url("bigstyle.css") Since people still use NN 4.x, they should be able to display the pages in some readable (not nice)

[Gimp-developer] gimpbilinear and alpha

2003-02-07 Thread David Necas (Yeti)
authors using them hardly can handle alpha blending correctly. IMHO functions operating on whole pixels are needed more than the existing ones (though they are also useful). Regards, Yeti --- gimp.orig/libgimpcolor/gimpbilinear.c 2002-11-20 22:29:15.0 +0100 +++ gimp/libgimpcolor

[Gimp-developer] IFSCompose and bugzilla question

2003-02-01 Thread David Necas (Yeti)
te Center menu items visible as buttons, so people who don't try right clicking in the design area know about them * changed confusing numeric frame title to "Transformation n" * changed the button layout to two centered groups (it looked approximately this way before too, but prob

Re: [Gimp-developer] New Gimp FAQ: Call for questions

2002-12-19 Thread David Necas (Yeti)
zillion things user can do wrong, if he/she is clueless, and when you finally find them all, the first user you test your novice mode on will find a new one. IMHO novice mode (if ever implemented) should restrict the things user can do to some sane set (simpl

Re: [Gimp-developer] Re: alpha vs. transparency / translucency

2002-12-19 Thread David Necas (Yeti)
ng would change (think about all the hscales, entries and curves). Yeti ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

[Gimp-developer] gimp_coordinates and "value_changed"

2002-11-10 Thread Yeti
elivered when the value changes, which work regardless of the chain button state? (Disassembling the GtkTable and connecting directly to spinbuttons/entries doesn't count, though it surely is a way). Thanks, Yeti ___ Gimp-developer mailing list [EMA

Re: [Gimp-developer] tile cache size (was Re: The Occasional BugList)

2002-11-07 Thread Yeti
So the formula would be something like: > min (32 MB, max (free * 0.9, total - 64 MB)) Didn't you mean something more like max (32 MB, free * 0.9, total - 64 MB) ? The way you wrote it no one would get more than 32MB, which probably

[Gimp-developer] GFlare fixes [patch]

2002-11-05 Thread Yeti
flare/gflare.c 2002-11-05 18:50:16.0 +0100 @@ -4148,7 +4151,7 @@ gtk_widget_show (toggle); entry = ed->polygon_entry = gtk_entry_new (); - gtk_widget_set_usize (entry, ENTRY_WIDTH, 0); +// gtk_widget_set_usize (entry, ENTRY_WIDTH, 0); g_snprintf (buf, sizeof (