The specs:

• Intel Atom Z520 Processor
• 1GB RAM
• 16GB solid state drive, 16GB SD Card, 20GB Eee Storage
• 8.9″ LED-lit resistive touchscreen
• Windows XP Home
• WLAN 802.11b/g/n (draft)
• 225mm x 164mm x 25.2-28.4mm
• 0.96 kg weight

The two worlds are diverging rapidly. Traditional enterprise software development (the kind associated with “programming in the large”) tends to be slow, costly, inflexible. Solution sales, marketing, and support tend to be correspondingly process-heavy and inertia-laden. The Web, on the other hand, is agile, fun, and friction-free. It has changed the way people look at computing. It has changed expectations (and conversations) around marketing, pricing, maintenance, support, and just about every other aspect of the enterprise-software experience.

Kas Thomas:  A reality checklist for CMS vendors.

Honestly I found it quite enlightening. Scientific? Perhaps not as there were far too few questions to normalise the results using their anonymous service but still something for me to think about.

Here is my ideal work culture:

I disagree with some outcomes, for example “proactive” should be weighted more!

CPU info:

• cat /proc/cpuinfo
• cat /proc/cpuinfo | grep ‘model name’

Memory info:

• cat /proc/meminfo
• cat /proc/meminfo | grep MemTotal
• cat /proc/meminfo | grep MemFree

Storage info:

• cat /proc/partitions
• hdparm -I /dev/sda


I have been interacting with some organisations here in Queensland that feel that feel that web accessibility does not apply to them.

Can I point out that:

Under section 67(1)(k) of the Disability Discrimination Act, the Australian Human Rights and Equal Opportunity Commission (Hreoc) issues guidelines for the purpose of avoiding discrimination in this area.

- Computerworld

The W3C WCAG checkpoints are the measure of compliance.

Sure for private organisations there is “unjustifiable hardship” but for government sites this does not apply.

I wrote a position piece on this topic back in 2003 or 2004 maybe. I will dig it up and post it up here – I wonder if my comments in that paper still stand today?

Sumopaint is a fast, easy, simple but powerful image editing software.

Try it out here: http://www.sumo.fi/products/sumopaint

Wow. I was impressed.

I grabbed their Reporting Evaluation tool and had it up and running in no time. I hooked up a MySQL datasource and produce reports almost immediately (well if you discount a few distractions and user errors).

A good thing about this, is that I can now slot Pentaho into my next project.

1. Run puttygen.exe
2. In the “Parameters” section select your encryption standard, I use SSH2 DSA. Press Generate.
3. Move your mouse randomly in the small screen in order to generate the key pairs.
4. Enter a key comment, which will serve to identify the key you are generating.
5. Type in the passphrase and confirm it. The passphrase is a password and is used to protect your key. MAke sure oyu remember this password as you will be asked for it when you connect via SSH.
6. Click “Save private key” to save your private key.
7. Click “Save public key” to save your public key.

I have just been handed a system without anything – no documentation, no history, no specifications, and no technical information or staff at all.

So what is the command to find out? Just type this below:

uname -a && cat /etc/*release

from    Roger Hudson
date    Wed, Sep 17, 2008 at 5:02 PM
subject    [WIPA Accessibility] forms and WCAG 2.0

In June I prepared a paper for the WIPA site which compares the accessibility Checkpoints of WCAG 1.0 with the Success Criteria and Techniques in WCAG 2.0. The paper, “Migrating from WCAG 1.0 to WCAG 2.0” can be found at http://wipa.org.au/papers/wcag-migration.htm

Following on from this, I have recently prepared an article that concentrates on making accessible forms. The article provides practical advice and compares the WCAG 1.0 accessibility requirements relating to forms with those contained in WCAG 2.0 and is at http://www.usability.com.au/resources/wcag2/

The article contains 6 video segments where Andrew Downie demonstrates screen readers in action on specific aspects of forms. The videos are also available here:

Label and titles: http://dotsub.com/view/9787ebec-941f-4e04-a5dc-f6ed7fde7247

Forms in datatables: http://dotsub.com/view/b885eaad-5397-4db6-9970-ee39f51ed7ab

Fieldset, Legend and nested fieldsets: http://dotsub.com/view/0064d19b-a8da-4729-86f7-a45aaa5bdd57

Form errors and corrections: http://dotsub.com/view/9276a7d3-cca5-4285-9a5d-89b21c0f9e57

Dynamically populated JavaScript Select Menu: http://dotsub.com/view/4e2b28d0-4c13-4e98-8ce3-b380ef4be710

Show and hide form sections: http://dotsub.com/view/1cb6c35a-fc12-4f90-8faa-b5490d87ac2d

I hope you find this useful

Roger

Without doubt Roger, this is a great resource. Thank you!