Again, I don't personally see any value in doing this. There is no issue in having a dependency on the SVG JARs, either from a licensing or deployment perspective, and you'd only be saving a single class (Drawing) in the WTK JAR. You'd need to add it to another JAR, which will probably *increase* download size slightly. Finally, as I mentioned, you'll lose the ability to specify SVG files in markup:
<ImageView image="@foo.svg"/> So this gets a big -1 from me. On Sep 8, 2011, at 10:02 AM, Sandro Martini wrote: > Hi Greg, > >> Image is the base class for Picture and some other internal image classes > as well. Moving it outside of WTK would basically eliminate all graphic > support in the platform. Probably not a good idea. > Yes for sure it will not be a good idea :-) . > So I'll try to strip out only the svg part from it, and move in another > class (if possible that extends ImageView). > >> My mistake - should have been "@foo.svg". > Don't worry ... > > So if there aren't other objections I could try to prototype something (for > the 2.1), and commit only new classes (in new subproject) before making any > change (deleting/removing some code) in old ones ... > > I'll create a JIRA ticket targeted to 2.1, just for reference. > > Bye, > Sandro > > > -- > View this message in context: > http://apache-pivot-developers.417237.n3.nabble.com/Move-Wtk-classes-related-to-SVGSalamander-in-a-dedicated-wtk-svg-or-similar-subproject-inside-Pivot-tp3317312p3319811.html > Sent from the Apache Pivot - Developers mailing list archive at Nabble.com.
