Life In Texas & The Flash IMS
All very good! Tiring…but definitely good. I’ve updated the site again and gone back to a simple blog system again. I found I simply don’t have enough time for much more than a blurb here and a blurb there.
When I’m not busy at work, I’m busy at home building an IMS (Image Management System). The principles behind it are very similar to those of a CMS but I’ve added an interesting little twist…
I’ve always been in pursuit of a truly dynamic way to handle image content in Flash. Traditional methods require that you push content into Flash from text files or XML files. For the traditional developers and site managers out there, this isn’t much of an issue.
Let’s say however that a client wants/needs to be able to edit image content inside their Flash site and your client isn’t HTML saavy or have staff on site who can manage the content for them once the site is complete. What then? I have recently run into this problem.
The past 5 years, I worked for a small photography studio in a Chicago suburb. Late last year, I moved to Texas. Prior to the move, a website change only required a call down to my office (in the crypt…j/k) and I would be able to update the site in minutes. Now that I am in Texas, when a site change is required, it often entails conference calls, e-mail correspondence and attachments and because I work 100 miles away from home and my labtop, it is almost always hours before I can make any physical change for them.
My solution was to create an OO CMS/IMS coded completely in PHP5 that would run from a MySQL database and give them the ability to change the content inside their site (completely Flash based) without needing to call me for the “simple” stuff. What I’ve was able to achieve was a uniquely simple admin panel that gives them the ability to edit not only their text based content but also their image content on the fly in the easiest way possible.
Now, instead of Flash having to make a ridiculous number of URLRequests for each image, remembering the entire site structure etc, I’m able to use a single URLRequest inside a custom AS3 Class to bring an array of mySQL stored and PHP generated data back into Flash. The result was a cleaner, simpler method for handling and controlling what data Flash would recieve and when.
As a result, I’ve also been able to make subtle, appealing visual changes that simply weren’t possible before because of all the content that needed to be stored to render out each menu, gallery or text blurb that were already hammering the system to its peaks. For instance, the senior menu which contains 7 different galleries, 150+ images (plus their thumbnails) and over 30 plus text blurbs, couldn’t afford much in the way of visual stimuli prior to removing all of these calls and classes from Flash that are responsible for displaying thumbnails, cycling timers, etc.
I’m putting the finishing touches on the system now and plan to bring it online by mid-April when I update the Fedler Studio site. Once the site goes live, I’ll be back to posting on my blog on a regular basis and hopefully providing insight into what I did as well as the lessons I learned.
Later!