My list of unanswered questions has been given a more lasting home. If you have not enough troubles of your own, please see http://srufaculty.sru.edu/david.dailey/svg/svg_questions.htm) for things that have been troubling me.
Of particular interest to me of late has been #6 concerning jig-saw puzzle carving. Here's what I have figured out: 6. To make a jig-saw puzzle using SVG, one may a) chop up an image into little movable chunks using numerous clipPaths applied to numerous copies of an image (see for example, <http://srufaculty.sru.edu/david.dailey/svg/clips2.svg>http://srufaculty.sru.edu/david.dailey/svg/clips2.svg). The problem is that this appears to use lots and lots of RAM and bogs down when the number of rows and columns gets large. For those using IE/ASV see also http://marble.sru.edu/~ddailey/svg/clipembed16.html in which the loci of clipPaths are permutable according to a user-supplied string of less than rows x cols characters. b) <http://srufaculty.sru.edu/david.dailey/svg/later/offsets7.svg>use feOffset's and feTile's to slice an image (be prepared to wait a while for it to render). I didn't see any easier way to grab the parts I wanted to move than this. It is way too time-consuming (I assume this is processor rather than RAM related) to be practical on a large scale. c) build a checkerboard of red-scale values underneath the image and then distort the image using <feDisplacementMap> and the red-channel. See <http://srufaculty.sru.edu/david.dailey/svg/later/displace2.svg>attempt1 or <http://srufaculty.sru.edu/david.dailey/svg/later/displace4.svg>attempt2 by way of illustration. The approach looks like it will be fast and generalize easily to large images with lots of slices. The hassle is that the exact distance by which pixels are moved, while clearly related to the displacement's scale attribute and the red-scale value of the underlying map, seem not to be entirely predictable (see <http://srufaculty.sru.edu/david.dailey/svg/later/displace7.svg>attempt3). The <http://www.w3.org/TR/SVG11/filters.html#feDisplacementMap>W3C spec actually spells out how the pixel loci will move, so maybe I'm just misreading it. The other hassle, of course, is that this uses filters and not many browsers are currently handling it. Is there an easier way? Can I somehow just grab the pixels out of a rectangular section of a bitmap in SVG and move (just) them around? I think I may just be missing something key in the SVG tool set. [Non-text portions of this message have been removed] ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
