Majority of the calls you would ever make to Facebook API require user access token. There are some however, that require app access token instead. These are normally calls you do on behalf of the app not user. An example of such situation would be creating a test users, or reading Insight data.
To my surprise app access token is also required when you want to read or set user scores.
For those who are not aware of this, you can set and read score value for an app user. For this to work, you have to set the type of your application to “Game”, in the FB developers app general settings page.
As current Adobe’s Facebook API didn’t support making such calls, I modified the source code (for web development) so that it would.
Btw, if anybody from the Adobe’s Facebook API administrators is reading this, please feel free to include these changes in your next version. You can download the modified source here.
So how do you use this ? Here is the example how to set and read user scores, and also how to read scores of the users’s friends that have played the app/game. Read the rest of this entry »
It has been a while since Facebook announced changes to their API , including the introduction of new customisable open graph actions. Probably most famous example being The Guardian app publishing : “Mike Nolan is reading : “How to grow a dandelion” article on Guardian. Or some other user “Is listening to Depeche Mode” on Spotify. While you can get plenty of tutorials on how to achieve this in HTML / PHP I haven’t been able to found any on how to do this in Flash. It might be that my googling skills are diminishing, or the fact that you actually can’t do this PURELY in flash. Why ? In a similar way the “share” functionality works , for this to work properly, Facebook must read html metadata from your page, and use them to construct the ticker update. You can however trigger publishing the action from flash and with a bit of php magic link deeplink from the published action on ticker back to your app. Here’s how: Read the rest of this entry »
Don’t get me wrong. I LOVE FDT 5. I think it’s the best AS3 development IDE period. (The second best being intelijIDEA, if you must know.)
Especially with the new refactoring enhancements, improved mobile workflow, haxe support, build in Joa’s apparat / stripper / reducer abc optimisation tools and my two belowed magic shortcuts ctrl+1 and ctrl+shift+o that fix just everything you could wish for in the code. Having freshly upgraded from the version 4 Max to FDT 5 Max I was excited to try the new Air 3.2 gpu accelerated molehill capbilities on the iOS and android devices , perhaps revisit my Augmented Reality Demo so I can compare the performance now.
Made the simple hello world project, got all the appropriate certificates and provisioning profiles from our Apple Dev center, all the icons sizes, changed the app xml descriptor to say air 3.2 in the namespace, and hit the run button.
Instead of nicely compiled swf/ipa file I got this error message : An internal error occurred during “Compile”
Now, if this was an actionscript error, you could follow it up to stack, see where it originated, what caused it and hopefully know how to fix it. Unfortunately this is INTERNAL error of FDT threw in Java, so all I could try was to blindly try to change some settings, tweak some launch parameters. To no avail. Luckily after some time spent googling I was able to find this issue being added to FDT’s bug tracker. It was caused by using the SDK 4.6.0 ! And solution ? You can still use the latest sdk, just have to go to the SDK xml descriptor file and manually rename it’s version tag to 4.5.0.
Once I found the ‘solution’ for the SDK problem, I thought I was on my merry way to the land of mobile development. Unfortunately, that wasn’t the case.
Although swf now compiled fine, instead of getting ipa file, I got message : application descriptor not found
Although there clearly WAS an application descriptor file! To cut the long story short, there was again an entry for this in the bug tracker.
The issue is missing stringAttribute key=”ADL_DESCRIPTOR_FILE in the launch file. Once I added line
to my .settings/launch/Air32Demo.launch file the ipa file has compiled correctly.
So at the end it all ended well. Right ?
Here’s my problem though..
Both of these problems were marked as “Solved” in the bugtracker. To me they are not solutions. These are “hacks” in the best case.
They’re both completely non transparent bugs, without any intuitive solutions. I think that for a $600 software, these ARE showstopper bugs, and should be dealt with immediately by releasing correction patch!
I recently downloaded the latest version of Unity 3D 3.5 demo – release candidate 1 to further test the flash export capabilities. I have to say I was impressed and it’s certainly a big step forward – long list of bugfixes and some new implemented features speaks for itself.
To test the flash conversion I made the 2 demos.
Click on the images to play demos.
Car demo
First it’s just a very simple demo with high poly car model, plane , camera and one directional light. I wanted to see how the dynamic shadows would be rendered and whether the high poly model would cause any performance issues. It’s using standard fps controler and a mouse look for the camera. To get reasonable looking dynamic shadows shadow resolution had to be “Very high Resolution” and also Shadow distance in Quality settings had to be increased to 300. Otherwise shadow started to disappear if you moved even slightly away from the car with the camera.
PROs:
Model renders smoothly and fast enough (as expected if you have good GPU).
Lens flare effect on the light now renders correctly
CONs
There’s a banding effect on the shadowed area both on the floor texture or inside of the car
Some materials were not correctly transferred from the max files
Car racing tutorial demo
NOTE : PLEASE DRIVE SLOWLY OTHERWISE SCENE WILL STOP RENDERING!
This was the conversion of a racing game tutorial . This is of course much more complex example and there were multiple issues with this conversion. Quite a lot of issues had to do with terrain object, which is currently not supported for flash platform build target. Removing Terrain, solved about a half of the compiler errors, but I had to remove also parts of code that referenced it, and with it also code that check the rendering and hiding the objects that don’t need to be rendered.
There were compiler errors that had to do with classes of the same name being defined twice. For example SoundControler was a class in C sharp but also in Javascript. Or Skidmarks was defined as a C sharp class but existed also as a shader under the same name.
I think it’s a pity that Terrain object isn’t supported as it brings a lot of convenience to the environment creation. I think there already must be an algorithm to converted it to mesh and apply textures ? As GPU can only work with polygons ? Why not do that for flash conversion as well and have a settings to how much detail would terrain have?
Ok, so here are some cons and pros
PROs
car runs pretty smoothly all the physics and lightning works quite nicely
lens flare now works fine as well
CONs
the same banding effect on the shadowed areas
no car sound effects only when collision occurs
for some reason if you speed up with the car it will stop rendering scene (ok this one might have to do with me disabling some parts of the script to get rid of compiler bugs : – ) )
there’s a slight space between the shadow and an object casting that shadow (you can notice that on the wheels for example)
Even without terrain the demo has 22 MB. Non development build.
Other than that, it’s pretty sweet and playable (apart from speedy non render bug).
Had some free time around Christmas, so I decided to have a look at Unity 3D since it looks like (at this time) only reasonable way to do 3D in flash. Yes there are other 3D engines out there like Alternativa, Flare 3D, Away 3D, but none of them have a visual editor that comes even close to the Unity’s IDE.
The version that supports export to flash have been around a few weeks now, so I thought I’d give it a try.
Firstly I did a scene with the high poly count that tested the GPU rendering. This was absolutely fine, as the performance relied heavily on the GPU.
One thing I noticed though, that Terrain object wasn’t being rendered ? I guess it’s because in Unity Terrain is more of an abstract construct / game object rather than actual mesh.. Although, I’d imagine it would make sense to converted to editable mesh for flash ?
Secondly I tried converting an existing FPS game. It was a FPS tutorial made by Graham McAllister.
The conversion was pretty straightforward, there were a few compiler errors that needed fixing, but nothing too major.
The game itself work quite allright, there are some bits missing (like the lines of fire from the automated shooting robots) , but I guess it could be down to me not having a pro version..
The swf file size is 8.6 MB which is pretty hefty compared to normal 2D games or websites, but then, it’s a complete game , with lots of textures, meshes and sounds.
Also absence of mouse lock is quite evident, but this is fault of the flash plugin, not Unity. Support for mouse lock is coming soon though!
All in all, this is still a preview version, I imagine a lot of things will be fixed , optimised , added.
So far I am quite impressed (well done Ralph and team !) and we’ll see how will it compare to the Unreal Engine to flash conversion!
It was build using Canvas so should work on most of modern browsers that support HTML5.
Just a simple particle wall, with randomly coloured particles of red-ish hue, reacting to mouse movement (or ‘wind effect’ if you will) also if you press and hold the mouse, they will change in intensity.
I’ve started building this demo as a part of the “playtime” during the HTML 5 workshop called “Intro to creative Javascript and HTML 5 Canvas” with Seb Lee-Delisle at FOTB conference in Brighton, finished it today, (added a background and a dynamic resizing based on the window dimensions).
The positive thing about working with HTML 5 is that it made me very thankful for Flash plugin. No hacking around for unsuported features, no shims, no version degradation fallbacks… Just works in every browser. Haven’t really appreciated this until I’ve experienced html 5. Another thing that I become to appreciate is ActionScript as a language. OOP features that creates supports for encapsulation such as strong typing, private / protected variables, supports for real classes.
It felt like traveling back in time , to a time of flash plugin version 5/6 and AS2, when its scripting capabilities were quite limited, and flash multimedia / display capabilities were quite crude, compared to it’s current capabilities.
Fortunately , there seem to be a solution! It’s strongly typed modern language / platform called haXe (similar to C# or Java) which can output to several target platforms / languages, one of them being JavaScript. Good news is that my programing IDE of choice (FDT) will support this in the next version which is comming very soon!
Last week Adam Feldman Google’s APIs Product manager announced on the official Google Code blog that they are announcing some new apis but more importantly shutting down some old ones.
Among them a very popular Translate API.
This decision came as a big surprise to many developers, myself included. I have used this api in an CMS Flex App caled SiteManager. SiteManager has a copy module and it’s used as a copy source for multilingual flash campaign websites. I used it to quickly generate non english copy for other versions of the site, to have a good idea how the multilingual labels and text would sit within the website whether there are any space or alignment problems etc.. It was just a great way to preview site in other languages before the officialy translated copy arrived from the client.
Now this is gone and while there are other alternatives (I recommend checking out the Microsoft Translator V2 ) this decision raises some questions about Google as a company and their relationship to developers.
I personally like(d) Google a lot, they were an example of a great open and innovative company, with a real love for developers. This love wasn’t just proclaimed but proved by many free APIs they provided for us developers.
But after this how can you trust Google API ever again ? What if this project I am working on and my customers will depend on it will be no longer working in half a year when Google decides to shut down a particular API the project uses? How am I supposed to explain that to my customers. What am I to do if they all demand their money back?
And what about their motto : “DO NO EVIL” ? Shutting down translate is clearly hurting many developers and many project, some of them non profit and designed to help other people from different countries. How is that NOT evil ?
And what’s next.. Google Maps ?!
The sad thing is , they have other alternatives like limiting the amount of queries per couple hundred a day for a free version and licencing projects that need more traffic. Or to simply find a way to prevent an abuse. Shutting down this API is simply uncharacteristic of Google, very sudden and unkind decision. I’d expect it from Facebook but not from them. What’s going on with Google?
This is one of those articles where title pretty much says it all.
Now with AIR 2.6 iOS camera support and the unrestricted camera feed access to developers in iOS4, we can finaly build some cool AR apps on the mobiles right ?. Well… in theory at least!
The Setup :
To see how it would perform, I made a quick AR demo using Flar toolkit 2.5.5 for motion tracking and pattern recognision and Papervision 2.1 for the 3D scene. Scene consist of a simple flat shaded 3Ds model, plus 4 interactive buttons. The whole scene has less then 170 polygons. A very lightweight scene with very low poly count. To make the conditions fair for both devices I kept the AR scene dimensions the same (hence it looks smaller on HTC Desire HD). Both apps use gpu rendering.
I exported the app into an iPhone format using latest available AIR SDK – 2.6. For comparison I also converted the flash project into Android format. I tested the iPhone version on iPhone 4 and Android version on HTC Desire HD.
The demo has 2 buttons that enable the user to turn off the motion tracking/pattern recognition - (FLAR ON/OFF), and scene 3D rendering. By turning off the 3D rendering, and seeing the changes in frame rate, we can see how much resources are consumed only by the rendering of the 3D scene. By turning off the 3D rendering we can see how much resources are spent on the motion tracking.
Here’s the quick video showing the iPhone, and Android version
Framerate results comparison:
(Swf had frame rate set to 25fps)
And here are the lessons learned :
Lesson 1: Augmented reality can be implemented on mobile devices via flash conversion, just not in any usable manner
Although app will still run and function, the poor frame renders the application unusable. The problem is not just visual – stuttering screen playback, it’s also functional. If you have interactive elements in the scene such as buttons, low frame rate will make a click / touch detection difficult and user would have to try multiple times for a touch event to register.
Lesson 2: iOS conversion performance is superior to Android one.
Although both devices run on a similar hardware (both have 1GHz processor) and the apps were converted from the identical swf file – Android performance was on average worse. Also, while framerate on the iPhone seemed to be pretty stable, on the Android it was generally erratic and fluctuating.
Why is this happening?
I personally think it’s due to the way the apps are being converted and run on the device. While iPhone app is generated by converting the swf file into a native app, android app is being converted into an android air app compatible file and run by the Air runtime wrapper that has to be separately installed on the device.
That , in my opinion , creates a performance decrease , as it requires an extra hardware abstraction layer between the code and the device hardware. Think of it as flash file being run inside a flash plugin in the browser, versus OS native app. By design, swf app will never achieve the same performance as the native one.
The question here is , why does Adobe approaches Android conversion in this way. As for the iOS, it is quite clear why the iPhone apps are converted to native format. Apple wouldn’t let them do the Air wrapper approach. For the Android , they don’t need to however, yet they choose to do it. From the marketing point of view , it makes perfect sense of course. In the same way the spread of flash plugin helps to spread the entire platform and the tools (mainly the creative suite).
From the developers perspective it’s not that great though.
It means that every Android user , in order to run your app, will have to download AIR for android runtime. Although this helps to keep the file size relatively small (android version 451Kb vs 5.3MB iPhone version) the air runtime itself has 17 MB!
I would really like to hear justification from Adobe, as they were really conscious about increasing the file size of flash plugin (still less then 3MB) when almost everybody has broadband at home, yet they’re OK with forcing people to download 17MB on 2G/3G mobiles? I think they might be shooting themselves (and developers ) in the foot here.
The extra AIR Runtime file size issue is bad enough, but if you add an inferior and erratic performance to the mix there is really no reason to prefer conversion to air vs native app.
I am aware that performance in AIR 2.7 is better (there’s no Android Air runtime available at this moment so can’t test this personally) and with flash 11 and molehill we might see even better increase when it comes to GPU rendering.
However; there will always be applications that rely heavily on the cpu and for those, native app conversion will be always superior option.
Recently I’ve worked on a mobile app for the company I work for , and instead of just showing company’s address or displaying it on a map I thought.. wouldn’t it be more helpful to give user directions from wherever he is to where the company is ?
To do this, you of course, need to utilise a few APIs:
1. Google Maps API to download map tiles and draw a poly line from user’s location to destination,
2. Air’s Geolocation API to determine current users location
3. Air’s Multitouch API to let the user pan/zoom and rotate the map.
Getting the google maps to show on your display list is pretty straightforward, there’s a couple caveats though. It is now compulsory to initialise map with a sensor parameter (just a Boolean switch expressed in string format indicating whether map is used on a device with geolocating sensor.)
Also , to get it working in AIR app, you have to pass the ‘url’ parameter. I used local host for this.
Getting user’s location is relatively simple, but it’s best to check first whether user’s device support’s it and whether it has been turned on :
private function getGeolocation() : void
{
if (Geolocation.isSupported)
{
geo = new Geolocation();
if (geo.muted)
{
alert("Please turn on the location or select a manual address input",showManualLocation);
}
else
{
geo.setRequestedUpdateInterval(100);
geo.addEventListener(GeolocationEvent.UPDATE, geolocationUpdateHandler);
}
}
else
{
alert("Geolocation not supported, please input your location manualy", showManualLocation);
}
}
Once we have the GeolocationEvent fired , we can determine user’s location from event.latitude and event.longitude.
However, Google maps Directions.load normally works with address format query, eg. “from 25 apple Street, NewYork to 22 Boulevard Street, San Francisco”. To get it working with LatLng you have to use this format (Thanks to Barry Hunter from Google maps forums for this tip)
private function geolocationUpdateHandler(event : GeolocationEvent) : void
{
originLatLong = new LatLng(event.latitude, event.longitude);
dirQuery = "from: Start@"+originLatLong.lat()+","+originLatLong.lng()+" to: Destination@"+fbfLatLong.lat()+","+fbfLatLong.lng();
initMap();
}
(fbfLatLong being hardcoded LatLng destination variable)
After the geolocation is known and direction query is formulater we can get directions by calling load function:
private function requestDirections() : void
{
//create directions
dir = new Directions();
dir.addEventListener(DirectionsEvent.DIRECTIONS_SUCCESS, onDirLoad);
dir.addEventListener(DirectionsEvent.DIRECTIONS_FAILURE, onDirFail);
dir.load(dirQuery);
}
Once the requested directions are computed and returned we can draw the route. I am also attaching a custom markers at the start and the end of the journey.
private function onDirLoad(event : DirectionsEvent) : void
{
map.clearOverlays();
var directions : Directions = Directions(event.directions);
var startLatLng:LatLng=directions.getRoute(0).getStep(0).latLng;
var endLatLng:LatLng=directions.getRoute(directions.numRoutes-1).endLatLng;
createMarkers(startLatLng,true);
createMarkers(endLatLng,false);
var directionsPolyline:IPolyline = directions.createPolyline();
map.addOverlay(directionsPolyline);
//get bound center
var directionsBounds : LatLngBounds = directionsPolyline.getLatLngBounds();
map.setCenter(directionsBounds.getCenter());
//get the zoom level from direction bounds
var zoomLevel:Number = map.getBoundsZoomLevel(directionsBounds);
map.setZoom(zoomLevel);
map.setAttitude(map.getAttitude());
}
It’s important to centre and zoom the map so that the whole journey is visible on the map.
OnDirFail is called when the given coordinates couldn’t be resolved, and then it’s probably best option to give user a chance to input the address manually.
Tested on Android 2.2 on Desire HD with Air 2.6 runtime.
Few days ago , Flex 4.5 Burrito and SDK Hero was again available for download so I went and downloaded the whole half a gig enchilada. After running the installer there was a warning : installer has detected that system restart was pending but that could be ingnored so I went on fit the install.
Install failed miserably about the time it tried to install some microsoft libraries. Oh joy. Well , at least ALL it’s needed was a machine restart, and all would be jolly good right ?. Or so I naively thought. I couldn’t be more wrong.
No joy. The same error message. The same install fail
After unsucesfull googling and restarting couple of times I gave up and went to bed as it was well after my usual bedtime (1 am)..
Evening of day two…
More googling. Finding out many more people have the exactly the sameproblem with other CS5 installers , but none of them had actually any luck in resolving the issue (or bothered to write about it).
Official Adobe solution to this problem is :
a. Choose Start, type regedit in the Search box, and press Enter.
b. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager.
Now that would be awesome, if there was actually any “InProgress” key in my registry. If you read comments, that was mostly the case with most users so this advice was pretty useless.
OK. to make a long story short, I did find somebody suggesting to erase : “PendingFileRenameOperations” from registry from a certain location.
I did not find any keys in that particular location, but searching troughout the entire registry for “PendingFileRenameOperations” revealed couple of instances.
I deleted them all and voilà ! the installer ran like a charm!
So if you have the same problem with the CS5 installer, try it, might help you as well.
Word of caution . Make sure your registry key has a NAME that matches “PendingFileRenameOperations” as there might be some keys that have this string as a data/value.
in my case it was : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore” key which value/data contained string “PendingFileRenameOperations” .
