Community Professional

Today was a terrific day for me as I was awarded among 239 other individuals Community Professional. This was a world wide search and of those 239 members awarded I am honored to be among them. Thank you very much Adobe, for this opportunity

Of course with any of these mentioned transformations, the origin point is always used when determining the new calculations. When dealing with offsets many people have been using the following way to adjust the origin point.

var newOriginX:uint,newOriginY:uint;
     newOriginX=newOriginY=16
var matrix:Matrix= new Matrix()
     matrix.translatePoint(newOriginX,newOriginY)
     matrix.rotate(45)
     matrix.translatePoint(-newOriginX,-newOriginY)

I prefer to use the actual properties and believe in the convenience of its setup, so I wanted to share another way since I could not find it documented online anywhere.

Both the above code and the following code produce the same effect. This is known as an Affine Transformation

var cos:Number=Math.cos(theta)
var sin:Number=Math.sin(theta)
 
 
        var matrix:Matrix = new Matrix()
	matrix.a=cos;matrix.b=-sin;matrix.tx=newOriginX-newOriginX*cos-newOriginY*sin;
	matrix.c=sin;matrix.d=cos;matrix.ty=  newOriginY+newOriginX*sin-newOriginY*cos;

Branching has always been a popular visual in the world of flash, and makes for a great experiment using the Canvas tag because one truly needs to optimize their code to the fullest.
Here I plant seeds around the cursor of the mouse and allow those seeds to grow to a specific length, and allow at random more seeds to grow from the current branches.

This experiment is highly optimized except for making reuse of dead seeds, which leaves me an area for improvement which is always good. This means that I can squeeze more speed out of the experiment.

Since Fire Fox does not yet implement the feature of forcing specific redraw areas, also known as: Dirty Rectangles, this experiment does not run well at all on Fire-Fox and should only be viewed on Chrome or Safari.

View the experiment here: Veins4

We promise to have much more for our audience when we return. Cheers.

The emergence of Javascript is what fuels the statement of HTML5 being the harbinger of Flash’s failure, but what allows HTML5 to gain the credit is the new introduction of the CANVAS tag. This tag is what everyone has seen that has caused the commotion within the industry.

Is it safe to say HTML5 is the actual user of this tag, or is the power behind this tag really gathered from Javascript? To answer this question really makes no difference, because the end result is that you need both Javascript and HTML to make these amazing things achievable. Will an html developer suddenly replace a flash developer?

Absolutely not. If “HTML5″ was to replace flash the answer would be a Javascript developer. It would be the role of the Javascript developer to manage the data that would be interpreted by the browser based on HTML5 specifications that are then fed to the canvas tag to achieve what has only been achieved with flash.

Its important to note that I have made many many tests with html5 which will soon be posted, and have found a few things that I would state as hurdles or road blocks from this really surpassing a plugin. So far the canvas tag is broken with Text being used on ios before version 4. Text is written upside down and no where near its origin point. This brings me to a critical point of the HTML5 proposal to surpass Flash. This fix can easily be made by Apple with an update to the software, but until they implement this or other browsers implement this, one remains at the mercy of building for many circumstances and less for global reach. This means that Site budgets will still have to increase if a client demands to have their site viewable for every device: Computer, Ipad, Iphone , and all browsers. If the time frame needs to be met within a specific period, this means the agency will need to toss more hands onto the project which means higher labor costs. In the end companies will be less encouraged to have sites that work well for every device to save costs.

If they don’t care about this, then forget everything I stated in the last paragraph, although this will most likely never be the scenario for the advertising world.
Flash on the other hand does infact reach its audience only having to be written 1 time and one time only. This is because the player interprets the code and never varies based on browser implementations.

This keeps the cost of a flash budget from deviating from multiple builds.

Another nice feature of HTML5 specifications is the CSS revision. CSS3 has finally allowed developers to round corners more easily than it previously has been to achieve a desired design, and has now implemented a native implementation for displaying fonts a user may not have on their computer. This has been achieved though unconventional methods of adding many fonts into a folder in different formats that can be read by a browser/device specific to what is required. This feature is currently at the mercy of 2 possible issues. The first is that many fonts have a clause that you can not offer a font to the public in a changed manner from which it originated. Meaning if I turn a .ttf into an .svg I have breached the Terms and conditions of the font and can find myself on the end of Charges from the font maker. The second issue to this latest feature, is that each font format differs in their file size, meaning to render certain fonts might take longer to load and display than others depending on the viewers broswer/client.

This leads me to wonder why so far no standard has been implemented in Javascript and HTML for tapping into the browser to determine how many bytes are loaded of how many total bytes. In my opinion, this very simple addition would allow for HTML5 to be more like flash.

So far, HTML5 appears to be the wet dream of a javascript developer who always wanted to get into flash or processing, but never wanted to learn a new language other than javascript, but in my opinion of being a flash developer using HTML5 currently at work, flash was this well ahead of its time. Flash is a language that found a way through a plugin, to break away from all unique flaws of each browser, and supplied direct content to the user without the developer having to code things more than once. Actionscrip 1 is in fact of the ECMA script language and is a mirror image of Javascript. ActionScript 3 is nothing more than the rein-visioning of a web language that has not been hindered by 3 different browsers because they did not have to make any changes to their software for the developers work to be more than what it was.

Do I feel HTML 5 is truly a flash killer? Absolutely Not. Do I feel that Agencies might be too afraid to sell Flash? Absolutely yes.
HTML 5 has gained a lot of recognition among the tech world due to Apple’s refusal to add flash to their alternate devices to a computer. This can cause an issue to the flash community because flash developers don’t have a say in what a client wants. If a client hears the buzz over HTML 5 or Flash this is what the client will want.