Latest Entries »

Weird little error, couldn’t find any fl.* classes in a basic as3 ‘flex’ project in flash builder 4.

import fl.transitions.Tween;
import fl.transitions.easing.*;

Both of those caused an error. The solution turned out to be adding the flash.swc file as a library.

The path on OSX for Flash CS5 is:

/Applications/Adobe Flash CS5/Common/Configuration/ActionScript 3.0/libs/flash.swc

To add it (in Flash Builder 4) go to project / properties / Actionscript Build Path / Add SWC… and browse to that location.

I’m a noob to flash so forgive me if this is common knowledge. Took me a little while to figure out.

It seems to me that you’ve put a lot of talk out there recently about how websites should be fast! How the google vision of the internet in the upcoming years was all about speed! You even included metrics in your search results on how fast a server can serve a page to you. [link] You made Chrome/Chromium, a blazingly fast browser which is dedicated to being fast above all else. You even have a website set up to try and help webmasters speed up their own websites [link].

So why do you do this incredibly annoying double (or even triple) loading a page? What I mean by that is loading a page…then loading the content of the page with ajax. If you’ve ever used Google Analytics you would know what I mean, and now they’ve spread the scourge to their new version of Adsense (v3 to be precise). When you open Google analytics, it ‘loads’ the initial page and dom along with the javascript. Then it has a Loading message while it loads in the different sites I have and makes the nice table for them. AND then it loads all the data in with ANOTHER ajax call.

Honestly, it’s slow. Yes, it has a ‘fast’ response time if it comes to loading the initial page but the actual loading of the site is slow! You can talk about speed all you want, but when it takes three separate loading screens/messages/calls to load the page, its not that fast.

I know this obsession with client side code generating the content/html reduces load on the server, and many people have this ‘visionary’ idea that the server shouldn’t ever even think about putting together html. While it sounds good in practice, it almost always ends up being slow and having weird rendering flickers while loading the page then the data. This is honestly not that ideal, and it keeps happening more and more. I don’t want to have a page load, then flicker and flash while its loading in the actual page. Sure, this will ‘technically’ make it ‘fast’ according to your response time standards, but guess what? To a user, it’s slower.

This isn’t just a Google thing either, everyone seems to be doing it. Microsoft is just as bad, the new Bing Webmaster Tools has 4 different loading messages/calls when you open the page. It doesn’t make sense to do this! Even if you do want to have the page load itself with ajax, why would you have FOUR separate calls for it?

This idea that you had about how you want to speed up the web seems to be schizophrenic. On one hand you put in metrics to benefit fast response time sites, and create a fast browser….but at the same time slow it down with these applications and their endless loading messages. Most of this trend seems to me to come from Google AppEngine and GWT, with which you pretty much are forced into this approach.

Please google, stop this trend. Make your applications and pages faster. Not just faster to load the initial empty page, but faster to load the page and content!

A good comprimise that seems to have been implemented by some people (like facebook and amazon) is loading part of the main content on page load and then loading the rest in with ajax. That way the user can have some information immediately to start processing and by the time he is done the rest of the page is loaded. This, while still not perfect, is far far better than the Google method right now.

Have you noticed visual studio cutting off part of your context menu and making you scroll? Even if you have the screen space to show the entire thing? See the picture below to see what I mean.

Scrolling Context Menu

Thankfully, there has been a fix!

Visual Studio Blog Announcement

Install the two patches referenced on that page and you’ll be all set! In case that page goes down, here’s direct links to the patches. Note, on those pages you need to go to the download tab to get the actual patch installers.

Apparently this will be rolled out in SP1 for VS2010, but it was driving me nuts in the meantime!

I had some really weird issues while setting up Visual studio 2010 with Qt 4.7. The most important thing (that I stupidly didn’t realize) was the fact that you CANNOT use the VS2008 compiled libraries and dll’s (available on the Qt webpage) if you don’t have VS2008 installed. The reason is because the Qt SDK you download is a debug build which is dependant on the VC9.0 DebugCRT, meaning it needs the Visual C++ 2008 Debug Runtime installed, which is NOT available as a redistributable installer. The only way to install the DebugCRT is to install the entirety of Visual Studio 2008.

The reason this was complicated to figure out was because most of the computers I installed it on had VS2008 allready installed on it, so only a couple computers wouldn’t compile properly. It also wasn’t helped by the fact that the errors given by it were pretty esoteric. There also were some errors caused by different paths being set wrong, a list of some of there errors is just below.

  • The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
  • This application has failed to start because the application configuration is incorrect. Review the manifest file for possible errors. Reinstalling the application may fix this problem. For more details, please see the application event log.
  • Error MSB6006: “cmd.exe” exited with code 3.    C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets

To solve these problems and get Qt working properly with VS2010 you have to compile QT from source, which means you’ll have to download the 4.7.1 source sdk. You’ll also need to have the Visual Studio Qt Add-in installed.

View full article »

I wasn’t able to find any great instructions on how to  compile QT 4.7 with VS 2010, which is needed if you aren’t developing with VS2008. This tutorial covers how to compile QT 4.7.1 with 2010, and it should work with newer versions of Qt but I can’t be sure it will.


  • Qt SDK Source (link)


  • Microsoft DirectX Software Development Kit which can be downloaded here,
  • Microsoft Windows Server 2003 R2 Platform SDK which is available here.

Both of those need to be downloaded and installed before you can build the SDK. You also need to have perl (link).

….to be finished.