Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
> > The ranges aren't enforced because we don't have the EXSLT > > math functions available. If that's a problem they should be easy to > > compile in. > > we dont? exslt has been in for a while for it's str: module (some > tokenization, i cant recall where). ain't the math part in the default > libexslt? Ahh - missing the math: prefix. Anyhoo, they work with nodesets, not with arbitrary values, so that don't do what I need. I've just added upper- and lower-limit boundary checking the card way http://swfmill.org/trac/changeset/160 > > All this is part of the following changeset: > > http://swfmill.org/trac/changeset/159 > > looks good. Groovy! > > Note that I made a 'global' variable of the movie version, since it > > only makes sense to add the tag if the movie version is greater than > > 7. > > fine, why not? Cool! > > PS. Noticed that you'd applied a change commenting out static linking > > in the swft Makefile.am. I might have mistakenly left that in one of > > my patch files and should probably be uncommented. > > uhm- static linking on osx, /sigh/. i recently checked in release-mac.sh that > i run to compile on osx. you might notice some rather ugly manual linking > step, i never had autoconf properly link statically on osx- thankful for any > advice :) Pah - I commented out the static linking because I couldn't get it to compile. > it's great to see somebody give some care to swfmill, really. I <3 swfmill ;o) > what do you think about finally doing 0.2.12 around 1st? i'd ask the regulars > on this list for some broader testing before weekend, so we can finally get > this load of bugfixes and flash8 tags out the door... in fact i wouldn't care > too much about some "flash8 compatible" claim, but instead ask for testcases > and requests about what you/we've missed about it 'til now, for a followup > 0.2.13... I think this is a good idea. Cheers, Steve -- Steve Webster http://dynamicflash.com ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
Sweet! "just what i'd have done". "Steve Webster" <[EMAIL PROTECTED]> (on Tue, 25 Jul 2006 16:38:22 +0100): > The ranges aren't enforced because we don't have the EXSLT > math functions available. If that's a problem they should be easy to > compile in. we dont? exslt has been in for a while for it's str: module (some tokenization, i cant recall where). ain't the math part in the default libexslt? > All this is part of the following changeset: > http://swfmill.org/trac/changeset/159 looks good. > Note that I made a 'global' variable of the movie version, since it > only makes sense to add the tag if the movie version is greater than > 7. fine, why not? > PS. Noticed that you'd applied a change commenting out static linking > in the swft Makefile.am. I might have mistakenly left that in one of > my patch files and should probably be uncommented. uhm- static linking on osx, /sigh/. i recently checked in release-mac.sh that i run to compile on osx. you might notice some rather ugly manual linking step, i never had autoconf properly link statically on osx- thankful for any advice :) it's great to see somebody give some care to swfmill, really. what do you think about finally doing 0.2.12 around 1st? i'd ask the regulars on this list for some broader testing before weekend, so we can finally get this load of bugfixes and flash8 tags out the door... in fact i wouldn't care too much about some "flash8 compatible" claim, but instead ask for testcases and requests about what you/we've missed about it 'til now, for a followup 0.2.13... -dan -- http://0xDF.com/ http://iterative.org/ ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
> > shall i step back and let you teach that to swfml-simple? > > Can do. Won't be until this evening though. Done early. Specified like this: Possible values/defaults render: - simple (default) : No anti-alias rendering. - advanced : Use advanced anti-alias rendering grid: - none (default) : Do not align to grid - pixel : Align text to pixel grid - sub-pixel : Align text to sub-pixel (1/3 pixel) grid. Good for LCS monitors. thickness: - -200 to 200 sharpness: - -400 to 400 The last two define the inside and outside clipping for font glyph rendering. The ranges aren't enforced because we don't have the EXSLT math functions available. If that's a problem they should be easy to compile in. All this is part of the following changeset: http://swfmill.org/trac/changeset/159 Note that I made a 'global' variable of the movie version, since it only makes sense to add the tag if the movie version is greater than 7. Nice! PS. Noticed that you'd applied a change commenting out static linking in the swft Makefile.am. I might have mistakenly left that in one of my patch files and should probably be uncommented. -- Steve Webster http://dynamicflash.com ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
Hi Dan, > thanks for the details.. No worries. > > > > > thickness="-47.0" sharpness="100.0"/> > > > > > > ...or maybe just add those attributes to the element. > > Maybe not though, since it already has lots. > > i agree, let's take the first route, although i'd opt to call it > "text-settings", if only to avoid possible confusion with whatever other > settings we might come across. > > render="advanced" would be useFlashType="1"? Yes. > shall i step back and let you teach that to swfml-simple? Can do. Won't be until this evening though. Cheers, Steve -- Steve Webster http://dynamicflash.com ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
Steve, thanks for the details.. "Steve Webster" <[EMAIL PROTECTED]> (on Tue, 25 Jul 2006 14:22:50 +0100): > >thickness="-47.0" sharpness="100.0"/> > > > ...or maybe just add those attributes to the element. > Maybe not though, since it already has lots. i agree, let's take the first route, although i'd opt to call it "text-settings", if only to avoid possible confusion with whatever other settings we might come across. render="advanced" would be useFlashType="1"? shall i step back and let you teach that to swfml-simple? -dan -- http://0xDF.com/ http://iterative.org/ ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
> "simple" support for this should be (as you said) easy-- i'd just need some > clearing up-- > > a) the "objectID" in CSMTextSettings, would it refer to a font or a textfield? Any one of DefineText, DefineText2 or DefineEditText. > b) what sane values can gridFit take? 0 - No grid fitting 1 - Pixel-level grid fitting 2 - Sub-pixel (1/3 pixel) grid fitting - apparently good for LCD screens > c) what's the range of thickness and sharpness (although that's really > irrelevant for the simple tag). Thickness: -200 to 200 Sharpness: -400 to 400 > d) would this look ok (assuming "font" as answer to a), and "dunno" for b)): > > sharpness=".5"/> > > or should we maybe add that info to either or (dependent > on answer a)?, probably as a contained "" tag? A contained tag might be best. Something like this? ...or maybe just add those attributes to the element. Maybe not though, since it already has lots. Cheers, Steve -- Steve Webster http://dynamicflash.com ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
Hey Dan, > > DefineFontInfo3 and DefineFont3 are complex beasts which contain > > hinting information for font glyph pairs. I wouldn't even know where > > to start with this. > > i suppose you mean kerning, not hinting? kerning was/is already supported > with DefineFont2, it was simply unused by the FlashIDE until flash8. the late > players seem to interpret it fine (see http://0xdf.com/?p=50 ). So unless > it's really "hinting", DefineFont3 would be interesting only for swf2xml > magic. I wouldn't know where to get hinting info from-- TTF supposedly > contains a turing-complete hinting language, which is patent-encumbered. i > doubt flash supports much like that (tho i might be mistaken). It really is hinting - sort of. The new DefineFontAlignZones tag (which we're calling DefineFontInfo3) defines the borders of each glyph to use pixel snapping. Don't know where I got the 'pairs of glyphs' bit from - I might have skipped a page onto the kerning information. Full hinting is seemingly beyond the capabilities of the Flash Player. > Personally, i'd be fine with the current (minimal) > DefineFontInfo3/DefineFont3 support. It means those tags can be imported > fine, and that should be what matters most. But then again, i'd personally be > fine without any flash8 tags (it would decrease me having to resort to wine > :)... > > if anyone requires swfmill to fully understand those tags, please at least > come up with a usage scenario :) I agree with this. At the very least now they will round-trip from swf => xml => swf Cheers, Steve -- Steve Webster http://dynamicflash.com ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
"Steve Webster" <[EMAIL PROTECTED]> (on Tue, 25 Jul 2006 13:55:45 +0100): > (http://swfmill.org/trac/changeset/158) "simple" support for this should be (as you said) easy-- i'd just need some clearing up-- a) the "objectID" in CSMTextSettings, would it refer to a font or a textfield? b) what sane values can gridFit take? c) what's the range of thickness and sharpness (although that's really irrelevant for the simple tag). d) would this look ok (assuming "font" as answer to a), and "dunno" for b)): or should we maybe add that info to either or (dependent on answer a)?, probably as a contained "" tag? -dan -- http://0xDF.com/ http://iterative.org/ ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
"Steve Webster" <[EMAIL PROTECTED]> (on Tue, 25 Jul 2006 13:55:45 +0100): > Well, I at least got the DefineTextInfo tag sorted out (which MM > actually call CSMTextSettings) in swfmill-ll syntax > (http://swfmill.org/trac/changeset/158) and basic syntax shouldn't be > too hard to add. cool, i'll check it out... > DefineFontInfo3 and DefineFont3 are complex beasts which contain > hinting information for font glyph pairs. I wouldn't even know where > to start with this. i suppose you mean kerning, not hinting? kerning was/is already supported with DefineFont2, it was simply unused by the FlashIDE until flash8. the late players seem to interpret it fine (see http://0xdf.com/?p=50 ). So unless it's really "hinting", DefineFont3 would be interesting only for swf2xml magic. I wouldn't know where to get hinting info from-- TTF supposedly contains a turing-complete hinting language, which is patent-encumbered. i doubt flash supports much like that (tho i might be mistaken). Personally, i'd be fine with the current (minimal) DefineFontInfo3/DefineFont3 support. It means those tags can be imported fine, and that should be what matters most. But then again, i'd personally be fine without any flash8 tags (it would decrease me having to resort to wine :)... if anyone requires swfmill to fully understand those tags, please at least come up with a usage scenario :) -dan -- http://0xDF.com/ http://iterative.org/ ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
hey Dan, > > so, now there's only one bug (out of former 9) left (#4, > > http://swfmill.org/trac/ticket/4), and for that i'd need more info. > > DefineFontInfo3 and DefineFont3 (as noted above) are minimally-supported. > > about DefineTextInfo, i'd need more info/reverse-engineering. if someone > > can find info about this, or at least produce sample SWFs using the "custom > > anti-alias"/"anti-alias for readability" settings, please do so, and attach > > to the bug report (along with one with plain settings, for comparison). > > I've been inspired by your work and will see if I can get this > implemented at lunch time. Well, I at least got the DefineTextInfo tag sorted out (which MM actually call CSMTextSettings) in swfmill-ll syntax (http://swfmill.org/trac/changeset/158) and basic syntax shouldn't be too hard to add. DefineFontInfo3 and DefineFont3 are complex beasts which contain hinting information for font glyph pairs. I wouldn't even know where to start with this. Cheers, Steve -- Steve Webster http://dynamicflash.com ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
MARTIN Pierre <[EMAIL PROTECTED]> (on Tue, 25 Jul 2006 14:25:09 +0200): > What you mean by "device fonts"? Does it embed the font in the SWF still? .. i thought that was flash lingo :) the "device" in "device fonts" relates to the output device- usually some pc running the flash player. "device fonts" means using either one of the two fonts that come with flash player (_sans and _serif, AFAIK), or a font installed on the user's system. this is really only good if you want to keep filesize to a minimum for some reason. if you prefer good design, embed your font :) i would guess you'd find many posts on flashcoders or similar relating to device fonts for the more intricate details. -dan -- http://0xDF.com/ http://iterative.org/ ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
Hello, a little question for you Dan: What you mean by "device fonts"? Does it embed the font in the SWF still? Thanks, Pierre. daniel fischer wrote: hey all, the oven-fresh prerelase 0.2.11.14: http://swfmill.org/pre/swfmill-0.2.11.14.tar.gz http://swfmill.org/pre/swfmill-0.2.11.14-win32.zip http://swfmill.org/pre/swfmill-0.2.11.14-macosx.zip completes my late round of fixing reported bugs. compared to yesterday, this includes: - another fix for DefineText2 (bug #5) - minimal support for DefineFontInfo3 and DefineFont3 (so these can now be imported) - fix import of assets with filenames containing special characters (long-standing bug #1) - this has only been tested on linux, but i'm optimistic :) - support for "device fonts". if you want to use device fonts, do something like: so, now there's only one bug (out of former 9) left (#4, http://swfmill.org/trac/ticket/4), and for that i'd need more info. DefineFontInfo3 and DefineFont3 (as noted above) are minimally-supported. about DefineTextInfo, i'd need more info/reverse-engineering. if someone can find info about this, or at least produce sample SWFs using the "custom anti-alias"/"anti-alias for readability" settings, please do so, and attach to the bug report (along with one with plain settings, for comparison). hope this showed some initiative and that reporting bugs actually gets them fixed (or at least thought about) -- some day :) phew, it's gonna be a long list of changes for 0.2.12! -- anyone interested in working over the docs? -dan begin:vcard fn:MARTIN Pierre n:MARTIN;Pierre org:Creative Hazard adr:;;17 rue de Verdun;Nontron;Dordogne;24300;France email;internet:[EMAIL PROTECTED] tel;home:+33 5 53 56 18 36 x-mozilla-html:TRUE url:http://www.CreativeHazard.com version:2.1 end:vcard smime.p7s Description: S/MIME Cryptographic Signature ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
Re: [swfmill] [ANN] prerelease 0.2.11.14 - bug count down to 1
Hey Dan, > completes my late round of fixing reported bugs. compared to yesterday, > this includes: > - another fix for DefineText2 (bug #5) > - minimal support for DefineFontInfo3 and DefineFont3 (so these can > now be imported) > - fix import of assets with filenames containing special characters > (long-standing bug #1) - this has only been tested on linux, but i'm > optimistic :) > - support for "device fonts". if you want to use device fonts, do > something like: > > The man is on fire this week. Nice work! > so, now there's only one bug (out of former 9) left (#4, > http://swfmill.org/trac/ticket/4), and for that i'd need more info. > DefineFontInfo3 and DefineFont3 (as noted above) are minimally-supported. > about DefineTextInfo, i'd need more info/reverse-engineering. if someone can > find info about this, or at least produce sample SWFs using the "custom > anti-alias"/"anti-alias for readability" settings, please do so, and attach > to the bug report (along with one with plain settings, for comparison). I've been inspired by your work and will see if I can get this implemented at lunch time. By the way, are we still waiting for my swfmill-s support for filters or did I fix that already? It's been so long... Can someone tell me what we're now missing in terms of Flash 8 support? Maybe add a ticket or two to the Trac setup? Cheers, Steve -- Steve Webster http://dynamicflash.com ___ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
