der hess » Programming http://blog.derhess.de am medialen werkeln Mon, 26 Jul 2010 12:07:27 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 Mr. Doobs Harmony drawing APP ported to MAX / MSP http://blog.derhess.de/2010/07/08/mr-doobs-harmony-drawing-app-ported-to-max-msp/ http://blog.derhess.de/2010/07/08/mr-doobs-harmony-drawing-app-ported-to-max-msp/#comments Thu, 08 Jul 2010 13:23:52 +0000 admin http://blog.derhess.de/?p=1358

For exploring the JavaScript API in MAX / MSP / Jitter I decided to port the Harmony Web Application by Mr. Doob. I really fall in love with the different brush styles. MAX / MSP / Jitter is pretty cool for doing audio visual stuff, and I think the different brush style might be nice for this. Fortunately, Mr. Doob published the source code and the code is nice, too! Therefore, it was not so difficult to understand the code.  During my porting process I had to consider four things:

  1. Object Oriented Programming and working with more JavaScript files don't work so easily in Max/MSP. For the reason of simplicity (and KISS), I decided to write everything in one JavaScript file.
  2. JSUI (JavaScrip UI) in Max/MSP does not support the normal drawing functions. I had to port the drawing functions to OPEN GL drawing functions. Which is also positive for the perfomance, I think...
  3. The coordinate system is different. I had to transform the Pixel values to the OpenGL coordinate system.
  4. MAX /MSP does not support the standard Interval function setInterval. The JavaScript Object Task is the substitute. In the end I think it is a cleaner solution

After dealing with these minor obstacles, everything worked fine. I was quite surprised how good the JavaScript performed in Max/MSP. Furthermore, in combination with Jitter and other available Max/MSP Objects you can rock with JavaScript!

For a better understanding, I created a short introduction video clip. It shows how to use the JSUI Canvas and how to use the programmable input channels. In my example zip file is included one Max patch, which works with colorTracking as an input channel. Choose your cam input, and afterwards click in the camera picture which color should be tracked. In the end it gives you an inspiration how different we can interact with the canvas.

Mr. Doob was disappointed a little bit, how the people used his source code. So please keep in mind his blog post and share your code changes. I also publised my source code on google code.

Download  Harmony for Max/MSP/JITTER

Share/Bookmark

No related posts.

]]> http://blog.derhess.de/2010/07/08/mr-doobs-harmony-drawing-app-ported-to-max-msp/feed/ 3 My most important Twitter Messages #6 http://blog.derhess.de/2010/07/05/my-most-important-twitter-messages-6/ http://blog.derhess.de/2010/07/05/my-most-important-twitter-messages-6/#comments Mon, 05 Jul 2010 13:13:36 +0000 admin http://blog.derhess.de/?p=1343
  • My most important Twitter Messages #5
  • My most important Twitter Messages #4
  • My most important Twitter Messages #3
    • ]]>     Twitter von der hess
    A small summary of my Twitter messages from March - June 2010:

    Allgemein (General)

    Generative Art:

    Info Design and Visualization

    UX and Interaction Design:

    Projekte und Experimente (Projects and experiments)

    Neue Technologie (new Technologies)

    Programmierung und Software Design (Programming)

    Physical Computing

    Game Developing:

    Flash and Flex

    Share/Bookmark

    Related posts:

    1. My most important Twitter Messages #5
    2. My most important Twitter Messages #4
    3. My most important Twitter Messages #3

    ]]>     http://blog.derhess.de/2010/07/05/my-most-important-twitter-messages-6/feed/ 0     Creative Coding Tools, which is the best? http://blog.derhess.de/2010/06/02/creative-coding-tools-which-is-the-best/ http://blog.derhess.de/2010/06/02/creative-coding-tools-which-is-the-best/#comments Wed, 02 Jun 2010 12:15:00 +0000 admin http://blog.derhess.de/?p=1308
  • My most important Twitter Messages #6
  • My most important Twitter Messages #5
  • My most important Twitter Messages #4
    • ]]>     Now I am almost studying Interactive Art for one year. Me, as a Flash and Flex Developer, like coding with audio-visual and interaction-based content. But if I am honest, in the last time I did not use Flash in my projects at all. I had to deal with some other powerful creative coding tools. Some of these tools provide me, as an artist, much more freedom than the Flash plattform can ever provide. For example, creating a visual output for multi-displays applications, programming on hardware (arduino), some real-time video tracking (face detection) experiments, using special Open-GL Renderer for 3D graphics and so on. But I also ran into problems, which I would never have with using Flash. Especially, when I worked together with unexperienced programmer. For this reason, I will describe some of these creative coding tools with their inherent advantages and disadvantages. After this article you should have a good overview about the available tools in creative coding.

    Creative Coding Tools Overview

    Creative Coding Tools Overview

    Adobe Flash (text-based coding)

    Adobe delivers a very good IDE for creative coding. Many people complain about the IDE, but it is the best tool to start coding for media designer, artist etc. You have the whole familiar layer infrastructure from Photoshop, and you can easily import your Photoshop, Illustrator graphics. After importing the graphics and the artist can start coding directly on the graphics. To see the graphics visually and arrange them on the stage, and then coding seamlessly with them (connected via symbolname = variable name) minimizes the obstactles for newbies so much. The same is valid for working with interactive video and audio. I know the Flash IDE is not cheap, but it is definitely the money worth for getting a perfect start. After reaching the intermediate level, you can switch to Flash Builder Coding Editor. This editor is quite advanced and it is free for students and teacher.

    In a summary Flash is perfect for starting creative coding. For heavy graphic and media (video + audio files) projects it is perfect and delivers a unique workflow. Flash is also a very good solution for web-based project and the community is very big and active. So you can be sure to find a whole set of additional libraries and help. Because of the simplicity the Flash Plattform has got two disadvantages. The lack of perfomance compared to other technologies (C++, Java, Python) can be a problem for complex visual renderings and algorithms. The second disadvantage is the less freedom for physical computing based projects. An Alternative for Flash is Microsoft Silverlight

    Processing (text-based coding)

    Processing is a specific Java based framework for creative coding. Ben Fry and Casey Reas simplified the programming language Java, so it is easier for media artist diving into creative coding. In my opinion, it is not a good solution for starting creative coding with this tool, even it is for free! In my class and at my old university I often saw the same misunderstanding in the beginners eyes when they started with processing... This whole text-based coding without any reference to the graphics is still too abstract for beginners. That lead for unhappy artist. Then maybe they  started hating programming... That is not cool... Maybe the new IDE project Kaleido can solve this.

    The syntax of Processing is quite similar to ActionScript. So it is not so difficult for Flash Coder to switch to Processing and vice versa. Processing is able to use Open-GL. In this case it makes much more sense to use this tool for 3D Project than Flash. Even you can connect Java Libraries with your Processing projects. That enables completely new application possibilities. Speech recognition, video tracking, working with Bluetooth Networks are only a few examples. Also collaborative coding via SVN is quite easy in Processing and the active community is the best evidence for this.

    Max/MSP/Jitter (node-based coding)

    This tool is a node-based  programming tool for media artist. Every node has an input and a output. The artist can connect this nodes with cables, like it was used to do in the earlier times with the audio synthesizer. The node-based approach may be a good starting point for beginners. For experienced programmer (also for me) it can be very weird to programm in this environment. But if I am honest, Max/MSP/Jitter delivers a big repertoire of audio effect nodes, video effect nodes and User Interface elements. Also working with hardware is quite well supported in this environment. Connecting MIDI devices, special sound-cards and several displays (or projectors) to Max/MSP/Jitter is not a big problem. For this reason Max/MSP/Jitter is perfect for live audio-visual performances and media installations. A further advantage is the extensibility of Max/MSP/Jitter. Advanced programmers can use the included JAVA  API or JavaScript API for creating and extending new nodes (e.g. OpenCV in Max) and user interface elements. Only for web-based projects this tool is almost useless, and even working together with other artist seems not so easy. Alternatives for the commercial based product MAX/MSP/Jitter can be PureData (mainly for audio processing), VVVV (video and visuals) and EyesWeb Framework (video and stage-based installations).

    openFrameworks (text-based coding)

    With openFrameworks we enter the big world of C and C++. C and C++ is quite old and for this reason the language has got some ugly inherent characteristics. For advanced programmer the concept of pointers is quite easy to understand. In contrast intermediate programmers will get surely fucked up with the header file concept. Beginners are going to get lost in this big world... That sounds terrible, but it  is not so worse. C and C++ provides the biggest freedom an artist can ever get. For getting this freedom the artist has to put some effort into it.

    Afterwards the artist can code directly on hardware (e.g. Arduino). Also high-end performance optimizing of your application is possible here. Especially for heavy 3D -based projects you are supposed to use this platform. The team around openFrameworks created successfully an easy to use C++ Library for audio-visual coding. Their tutorial page gives an easy start and their classes makes it quite easy working with audio,video and drawing operations in C++. The openFramework approach is very similar to the Processing project in Java World. It exist an active community, who extend the openFramework toolkit successively. A disadvantage of openFrameworks could be the slow development process. If no suitable add-on is available for your project (for instance: network-based multi-user interaction) it can get very fast complex and time-consuming to solve this technical issue. An alternative for openFramework could be Cinder.

    The End

    The table above reveals that there is no real winner available. All the tools do a great job in their special domain. So Flash and Processing are very good tools for web-based projects, openFrameworks and Max/MSP/Jitter are better for media installations and complex animations. Beginners should check which tool is really easy to learn. An easy start and enjoying coding is very important in the beginning! Advanced Programmer and artist should distinguish between perfomance-based/hardware-based or graphic-based/media-file-based/web-based projects. For perfomance-based/hardware-based projects openFrameworks, Max/MSP/Jitter and maybe Processing is the best solution. For web-based and media-file/graphic-based projects Flash delivers a very good solution. In some cases (e.g. big Information Design projects) Processing is more suitable... So Happy Coding and visit CreativeApplications.Net to see what is possible!



    Share/Bookmark

    Related posts:

    1. My most important Twitter Messages #6
    2. My most important Twitter Messages #5
    3. My most important Twitter Messages #4

    ]]>     http://blog.derhess.de/2010/06/02/creative-coding-tools-which-is-the-best/feed/ 6     My most important Twitter Messages #4 http://blog.derhess.de/2010/01/05/my-most-important-twitter-messages-4/ http://blog.derhess.de/2010/01/05/my-most-important-twitter-messages-4/#comments Tue, 05 Jan 2010 14:03:16 +0000 admin http://blog.derhess.de/?p=1188
  • My most important Twitter Messages #6
  • My most important Twitter Messages #5
  • My most important Twitter Messages #3
    • ]]>

    Twitter von der hess
    A small summary of my Twitter messages from November - December 2009:

    Allgemein (General)

    Generative Art:

    UX and Interaction Design:

    Projekte und Experimente (Projects and experiments)

    Neue Technologie (new Technologies)

    Programmierung und Software Design (Programming)

    Game Developing:

    Flash and Flex


    Share/Bookmark

    Related posts:

    1. My most important Twitter Messages #6
    2. My most important Twitter Messages #5
    3. My most important Twitter Messages #3

    ]]>     http://blog.derhess.de/2010/01/05/my-most-important-twitter-messages-4/feed/ 0     My most important Twitter Messages #3 http://blog.derhess.de/2009/11/06/my-most-important-twitter-messages-3/ http://blog.derhess.de/2009/11/06/my-most-important-twitter-messages-3/#comments Fri, 06 Nov 2009 20:03:47 +0000 admin http://blog.derhess.de/?p=1144
  • My most important Twitter Messages #6
  • My most important Twitter Messages #4
  • My most important Twitter Messages #5
    • ]]>

    Twitter von der hess
    A small summary of my Twitter messages from September - October 2009:

    Allgemein (General)

    UX and Interaction Design:

    Projekte und Experimente (Projects and experiments)

    Neue Technologie (new Technologies)

    Programmierung und Software Design (Programming)

    Game Developing:

    • Great news. The unity Game Engine is now free for Indie Game Developer
    • Do you need sounds for your (Flash) Game? Then check this cool app Thx to 8bitRocket.com

    Flash and Flex

    Share/Bookmark

    Related posts:

    1. My most important Twitter Messages #6
    2. My most important Twitter Messages #4
    3. My most important Twitter Messages #5

    ]]>     http://blog.derhess.de/2009/11/06/my-most-important-twitter-messages-3/feed/ 0     The new YouTube AS3 Chromeless API in Flex, Air, Flash http://blog.derhess.de/2009/10/27/the-new-youtube-as3-chromeless-api-in-flex-air-flash/ http://blog.derhess.de/2009/10/27/the-new-youtube-as3-chromeless-api-in-flex-air-flash/#comments Tue, 27 Oct 2009 16:23:27 +0000 admin http://blog.derhess.de/?p=1098
  • Vimeo Moogaloop in Flex – FlexVimeoPlayer Component
  • Working with Vimeo Moogaloop API in Flash
  • Die Gretchenfrage: Wann Flash und wann Flex?
    • ]]>     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.

    The other classes just simplify the coder's life. So I created some static classes for the various video quality parameters (YouTubeVideoQuality Class), the various PlayerStates (YouTubePlayingState), the YouTube errors (YouTubeError) and of course the available YouTube events (YouTubeEvent).

    I wrote an example application for you, which should be very easy to understand. In this very small Flex application you can stop, play and pause the YouTube videos:

    //----------------------------------
//  YouTube Player Control
//----------------------------------
private function handlePlay(event:MouseEvent):void
{
	youTubePlayer.playVideo();
	this.addEventListener(Event.ENTER_FRAME,handlePlayingTime);
}
 
private function handlePause(event:MouseEvent):void
{
	youTubePlayer.pauseVideo();
	this.removeEventListener(Event.ENTER_FRAME,handlePlayingTime);
}
 
private function handleStop(event:MouseEvent):void
{
	youTubePlayer.stopVideo();
	this.removeEventListener(Event.ENTER_FRAME,handlePlayingTime);
}
 
// frame-based Intervall for showing loading and playing process
private function handlePlayingTime(e:Event):void
{
	labelTime.text = youTubePlayer.getCurrentTime() + " / " + youTubePlayer.getDuration();
 
	progresPlayingVideo.minimum = 0;
	progresPlayingVideo.maximum = youTubePlayer.getDuration();
	progresPlayingVideo.setProgress(youTubePlayer.getCurrentTime(),youTubePlayer.getDuration());
 
	progressLoadVideo.minimum = 0;
	progressLoadVideo.maximum = youTubePlayer.getVideoBytesTotal();
        progressLoadVideo.setProgress(youTubePlayer.getVideoBytesLoaded(), youTubePlayer.getVideoBytesTotal());
}

    Some behaviours of this Flex-based YouTube component is adjusted for the Flex Framework. If you would like to change the size of the YouTube Player, you can use the witdh and height properties of the component. Furthermore there exists some other properties:

    [Bindable] public var volume:int;  // Value between 0 and 100
[Bindable] public var playerState:Number; // Read-only!!!!
[Bindable] public var playbackQuality:String; // Use the static variables of the YouTubeVideoQuality class

    Handling and managing of the YouTubeEvents are the last thing I would like to explain. I support the same 4 events, which the YouTube API supports. The only difference is that I wrapped the data of the events in a special YouTube Event for an simpler event handling and code completion.

    [Event(name="youtubeStatus", type="de.derhess.video.youtube.YouTubeEvent")]
[Event(name="youtubePlayerLoaded", type="de.derhess.video.youtube.YouTubeEvent")]
[Event(name="youtubeError", type="de.derhess.video.youtube.YouTubeEvent")]
[Event(name="youtubeVideoQuality", type="de.derhess.video.youtube.YouTubeEvent")]

    So here I is my code of my app. I think it is very self-explanatory...

     /* Here should be some code but wordpress always crashed
because of parsing problems... Please download the code
and look at line number 23-112 in the src folder the file
flex_youTube.mxml */

    The rest of the functions contains exactly the same functionality as the YouTube API. If something ambiguous, please look at the YouTube API documentation or leave a comment. THX!

    Download the Flex YouTube components and source code


    Share/Bookmark

    Related posts:

    1. Vimeo Moogaloop in Flex – FlexVimeoPlayer Component
    2. Working with Vimeo Moogaloop API in Flash
    3. Die Gretchenfrage: Wann Flash und wann Flex?

    ]]>     http://blog.derhess.de/2009/10/27/the-new-youtube-as3-chromeless-api-in-flex-air-flash/feed/ 12     Independent (Flash) Developer: Is it possible?! http://blog.derhess.de/2009/10/05/independent-flash-developer-is-it-possible/ http://blog.derhess.de/2009/10/05/independent-flash-developer-is-it-possible/#comments Mon, 05 Oct 2009 09:15:38 +0000 admin http://blog.derhess.de/?p=1038
  • Flash Indie Developer Part 3: Short list of risks
  • (Flash) Independent Developer: Traum oder Wirklichkeit?!
  • Flash Indie Developer Part 10: Abschluss
    • ]]>     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.

    Comparing the job opportunities

    Comparing the job opportunities

    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.

    (Flash) Independent Developer Universe?!

    The (Flash) Independent Developer Universe?!

    _

    I will start with the basement of an Independent Developer:

    After this introduction stuff I will go on with the biggest topic generate revenues with your shit ;-) It is not about becoming rich, how I have already mentioned! It's more about how I could survive outside in the big digital jungle. I defined for me five important sources of income. Mostly this topic depends a lot on your strengths and weeknesses. Maybe or even surely, there exist some more possibilities of  income. If you find any other possibilities please post a comment! I decided me for these ones:

    • Online Advertisement
    • Lectures and courses
    • Online Shops
    • Game Developing
    • Contests

    Every source of income will be explained more in detail later. Additional, I will compare these sources income to each other. So that you can see your portfolio of income.

    I really hope you will enjoy this blog series and leave a comment for my points. THX! :-)

    Share/Bookmark

    Related posts:

    1. Flash Indie Developer Part 3: Short list of risks
    2. (Flash) Independent Developer: Traum oder Wirklichkeit?!
    3. Flash Indie Developer Part 10: Abschluss

    ]]>     http://blog.derhess.de/2009/10/05/independent-flash-developer-is-it-possible/feed/ 3     An Adobe Air Component for the Vimeo Moogaloop API http://blog.derhess.de/2009/09/22/an-adobe-air-component-for-the-vimeo-moogaloop-api/ http://blog.derhess.de/2009/09/22/an-adobe-air-component-for-the-vimeo-moogaloop-api/#comments Tue, 22 Sep 2009 09:00:00 +0000 admin http://blog.derhess.de/?p=1006
  • Vimeo Moogaloop in Flex – FlexVimeoPlayer Component
  • Working with Vimeo Moogaloop API in Flash
  • An example how to use the VIMEO Moogaloop Javascript API
    • ]]>     Vimeo Moogaloop API Picture Adobe Air
    space50px
    I have already mentioned it in an earlier blog post that I am still working on a vimeo component for the Adobe AIR environment. Now I have created version which is stable enough for a intensive testings.  So if you would like to use it for your Air Application, don't hesitate to use it. I would be very happy about some feedback messages from you.

    Now I describe some special functionality compared to my FlexVimeo Player component. Because of the incompatible command Security.allowDomain() in the Adobe Air environment  (which is essential for working with the Vimeo Moogaloop API ), I had to create a seperate remote player. This remote player receives control message and send control messages via LocalConnection to the AirVimeoPlayer Component. So if you use my AirVimeoPlayer Component, you must always use my remote_vimeo.swf File for controlling the Vimeo Moogaloop API. It works in the same way as the youTube AS3 API Wrapper.

    The other not so nice thing is that I ran in some perfomance issue because of sending to many messages via LocalConnection. So I had to put down the amount of update message for the PlayingState.Playing, but that should not be problem for you. In my cases it works fine.

    Otherwise the API of the AirVimeoPlayer is almost the same as the FlexVimeo Player API. So I supported absolutely the same functionaltiy. You can listen to the Events:

    [Event(name="vimeoPlayerLoaded", type="de.derhess.video.vimeo.VimeoEvent")]
[Event(name="vimeoDurationChange", type="de.derhess.video.vimeo.VimeoEvent")]
[Event(name="vimeoStatus", type="de.derhess.video.vimeo.VimeoEvent")]

    space50px
    For controlling the User Interface and the Vimeo Video, you can use these functions:

    public function stop():void;
public function play():void ;
public function pause():void;
 
/**
 * Seek to specific loaded time in video (in seconds)
 */
public function seekTo(time:int):void;
 
public function unloadVideo():void;
public function destroyPlayer():void;
public function toggleLoop():void;
 
//----------------------------------
//  Screen and RenderManagement
//----------------------------------
 
/**
 * enable HD for the player, but it seems that it is not working?!
*/
public function hd_on():void;
public function hd_off():void;
 
public function showLikeScreen():void;
public function showEmbedScreen():void;
public function showHDScreen():void;
public function showShareScreen():void;
public function showVimeoScreenControlls():void;

    space50px
    And the properties of the AirVimeoPlayer are still the same as the FlexVimeoPlayer Component, except the additional property remotePath:String, which defines the url where the remote player is.

    [Bindable] public videoClipID:int; // The vimeo video clip id
[Bindable] public duration:Number; // read-only property
[Bindable] public currentTime:Number; // read-only property
[Bindable] public playerState:String; // Have look on the VimeoPlayingState Attributes
[Bindable] public playerColor:uint; // HexValue of the Player Color
[Bindable] public volume:Number; // Volume of the video Player instance
 
[Bindable] public remotePath:String // This is the new property
 
//--------------------------------------------------------------------------
 //
 //  Additional getters and setters
 //
 //--------------------------------------------------------------------------
[Bindable] public isPlayerLoaded:Boolean; // read-only property
public isVideoPlaying:Boolean; // read-only property

    space50px
    I think this information is enough about this kind of component. You can download the testing vimeo app or the whole vimeo air package, which contains the air installation data and all needed source files.

    Download the Vimeo Air Component Package


    Share/Bookmark

    Related posts:

    1. Vimeo Moogaloop in Flex – FlexVimeoPlayer Component
    2. Working with Vimeo Moogaloop API in Flash
    3. An example how to use the VIMEO Moogaloop Javascript API

    ]]>     http://blog.derhess.de/2009/09/22/an-adobe-air-component-for-the-vimeo-moogaloop-api/feed/ 3     Meine wichtigsten Twitter Messages #2 http://blog.derhess.de/2009/09/09/meine-wichtigsten-twitter-messages-2/ http://blog.derhess.de/2009/09/09/meine-wichtigsten-twitter-messages-2/#comments Wed, 09 Sep 2009 09:51:21 +0000 admin http://blog.derhess.de/?p=983
  • Meine wichtigsten Twitter Messages #1
  • My most important Twitter Messages #6
  • My most important Twitter Messages #5
    • ]]>     Twitter von der hess
    Hier eine kleine geordnete Zusammenfassung meiner wichtigsten Twittermeldungen:

    Allgemein (General)

    Projekte und Experimente (Projects and experiments)

    Neue Technologie (new Technologies)

    Programmierung und Software Design (Programming)

    Game Developing:


    Mobile and Flash Lite

    Flash and Flex


    Share/Bookmark

    Related posts:

    1. Meine wichtigsten Twitter Messages #1
    2. My most important Twitter Messages #6
    3. My most important Twitter Messages #5

    ]]>     http://blog.derhess.de/2009/09/09/meine-wichtigsten-twitter-messages-2/feed/ 1     An example how to use the VIMEO Moogaloop Javascript API http://blog.derhess.de/2009/08/19/an-example-how-to-use-the-vimeo-moogaloop-javascript-api/ http://blog.derhess.de/2009/08/19/an-example-how-to-use-the-vimeo-moogaloop-javascript-api/#comments Wed, 19 Aug 2009 14:49:34 +0000 admin http://blog.derhess.de/?p=935
  • Working with Vimeo Moogaloop API in Flash
  • Vimeo Moogaloop in Flex – FlexVimeoPlayer Component
  • An Adobe Air Component for the Vimeo Moogaloop API
    • ]]>     Last time I worked a little with the Moogaloop JavaScript API, because I thought it would be a nice workaround solution for integrate the Moogaloop API in an Adobe AIR Application. First time I tried the example code from the vimeo api documentation and it worked fine on my webserver. But for my case I did not want to use the SWIFF JavaScript Code. Only the SWFObject Code for embedding Flash Content in HTML was for me o.k. So I spent a few hours to get this API work without this SWIFF JavaScript thing. I tried a lot, failed a lot, cried a lot and laughed a lot about myself and my limited JavaScript knowledge. So now I am happy with my current version, because it works fine without this SWIFF thing, except loading a new Video (or should I say loading a new clipID) into this SWF Container failed. So if anyone has an idea, please post a comment here!

    Download SWFObject  Code Example

    Share/Bookmark

    Related posts:

    1. Working with Vimeo Moogaloop API in Flash
    2. Vimeo Moogaloop in Flex – FlexVimeoPlayer Component
    3. An Adobe Air Component for the Vimeo Moogaloop API

    ]]>     http://blog.derhess.de/2009/08/19/an-example-how-to-use-the-vimeo-moogaloop-javascript-api/feed/ 4