Posts Tagged ‘JS’
I’ve made a nice little FBJS Slider that I use quite often for animation within facebook. I hope that little snippets and code like this will help other developers make more interested and appealing Facebook applications, like we do at Room 214 currently. First with the styling #slideWrap creates an extremely wide canvas for the [...]

I’ve only recently started developing Facebook Apps and being a strong front-end developer I was confident that I would be able to pickup FBJS quickly. My confidence what short-lived however, once i discovered that Facebook had a very restricting framework and cache system that would make JS programming something quite a bit less desirable than awesome frameworks like jQuery.
There are many ways to communicate and store data from front-end to back-end, but many require AJAX which may take too much time to develop or might not fit the project correctly. A neat alternative to save data and be able to access that data from the server is using browser cookies. Cookies can be created and destroyed by javascript, and while the syntax can be confusing, I’ve gathered this little script that will make it easier to use…
sIFR (scalable Inman Flash Replacement): allows for dynamically-generated snippets of text to use any font supported in Flash using a combination of JavaScript and Flash embedding to replace characters on the page.
In my last post regarding sIFR, I compared sIFR against Cufon and FLIR. Since there is a great deal of interest in them, I decided to go deeper into what I believe is the superior out of the three..
Combining a poor economy with an ever changing web makes it challenging to stay on the cutting edge. With multiple web languages, platforms, and techniques it’s important to dedicate your time to being versatile and flexible while not wasting time learning skills that you won’t use. In the past 2 years I have learned and mastered many tools and techniques, and I’m here to share what has been valuable and where you can trim the fat from your day.
In the past few years we’ve seen a growing trend towards forcing new typefaces on the web. CSS defines a property for browsers to support a property called @font-face which lets the developer define new typefaces and include the original font file for the browser to download and render the site with. Support for this feature has been implemented in Safari and is due to release with the next versions of Firefox and Opera…