Quickfix & Browser Discussion

In my blog article, "Fun-fun-FUNctions...with IE8", I offer a quick-fix for developers having JavaScript issues when creating content for Windows Internet Explorer 8 browser. While both the example and the workaround code is relative simple, there is a larger discussion at work here: browser compatibility.

Certainly, we developers may have a favorite or preferred browser to develop for, but in the end, our code must be malleable and flexible, able to 'live' inside whatever browser or environment our client(s) require.

Because our Team has many different clients, all with different browser/environment needs, we have become very proficient in the (at-times-not-so-simple) task of just 'making it [the project] work'.

Sometimes the solution is a quick-fix, like the in the article above; sometimes the solution is more involved and may require a complete re-writing of code...or (if we get lucky,) tracking down, learning, and using a new code-set or development tool.

Pay no attention to that
JS code behind the HTML page!

We make the magic happen, across many different platforms and settings. Yet, unlike that famed and faraway 'Wizard', we do not mind showing others what happens 'behind the curtain'.  We like to share and hope to learn from others that share with us, as well.

Feel free to share your tips, tricks, and workarounds with us so that we can all learn from each other...especially as more and more of us begin developing projects across multiple browsers. Tweet us: @mas_edev, @eLearnDevGeek, @damoEdev, or @gardelearndev.

Cheers!

Great post in UXmag.com on User Experience Leadership.

I wanted to point out a great article I read today on UXmag.com - 5 tips for effective UX Leadership by Paul Holcomb. His insights speak to many of the frustrations I know I feel when working on a project, especially when working in isolation (functional silo!). How do you move beyond being seen as the deliverables person, and move into a more strategic role within your company, or with your clients.

Greg often talks about what questions need to be asked BEFORE a project starts - and it is almost as if he and Paul got together on this article. I think it is because, from a UX perspective, these are common sense considerations. But common sense depends on common perspective, and when most of our co-workers or clients are NOT looking at things from the UX perspective, but rather from a project management or team management or even SME perspective, those things that are common sense to us aren't necessarily going to be common sense to them!

Check it out - its a great read!

Wade

Using Photoshop Actions for Rapid, Quality E-Learning Images

When developing eLearning courses, particularly those of a longer variety, we often create re-usable page templates that include elements such as the GUI, a content area, and a designated space for graphics.  A simple picture (and its thousand words) often is the best visual tool for supporting the content, but just plopping down a raw image typically will jar the overall look-and-feel (especially if your GUI is up to modern standards) and can throw off the entire course (think of a Porsche with primer paint...).

Giving the image an appropriate border treatment or other graphic enhancement (whether we’re talking altering the photo itself or adding things like drop shadows or reflections) will allow your image to work like a part of the team, rather than a distraction that should be benched.

Of course, image treatment takes work and time...and remember my reference to courses "of a longer variety?" What to do when you need treated images on several pages?

You could spend all your time replicating the same graphic design technique over and over...Or you could do it once while recording your technique in Photoshop as an action and then apply that action to your stack of images, potentially saving you countless hours otherwise spent in a PS rut.

http://www.republicofcode.com/tutorials/photoshop/mass_resize/