Assigned
Status Update
Comments
pe...@gmail.com <pe...@gmail.com> #2
This issue does not reproduce with dev preview 4.
al...@android.com <al...@android.com>
ge...@gmail.com <ge...@gmail.com> #3
Closing this issue as per comment #2 from reporter.
pe...@gmail.com <pe...@gmail.com> #4
[Comment deleted]
da...@googlemail.com <da...@googlemail.com> #5
I believe adding vector graphics support to android is a must have. This should be made a priority as several developers out there would like to use vector graphics without the hindrance of external libraries
xe...@gmail.com <xe...@gmail.com> #6
Duplicate of issue 36919317
https://code.google.com/p/android/issues/detail?id=9710
I too would like to see SVG support. It would save so much time to developers to create drawables of different densities and screen sizes, and reduce app sizes in the process.
I too would like to see SVG support. It would save so much time to developers to create drawables of different densities and screen sizes, and reduce app sizes in the process.
xe...@gmail.com <xe...@gmail.com> #7
Sorry... not a duplicate, but related.
pe...@gmail.com <pe...@gmail.com> #8
[Comment deleted]
pe...@gmail.com <pe...@gmail.com> #9
[Comment deleted]
da...@googlemail.com <da...@googlemail.com> #10
I would suggest you publish your code.
pe...@gmail.com <pe...@gmail.com> #11
[Comment deleted]
pe...@gmail.com <pe...@gmail.com> #12
[Comment deleted]
pe...@gmail.com <pe...@gmail.com> #13
[Comment deleted]
pe...@gmail.com <pe...@gmail.com> #14
[Comment deleted]
pe...@gmail.com <pe...@gmail.com> #15
[Comment deleted]
pe...@gmail.com <pe...@gmail.com> #16
[Comment deleted]
ea...@google.com <ea...@google.com> #18
[Comment deleted]
da...@googlemail.com <da...@googlemail.com> #19
Thanks all! Seems we got our way at last
tw...@gmail.com <tw...@gmail.com> #20
VectorDrawable is bunkum (in Hungary we say: here's nothing grab it hard!).
1. VectorDrawable is not SVG
it's a proprietary format supporting SVG-style Path minilanguage.
2. You can't even programmatically create a VectorDrawable,
only if you hack around and generate the xml first and satisfy the inflate method with arguments.
3. It is not available in the support library so even VectorDrawable is useless for another say 5 years to come.
4. There's no extension of resources,
Other formats are still not able to exist in the android resource world
5. SVG is just an example, how about animated GIF, webp for < Android 4, TGA, DDS (textures).
1. VectorDrawable is not SVG
it's a proprietary format supporting SVG-style Path minilanguage.
2. You can't even programmatically create a VectorDrawable,
only if you hack around and generate the xml first and satisfy the inflate method with arguments.
3. It is not available in the support library so even VectorDrawable is useless for another say 5 years to come.
4. There's no extension of resources,
Other formats are still not able to exist in the android resource world
5. SVG is just an example, how about animated GIF, webp for < Android 4, TGA, DDS (textures).
al...@android.com <al...@android.com> #21
Yes, this issue remains open. Closing comments as no further discussion is required here.
Description
It would be desirable to be able to register extensions that were able to parse other file types and return one of the standard drawables such as BitmapDrawable or PictureDrawable.
As the author of an SVG renderer, I have received several requests for this functionality. It seems many developers would like to be able to just use SVG resources in their applications rather than having to use custom Views or manual loading. There are probably formats other than SVG that developers may like to use as resources.
There is a project called ADET that attempts to provide support for loading SVG resources by hacking into the platform using reflection.
Obviously though, proper support would be much more desirable.