der hess

I was very pleased that YouTube released a ActionScript 3 API for their Chromeless Player. I looked at some availabe code snippets on different blogs and unfortunateley, I had to realize that the API is not really object-oriented and a little bit annoying to work with (because of the missing code completion).

My current project - an independent Web Video Player - is still using the old workaround YouTube API Tubeloc and I have to change this. That is the reason why I created a Flex Component for the new YouTube AS3 API. If you would like to use my code for your Flex or Air projects, please feel free to use it and if you will find some bugs, please leave a comment!

Now I will start with some explanations of my code. I create 4 classes, which manage the whole YouTube Chromeless API. The class YouTubeAs3 contains all the most important functions and is based on the Flex Framework(!). The classes AirYouTube and FlexYouTube extends the YouTubeAs3 class. Both classes are Flex Framework based classes. I had to divide the YouTubeAs3 class into these 2 classes, because the Adobe Air environment don't support the command Security.allowDomain() and it is cleaner to use this command for a web-based projects. So therefore please use the FlexYouTube component for web-based projects and the AirYouTube component for your Air projects. The fourth class FlashYouTube is an only Flash plattform based class, that should be very handy to use for non-Flex projects. Read more...

I was very pleased that YouTube released a ActionScript 3 API for their Chromeless Player. I looked at some availabe code snippets on different blogs and unfortunateley, I had to...

For every project you should check your skills before you start. It helps a lot for preventing possible problems and makes the life easier. Thus I highly recommend to do a self-assessment before your start as a Flash Independent Developer. After this self-assessment you should have a very clear picture about your abilities, skills and of course your weaknesses. It is very important that you know your weaknesses because you can outsource some of this problems to your network buddies.  An independent team-oriented working approach works in this case very well, because it replaces your weakness with a strength of another person. It works like the Captain Planet or the A-Team metaphor

On the mindmap you can see the 4 core skills: Design, general knowledge about New Media, Programming (Computer Science) and soft skills. As an employee it is not so important that you have skills in each of these core skills, but as an Independent Developer you have to be an allrounder. gSkinner wrote a nice post about the must-have qualifications as a Flash Developer. I would like to add the points doing project management and creating networks to this list. An (Flash) Independent Developer has to be fancy to do project management tasks and get in touch with other people. If you don't like it, then you should not become an (Flash) Independent Developer! But I think the completely different charakter of the tasks make the life of an (Flash) Independent Developer so much more interesting.
Read more...

For every project you should check your skills before you start. It helps a lot for preventing possible problems and makes the life easier. Thus I highly recommend to do...

A couple of months ago I started thinking about becoming an Independent (Flash) Developer. So I wrote a blog series in German about this topic. This blog series describes my idea behind the passion of an Independent (Flash) developer. Unfortunately, the feedback was quite less for me and zproxy is right, when he said I should write this in English because of the less size of German speaking flash developers and that it is also an interesting subject for all English speaking flash developer... So I decided to translate all my articles about this subject in English. Who is able to read German can have a look on the complete series here.

Firstly, before I started any activity into this direction of becoming an Independent (Flash) Developer, I had to define my personal idea of an Independet (Flash) Developer.

So my main goal is to do cool things with Flash or other Technologies, which I really enjoy to realize. That could be a Flash Game, or an open source library for a special problem or just a nice software or anything, what you can imagine.

After this process of creation I must have a product, which brings some money in my pocket, so that I am able to pay my rent and living costs. So the most important thing for me is that this product has a relation to things I love to do! The earning or the income plays minor role. I hope when you do cool things the money will come...

In addition to this, I thought freelancing could be the solution. Do some small projects, which are ok for me and spend the rest of my time with the cool things I would like to do... But later I noticed for me that is not the freedom I want to have. So I spent more and more time to find a nice solution and I think I found a  plan which could work. I am going to tell you the details in this blog series about the passions and opportunities of an Independent (Flash) Developer.

The information size of my solution is too big for one blog article, so I divided it in 10 parts. Every part explains a very important part of the Independent (Flash) Developers journey. I created a Mindmap for you which shows all subjects and relation beyond my blog series I am going to mention.
Read more...

A couple of months ago I started thinking about becoming an Independent (Flash) Developer. So I wrote a blog series in German about this topic. This blog series describes my...