Comments for ini na!!

Comment on Why I might not want to use Flex by Ahmad Fathi Hadi

Ahmad Fathi Hadi — Tue, 30 Dec 2008 07:21:10 +0000

Indonesian Flash Platform Community

itu user group kan mas ?

Comment on Why I might not want to use Flex by admin

admin — Tue, 23 Dec 2008 18:10:57 +0000

@Fathi, usergroup yang mana ya?

Comment on Why I might not want to use Flex by Ahmad Fathi Hadi

Ahmad Fathi Hadi — Tue, 23 Dec 2008 17:20:16 +0000

Selamat yah buat User Group-nya !

Comment on Why I might not want to use Flex by Michael Forrest

Michael Forrest — Mon, 08 Dec 2008 11:14:03 +0000

Hi - I just found your blog, seems very clear.

Since you’re talking about the pros and cons of Flex, here’s my impassioned thinking about why I don’t like using Flex either

http://grimaceworks.com/blog/221_Why+I+don‘t+like+Flex

Comment on Why I might not want to use Flex by julien

julien — Mon, 01 Dec 2008 15:47:09 +0000

as a java developer, i really encourage you to take a look @ flex, you’ll like it

Comment on Looking Flex Developer by Teddy Sopyan

Teddy Sopyan — Wed, 26 Nov 2008 03:23:33 +0000

Wah…
Aku tertarik banget ni ama artikel nya …
Bagus banget untuk masa depan dunia web …
Oh iya kpn2 aku mo konsultasi ttg flex …
tapi aku nggak tau hrs kmn / lewat YM mana ..??
klo YM ku sama dgn alamat e-mail ku ,…
aku tunggu ya ..

Comment on Externalize Font with font subset, font weight and font style at the same time by gowai

gowai — Thu, 09 Oct 2008 03:17:12 +0000

thanks. that’s solve my problem.

Comment on Externalize Font with font subset, font weight and font style at the same time by localToGlobal » Blog Archive » news review -> 40th week of 2008

localToGlobal » Blog Archive » news review -> 40th week of 2008 — Sat, 04 Oct 2008 09:08:10 +0000

[…] > ini na!! » Blog Archive » Externalize Font with font subset, font weight and font style at the same time […]

Comment on Externalize Font with font subset, font weight and font style at the same time by admin

admin — Tue, 30 Sep 2008 20:53:01 +0000

Hi Rich,

Thanks for the comment..

Yup I think, the difference between the way I was doing is it only need one font file for embedding all style and weight of font, whereas you did for Arial Narrow need 4 font files (Arial Narrow.ttf, Arial Narrow Bold.ttf, Arial Narrow Italic.ttf, Arial Narrow Bold Italic.ttf).

IMHO, with only need one font to externalize, I think it will easier for working with some rare fonts (and we didn’t need font family for reference the bold/italic style).

BTW, I’ve countered compile error if embedding some fonts with combining fontWeight/fontStyle with unicodeRange.

Thanks!

Comment on Externalize Font with font subset, font weight and font style at the same time by Rich Rodecker

Rich Rodecker — Tue, 30 Sep 2008 20:29:07 +0000

Hmm..

Unfortunatelly if we combining subset tag (unicodeRange) with fontWeight / fontStyle tag will cause a Flex compile error.

I don’t believe this is the case, as I do it for all the fonts I export. You can see this right in the code I posted at the article you linked to (http://www.visible-form.com/blog/dynamically-loading-fonts-at-runtime/).

Flex still generates a seperate FontAsset reference for each version of the font you embed, so as far as I can tell, the only real difference between the way you are doing it and the way i was doing is that you are embedding a swf first, and referencing the the embedded fonts, whereas I referenced the ttf files directly.

Whatever works though…probably shouldn’t be such an issue in the first place.