Comments for Nils...ActionScript Developer

Comment on Smoothing with OSMF: Harder Than You’d Think by pg

pg — Mon, 19 Mar 2012 20:44:21 +0000

Thanks for this – just what I needed and works like a charm.

Comment on Getting Sassy by Edilson

Edilson — Wed, 29 Feb 2012 14:49:34 +0000

Semantic CSS and OOCSS, dlglaticamoy, will never live together in harmony. It is clearly one or the other. Following the OOCSS model you will quickly start creating a library of non-semantic css widgets’ that you apply to your markup. Being a preacher of building a project styleguide, I was OOCSS before OOCSS was a thing. But now becoming a more experienced Ruby developer, I am coming to the same conclusions as you are with the coupling of OOCSS and SASS. In fact, I can’t see any other way of doing it. A great example. I am working on a project where I have aside bubbles for additional information. Going with OOCSS I would need to have a class of something like more_information appended to both to cover the simular UI cases. Then to adjust for the delta between the two, I then would add the class of call_to_action’ and white_papers’. But using SASS, I can simply use the single semantic class and then using the similar UI as a mixin within SASS, I can reuse that style without copying and pasting. So in essence, I guess what we are saying here is in principal the same thing, build re-useable elements within your CSS and have a way to easily re-use that code. I guess you could say, OOSASS?

Comment on Printing Multiple Spreads on One Page with InDesign and Acrobat by Jason

Jason — Sun, 19 Feb 2012 17:31:43 +0000

Thanks for this tidbit – it did work for me!

Comment on Smoothing with OSMF: Harder Than You’d Think by dkehl

dkehl — Thu, 19 Jan 2012 03:16:02 +0000

I found an alternate way of setting screen smoothing when using an F4MElement, which doesn’t have a direct reference to the smoothing property. If you listen for the DISPLAY_OBJECT trait, you can retrieve a DisplayObjectTrait from your mediaElement object. This trait has a property called displayObject, which is the object that is responsible for displaying the media. While the property is of type DisplayObject, the actual implementation is of a class called VideoSurface, which has a smoothing property you can access and change.

So you can do something like this:

var mediaPlayer:MediaPlayer = new MediaPlayer();
//This should theoretically be any kind of MediaElement subclass
mediaPlayer.media = new F4MElement(url);
mediaPlayer.media.addEventListener(MediaElementEvent.TRAIT_ADD, traitListener);

private function traitListener(event:MediaElementEvent):void
{
if(event.type == MediaElementEvent.TRAIT_ADD && event.traitType == MediaTraitType.DISPLAY_OBJECT)
{
var displayObject:Object = (mediaPlayer.media.getTrait(MediaTraitType.DISPLAY_OBJECT) as DisplayObjectTrait).displayObject;
//Set the smoothing value to what you want.
displayObject.smoothing = smoothingValue;
}
}

Comment on Advertisement Plugin in REOPS for Timeline Happiness by Advertisement Plugin in REOPS for Timeline Happiness | RealEyes Media

Advertisement Plugin in REOPS for Timeline Happiness | RealEyes Media — Fri, 02 Dec 2011 17:10:13 +0000

[...] By: Nils Thingvall [...]

Comment on CKEditor is Awesome! by Using CKEditor Allows Your Clients to Edit HTML, Add Images | RealEyes Media

Tue, 08 Nov 2011 22:11:37 +0000

[...] like to use in your own workflow, be sure to check out what Realeyes developer Nils Thingvall has to say about it. Nils’ article gives you helpful tips on configuring your editor to work with image [...]

Comment on Smoothing with OSMF: Harder Than You’d Think by admin

admin — Mon, 07 Nov 2011 22:17:04 +0000

Robert, that works if the top level element is a VideoElement. The problem arises when the VideoElement is wrapped in layers of ProxyElements, SerialElements and the like. Then you’d have to loop through the whole structure to find the VideoElements. By hijacking the element in resolveItems, I can check the elements at the very core of the onion of elements and set smoothing there.

Comment on Smoothing with OSMF: Harder Than You’d Think by Robert S.

Robert S. — Mon, 12 Sep 2011 18:53:32 +0000

You could check if the MediaElement is a VideoElement. For example:
var mediaFactory:MediaFactory = new DefaultMediaFactory(); mediaElement = mediaFactory.createMediaElement(new StreamingURLResource(httpStreaming));

if(mediaElement is VideoElement) { (mediaElement as VideoElement).smoothing = true; }

Comment on Smoothing with OSMF: Harder Than You’d Think by acromm

acromm — Thu, 14 Jul 2011 01:03:25 +0000

it works! thanks again

Comment on Smoothing with OSMF: Harder Than You’d Think by acromm

acromm — Wed, 13 Jul 2011 20:50:14 +0000

We will try this. Thanks a lot!!!