Archive Page 2

A streetview car named “Google”.

The Google StreetView car was recently spotted by a friend of mine driving around here in Shepparton. It was apparently a black sedan, pole camera on the roof, Google magnet logo on the door. It’s unknown whether they’re taking photos of the Shepparton area (which is unlikely, but would be ubercool) or whether it’s just a Google employee borrowing the Google-mobile for the weekend to visit family in the region (more likely, but less interesting), but I’ll be keeping an eye on Google StreetView in the future.

UPDATE: Confirmed! I was out at lunchtime visiting a client and saw the black Google car heading down the main street. What he was doing there, I still don’t know.

Shepparton Show Me and Show MeBay goes live!

Shepparton Show Me WebsiteThe Shepparton Show Me and Show MeBay websites have finally gone live. Mad Web Skills has been responsible for almost every aspect of development for these websites including web design, information architecture, user interface design, database development and php scripting.

The Shepparton Show Me website is running on Mad Web Skills’ own cmsharp content management system, so the client was able to update and manage all website content, including file download areas and photo galleries (with a little help from myself to polish up the content and apply some consistent styling). There’s a few more areas still to be developed for this website over the coming months, including a weblog and secured password-protected areas for committee memebers to use for internal communication.

Show MeBay ScreenshotShepparton Show MeBay is a promotional website running under the Shepparton Show Me banner for a couple of weeks. It’s an online auction with a difference! Instead of bidding with money, you bid with specially coded Shepparton Show Me Dollars which you can get by shopping locally at participating retailers. Users can then register on the website and redeem these Show Me Dollars into their account balance and use them to bid on some great prizes! (Mad Web Skills is also providing one of the prizes — domain name, web hosting and weblog for one year!)

This is the first time such a promotion has been run by the Shepparton Show Me Committee so it’s a bit experimental. Personally I think it’s a great idea and I hope it really takes off and we see it again soon.

“I am not a Snook!”

Apparently I look a bit like Jonathan Snook.

One of these things is not like the others…

At Web Directions, it was mentioned to me by no less than three separate people that I kinda look like the man. In fact, the first one of these people came up to me during the morning tea break, shook my hand and said with a big smile “Jonathan Snook, I presume”. I can’t quite remember who said it, or if they were joking or not. Of course, I thought that they were joking, and it kinda threw me back a bit. I think I responded with a weird laugh and a “Yeah right!”.

So if you’re reading this, handshake guy, and you weren’t joking and thought I was Jon Snook, I humbly apologise for acting like a dick. That’s all I wanted to say. :)

Technorati Tags: ,

WDS07 report: finally!

This is being posted 12 months late, and nobody will probably read this, but I thought it would be good to keep if only for my own reference. Here are the notes I took during Web Directions 07, found in some obscure folder on my MacBook. It seems I didn’t take notes for every session, but here is what I did happen to note down.

Andy Clarke - Think like a mountain

Andy’s main topic was the use of comic books as an influence on art such as movies and extending that concept to the web. He used Sin City and Watchmen as an example. I’ve since read the Watchmen graphic novel, so big thanks to Andy for putting me on to that one!

Many comics span the gaps between panels with design elements, as well as varying the size of the panels. Bringing this across to grey-box layouts for the web, large panels can be used not just for large amounts of content, but to add emphasis, as does sparring use of colour. Reiterating his point from his workshop, make use of new CSS technologies; don’t limit yourself to just capabilities to the lowest common denominator (I’m looking at you, IE6).

Finally, Andy officially announced the CSS Eleven, an international group of visual designers and developers who are committed to helping the W3C’s CSS working group to better deliver the tools that are needed to design tomorrow’s web. They planned to deliver two months deliberation on each CSS3 module, then open for public comment via wikis. It sounded good at the time, but I don’t think much came of it at the end. (I’m currently at WDS08 so I might hit up Jeff Croft or Jina Bolton about what’s happening with it at the moment.)

Chris Wilson - Microsoft - Moving the Web Forward

Chris gave quite a defensive talk about the future of the web from a browser vendors point of view (namely IE), addressing some of the criticisms they receive.

Scott Berkun - The myths of innovation

Scott is a captivating speaker who gave a nice motivational talk about innovation, and how that term gets loosely applied. There’s more to innovation than most people realise, and also in many cases origin stories get made up to glamourise the discovery of the idea, the eureka moment, often ignoring much of the hard work involved in reaching that point. He also dissected the anatomy of innovation. Quite interesting.

George Oats - Human Traffic

George is an original team member from Flickr. We made the assumption that George was male, but were surprised that not only was she a she, but she’s also an Aussie. George gave us a history of Flickr, how it started off as a game, before becoming a photo sharing site. She spoke of the rapid growth of their user base, and what this meant to the future of the company. Flickr has been perpetually in beta for so long that they coined the phase “Gamma” meaning “constantly in development”. I love these real-world examples about start-ups, and how they make it big.

Ben Winter-Giles - Managing Agile Projects

I’m not sure what Ben ended up talking about because I left 10 minutes into the session and headed next door. I hate to say it, but he kinda irritated me. First he went on about the Chinese gardens in Darling Harbour, then rambled on about waterfalls, and laptops. Then he compared horses (and the positions of their eyes on their heads) to humans, then monkeys compared to tigers. Then it was dogs… That was enough for me so without further ado…

Aaron Gustafson - Learning to Love Forms

We missed the preliminary, introduction stuff to this session, but it meant we got straight into the good stuff. I get a few handy hints and tips about how to not only style forms to make them look purdey, but also about how to mark them up properly, improve accessibility, and use proper semantics. The handiest bit of knowledge I learned was about being able to style legends easier by wrapping the contents of the legend element in a span set to display: block, then styling the span. Nice!

Mark Mansour - Red Bubble

Another one of these great start-up presentations. Five things you need to create a new application/startup:

  1. Good people. Respectable, clever. A balanced attitude between getting things done, and getting things right. A culture of caring about your work.
  2. Good tools. Communication tools: Campfire, Wikis. Development tools: Version Control System, Automation tools, Database Re-factoring. Testing tools. Unit testing. Functional testing: Selenium. Continuous Integration. Management Tools. Issues/bug trackng. Storyboarding: put all your tasks (stories) on to physical cards and plan out your “to do”, “doing” and “done” areas, as well as an overflow area for “nice to have” tasks. Use little avatars of team members to show who’s doing what. Documentation.
  3. Simple Development Process. Agile, iterative process.
  4. Ship it!
  5. Fun! Dont mistake seriousness with professionalism. Embrace Ceremonies.
  6. Redbubble used a weekly iteration cycle - Thursday - Wednesday.

    Adrian Holovati - Being smart about your data

    Adrian Holovati was one of the developers of the Django framework for Python. Serendipity! Desirable discoveries by accident. Using effective click-throughs all over your data is good because it increases stickiness as well as usefulness. In order to make this happen, you have to be smart about your data. Start with structures data, but this is half the battle. It needs to be collected by humans, but once you’ve got it, the rest is a piece of cake. All data has structure, so give your data “the treatment”. Advantages: using permalinks for concepts is great (linking to tags or data views). There are also SEO advantages about having things granular.

    Mark Pesce - Mob Rules

    I didn’t take any notes during this final closing keynote because Mark Pesce is such a brilliant, captivating speaker. Nothing I say here can adequately cover Mark’s speech, but I’ll briefly and pointlessly try to give you the gist. Mark describes the mob as a kind of big floating cloud. It’s unstoppable. It’s faster and stronger than you, but at the same time, the mob IS us. The network is not the internet, nor is it the wired, the wireless or in fact any infrastructure. People are the network, and the mob gets what it wants. Mark targeted the telcos, advertising and the pharmaceutical industry as areas where the mob will overthrow, giving the example of mesh networking. I think I’ll just stop here, because I’m sure I’m not doing a good job of explaining this. Needless to say, as always, I left Mark’s speech ever invigorated, inspired and motivated to go forth and do great things. Embrace your obsessions - you will be rewarded!

WDS07: Workshop Day Two

Not really a workshop per se, but the W3C SIG day where various working groups presented a look into what they were up to, and where they were headed. I’ve had bugger-all to do with W3C and it’s inner workings so I was intrigued as to what they actually did. In retrospect however, I should have went to the Javascript workshop which from all reports was pretty good.

Bert Bos (CSS3) covered some of what Andy Clarke spoke about at his workshop yesterday, echoing some of the more cooler features of the CSS3 specification. He illustrated how the advanced layout and grid positioning modules worked, which is super exciting for designer types. This new methodology, along with the new CSS3 selectors module, makes the selector alias theory I had the other week kinda redundant, as markup will no longer require any reference to where the content fits in the the grid, and also makes selecting specific elements easy, even if they are not marked up with a class or id. Bert also touched on the new advanced background images and borders (especially using images for borders). This really excites me (as much as a W3C spec can, I guess).

David Ratcliffe (GRDDL) spoke on a subject that I have no knowledge of and little interest in. GRDDL stands for Gleaning Resource Descriptions from Dialects of Language which is basically a stupid way of saying “bridging the gap between semantic markups” (but I guess BTGBSM is not a very good acronym). I got lost a few times here, looking off into the distance with circus music playing in my head…

Sofia Celic (WCAG 2.0 Draft) first covered the principles of the new draft for accessibility guidelines. There’s some new terminology used, with Checkpoints now being called Success Criteria. Also, some of these criteria are now worded to include more specific values (such as text-sizing should be resizable to between 50% and 200% without loss of content or functionality). This brought the comment “That’s a load of crap” from one audience member. Apparently these values were not based on any real research, illustrating that perhaps some wording may need to be reviewed. Finally, the new draft has the focus moving away from making content accessible to everyone, now targeting solely people with disabilities. A few hard questions from the audience were met with shrugs.

Anne Cregan (Semantec Web) spoke of a framework for sharing data led by the W3C based on RDF. This session reminded me of a comment I heard yesterday that the W3C is run mainly by academics and researchers and doesn’t really relate to web workers in the field. This is where I realised that I’d perhaps chosen the wrong workshop for today, as the circus music returned to my head. Lots of big words like ontology and axioms. Anne believes that this framework needs a killer app before people will see how cool this stuff is, but I just saw a solution where no problems exist (for me anyway).

Chris Wilson from Microsoft (HTML5 and the HTMLWG)started off with a bit of history about the WHATWG and the HTMLWG, then explained that the HTMLWG operates under the W3C Patent Policy, so Chris spent a bit of time talking about how the open standards the HTMLWG deals with needs to be free from IP complications. HTML5 aims to evolve from HTML4 to better describe the semantics of documents and applications, as well as integrate new UI controls such as datagrids etc. They concentrate on a few main principles: compatibility (graceful degradation, supporting existing content, not reinventing the wheel), utility (solving real problems, media independence, security, design, etc) and interoperability (well defined behaviour, avoiding needless complexity, error handling, etc). Chris also spoke of some of the challenges the group faces such as dealing with the openness of of the group which has over 400 members, so understandably there are problems with tone/politeness as well as evaluating the consensus of a subject.

Renato IannellaEugene LevyRenato Iannella (The Policy Aware Web) gave a very political presentation about… *cue circus music* doo doo do-do do doo dooo… Huh? What? Yeah, I kinda lost the plot at the start, but he kinda looks like Eugene Levy, which amused me enough to keep me going to the interesting stuff. :) His talk was about supporting the varied policy languages to control various infrastructures of web usage. The privacy policies you see everywhere are part of this, but there are so many other areas that need to be supported such as accessibility, DRM, mobile sector, content licensing (eg. creative commons, GPL) etc.

Marcos Caceres (Widgets 1.0 Spec) was interesting enough, as he covered something that I’d never really thought about: standardising widgets (single function application often based on web technologies). A widget engine is the software on which widgets run, be it OSX dashboard, YahooUI, etc. but there is currently no interoperability between widget engines. The Widget 1.0 Spec addresses areas such as packaging up widgets, auto updates, embedding widgets in HTML pages, how they’re coded and rendered.

Dean Jackson (SVG) is an entertaining speaker. His talk was on a topic I’d had very little interest in, but by the end I was sold on the idea. SVG isn’t particularly relative to me at the moment, but it was interesting to see how SVG is in use on the web right now in ways that we might not be aware of, such as routes and polygons in Google Maps. Also SVG comes standard on many mobile devices today, especially 3G devices. Desktop UI’s such as Gnome or KDE use SVG for their icons too which was surprising, so it’s fast becoming a vendor-neutral, open standard for vector graphics. Dean suggested that we all go out and have a go at authoring something in SVG, as it’s simply an XML format. SVG is implemented at the same level as HTML, CSS and Javascript, not by plugin, so it can also be styled by CSS natively by the browser, but unfortunately, as usual, IE falls behind with its non-existent support.

So while my look into the world of W3C and it’s various special interest groups was interesting in parts, I think I’ll stay in the trenches, and leave the groundwork to the boffins.

Technorati Tags:

WDS07: Workshop Day One

I was going to give the live blogging thing a go this year, but due to the lack of wifi here at the Powerhouse Museum, I decided to just take a few notes from Andy’s workshop from time to time, then collate them into something to post at the end of the day. This worked out better actually, as I didn’t particularly feel like having the MacBook out the whole time.

By morning tea break Andy Clarke has just covered the general concepts for today’s workshop. It seemed like a tough crowd in that many attendees were finding it a little difficult to either accept or understand some of Andy’s concepts. He started off talking about an alternative to progressive enhancement, where instead of using dodgy browsers (I’m looking at you, IE6) as a baseline for design, then adding enhancements for newer browsers, Andy suggested that we should aim for the top, using all that CSS 2.1 has to offer (and even CSS 3 in some cases), forgetting the notion that the design should look the same in all browsers. Basically, Andy was suggesting that it was often better to use poorly supported (by IE) CSS rules rather than add extra cruft to your markup to achieve the same effect in IE6.

This is an approach that I’ve taken in a few of my designs, mainly in cases where I’ve over-estimated IE6’s capabilities and have been forced to remove certain design elements, such as using transparent PNGs for glow effects, etc. (eg. See how the Sheppparton Villages website’s content area’s light-bloom effect changes between modern browers and IE6. This is less to do with CSS and more to do with PNG-24 alpha support, but the concept’s the same.)

I guess it’s all about where you set the bar for what you’re willing to let IE6 go without. Some of Andy’s examples were a little more than I would accept (ie. I wouldn’t want anything to look out of place or wonky in IE6), but I agree with the general message that, hey, we’ve got these cool CSS rules we can use to make things look cool. Why wait for people to stop using IE6 before we use them to enhance a design for those using modern browsers. It takes a little lateral thinking, but like Andy, I enjoy the challenge that it brings.

I’m about to head out for a bite to eat and a bit of shopping. In a classic example of awesome preparation, I remembered to bring my camera to Sydney, but forgot a USB cable or a SD card reader.

Technorati Tags:

WDS07: Pre-conference recon.

It’s that time of year again when the ol’ weblog gets it’s yearly workout. I arrived in Sydney this afternoon, and after settling into my hotel room (with LCD TV! Yay!), getting all showered up (By the way, WTF? What kind of hotel has the hot tap turn on anti-clockwise, and the cold tap turn on clockwise?), I’m about to venture forth for bite to eat then take a walk to get my bearings to the Powerhouse Museum (the venue for tomorrow’s workshop with Andy Clarke. I’m really looking forward to this conference, as I’m not only a fan of Andy’s work, but also of his way of thinking. He’s very inspiring.

Also as part of the pre-conference buzz-building is all the social network web gizmos that go along with it. I’ve got the Flickr tagged, the Twitter feed, the Technorati tagged, the Facebook group, along with the official website, all bookmarked and open in my Firefox tabs. If I’ve missed anything, let me know :)

On a similar note, I’m a little saddened that last year’s Web Connections website wasn’t re-jigged for this year’s conference. Although, as illustrated above, there’s no shortage of networking apps linked to the conference, it was handy to have everything in the one place. Perhaps if the Facebook group was utilised a little more… Anyhoo, I’ll be kicking around Sydney throughout the conference, so if you want to catch up, give me a hoy-hoy.

Technorati Tags:

Content and presentation separation anxiety

Recently there has been a bit of discussion about the ol’ separation of content and presentation after the release (and subsequent point upgrade release) of Blueprint, a most excellent CSS framework by Olav Bjørkøy (also based on the work of others) for the quick deployment of grid layouts and baseline typography. B

Among the voices heard was Jeff Croft who stood up for the framework, stating that in the real world of commercial web development, it’s less important to adhere strictly to keeping presentational class names out of the markup.

Where web standards and other best practices don’t provide great benefits, find solutions that do.

This, in turn, started a mini-barney in the comments between himself and Jeremy Keith (which has rightly been removed), highlighting that even the web-celebs are having trouble agreeing on the issue.

What I would love to see (and please enlighten me if something like this already exists, or is planned for CSS3) is something like definable style aliases. For example, instead of having the following in your markup:

<div id="header" class="column span-2 append-1">Content...</div>

… we just could use:

<div id="header">Content...</div>

… and then define something like the following in your stylesheet:

#header {
     alias: '.column', '.span-2', '.append-1';
}

This way you could keep the extraneous presentation-related classes out of the mark up and associate them to meaningful identifiers or classes in the stylesheet where they belong. From what I can gather, the problem most people have with the likes of Blueprint is not with having class names based on presentation, but the fact that they get all mixed up with the markup.

I’d love to know what you you think, especially if you know something I don’t. :)

Technorati Tags: ,

Safari for Window, for like, realsies.

That’s right. Apple has shocked-and-awed me by announcing that as of the current version (3 Beta), Safari is now available for download as a native Windows application. Well, when I say native, it still looks like it’s just a screenshot of an OSX app, gun-metal grey chrome and all. I wish it looked a little more like a windows app, especially with the way the Preferences window behaves, but for the first release, I’m quite pleased. Performance is good, and I find the HTML rendering to be very accurate. I don’t quite think I’m ready to switch from Firefox just yet, but it’s great to be able to test for Safari without firing up the Mac.

Technorati Tags: ,

Forms… Gotta love em…

Eric Meyer has written an informed piece about how styling forms with CSS is the bane of our existence. Okay, well maybe that’s a bit extreme, but we’ve still got a long way to go until we can fully control the appearance of our web forms (without the use of javascript, that is).

While on the subject of forms, Pixel Acres’ FormBuilder PHP class can definitely make things easier. Usually when time is not on my side, its all too tempting to just chuck a form into a table and be done with it, but now I can get it all done just as quickly, and fully CSS no less. :)

Technorati Tags: