Oliver Nassar

This isn't a really important post, it's just something I think need's to be expressed and accepted; it must be accepted. Mootools, YUI, jQuery, Dojo etc. are great. They help a person with very tedious javascript techniques, speed up your applications, and make the UX much richer.

But they are not frameworks. I know this probably just seems like a semantics issue, but I want to make it clear that they are not frameworks, they are libraries. From http://dictionary.reference.com/browse/framework

I was in an interviewing not too long ago for a company with a terrible terrible idea, with easily the most terrible team leader I've ever had the misfortune of speaking with in a professional context, when someone in the interview asked me about 'Progressive Enhancement'.

I didn't know what the term meant, and when he explained it to me, it made logical sense; it's something that I've been doing for years, but I just never knew the formal name of it.

In developing my own mash-up of a framework, drawing inspiration from a lot of different areas, I ran into an interesting hurdles.

Since my framework is MVC based, I ran into a problem whereby calling an action/method in a controller should only be fulfilled if the number of parameters passed in was valid. So for example, if I was dealing with a user's model, and I wanted to return the email address for the user, I would normally access it via a url pattern such as: http://www.website.com/users/details/email/

In JS, I ran into a problem where I needed to create a shortcut string, and then turn that string's value into a reference to a different object.

So for example, I create a string called 'oliver' under the variable shortcut like so: