<br><br><div class="gmail_quote">On Thu, Apr 17, 2008 at 5:15 AM, Gary Chambers <<a href="mailto:gazzaguru2@btinternet.com">gazzaguru2@btinternet.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It might be nice that we have some more paint rules in BitBlt. A "fuzz/blur"<br>
effect would be nice and take the load off the Squeak code for such things.<br>
<br>
Just wanting to get more contemporary with the ui look without large<br>
performance penalties.<br>
<br>
Not quite liking the way that effects are hidden behind canvas (leading to a<br>
bloated interface, perhaps (c.f. #drawImage... #drawTranslucentImage...)).<br>
Not sure where the balance should be. Looks like a choke-point that is too<br>
useful to bypass on a case-by-case basis.<br>
</blockquote></div><br><br>If you were to implement some more interesting effects in BitBLT, how would you make sure that Morphs that use this code will still work on other targets such as Rome, Postscript Canvases, VNC etc?<br>
<br>Gulik<br><br clear="all"><br>-- <br><a href="http://people.squeakfoundation.org/person/mikevdg">http://people.squeakfoundation.org/person/mikevdg</a><br><a href="http://gulik.pbwiki.com/">http://gulik.pbwiki.com/</a>