I think that that the link should open the unsubscription web page in my browser where I must confirm my unsubscription. (I could have clicked the link by mistake so it’s nice to provide a confirmation button) When I confirm my unsubscription all I want is just a message that says whether or not I successfully got unsubscribed. What I see in a lot of newsletter-systems that you unsubscribe from is that you get a unsubscription success email. Yes, another email you don’t want. I wanted to opt out from the newsletter subscription because I didn’t want to get any more emails.

If you have any other thoughts on this topic, please add a comment!

/Simon

First off, take a look at the demo here. In writing moment the fastest known player was done in less than 25 secs!

This is how I’ve set up the files for the game:

I’ll actually not write any code in this post, I’ll just simply go through each function in the javascript (that is the core of the game) and talk about what each function does. I’ve compressed the files of the game so if you want, you can download them and take a look at the code in your editor when you continue your reading below.

The .html-file is quite straightforward. It has a container-div where the javascript put the actual gameboard, it initiates the javascript and some other stuff. I don’t think there’s any need to go into this file in detail so I’ll just leave it there. The CSS is, as always, just used for the presentation. The image is used for the backside-cover of the cards. The javascript file named memory.js is the interesting part. So let’s take a look at this file and go through each function step by step.

initialize()

The initialize function has a few default options that can be dynamically changed from wherever you initiate an object of this class. This approach by using the Object.extend-functionality on the default-options is, in my opinion, very powerful since it adds a lot of flexibility to your code.

I said I wouldn’t post any code in this post but there might be a point to show how you can change these default options. You do that where you create an object of the memory class (in this case in index.html) and this example below shows how you could change the rows and cols without altering the javascript-file itself:

var m = new Memory({
rows: 3,
cols: 4
});

So, let’s get back to the initialize function, as you can see, we first set the options for this class. As you see above, the code is dynamic so you can change how many rows and cols you want on your gameboard. Please note that there’s no functionality that checks whether the total amount of cards is an even number or not so if you change these params, please have in mind that the cols multiplied by the rows should sum up to an even number.

After that we initiate some of the other default properties of this class and then we call the initCards-function.

initCards()

In the initCards-function we create the cards for the gameboard. We use some loops to make this happen and we check if a color already has been used. It also shuffles the array that is containing the cards. When this function has done what it’s supposed to the code then goes on to the createBoard-function.

createBoard()

Here, the actual gameboard is created and as it creates each card it also adds an onclick eventlistener to each card. When a card is clicked the flipCard-function is triggered.

flipCard()

When the player clicks on a card, this function starts to run and it starts the timer (if it hasn’t already been started) and then it flips the card you clicked and check whether the player has found a pair or not. This is done with the help of the function named getCardNumberFromId().

We’ll that’s it, I’ll not go into more details so if you have any questions or feedback, please post a comment! I’d really like some feedback on the code and if you guys would have done anything differently.

/Simon

I finally solved the problem by downloading version 1.6.12 (instead of the in writing moment latest version 1.7). The Coda-people keeps a museum of older versions of Coda if you want to download them which is a great idea (why don’t everyone do this?), you can find it here: http://www.panic.com/museum/coda/older/

I really don’t know why it stopped working for me. I really like Coda as a developing tool and I know that this works for others in the latest version. Maybe I just had bad luck when upgrading to Snow Leopard I guess? Just thought that this information could be useful if this happens to someone else.

Cheers!

/Simon

I’m going there together with three of my co-workers and you can follow our epic JavaScript adventures at http://creunaatfullfrontal.tumblr.com.

Please do!

/Ida

Ps. Will of course post a full summary of the conference once I’m safely back home again…

// Johan

This is not an in-depth article and, if you want, you can read more about it on jQuery Mobile’s official site that you find here http://jquerymobile.com/2010/10/jquery-mobile-alpha-1-released/

If you want to see the demos, take a look here: http://jquerymobile.com/demos/1.0a1/

/Simon

Being the Child of the Shoemaker

Ida talks about why web developers have poor sites and how to remedy the situation.

Toka Koka Bitches

The post that got us hits from people searching for ”Swedish bitches” :/.

What Role Will Domain Names Play in the Future of the Web?

Simon raises an interesting debate weather domain names will play an important role in our future or not.

Escaping From Encoding Hell

The ultimate guide for when you’re stuck in encoding hell

We are Craftsmen

I take up the similarities between two, on the surface, very different professions.

A big up for project 52. Without them many of these posts would still just be unborn ideas locked inside our heads.

These articles aren’t about trying to force people into something that will steal time and hurt the overall design of their projects. My intention with these articles, as I mentioned in my comment, is to raise some sort of awareness of accessibility among designers. I’m of the strong opinion that the web should be open, free and accessible to as many people as possible regardless of equipment or physical state. I do not agree with people who think the web should only be accessible if you got the latest in technology or a perfect health. Of course it’s not always possible to accommodate for everyone. But having accessibility in mind doesn’t cost anything. I would also like to point out that the tools I link to in these articles are simple test-tools that requires a maximum of minutes in test time.

What about colors?

So back to the topic. There are two things I would like to point out regarding colors. First: I love color. No that’s not it. First: (second try). All colors doesn’t look the same on all devices and screens. This is important to remember. Secondly: There are some combination of colors that some people have trouble to different between. Yes, I’m talking about variations of color blindness. Between 7 – 10% of all males are affected by the red-green type. Because of this it’s necessary to make sure that the most important elements on your web site is easy to distinguish. Elements to check may be navigation, buttons that leads to different kind of actions and other important information.

How do I test my colors?

There are several cool tools out there. I will mention a few here.

1. One really cool tool available for Mac is Sim Daltonism. With it you can simulate different kinds of color blindness and look at your design in a way a person with color blindness would.
2. Coblis – Color Blindness Simulator is an online tool that lets you upload an image to check for problems.
3. Colorfilter is another online tool that lets you test a website. I don’t really know how useful like this is since when there is a live web site it’s usually too late or extremely hard to adjust things.
4. Send your design to friends. Yes, I know. This is not a tool. But consider sending your design to some friends. If possible friends with color problems and ask for their opinion. If nothing else they might be able to track down problems in colors due to differences in screens and devices.

If you feel an urgent need to find out more about color blindness the blog “Grey Means Go” offers some nice reads.

That’s it for now.
Have fun designing with colors!

/Ida

What?

Ok, it’s HTML5. And yea, it’s the new buzz word. And yup, this book is about that cool new thing. So let me tell you what you’ll find in this book. You will find out a bit about the history behind HTML5. You will learn a bit about what’s included. And what’s not included. No CSS3. Of course. Yes, I know CSS3 is cool too but you need to pick up another book for that. CSS3 and HTML have never and probably never will be the same thing.

Who should read?

Look at the title again. See that word? Designers. Exactly. If you are a web designer trying to improve your knowledge in frontend and get the hang on what’s new and exciting this book is for you. I would also dare to say that this book is not unfit for anyone working with the web. Really. The language is smart and not hard on you. Good words and the tone is delightful. (Always wanted to use that word.)

Who shouldn’t read?

If you have closely followed what’s been happening on the web during the last six years I would say that this book got no news for you. The same goes for people who have read every article in HTML5doctor, diveintoHTML5 and have feasted on the specs of WHATWG and W3C. This book didn’t gave me any revolutionary news. I guess I’m too geeky with my feeds. (If this did sound like I’m a cool enlighted web dev that’s on top things… well… well… then you can think of me as a cool enlighted web dev who is on top of things. ) Even so this book is enjoyable. If not for mere reason than boosting the ego and feeling like you actually know something.

Aight. Me be out.
Not feeling comfortable about boosting my ego in public.

/Ida

Ps. If you don’t care to read/buy this book you might enjoy this talk by the author Jeremy Keith