• L2709_Presentation.ppt
• L2709_Workbook.pdf
• FlashP2PLib.fxpl
• MAX2011MobileVideoChat.fxp
• EyeChat.fxp
• EyeChatDesktop.fxp

The last two projects are completed versions that you can use for testing or to skip ahead.

I plan to follow up with posts related to the P2P logic used in this sample application. Any questions, let me know. Thanks to all who attended!!

L2709_DSMVCA.zip

PROS

• Support SVG + HTML 5

- canvas
- scaleable
- accessible text

• Generate CSS3
• Live, selectable text

- use JS to manipulate

• Lots of power to chop up designs (think PS slices)
• CSS Export!!! (Export Selected as CSS)

- export object
- export object styles
- export text styles via Character Styles tab
- export gradients!!

• Link to exported CSS via DW
• FREE download from Adobe Labs on 9/13 (Get it Today!!)

CONS

• Doesn’t generate HTML; just CSS
• IE9 can render natively; older versions have to use a plugin

Would write more but I’m anxious myself so I’m off to install my copy and start creating!!!

To view the demo in its own window, click here.

1. Open the following files:
a) /install_dir/sdks/3.5.0/bin/jvm.config
b) /install_dir/sdks/4.0.0/bin/jvm.config

2. Locate the following line found under # Arguments to VM:

java.args=-Xmx384m -Dsun.io.useCanonCaches=false

3. Increase the memory size to a larger value like the following example:

java.args=-Xmx512m -Dsun.io.useCanonCaches=false

The max you set this value to is determined by your available memory along with some workflow considerations but this should alleviate your heap issues and smooth out Flash Builder compilations considerably…

Dear Steve,

After reviewing your recent comments regarding Flash and the recent amendments to the Apple Developer TOS, I decided to share with you my response to a few of your positions. First, with regards to 3.3.1, Apple should only do QA based on app quality and NOT on app origin. Are we to seriously believe that an iPhone app built with Unity, Flash, etc. pails in comparison technologically to one built via Xcode? Are we to further believe that there are ABSOLUTELY NO poorly written Obj-C apps in the app store? If so, where are the benchmarks and metrics to support these claims?

Logical decisions are typically made based on data collection in some form or fashion. In the absence of such information, those “logical” decisions are eventually revealed to be more subjective in nature vs. being purely objective. Again, if there is data to support the claims against iPhone apps developed in Flash and compiled to *.ipa, please point us to that data.

Now, as to your assertion that Flash is the #1 reason Macs crash, again, we’d like to see empirical data that supports this claim. Having used apple desktop and laptop computers for more than a decade, I’d have to respectfully disagree with you. I’ve personally experienced kernel panics resulting from locked up processes with non-Flash applications (eg, iTunes, Safari, etc). To my knowledge, iTunes makes no use of Flash but yet it has caused my system to enter into a kernel panic on several occasions. Are we still to believe that Flash is the only big bad wolf lurking in the OSX forest? I seriously hope that’s not your intention. Will your position change when Adobe produces a Flash Player version that takes full advantage of hardware acceleration? I certainly hope so because then we’ll know that you’re truly the visionary tech leader that we all hope you to be.

Does this absolve the Flash development community from doing our part to improve the situation? NO!!! Unfortunately, many Flash apps are created by would-be developers that have no clue about memory management, garbage collection and the like. It is far too easy to create Flash apps that consume all of a browser’s memory, don’t close properly and eventually obstruct a user. But, I submit that this same fact holds true regardless of the language or platform used to create said applications. In other words, sloppy coding is the problem not the technology. This is from the perspective of a developer fluent in several languages including Obj-C and ActionScript.

I understand you have your business goals and a board of directors to please, but I implore you to work with Adobe rather than against them. Work with Google, Facebook and the like to make the future of technology truly open which benefits us all. Ultimately, we MUST support a free market economy in order to achieve this technological utopia, the results of which will be exponential growth that lasts for a millennium. Yes, it truly can be that explosive. The only thing standing in the way is our present day greed for money and power.

I sincerely hope that you soften your stance and work with the other technology leaders to usher us into that state of tech bliss…

P E A C E

Hasan

Whether you’re upgrading because you’re using BETA versions that change rather frequently or upgrading to the next major release, you don’t want to lose all your hard work invested in configuring your setup. Here’s how I handle it and hopefully it’s useful to you. If you have other cool ways to persist workflows between upgrades, please share them.

Workspaces

I’ve created a workspaces folder in a custom directory on my HD where I store all the workspaces I like to use with Eclipse-based IDEs. I separate them by IDE and then by purpose. So for Flash Builder, my workspace hierarchy is like this:

/workspaces
  /_fb4
    /air
    /as
    /flash
    /flex

This is where all of my IDE preferences and workbench layout settings are stored. Centralizing them here allows me greater flexibility when upgrading since I never have to worry about any changes to installation procedures overwriting my custom settings. Nevertheless, I backup my workspaces prior to upgrading and since their small text files it only takes a second to archive.

Documents Directory

On OSX, the Flash Builder installer creates an Adobe Flash Builder 4 directory in your Documents directory. The installation instructions advise you to uninstall any previous versions of Flash Builder before installing the new version. Following this advice will delete this folder if it already exists. So, be sure to back this up prior to uninstalling your current version. That way you can cherry pick anything you need after installing the new version.

Applications Directory

You should also backup up your program installation in your Applications directory for the same reasons as with the folder in your Documents directory. If you’ve heavily modified your install with additional plugins, etc., this is vital!

Plugin Restoration

Where are all my cool plugins? They got wiped during the upgrade process but if you followed my advice and backed everything up, you’ll be back up and running in a minute or two. There are generally (2) locations where plugin info is stored for Flash Builder. If you pull the data from your backups and place them in the following locations, you should have full access to all your plugins post-upgrade (provided they still work with the latest release)

#1 – /Documents/Adobe Flash Builder 4/.metadata/.plugins
#2 – /Applications/Adobe Flash Builder 4/plugins

Although this post is slanted more towards upgrading on OSX, it should be similar for other operating systems. Any issues, let me know…

I’m truly honored to have been chosen as a member of this select group and look forward to expanding my community efforts throughout this new year. Having missed FlashCamp Brasil this past weekend, this revelation makes the trip to FITC Amsterdam that much more rewarding. See you there!!