I had a head scratcher earlier tonight. My wife was able to see the website I’d just launched for her, but I wasn’t. There we were, sat on the same sofa using the same wi-fi with the same UR in our web browsers and yet, we were seeing different websites. How come?
I’m not a server administrator so it took a few minutes to realise that it was to do with which DNS servers we were using. When a new website is launched it can take a couple of days for the new IP address to propegate through all the DNS servers around the world. Because the update happened so recently we realised that we were using different DNS servers, one of which had updated and the other which hadn’t.
The solution was surprisingly simple.
Apple > System Preferences > Network > Advanced > DNS
On the left hand side of the screen you’ll see some IP addresses. The IP address at the top is the one that you’re currently using to surf the web. Simply drag another IP from further down the list to the top. Press OK > Apply and refresh your browser to see if things change.
It’s been eleven years since Steve Jobs revolutionised our back-pockets with the iPhone and dealt Flash w
hat many thought would be a mortal blow. So why is it Flash refuses to die? The recent update of the same in-all-but-name Adobe Animate was incredible.
In banishing the humble SWF to the wilderness I Steve broke something more fundamental, progress. With all, it’s faults Flash tried new things, and challenged conventions. The conservative development community chose standards over tearing up the rule-book and in doing so may have stifled creative expression.
I recently did a project for coca-cola, which required a dynamic flip clock to count-down to Christmas, but it involved an intricate transition involving Christmas wrapping paper tearing across the screen to reveal the dynamic element underneath. To complicate this still further, the whole scene was full of falling snow. As is often the case with Out of Home, so much of what we do is constrained by very archaic bandwidth considerations. So the only way to easily accomplish this kind of execution was to resurrect the trusty transparent FLV and create a multi-layered application using transparent video. I had to download an old version of Adobe Media Encoder CS6 because that was the last app in which Adobe included support for FLV. In the end, the project went off without a hitch although I’m still not sure how I might have accomplished this so easily in HTML.
If anyone out there has any tips on how I might layer-up transparent video, over a dynamic clock element in HTML5 I’d like to hear your thoughts.
As Flash has evolved over the years Adobe has continually jettisoned legacy technology. ActionScript 1 and 2, the bandwidth profiler, even projectors fell by the wayside (in CC at least). Sometimes these features re-surface in new releases, like the motion editor for example, but it seems that once the ability to target a specific Flash Player version is dropped, it remains dropped. In Flash Pro CC2014 the oldest targetable Flash Player is version 10.3.
Sadly, this has been causing me some headaches. There are still some advertising platforms out there which specifically reject anything more recent than Flash Player 10.2. This is a problem because the last time Flash supported this player was way back in Flash Professional CS5.5.
Finally, I decided enough was enough and resolved to solve this problem once and for all. Here’s how I did in.
Firstly download the playerglobal10_2.swc from Adobe’s archive
Rename it playerglobal.swc
Go to “Applications/Adobe Flash CC 2014.app”
Right-click the Adobe Flash CC 2014 application and select “Show package contents.”
Go to this folder:
/Applications/Adobe Flash CC 2014/Adobe Flash CC 2014.app/Contents/Common/Configuration/Players/ActionScript 3.0
Duplicate the directory FP10.3 and rename it FP10.2
Replace playerglobal.swc with the version you just downloaded. Remember to change the name from playerglobal10_2.swc to playerglobal.swc
Next you duplicate /Applications/Adobe Flash CC 2014/Adobe Flash CC 2014.app/Contents/Common/Configuration/Players/FlashPlayer10_3.xml and rename it FlashPlayer10_2.xml
Open FlashPlayer10_2.xml in a text editor delete everything and replace with the following:
Now relaunch Flash Pro CC 2014 and behold Flash10.2 has been added to the targetable Flash Player list.
Finally, if you want, you can delete Flash CS5.5 from your system (unless you want to run the Gaia Flash Framework for Flash – in which case your stuck with CS5.5 for a while longer.)
Sometimes I think we threw the baby out with the bathwater. An animation that weighs in at less than 100KB in Flash, currently weighs in at around 8MB in Processing. Admittedly it's made using pngs rather than vectors but that does seem a little huge. I used 122 pngs to make the animation above, in Processing. It turns out that each frame in the Podman animation weighs in at around 20KB, work it out for yourself, that's pretty huge. So I had a look at how I could compress the pngs to their smallest possible size. I turned to the two big hitters Photoshop and Fireworks but they have next to no PNG24 compression control. If my Podman is to have a nice fluffy drop shadow and a soft edge, I needed the semi-transparency available in the PNG24 format, with some extra control over the compression. PNG24 is billed as a lossless format, meaning it doesn't throw away any information, it just tries to compress the file, with no data loss. I remembered dealing with IE6 and it's buggy handling of transparent pngs. I stumbled upon a tool called ImageAlpha written by a clever bloke called Kornel Lesi?ski. This brilliant free application adds a whole suite of extra compression options to those that ship with Photoshop and Fireworks. You can specify the number of colours, choose from range of compression algorithms, toggle dither and specifically ensure that the exported image is IE6 compatible. Pretty amazing if you ask me. Why these features aren't in either of Adobe's products is beyond me.
Although I was well on my way to success. My woes weren't over yet. I had 122 pngs to re-export and ImageAlpha, doesn't seem to support batch processing of multiple files. After consulting the ImageAlpha website I stumbled across this tantalising statement:
ImageAlpha is mostly based on pngquant. You'll find compiled pngquant executable in ImageAlpha.app/Contents/Resources directory."
This was music to my ears. After visiting the GitHub link, I realised that png heaven was close.
Follow these steps.
1) Do a test export of a .png using the ImageAlpha application. Make a note of the number of colours etc.
2) Select the ImageAlpha application in the Applications directory, right click / ctrl+click the application icon and select "Show Package Contents".
3) In the "Resources" directory you will find a magical executable file called "pngquant" the path to this files will be something like: "/Applications/ImageAlpha.app/Contents/Resources/pngquant" right click / ctrl+click and select "Get Info" to be sure. You will find the path under the "General" drop down arrow. Copy down the path, including the name of the application itself "pngquant".
4) Open Terminal.
5) Paste in the path to "pngquant" adding "-h" immediately afterwards, in my case it looked like this:
This will print out some information onto your Terminal window. It's actually a set of instructions on how to use pngquant, and to perform the batch processing of our 122 pngs.
This is the most useful part of what gets printed out on the Terminal window.
usage: pngquant [options] [ncolors] [pngfile [pngfile ...]]
--force overwrite existing output files (synonym: -f)
--nofs disable Floyd-Steinberg dithering
--ext new.png set custom suffix/extension for output filename
--speed N speed/quality trade-off. 1=slow, 3=default, 10=fast & rough
--quality min-max don't save below min, use less colors below max (0-100)
--verbose print status messages (synonym: -v)
--iebug increase opacity to work around Internet Explorer 6 bug
--transbug transparent color will be placed at the end of the palette
I know it looks complex, displayed there on a spooky Terminal window, but it's really simple honest. Each one of these options is an instruction, that gets sent to "pngquant"
6) Finally I constructed the following line to complete my task: /Applications/ImageAlpha.app/Contents/Resources/pngquant --nofs --iebug 64 Documents/Processing/Podland/Podland/test/*.png
it breaks down as follows:
[Path to "pngquant"] [--nofs = no dithering] [--iebug = fix the ie bug] [number of colours] [path to my directory ending in the wildcard "/*.png" to process all images ending with the ".png" extension at this location]
7) Hit return.
8) Check out your directory and enjoy your freshly exported images.
NOTE: My animation is still 1MB though. Next stop: SVG.
I’ve been fiddling around with Processing for a couple of months. It’s quite honestly the most excited I’ve been about any technology since ActionScript arrived in Flash 5. Here’s a little embedding experiment using Keyvan Minoukadeh’s excellent Processing JS plugin for WordPress. Make sure your get the right one!
These are the first, rather rubbish, Processing Sketches I ever wrote; saved here for posterity and encouraging me to pull my finger out and post the recent stuff, when it’s finished.
I recently took up the Google Chrome challenge and ditched Safari to see if the habit took. Sure enough I’m loving Chrome, although I noticed that some sites displayed type incorrectly. Replacing fonts with peculiar glyphs and generally screwing up.
I checked the sites in Safari and Firefox, and the type displayed perfectly. So, what do I do?
Well, I noticed that the typeface in question was Arial, common enough. So I thought, maybe Chrome is looking in the wrong place? I use Font Explorer to manage my fonts, so I tried deactivating every Arial font on my system. Then I closed Chrome and reactivated all the Arial fonts again. Effectively re-setting the Font Explorer library entry for Arial. Guess what? It worked!
However a day later the same thing happened again. I successfully went through the same rigmarole again, but now, two weeks later, I’m beginning to ignore the display error, which is hardly ideal.
Seems a bit rubbish to me.
Here’s a picture of the offending bug. If anyone can suggest a more permanent solution I would be grateful.
After scrabbling about I finally I found a solution. It turns out that it’s actually an issue with FontExplorer X Pro. You need to make sure that it is set up to answer font requests from Chrome.
Here’s how you do it.
FONT EXPLORER X PRO > PREFERENCES > FONT REQUESTS and add Google Chrome to the list and ENABLE (or Allow) the PERMISSION.
I hope this brief post is of some use to someone out there.
I’ve recently discovered the joys of the Gaia Framework for Flash. It’s an awe inspiring framework designed to allow Flash designers or developers to rapidly develop really complex applications very easily. One of the best things about it is an adherence to accepted best programming standards. An application built in Gaia kind of takes care of itself. My current project features hundreds of videos and pages. Gaia managed to make short work of organising them all into something that not only solved the problem but also kept everything neat and tidy. I could preload / cache / transition and bookmark, pages, video, content, elements, everything! It implements swfObject, swfFit, swfAddress and Greensock automatically putting every library you could need at your finger tips.
It also makes you think about how you could use it in other projects. It is just made for presentations.
Next time somebody asks me for a Powerpoint presentation done in Flash. I’ll be using the Gaia Framework.
If you were putting together a presentation in Gaia you could build your slides first and bring them all together before the client has time to approve them. Leaving you free to do the alterations rather than finding yourself torn between finishing the application and polishing the content.
One of the best features of Gaia is the XML Scaffolding feature. You write an XML schema describing your application, import the XML into the Gaia panel in the Flash IDE and press the button. Hey Presto! All your Flash files, AS3 classes, symbols, swf, pre loaders, AS imports etc, all get built automatically.
I’ve had a few issues with open Flash files crashing the Flash IDE during a Gaia export but this has never really bothered me. It just encourages me to avoid putting code on any timelines. It’s all open source and free to use. The support and documentation on the website are second to none. Steven Sacks has done an amazing job.
There may be times when it is essential that a Flash animation is available to users on Apple devices such as the iPhone and the iPad. Here is a technique that addresses this requirement using Google’s rather wonderful open source project Swiffy.
Firstly, your Flash movie should be no larger than 1MB and ideally exported for Flash Player 5 although Swiffy supports most of the AS2 specification. For those of you who don’t remember, you can do a great deal with Flash 5 and AS2. Probably a great deal more than Safari on the iPhone will allow us to do.
When you process your swf, Swiffy outputs an html page that you can place on your page using an iFrame. I know, I know an iFrame! However we’re only using our iFrame to serve alternative content to less than 5% of our visitors. There’s nothing for Google to index so it makes very little difference to the end user. I’ve added an alternative version to the header of this page, making the animation, podman cursor follower and all, viewable to iPhone users, for what it’s worth. It’s pretty clunky, probably only making 8 frames a second on my iPhone, but it’s a pretty complex multilayered animation, with lots of bitmaps and transparency. While the animation in the header of this page may not have been designed for WebKit, it could probably be optimised quite easily. A little trial and error goes a long way. Maybe I’ll follow this article up with a sequel.
This one always catches me out and I find myself looking up the same thing time and time again. So for future reference I thought I’d make a note.
When you install Joomla there’s an setting check that lists any problems with your set-up that may effect the running of Joomla! In my case (both on 1&1 AND on MediaTemple) the Recommended Settings have flagged Display Errors as “On” when it should be set to “Off” – The solution is pretty simple.
Open the htaccess.txt file installed with Joomla! add: