On 11/24/15, 12:06 AM, "omup...@gmail.com on behalf of OmPrakash
Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:

>On Mon, Nov 23, 2015 at 11:54 PM, Alex Harui <aha...@adobe.com> wrote:
>
>>
>>
>> I decided to take a quick peek.  It looks like a change was made to have
>> charts use mx:Label instead of s:Label by default.  That could result in
>> some surprises for folks who haven't embedded non-CFF fonts in their
>>apps.
>>  The mustella tests embed both CFF and nonCFF fonts and thus only see
>> subtle rendering differences between TextLine and TextField.
>>
>> I'm a bit worried about the backward compatibility impact.  What do
>>others
>> think?  Of course, I could be wrong...
>>
>>
>For me, this fixed a major issue with Charts.  So, I am okay with this.  I
>am used to adding the same font twice, once as CFF and once as nonCFF.
>IMHO, this is not a big deal.
>I believe this is one of those times where only Mustella would complain
>:-)

Well, I suppose we'll find out ;-)

Was it ever possible to use Spark Label and embedded fonts in a Chart?
Maybe nobody is really in this situation.  Otherwise, someone who was
relying on some CFF capability will be broken, but maybe right-to-left
text and other CFF stuff don't work in Charts.

Did Charts have other dependencies on MX?  Or are there folks using
Spark-only projects that will now have compile issues?  Would it be better
to fix the ability to use Spark Label in Charts?  What is the impact on
Mobile apps when you embed both fonts or start using MX controls in Mobile
apps?

Thoughts?
-Alex

Reply via email to