I would definitely recommend this; especially if you're a developer looking to host a personal webpage for employers to look at. You can also create a page for each of your projects on GitHub!
YUMI is OK if you spend the time to download the distros ahead of time and store them all on your USB key. NetBoot is good if you want to get a distro you haven't downloaded yet. That way you have a lot more distros available than can fit on your thumb drive. The downside is that you have to download them every time you install them.
thats strange, we did have an issue with older versions of chrome so it might be a problem with certain webkit version, i'll check that out. thanks for letting me know.
Have you thought about generating the coarser data (country, county, city) from the location when possible? Or would having a half-filled form be confusing for users?
At the moment it's just a lookup to the database. It does have the ability to save and show more fields than whats on the signup form (see the demo - http://localyser.com/demo.html), that form is mainly tailored to match the how PAF data is returned for an easy drop in.
good call on open street map, i'll try and get in touch.
Just to be clear about what I thinking, because I'm not sure I expressed myself well:
If I type in a postcode and house number on a site using the Royal Mail PAF, then it goes and gets my address. Currently, your service won't. But if I enter my full address once on one site using it, it'll then be keyed against my postcode and house number and appear automatically on others.
That very first time I enter a new address you could probably do various clever things to make entering my address easier. It shouldn't be difficult to map any postcode to a country (Scotland, England etc.) and other larger regions. In cases where it's not 100% possible you could probably return a (potentially incomplete) list of nearby streetnames, towns etc. which could trigger an autocomplete when the user starts typing the first letter. Once they've chosen a streetname then that may in turn dictate the rest.
Most of this data could be extracted from OpenStreetmap or directly from the Ordnance Survey Open Data, particularly Code Point and OS Locator, meaning you'd only need users to confirm a street name, and enter a house name or number to get a full record.
(It would be nice to allow users to report errors in the OS Locator street names too. There's been a few errors found in both sets by comparing the OSM data against the OS.)
sorry, i was getting the wrong end of the stick on that.
That is a good idea but your original point might be right, empty fields could be a bit strange. I'll give it a try and see how how it looks (probably not till the weekend - client work to do).
Yeah, the interaction design is the hard bit and probably needs tested on "normal" people before you could be confident that it's actually helpful.
Maybe just having the autocomplete's available to save typing (and typos) and then only completing the rest of the form once you have the user enter enough that you're sure you can finish the rest of it (which sometimes might be the street, but other times the town/county) might work?
I've just realised that unless you know your data was 100% complete you'd not be able to do a guaranteed correct lookup from the post code and house number alone, since there may be clashes with houses on nearby streets you don't yet know about, and even if you present a dropdown list you still need a fallback form for new data entry. So that's a pretty tricky UI challenge regardless.
Do you have any example data that people can try to see how it works when your demo recognises postcodes?
Yes, please, click on our blogspam for more blogspam about prior blogspam controversy. All on the same site! Its like getting five clickthroughs in one!
