Comments for b-log - betriebsraum weblog

Comment on Efficient Gesture Recognition and Corner Finding in AS3 by sarah

sarah — Tue, 15 Nov 2011 08:03:44 +0000

I keep trying to download your code, but it wont run on my machine…
I says there’s an error on btnAddGesture

Comment on Faster parallel MXMLC compilation using Ant by HC

HC — Thu, 20 Oct 2011 09:24:40 +0000

Nice Article!

Now, i can build multiple modules using script.
My problem is with custom component.
Some of my modules use custom component (created in same project).

At the time of build, i am getting following error.

[mxmlc] C:\FxProject\src\Module\Module1.mxml(9): Error: Definition components:comp1 could not be found.
[mxmlc] import components.comp1;

If anyone have idea, please suggest solution.

Comment on JavaScript Development vs. Flex Development (and why today, web development sucks…) by Abhijit

Abhijit — Sat, 01 Oct 2011 12:37:59 +0000

Hey this is a great article. I have been in Adobe Flex 3 development since last 18 months. Flex/Flash definitly makes a developer’s life more easy….you can focus on delivering rich user experience instead of wasting yur time on tasks like mulitple browser support.

Comment on Faster parallel MXMLC compilation using Ant by 5kn

5kn — Thu, 25 Aug 2011 13:05:33 +0000

Nevermind, missed that you had the parallel attribute on the for loop, though your use of sequential is still excessive. Once your in a sequential state, you stuck in until your finished.

Comment on Faster parallel MXMLC compilation using Ant by 5kn

5kn — Thu, 25 Aug 2011 13:01:01 +0000

Not sure how you figure this to be running in parallel, and faster than a sequential build script. Probably worth checking how your code works beforehand or even glancing at the Ant documentation.

Your running everything in ‘sequential’ blocks which according to the Ant document runs each task one after another, what you want to use is ‘parallel’ which as the name suggestions runs things at the same time rather than in sequence. The way your using the ‘sequential’ task is pointless, Ant is going to run things in that order anyway since your never entering a parallel state. http://ant.apache.org/manual/Tasks/sequential.html

Would also be better to use the Ant tasks provided by the Flex SDK rather than calling the jars.

Comment on Runtime font loading with AS3 / Flash CS3 (not Flex!) by Seshadri@MF

Seshadri@MF — Thu, 18 Aug 2011 11:09:28 +0000

@santoshs: you need to have a mechanism to set the text format for the static text when the loading is over. And you have to take care that the fonts are already loaded in the main , before you try to access it.
What I used to do is , Load the fonts intially and when they are loaded save them in an class as static variable.Then I used to wait for the intial assets to be laoded(like font and child .swf), and when they are laoded, I call a method(s) in the child swf(s) to set the text format according to the loaded font in the staic variable. All other assets loaded afterwards will be using the staic variable text format to set their text after they are laoded. In this way you can get both your staic and dynamic text hold the loaded font.

Comment on JavaScript Development vs. Flex Development (and why today, web development sucks…) by ash

ash — Fri, 01 Jul 2011 19:56:29 +0000

You’ve got one language and one environment. The toolchain is mature and works pretty damn well. As Flex4 developers, we’re spoiled.

As I dabble in HTML5 development, I notice the complete opposite, everything is fragmented, from languages to libraries.

Although the browser as a platform will probably happen, competitive business pressures will never allow it to remain a consistent platform.

Comment on JavaScript Development vs. Flex Development (and why today, web development sucks…) by Ethan

Ethan — Thu, 23 Jun 2011 14:53:46 +0000

Excellent post. Just wanted to drop a comment and show support for Adobe. I also code in C# and Java.

Comment on JavaScript Development vs. Flex Development (and why today, web development sucks…) by Zoran Kovacevic

Zoran Kovacevic — Fri, 10 Jun 2011 20:57:37 +0000

Inconsistent behaviour in predominant application of javascript in real world browser environment (more or less browser specific DOM, CSS & HTML implementation) results in use of various community evolved abstraction mechanisms (to alleviate this condition – e.g. jQuery) and/or essential knowledge of browser specific issues and respective workarounds (hacks) which are sometimes very poorly documented. Tedious trial and error approach is unacceptably often still the only way to desired functionality. Instead of gaining a common web client infrastructure, browser manufacturers still manage to create (deliberately or not) significant browser environment discrepancies to introduce important lack of compatibility between various browsers. What is needed is a well documented and maintained javascript based industry standard software framework encompassing all relevant functionality applicable to the web client context. Only then will application of javascript in the web client context no longer be a ‘black art’ and become a universally accepted and respected standard approach. In this way javascript based development would have lower cost and produce web applications of better quality – especially for large and complex projects (not to mention being much more stress free, predictable and less ‘guru factor’ dependent :-) ).

Comment on Faster parallel MXMLC compilation using Ant by JustinG

JustinG — Fri, 03 Jun 2011 18:50:39 +0000

What exactly is a “module”? I’ve never seen that term used at all in the Flex development so far so I’m a little unsure of how to go about using this.