Archive for the ‘development’ Category

Scripting Enabled Day 2

Sunday, September 21st, 2008 at 5:08pm

Day two of the event was a “hack day” style event, where lots of geeks gathered with the speakers to try and build something useful. There were lots of mini-projects on the go.

I did a bit of hacking with some bookmarklets and javascript to switch to user-defined style sheets, giving the option of looking at any website as reversed video with much larger text, for instance. Here are a couple of screenshots:

[Regular video Flickr,  but with large text]

[Reversed-video style sheet is easier for users with some visual impairments or other disabilities]

I hope to be able to use some of the techniques in future projects.

I was also rather amused  by the tshirt one of the other geeks was wearing:

[Clueless!]

Scripting Enabled Day 1

Saturday, September 20th, 2008 at 4:31pm

I attended the excellent Scripting Enabled conference and developer day recently held in London. It was extremely enlightening about various aspects of the web and how users with varied access difficulties are affected by the decisions us developers make every day.

There were some excellent panels - links to the trascripts, slides and audio etc:

[Kath  hates the interweb!]

[Leonie and Artur talk about Screenreaders and JavaScript]

[The panel takes questions at the end of the day]

@media session 11

Friday, May 30th, 2008 at 4:21pm

Global Design - Characters, Language & More

Richard Ishida

Richard is the W3C’s Internationalisation Activity Lead.

Character Encoding

  • There are many options, but Unicode is the best - it supports many languages in a single character set - making it easy to architect multilingual solutions, and have a mix of languages on a single page (if required).
  • Makes storing and retrieving multilingual data in a database much easier
  • Also provides extra characters such as © ™ etc
  • Has wide support in browsers, scripts, editors, databases etc.

You can declare the encoding in the HTML:

<meta http-equiv=”Content-Type” content=”text/html; charset=utf-8″ />

Or if you’re using XML:

<?xml version=”1.0″ encoding=”UTF-8″?>

Databases must be told to save data as utf-8 also - to maximize compatibility. For more details, see:

Richard’s presentation: slides (PDF) | audio (mp3)

@media Session 9

Friday, May 30th, 2008 at 12:25pm

The Why and Which of JavaScript Libraries

John Resig took us through various scenarios when you write JavaScript:

  • Plug & Play:
    Drop in a widget, little or no JavaScript knowledge required, just customise some options and go - no flexibility
  • Some assembly required:
    Write common utilities, use pre-made code to distance yourself from browser bugs - flexible, until you hit a browser bug
  • Down and dirty:
    Write all code from scratch, deal directly with bugs, quirksmode can save your life - eccessively flexible - almost too flexible
  • Use JavaScript library:
    Makes JavaScript bearable, gets the job done fast, simplifies cross-browser support - easily customisable

John then did a comparison between the various JavaScript libraries, including jQuery, Prototype, YUI and Dojo, which are commonly in use. A developer survey showed that jQuery and Prototype were used by around 32% of developers; YUI was 22% and others around 14%.

John’s full slides give much more detail of each library’s strengths.

John’s presentation: slides (slideshare) | audio (mp3)

@media Session 8

Friday, May 30th, 2008 at 11:30am

Building on the Shoulders of Giants

Jonathan Snook

Culture
We come from a culture where developers tend to like to reinvent the wheel, whereas designers like to reuse. If, as developers, we want to use components of others’ work (under GPL or whatever), this provides us with some distinct advantages. Look how many times the Linux distribution has forked!

Tools
There are loads of PHP frameworks out there, and also for other languages. We dont’ have to write everything from scratch, but make use of pre-existing libraries and functions.

Flash - now has built in sockets support. Useful for charts in pages (if you need them)

Types of Data
Location, Time, Relationships etc

Pitfalls
Dynamic APIs can foul up your application; service availability; you are middleman - if something goes down people blame you, not the service provider.

Benefits
Dealing with well-tested code. Speeds up development. Solve problems outside original solution.

Ideas
Enables you to get stuff out fast. Iterate fast and often. Eg Overheard RSS feed built really quickly (using library elements from Cake PHP). You can see what works. You can put stuff out in hours, rather than days or weeks.

Jonathan’s presentation: slides (blog+links) | audio (mp3)