I definitely got the impression working with backbone that it was overkill for an app that’s this simple. It took me considerably longer to build than it would have done to do the same thing in jQuery (which I have done many times before). But considering that it’s a new and unfamiliar framework this was not surprising.

I am hoping that as I add more functionality to the demo app I will begin to appreciate the benefits of backbone and will be able to develop faster with it than without it… we shall see.

If not I can always start again and have a play with knockout!

Thanks for your tips around folder structure. I will look into it.

Merry Xmas!

Before you continue to extend it, move some files around. Structuring by extension is not useful, group by feature instead. Move dependencies into a vendor folder, helpers into a lib folder, feature specific files into an appropiate folder. Not much there yet, but once it starts growing, that’ll help a lot with navigation. Templates, JS and CSS files should share a folder when they’re related.

Thanks for your input. I have been meaning to update the post and mention that kind of technique for a while now. It is definitely a useful technique for some situations.

C

#myDiv2 {
position: relative;
background:#fff;
padding:8px;
border:3px solid #222;
}

#myDiv2:after {
content: ” “;
display: block;
position: absolute;
top: -6px;
left: -6px;
bottom: -6px;
right: -6px;
border:3px solid #666;
}

Beers afterwards are a must of course

http://dribbble.com/players/Stompfrog

C

Dribbble is elitist Come join us at http://www.conceptfeedback.com - similar concept, open to the public and there are cool kids there too!

Andrew