We just purchased our home here in Austin, Texas, and were super stoked to find out that the WHOLE house was wired for audio.
The downside was that once we built out shelves, mounted the TV, and set up all the equipment that the male adapter of the HDMI routed through the wall was – well… f@*kd.
I didn’t find any thorough, clear, and effective approaches of splicing an HDMI cable, so I’ve decided to log and then blog my efforts!
I’ve been working with Docker a ton lately, and recently decided to deploy Jenkins on Alpine within a compose of other private repositories/registries/etc.
However, as soon as I wanted to use Docker within a Jenkins Pipeline, things went south really fast.
So I know some of you have heard of my pending posts (yeah… I’m still working on them… sorta)…
But I just simply had to post this!
Super quick post… I’ve created a simple LayoutHelper for Josh Tynjala’s FoxholeControls.
This will help simple containers lay out their components without having to do a ton of custom property/member inspection for each child you want to lay out!
Another quick one comin at ya!
When working on porting over my very first foray into Flex, my Flex particle engine, to the more current Flex4.6 for mobile purposes, I realized I wasn’t getting key events or change events from a debug Spark TextInput!
This is a short post, in which I show how to set a common background for your Flex Mobile Application.
In Flex 3, there was a backgroundImage style property, but in Flex 4 things have drastically changed. Often times, this means you need to re-skin things in order to achieve your goals.
I recently was tasked to get part of an older Flex 3 application onto an iPad. Why not, right? I mean, FlashBuilder 4.5.1 and AIR 3.0 are awesome… This should be cake, right?
There’s a lil gotcha – Flex 3, or MX components, ooorrr Halo components, are not exactly welcomed on Mobile.
Fret not! I’ve figured out the task, and it’s rather simple. (more…)
While doing mobile development, one of the most frustrating things has been form input.
If you’ve looked at any Playbook development, you’ll see QNX has something called ReturnKeyType specifically for this reason.
Being as stubborn as I am, I wanted a plain Flex approach at accomplishing what I wanted, and not to use the QNX library.
Most of this actually is related to Mobile development with AIR, considering there isn’t a bunch of desktop development focus in the SDK.
Adobe released an early version of Flex 4.5 (Flex Her0) just before Adobe MAX last year, and tons of people grabbed it and started writing mobile apps with it.
Since then, quite a bit has changed both in common functionality, and under-the-hood things like List scrolling.
I couldn’t find any clear documentation about migrating your applications, so I figured I’d try to throw together as much information as I could think of.
I will be updating this frequently as I find more changes or caveats while converting my apps, or from what I hear from others.
So, I partook in the free Playbook offer sponsored by RIM, and developed a few applications for it.
This post is NOT about my apps, but rather touches on the process, as well as what I think about the Playbook as a device, and platform.