One thing to watch out for: The application accesses your photos as an anonymous user – so if you have restricted access to the originals then it can only see the next size up. You’ll know what I’m talking about if your photos look pixellated. To fix this you need to change the photos’ license option to “creative commons” – or probably uploading a bigger original and keeping all rights reserved would also work (didn’t try that yet). Now I’ll have to follow in @NickHodge‘s footsteps and go WordPress theme hunting to find something that matches my swish new photoblog

Cocoa Dev Central: Learn Cocoa. It’s a simple tutorial assuming no previous experience.

Some points raised around the proliferation of “because I can” programming – overuse of drag ‘n drop where a one-click could star, shortlist, etc

Principle: Keep a light footprint.

Posterchild is http://digg.com. One-click voting for items. Kevin Rose (founder) thinks that the one-click Ajax vote was key to Digg’s success. It removed usability pain points.

“Paradox of choice”: – The more choice you offer users withing a specific action, the less they like it.

“Design for Engagement”: Use invitations and feedback, treat it like impulse buying in the supermarket.

“Cross borders reluctantly”:

• “endless scrolling” – avoid paging.
• Hover details / “sneak peek” – users can preview in thumbnails on hovering so they dont have to click and leave the page.
• Inline assistance.
• Lightweight popups vs full window popups.
• Every page boundary you make the user cross is a “speedbump”.
• Rethink process flows.

Search results are a bad place for “endless scrolling” because you’ll kill your scalability.

Scrolling:

• Shortlist scrolling, image scrolling, scrolling within page “boxes” like divs works.
• Data the user “owns” like thier shortlists is better scrolled than paged.
• Direct selection like highlighting the selected rows works beter with non-paged (endless scrolling) and checkboxes work better with paged results. the user expects the system to remember wht they checked on previous paged (obviously )

Popups: Use in-context expands over popups (popups hide information)

“Prefer direct, lightweight, in-page interaction”

Principle: Give live feedback

• live suggustions
• autocomplete (ajax style)
• periodic refresh (ajax style, not meta refresh ).
• Busy Indicators – visual cue to inform user that something is happening
• “An ounce of preventive design is worth a pound of error-handling code” – I like that quote best
• Use live previews – only really relevant for highly interactive sites
• Use laws of proximity in providing feedback

Principle: Offer an invitation

• Patterns – hover invitation (tooltips / hover actions),
• tour invitation
• drop invitation (visually indicate drop zones etc)
• Keep actions out of it: The user must feel free to explore. Anything they do must be undoable easily. If a popup is shown, the close action must be as easy as the open was. Also don’t make actions happen that make the user feel out of control. Example “show big map” link that hides a lot of page content automatically if you hover on the link. Upsets the user.
• Speak to the brain: refers to the book “Mind Hacks” by Tom Stafford & Matt Webb, published by O’Reilly.
• Show transitions:
• Motion is useful for getting attention. Example – Flickr Zeitgeist. Movement makes people look at the widget, but they feel like they missed the action. makes them want to click to see what they missed.
• Motions are good for state changes – eg delete an item from a shortlist, it fades away
• Keep it sane – ie don’t overuse.

Principle: Think in objects

• Flickr – geotagging of photos. Basic OO principles carried through to UI design
• Think deeper interaction – Multivariate data, focus + context
• Embedded contextual infrmation and mashups

Key Principles for richness:

• Prefer direct
• Provide invitations beforehand,
• Think in objects and tie information to interactivity

References:

• Pattern Library: http://developer.yahoo.com/ypatterns
• Yahoo UI Library: http://developer.yahoo.com/yui/
• Yahoo Blog – http://yuiblog.com
• Bill Scott’s Blog: http://looksgoodworkswell.com
• This presentation: http://billwscott.com/share/presentations/2007/mix07/

Match.com demonstrated the use of integrated live messaging, and the potential looks huge.  suddenly they bring the ability to IM people who are logged in to Windows Live Messenger from the website.  This means that people do not have to actually be on match.com to be messaged through the website.  I would gues that the effective online audience at any point would be grown by a factor of ten.  That’s a compelling business case in itself.

When I’m in os/x though, I have been enjoying using Aqua Data Studio, which is also a free download and is available for windows as well. My favourite feature is that it has intellisense in the query window, something I’ve been waiting for Microsoft to do for years and years. It also allows me to manage all my databases from one tool, including mysql, ms sql, and a whole lot of other formats.

If I had followed my own advice I would have seen ImageMagick has a build for Windows and ships with a good tool for compressing JPEG and other formats, from the command line.  there’s a convert command and a mogrify command.  Mogrify overwrites the source file (ie changes it), compress will output to another file.  Brilliant.  Also released under the GPL.  If you have a website with a wealth of uploaded images and you want to save some space, consider running this over your old images.  Quality at 75% looks good, and the space savings are huge. 

Some of the key things we did were: 

• Established a more scalable architecture
• Introduced more effective use of css and table-less layouts 
• Introduced nUnit 
• Threw out SourceSafe and moved everything over to Subversion, eliminating checkouts blocking work and allowing a more structured branching release process. 
• Introduced some key Agile development ideas like continuous integration, user stories, code reviews and more 
• Moved towards Scrum as a management technique 
• Eliminated the old 1.0 and 1.1 framework bits and pieces and rolled out our first asp.net 2.0 systems. 
• Eliminated Crystal Reports (hurray!) 
• Brought in the use of more .net goodies like caching, master pages, section handlers and more 
• Introduced and rolled out the concepts of syndication and extensibility 
• Extended the dev team with some really good new people and grew with some really good old people  
• Shifted our culture towards being more inquisitive, more technically aware, and learning more of how to be creative (my personal favourites are no 9 and 29) 
• Extended the concept of offline processing for asynchronous tasks based on a simplification of a design I’ll admit to having pilfered from Seth

We didn’t acheive all that I would liked to have acheived, but all in all I would say that the team is operating a league above where we started out this time last year and I would call our efforts very successful.  And worth it

This search engine also indexes cvs and subversion repositories so if you have a web-accessible commercial svn repository you may want to review your security and block the crawler :P

Google have made the search results available via GData/XML feeds and are hoping for the developer communities to build tools to leverage it, such as IDE add-ins.

I declared a sample Titles enum just to test with:

    public enum Titles
    {
        Mr = 1,
        Mrs = 2,
        Dr = 3,
        Hon = 4,
        Miss = 5,
        Master = 6
    }

I then get the type of the enum, and then do a foreach loop to get all the values available.  Enum.GetValues retrieves all the values in the enum.  The behaviour of ToString and ToInt mean that it is possible to populate combos straight off of enums. 

     class Program
    {
       static void Main(string[] args)
        {
            Enumerate();
        }�br />         private static void Enumerate()
        {
            Type title = typeof(Titles);
            foreach (Titles item in Enum.GetValues(title))
            {
                Console.WriteLine(String.Format (“Title number {0} is \”{1}\”",
                    Convert.ToInt16(item), item.ToString()));
            }
            Console.ReadKey();
        }
    }