<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 25.04.2009, at 09:38, Karl Ramberg wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <div bgcolor="#ffffff" text="#000000"> On 2009-04-24 23:13, Jerome Peace wrote: <blockquote cite="mid:79433.10261.qm@web50301.mail.re2.yahoo.com" type="cite"> <pre wrap="">Hi Karl,
--- On Fri, 4/24/09, Karl Ramberg <a class="moz-txt-link-rfc2396E" href="mailto:karlramberg@gmail.com"><karlramberg@gmail.com></a> wrote:
</pre> <blockquote type="cite"> <pre wrap="">From: Karl Ramberg <a class="moz-txt-link-rfc2396E" href="mailto:karlramberg@gmail.com"><karlramberg@gmail.com></a>
Subject: Re: [Etoys] alpha property
</pre> </blockquote> <pre wrap=""><!----> </pre> <blockquote type="cite"> <pre wrap="">I think this would be a nice addition to the Etoys image as
well, with some needed integration with Etoys.
</pre> </blockquote> <pre wrap=""><!---->It is the etoy integration that is the problem.
Look at how etoys handles things.
Etoys has hobbled itself to avoid some bugs with translucency.
First it comes up default with a 16 bit display.
At that depth no translucency can be shown.
Switching to 32 bit depth can correct that.
But it doesn't help.
Sketch morphs have slots for the original form.
and a rotated form.
The last is the original form processed by the rotation/stretching/scaling that has be done to the sketch by the handles.
It is the rotated form that actually gets displayed.
In the processing the form is forced to be depth 16.
So you will never see translucent sketches
even if the base graphic and original form are translucent.
This is what stumped me.
Work arounds are hard to come by.
An ImageMorph is the other way to hold a form for display.
It was designed to be simple and does not allow direct scaling.
Etoys makes it very hard to get an ImageMorph and has no natural way for putting an image into one.
That leaves putting an image in a BitmapFill.
This might work but not from tiles.
And it is questionable to put time into development
when the mindset is hide faults by hobbling the languages abilities.
As you might be hearing from my tone, I am somewhat disappointed.
Yours in curiosity and service, --Jerome Peace
</pre> </blockquote> <br> Uh, I did not know this...<br> Well, I guess it should be posted as a bug/enhancement project on the bug tracker.<br></div></blockquote></div><div><br></div><div>It's a trade-off. At 16 bpp we have to shove around only have as much data as in 32 bpp. Our painting tools do not support alpha transparency. If you use translucency and gradients, powerful tiles like color-sees do not work as well. That's also the reason why we don't smooth rotated sketches, because it alters the colors. </div><div><br></div><div>Now that said, we actually do support alpha transparency in 16 bpp. You can take an ellipse and set its alpha to 50 and it works. One could do the same for images. Perhaps even more powerful would be a special kind of holder that would adjust all its childrens' transparency. That way, any object could be made translucent by embedding. </div><br><div> <span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Lucida Grande; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><div style="font-family: Helvetica; "><span class="Apple-style-span" style="font-family: Helvetica; ">- Bert -</span></div><br class="Apple-interchange-newline"></div></span> </div><br></body></html>