Fluid develops and sells the Fluid Retail™ suite of online merchandising tools that simplify, automate, and optimize online merchandising. Fluid also designs and develops award-winning interactive digital retail experiences for clients including Reebok, Timberland, JanSport, Mattel, and The North Face. For years Fluid has been a leader in the development of single page architecture rich internet applications.

Fluid is hiring skilled and passionate software engineers to work with technologies such as Flash, Flex, dHTML, CSS, JavaScript, XML, Java, and SQL. Fluid will provide the necessary technical training in these specific languages; we do not require prior experience with them. We do, however, require that candidates demonstrate proven ability and motivation. Specifically, we require:

• The proven ability to write superior object-oriented code in a language like Java, C++, ActionScript, or C#
• Demonstrated facility with object-oriented analysis and design techniques like design patterns and UML
• Written and verbal communication skills
• The organizational ability to manage time predictably and effectively
• Motivation for professional growth

Fluid also values related skills like illustration, photography, information design, visual design, digital music, and project management. Successful candidates will contribute to the conception, planning, development, testing, and deployment of innovative web development projects. You will be given as much responsibility as you show you can handle.

Candidates would work in Fluid’s San Francisco office. Fluid offers competitive pay and benefits. Please email your resume, a cover letter, and a code sample. Thanks for your time.

There have been a few requests for the the source to the Fire Sphere demo I posted forever ago. I’ve finally gotten around to cleaning up the code and getting it to work with the latest rev of PV3D.

The material applied to the sphere is created using a static PNG with a DisplacementMapFilter applied to it. The DisplacementMapFilter uses a BitmapData object that has had perlin noise applied to it to give the flame effect. A lot of other effects can be created this way as well. Things like rippling water or clouds. It’s just a matter of changing the original image and tweaking the settings of the filter and the noise.

You can get the source here. It’s really quite simple. The whole thing is under 200 lines of code.

Enjoy!

There seemed to be a little disappointment that my A* demo wasn’t actually searching in 3D. Maybe I should have called it A* visualized in 3D. At any rate I’ve revamped things and now have a demo that does search in 3D.

It wasn’t much of a stretch to get things working in the third dimension. The only thing I found particularly tricky was making sure that the path didn’t cut through a solid corner — move diagonally adjacent to a non-walkable node. Besides that everything was pretty straight forward. I also took the time to make sure the code was clean and at least somewhat documented. I haven’t bothered to try to do any optimization and I certainly haven’t put much time into splitting the functionality into proper objects. Nonetheless, here’s the source.

Note that you’ll need to add to your class path Away3D as well as Zeh Fernando’s Tweener w/ Bezier support which powers the animation in 3D.

Enjoy!

Path finding is hardly a new topic for the Flash community. For me however, it’s an area unexplored. While I’ve always found the topic interesting and enjoyed the demonstrations out there in the wild my direction has just simply never really taken me there. Instead I was probably reading about some agile development process or something nice ‘n’ dry like that. Anyway, as I’m now delving deeper into 3D and game development topics I’ve started experimenting with path finding. It’s quite fun and not really all that complicated. At least at the elementary stage that I’m at.

I’ve been working with the A* algorithm which uses heuristics to find the most optimal path from a start node to a destination node within a node graph. The algorithm has many uses, especially in game programming.

In my exploration I’ve combined the A* algorithm with Away3D to illustrate how an object could travel through a 3D environment based on a found path.

It doesn’t always find the best path. Probably something simple I overlooked. I actually find that this could be used as an advantage however. For instance, if this was a character in a game the less optimal path can represent a poor choice by the character giving it a bit of added realism. A thought anyway.