Here’s my way: A nifty JSFL script that recursively searches for PNG files and leaves corresponding SWFs next to them!I’ve noticed it bog down when trying to handle hundreds and hundreds of larger PNGs, so I highly recommend saving all .FLAs you have open before running this since if it can’t handle the load - Flash will crash. I’ll look into a fix for this when I get a moment. Let me know if you think of a good way to prevent it - I haven’t had a spare moment to take a look.

Save this to your commands folder ( download link after the code ):

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77

// author: Jeff Yamada
// warning: this might destroy your computer
 
fl.outputPanel.clear();
var dom = fl.getDocumentDOM();
var baseURI = fl.browseForFolderURL("Select a folder.");
var exportedSWFS = new Array();
var folderNumber = 0;
 
findPNGs( baseURI );
 
function findPNGs( folderURI )
{
	var directories = FLfile.listFolder( folderURI, "directories" );
	var files = FLfile.listFolder( folderURI + "/*.png", "files" );
	var i;
	if( directories != false )
	{
		for( i = 0; i < directories.length; i ++ )
		{
			var directory = directories[i];
			var type = FLfile.getAttributes( folderURI + "/" + directory );
			switch( type )
			{
				case "D":
				case "DH":
					findPNGs( folderURI + "/" + directories[i] );
					break;
				default:
			}
		}
	}
	if( files != false )
	{
		for( i = 0; i < files.length; i ++ )
		{
			convertPngToSWF( folderURI, files[i] );
		}
		clearLibrary();
	}
}
 
function convertPngToSWF( pngURI, fileName )
{
	var swfName = fileName.substring( 0, fileName.lastIndexOf( "." ));
	var swfURI = pngURI + "/" + swfName + ".swf";
	exportedSWFS.push( swfURI );
	dom.importFile( pngURI + "/" + fileName );
	dom.exportSWF( swfURI, true );
	clearStage();
}
 
function printReport()
{
	fl.trace( '==== ' + exportedSWFS.length + ' swfs created from pngs ====' );
	fl.trace( exportedSWFS.join( "\n" ));
}
 
function clearStage()
{
	dom.selectAll();
	dom.deleteSelection()
}
 
function clearLibrary()
{
	var libItems = dom.library.items;
	for( var i = 0; i < libItems.length; i ++ )
	{
		var item = libItems[i];
		dom.library.newFolder( "folder"+folderNumber );
		dom.library.moveToFolder( "folder"+folderNumber, item.name );
	}
	folderNumber++;
}
 
printReport();

png2swf.jsfl.zip

http://www.richinternet.de/blog/index.cfm?entry=911D4B57-0F0D-5A73-AF6F4D4D04099757

So far I’m LOVING this little plugin. A++!:)

1
2
3
4
5
6
7
8
9
10
11

var vars:URLVariables = new URLVariables();
vars.email = "your@emailaddress.com";
vars.password = "password";
vars.type = "photo";
vars.caption = "This is the photo caption!"; // optional ( and can use html )
 
var request:URLRequest = new URLRequest( "http://www.tumblr.com/api/write" );
request.method = URLRequestMethod.POST;
request.data = vars;
 
file.upload( request, "data" );

Yeah, I know, that was way too obvious, and a lame post, but I am trying to squeeze as much out of my wasted 4 hours as I can, so thanks for reading. 

I think one of the toughest parts of presenting is knowing what your audience already knows. I’m always afraid I’m covering material everyone is already well aware of. If anyone reading has any suggestions for going about this I’d love to hear. I’ve been writing the AIR Bible for a few months now and am finding the task of delivering content that is useful to both advanced and beginner developers at the same time to be highly challenging. I personally prefer to read something that is a little over my head, I can always re-read it and do the required research and experimentation to try and catch up, but I really don’t like textbooks that offer little to nothing that isn’t obvious. I once picked up a C# textbook and was rather disappointed that it spent a whole chapter on Arrays. I don’t blame the authors really, its really tough to know who your audience is, and there doesn’t seem to be a very obvious way of separating programming basics from the nature of a specific language or platform.

I’ll continue on with my struggle to deliver good material for all, but again would love to hear feedback on the subject, thanks in advance!

http://developer.mozilla.org/devnews/index.php/2007/12/18/firefox-3-beta-2-now-available-for-download/.

The runtime - What you need to run AIR apps.

The SDK - What you need if you don’t want to use either Flash CS3, Flex 3 Beta 3, or Dreamweaver

FlexBuilder 3 - What I use to develop. I occasionally use FlashDevelop, but rely on FlexBuilder for mostly all my actionscripting.

I really am enjoying working with Ben and Ryan, and all the research and learning that goes into writing. Most of all I’m really enjoying the aspect of giving back to the Flash/Flex community and contributing to the learning experience of fellow developers. The book is shaping up pretty well and I hope for and look forward to it being as helpful as so many textbooks have been for myself.

We should be on the book shelves sometime in the spring of ‘08, so keep an eye out!

I’m going to give an ultra quick rundown on getting started with developing applications in the Adobe AIR Platform. Its supposed to be only 10 minutes with a 5 minutes Q and A, so it will definitely be rapid. I’m hoping to get to “Hello World” at the very least though.

I’ll actually be jetting back to the FITC after party right after this, but there should be time to get there before the Schematic crew is totally hammered. I’m looking forward to this insane day!