MooWindowSession

  • 29 December

A few months back a guy named Thomas Frank figured out a clever way of carrying variables throughout a window session using window object's name property, which can hold a number of data bytes even if you navigate out of the site and come back.

What I did is a simplistic MooTools-based window session manager implementation.

The pretty cool thing about the library is the fact that the values of the session can be stored as simple strings of as objects, which makes it really easy for us to manage.

Storing a simple session


// init MooWindowSession
var Session = new MooWindowSession();
 
// store a string
Session.set("first", "first value");
 
// returns: "first value"
Session.get()

Storing multiple session values


// init MooWindowSession
var Session = new MooWindowSession();
 
// store an object
Session.set({
  first: "first value",
  second: "second value"
});
 
// returns: {first: "first value", second: "second value"}
Session.get()
 
// returns: "first value"
Session.get().first

Clearing the session


// init MooWindowSession
var Session = new MooWindowSession();
 
// store an object
Session.set({
  first: "first value",
  second: "second value"
});
 
// clear the session
Session.remove()
 
// returns: null
Session.get()

MooToolified – episode 1

  • 19 December

There are some very cool MooTools-based websites out there (and by saying out I mean in) which clearly need mentioning – which is the purpose of the MooToolified series.

Alexbuga.com

Alex Buga is the Creative Director down at MB Dragan – one of the most impressive southeastern Europe Interactive Agencies.

Visit Alexbuga.com

MacHeist.com

No introduction needed.

Visit MacHeist.com

zootool.com

I actually had a brief chat with Bastian Allgeier and as it turns out he’s the one-man-army behind the project – that is really impressive considering the amount of detailed work that was put in this website!

Visit ZooTool.com

TitaniumApp, but no GoldenApp

  • 16 December

After much disappointment with Adobe AIR and the whole dark age that it covered us with, there seemed to be a sparkle of light somewhere far in the horizon – Titaniumapp, his name was.

As noted, trying to create something nice with Adobe AIR ended up in being a total fiasco.

Fortunately there is a new player, his name is Titanium.

I have given it a go, hoping I can move my project to the new, more open platform. Installed the SDK, did some digging just to find out that Titatnium is not as open as the authors make us believe it is.

It’s using Prototype as the fundamental JS framework which unfortunately leaves us with the option of using highly namespaced JavaScript frameworks (YUI or jQuery) as the ones of choice.

This is pretty bad news.

It’s pretty much leaving developers who like to have everything under control (the Frameworks Holly War, don’t want to get into that today), with our pants down.

On the bright side, I like their logo.

Not quite enough AIR to breath with

  • 15 December

Adobe is really trying to bake something new and fresh like AIR, unfortunately it's doing it using outdated half-products, which can constitute in some really disappointing results.

A few months ago I have given some time into developing a project I came up with – which would be quite useful for many AIR developers – unfortunately while Adobe AIR was still a pretty fresh release I ran into many technical obstacles making it pretty impossible to finalize the output.

Now, a few months later, I’ve given it another go just to find that, even though AIR is now in half-way to reach a completely new iteration level, the obstacles are still there, plus a couple of new ones.

I’m a front-end developer so, quite obviously, what I want to use in AIR is the AJAX-HTML option… Adobe had indeed made some good decisions here, ending up with WebKit as the rendering engine – which makes us front-end developers super-happy. Yet, what doesn’t make us that happy is the fact that Adobe decided to trim-down the available features that WebKit provides us with. That leaves us really little to work with, ergo creating beautiful UI using ie. CSS 3 + the -webkit specific properties.

This brings me to the disappointing results point I’ve mentioned at the very beginning. All of the trimming-down, disabling features seem to be caused by Adobe deciding to use some of their obscure and somehow outdated technologies to deal with the completely new ones – which clearly don’t go together.

Come on Adobe, no opacity support? Really? Please.

In other news: I’m really hooked on Iron & Wine lately.

Categories

Recent Tweets

  •  

Current bookshelf