Closed GoogleCodeExporter closed 9 years ago
I agree that raster images should be supported in SVG-edit.
I've been thinking about this a bit. To continue to keep this a client-side
app only
I believe we will only be able to import the raster image via a URL.
Original comment by codedr...@gmail.com
on 8 Jul 2009 at 1:00
i concur. it has to be by URL.
Original comment by Christia...@gmail.com
on 8 Jul 2009 at 1:46
The widgetized version could support browsing for images directly, see http://
dev.opera.com/libraries/fileio/. You could browse for files, then read it to
base64
and then use it, or alternatively use a virtual mountpoint url while editing
and
then save it to base64 when exporting.
However, it'd be quite cool if you could search for and import images directly,
e.g
from flickr or some clipart site.
Original comment by erik.dah...@gmail.com
on 19 Aug 2009 at 6:09
I've attached a patch that gets including rasterized images to mostly work
including
setting the URL and resizing (though it doesn't stretch the image out of the
original
aspect ratio, which could be both a feature and a bug). It needs an icon for
the
image icon which isn't included in the patch (but still attached) called
image.png in
the editor/images directory (taken from tango). Another potential issue is that
the
default image URL is images/logo.png coded into svgcanvas.js which might have
slight
problems if you're decoupling svgcanvas.js and svg-editor.js. Also, after
drawing an
image, the editor locks you off from drawing almost any other shape because the
image
has no stroke or fill.
Original comment by Antimatter15
on 30 Aug 2009 at 4:09
Attachments:
Thanks a lot for this patch! If you don't mind I'm going to keep it off of the
trunk
until we branch for 2.3 (hopefully within a week or two).
Original comment by codedr...@gmail.com
on 31 Aug 2009 at 1:10
Original comment by codedr...@gmail.com
on 1 Sep 2009 at 3:10
So at least one issue left with this feature:
- fill/stroke get messed up when including an image (when an image is selected,
the
fill/stroke/opacities should not be changed (to 'none')
Original comment by codedr...@gmail.com
on 5 Sep 2009 at 11:21
Oddly the bug doesn't happen all the time though.
Original comment by codedr...@gmail.com
on 5 Sep 2009 at 11:35
Fixed final issue with this feature in r588.
Original comment by codedr...@gmail.com
on 5 Sep 2009 at 6:35
Original issue reported on code.google.com by
Christia...@gmail.com
on 8 Jul 2009 at 8:56