Highlights of Week 28/2011
- 48 Outstanding WordPress Themes of June 2011 (by Madalin Tudose)
- JavaScript language advanced Tips & Tricks (through Chris Heilmann)
- Useful Wireframing and Prototyping Tools – Roundup (by Jacob Creech)
- Introducing Usaura, the Fastest Way to Run Click Tests (by Dmitry Fadeyev)
JavaScript Pop-ups – Good or Bad?
Having witnessed a recent discussion on the WAI Interest Group list I asked myself, are JavaScript Pop-ups good or bad (or evil)?
Conclusion
It depends. But mostly bad
Con's
John Colby's from Birmingham City University arguments on why pop-ups are bad:
- Because people are warned about them (http://www.bbc.co.uk/webwise/guides/about-popups)
- Because of their association with scams, viruses, malware, sites using popups are 'less trustworthy'
- Users with sight or cognitive problems (http://soap.stanford.edu/show.php?contentid=47)
- (And personally) if they insist on using popups I'll go away.
Richard from Userite remembers us that:
...the pop-up almost certainly takes the focus away from the current window. Blind users will not know this unless you tell them AND provide a clear method to close the pop-up and return the user to the point immediately after where the pop-up activated. Also remember to provide a text based alternative for those who do not have javascripting.
with Charles McCathieNevile from Opera adding:
...that many users have pop-ups blocked by default now, so won't actually see it even if they are not blind.
Pro's
Harry Loots of the IEEE has a point when he says:
If it will supply useful information to the user, then don't kick against it, but make sure that the feedback / information so provided is accessible. For example, if the pop-up is used to confirm the product has been added and the user's browser does not support scripting/popups, a physical line of text may be displayed to confirm the product has been added (which can be hidden in the view seen by users who get the popup)
My Take
When a client asks for a specific design element, one needs to wonder where this need came from in the first place.
In the case that the client is not satisfied with visibility of system status. Try
- Improving titles and labels
- Adding non-obstructive instructions
- Providing feedback in an alternative way (as Harry pointed out), additional confirmation page always helps
- Keeping elements and its status (e.g. shopping cart belongs to the top right corner) in its user-anticipated location
- Using visual cues to show what just happened
Web GIS: Principles and Applications [Paperback]

Web GIS
I'm happy to introduce a new book which was co-authored by my colleague Pinde Fu: "Web GIS: Principles and Applications".
I'm really excited about this, not only because good GIS resources are scarce but also because he used screenshots of applications that I have designed over the past years, e.g. geodata.gov, GeoPortal Toolkit, Loma Linda Medical Center Response System, HydroViewer.
How much better can it get when your design ends up in a book?
Audience
While the content of the book is targeted at readers at all skill levels I can see it as a great teaching source as well as invaluable resource for managers and aspiring GIS developers to understand the principles of web applications.
Content
The content of the book is focused on the conceptual level (you won't find code samples) by trying to be systematic and as comprehensive as possible which I believe was done superbly. Nevertheless the authors do cover important new developments like geospatial Web services (REST), geobrowsers, cloud computing, geoportals, mashups, mobile GIS, Gov 2.0, geotagging, ArcGIS APIs for JavaScript, Flex, and Silverlight.
Table of Contents
- GIS in the Web Era
- Technical Basics
- Geospatial Web Services
- Geospatial Mashups
- Mobile GIS
- Geoportals
- NSDI in the Web 2.0 Era
- Web GIS Applications in E-Business
- Web GIS Applications in E-Government
- Hot Topics and New Frontiers
Templates for Building Map Applications with ArcGIS API for JavaScript
Templates for ArcGIS API for JavaScript
Creating web mapping applications has never been easier.
Esri offers a multitude of API's, from Silverlight to Flex and JavaScript.
Without discussing the design approach for your particular user-specific needs, I want to point to some great template resources that can serve as a starting point for customizing your app. The templates are based on ArcGIS Explorer Online viewer.
Follow this really nice tutorial on how to access the template gallery to get started.
Highlights of Week 30/2010
- How Web Designers Can Adopt a Global Mindset (by Christian Arno) - Cultural differences are shamelessly overlooked, depending on your audience that might be ok but you should know... read the article.
- User Interface Design Framework (by webalys) - a really nice set of flexible GUI elements, free icon library and a graphic style library.
- The Hackday Toolbox – getting you started faster (by Chris Heilmann) - wow, what a great set of resources to get you started with YQL for PHP and JavaScript.
- How to Navigate Design by Committee (by Andrew Follett) - Andrew outlines a feasible approach to steering design discussions into a successful direction.
- Accessiblity Forum 2.0 (by buyaccessible.net) - promising blog to follow if you are into accessibility.
- 10 Free Online Books for Web Designers (by Henry Jones) - add to your never ending supply of good stuff.
The importance of the JavaScript parseInt radix
Problem:
Just recently I had to implement an HTML form that allows users to enter percentage values. Like every good programmer I added client-side validation to check that the input values are between 0 and 100.
Using the JavaScript function parseInt(txtValue) with txtValue being the value of the input field our tester was able to submit the form with a value of 0137.
My first reaction was to restrict the maxlength attribute of the input field to 3 characters only. Even though this is a good and recommended practise there was clearly something else wrong.
Explanation:
The parseInt() function parses a string and returns an integer. The signature is parseInt(string, radix) with
- string (required) being the string to be parsed, and
- radix (optional) a number (from 2 to 36) that represents the numeral system to be used
If the radix parameter is omitted, JavaScript assumes the following:
- If the string begins with “0x”, the radix is 16 (hexadecimal)
- If the string begins with “0”, the radix is 8 (octal)
- If the string begins with any other value, the radix is 10 (decimal)
Solution:
So, what happened? Because I forgot to specify the radix and our QA tester tried the (however unlikely) case of 0137 JavaScript assumed it was an octal number and returned a value of 95. Lesson learned: Always specify the radix (if it decimal set it to 10
!!!!
PS.: Only the first number in the string is returned!
PPS.: Leading and trailing spaces are allowed.
PPPS.: If the first character cannot be converted to a number, parseInt() returns NaN.

