Re: [swfmill] (flash8) add linkage to jpg/png directly - *STILL* possible ? + Fonts (Text version of previous post)

[MARTIN Pierre]

Okay nice so, it means that the bitmap "data" is directly wrote to the binary swf, so i guess that loading a bitmap with the "loadbitmap" native is much faster than attaching the clip (depth seeking + stage context updating), getting the bitmap (the player may do a loop on the parent clip to get the target container given on it's name), draw to another bitmap (If memcpy it's fast...) then remove the container MC from the stage (Updating the graphic context again, depth updating)... Because Luke told me that at the end the background was identical because of a "wrapper" i was just wondering how it internaly worked...

Pierre


daniel fischer wrote:

Anyway, i felt kind of "in love" with swfmill and mtasc. Because i work as a C++ developper, i think maybe i can contribute with making a tool such as macromedia font embeding thing? I'm not sure if it already exists, so i need you to give me a guideline on where to look. Also, if i make this thing, i would be very happy if it can handle both X11 server fonts format and windows ttf + otf (i don't know binary format of any yet), so it is portable. The last point is that if i make it, i want it's output to be used both with swfmill, MMCFlash & haxe. That's why i'm telling you this, what's the best: outputing in a SWF file? Outputing to a translated bitmap thing which can be put in the XML that swfmillt will then parses? I don't know enough about fonts & flash yet. But i'm sure you can give me those clues... Anyway, thanks for the help, and good luck to all the team (How many people are actually working on the project?)

MARTIN Pierre <[EMAIL PROTECTED]> (on Fri, 21 Jul 2006 06:55:46 +0200):

  > Don't try with a lower version than 0.2.11.8. Build up your lib like this:

just for the record: dont try lower than 0.2.11.9 :)

  > One question thought... Was this a wrapper related problem? Or was it some direct 
access bitmap data thing? Because, i took the liberty to look at the source code and i had 
not enough time get the available tags list parser... So it's still foggy on my head about 
how it works compared to linking a bitmap with the "clip" keyword?

uhm- i'm not sure what you mean by either "wrapper related problem" nor "direct 
access bitmap data thing".

<clip> imports the bitmap data (DefineBits*), constructs a rectangular shape that uses 
the bitmap as "texture", and defines a sprite (MovieClip) that places the shape. This 
sprite is given the id you specify in the clip tag.

<bitmap>, on the other hand, assigns the id you specify directly to the DefineBits 
tag. It's simply that this wasn't of any use before flash8, and the <clip> method is 
what i observed from IDE output.

-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