RadioShack Mother’s Day Banner wins Beanie Award
RadioShack’s “Mother’s Day” Rich Media Unit
Chief Creative Officer: Pete Favat
Creative Directors: Stephen Potter and Paul Schauder
Art Director: Chris Geraghty
Copywriter: Matt Kaiser
Designer: Ben Daly
Producers: Skadi Gidionsen, Marcie Hartman
Backend Developer: Greg North
Flash Developers: Greg North, Bryan Paulus
UI Developers: Ben Daly and Bryan Paulus
Information Architect: Jennifer Dolan
Quality Assurance Manager: Bryan Raffetto
Account Service: Sarah Amitay, Caitlin Smith
Check it out:
PointRoll’s Beanie Award
RadioShack Mother’s Day Banner wins Beanie Award
It all starts with the shell. Seriously, a good site shell can make or break a project. It needs to be a combination of structure and flexibility, simple yet complex enough to keep the project from falling apart. Okay maybe that’s a bit much but truth be told the base structure of the site can really have an impact on the way a site performs.
I ran into this on many occasions. When I set out to in the initial stages of the build for Endlessdrama.com it became obvious that if the structure wasn’t though out well we’d never get through the project. Three developers with varying levels of experience tackling a high profile site.
As anyone that’s dabbled with Flash for more then 5 minutes can tell you there’s about a million and a half ways to accomplish the same thing. Solutions as simple or as complex as you could possibly imagine. When facing the fact that we had to have a site live in just over 2 weeks it became very important that even with a tight schedule we needed to thing things through.
We’d build a few sites in house before, I started to ask around and received varying feedback on the builds, it wasn’t sounding like I’d be able to leverage anything we’d built previously. Which was both a blessing and curse. A blessing because I’d be able to think through and design my own shell.
Bringing this back to the point and not be a dramatic story teller here’s what I did. I took a look around, didn’t find anything that seemed promising, found again that there were a 100 different ways to approach this. Being a fan of reusable code, I planned out a few different approaches using various object models. I planned before coding, thought about what the core functionality of every shell for any kind of site would be and went from there.
In the end deadlines caused me to have to stray from the generic abstract shell in order to keep our designer happy. The site turned out great and still had a really solid foundation that should allow me to go back and continue to abstract a bit more. I haven’t had a ton of time to rework the code much but when I do I’ll let you know.
While I’ve been working with Flash for several years now Flex is something I’ve been wishing I had a reason to work with. Up until this point I’ve just assumed that you’d use the Flex Builder to produce Flex Apps with but it seems that Eclipse may offer a better coding environment. So my day has been spent downloading and installing Eclipse, various plug ins and Flex Builder trials. I haven’t had a ton of time to work with any but all I know if I’m coming up with plenty of questions.
Is there any advantage to Flex Builder over Eclipse with the Flex Plug-in?
How do you purchase the Flex Plug-in? I can’t find it anywhere on the Adobe site?
Do you need to have the Flex SDK for FDT to work? It seems to be the only way I can get it to work so far.
After about an hour or so of toying around and lots of google searches, I have Eclipse working with the Flex Plug-in and FDT. I also have MTASC running. I haven’t had much time to actually try to use Eclipse at this point but I’m not really in the middle of any Flash work at the moment so. I’ll let you know when I do get to do some experiments.
I’d almost be willing to bet that you couldn’t have a discussion about Flash these days without the topic of Papervision3d coming up. It’s on everyone list of things to “get up to speed on”. There’s a wealth of tutorials out there and I’ve seen some great examples of it running on a few different sites. It’s incredible when combined with physics engines…
Anyway, here’s my addition to the growing list of “random rotating planes”. Why is mine cool? It’s not, I’m just excited that I was able to pull my materials in from my portfolio site’s XML file.
Here’s the URL, I’m going to have to dabble with getting flash embedded in MT next…
I’ve picked up several Flash and ActionScript related books in the past few weeks look for a review or two in the near future
I’m starting to see some trends coming from out creative department, I’ll post a few experiments / prototypes that I’ve been working on as soon as they are worthy.
There are some amazing things coming down the pipe here at work, obviously I can’t discuss them but once they go live I’ll be sure to post a link to see what we’re working on.
Yeah it was a short teaser of an update but I’m doing the best I can.
We just released a new site at work to promote ESPN Fantasy Baseball. Endlessdrama.com features TV soap stars, Baseball Players and ESPN Experts.
The site turned out great, I’m excited to have been a part of it. As one of the Flash Developers on the project I’ll talk more about my role and the process of building the site later.
Be sure to take a look at ESPN Fantasy Baseball – Endlessdrama.com
It seems that once again I’m finding myself looking at a Flash file that was built for a project and is now being “updated”. While the file works well, does what it’s supposed to and has been a successful project, it’s a great example of how not following Best Practices causes issues for the person that has to work on the file next.
The file has ActionScript in about 100 different places, variables named “pXsAt”, code on MovieClips and the same code appearing in at least 5 different places. While this was the norm only a few versions of Flash ago and again this file works and does everything it should. It’s a perfect example of why people need to make sure they use best practices. Convert to modern coding conventions and why projects need to be scoped properly, scheduled properly and of course why I should look at the mess I’m getting myself into just so I can do more Flash projects.
Back to my mess…
I picked up “Essential ActionScript 3.0 last week off Amazon. I’ve been paging through and reading sections that seem important and I’ve got to say, I’m really impressed with the book. It’s an O’Reilly book, so it’s not really news that it’s good.
I’m impressed with the way the book builds from example to example and chapter to chapter. Though most of the material so far, about 250pgs, is more a review then new information for me, I’ve picked out some things that I’m looking forward to adding to my projects.
In general, I haven’t hit the AS 3 specific material yet. Well, I have but this is still fundamental programming concepts mostly at this point. I’ll have to check in again later with an updated review.
I’ve been trying to find a way to structure my projects and client work so that the folder structure isn’t a complete disaster. We haven’t had great luck here at work getting everyone using the same structure and frankly not everyone really puts as much effort into working that way as others.
This probably seems like a silly post. You see lately it’s become a critical issue that working in an efficient, structured manner that I’m forced to post on this. Is it really that difficult to follow a directory structure? A naming convention? A way of working? Advancing your knowledge is a great help in working with other people, but setting and following best practices goes a long way to the success of a project.
Anyway, before I get to far off track, my goal is to get all my work into an ordered folder structure. My only concern is how much is helpful and how much is too much. Time will tell, hopefully in the end if I follow my own advise I’ll never have to worry about it again.
I need more coffee…
Not sure what award this is.
American Legacy Foundation’s “Singing Cowpoke” website won
Best Non-Profit Website!
Chief Creative Officer: Pete Favat and Alex Bogusky
Creative Director: John Kearse and Tom Adams
Associate Creative Director: Meg Siegal
Art Director: Samiah AbdulBasir, Meg Siegal, and James Adame
Copywriter: Roger Baldacci
Designer: Samiah Abdulbasir, James Adame, Miyoung Russell and Meg Siegal
Illustrator: James Adame
Producer: Barry Frechette
Ass Producer: Zach Jagentenfl
Programmer: Ebbey Mathew
Flash Developer: Chris Teso
Flash Animators: Jeff Hayes, Chris Teso
Flash Mechanic: Bryan Paulus, Joel Caruso
Information Architect: Joe Antonuccio
Account Service: Allison Begin, Tamy Waserstein, and Kelly Schutz