W3C home > Mailing lists > Public > public-indie-ui-comments@w3.org > April to June 2014

Feedback on comprehensiveness of situations to be addressed

From: Liam McGee <liam@taxonomics.co.uk>
Date: Fri, 9 May 2014 15:06:38 +0100
Message-ID: <CANmkZJmoOQhBDvi+GaWyxi8mVZbTQbioMnpRM1gfjaLvi-0A2g@mail.gmail.com>
To: public-indie-ui-comments@w3.org
Have had a good read through of indie-ui-requirements and indie-ui-context
- looks exciting, and quite a project.

My first reaction was to try to map standard UI widgets e.g. those found in
jQuery UI (http://jqueryui.com/) and a more complex set (
http://www.telerik.com/kendo-ui) to the document and see whther the use
cases covered them all... also some known niggly situations such as
captcha. As an occasional developer, it's how I would want to deal with it
- pick a widget I want to use, and then figure out whether it fits with
indieUI... and if not, how I can rewrite it to work.

The Working draft at present seems to deal well with drag and drop, maps
etc., but not captcha, calendars, schedulers, task/action lists, color
pickers, nesting and splitting panels, responsive/adaptive content (i.e.
different content for different screen sizes, rather than simple
rearrangement of the same content), progress bars, file uploads, image
editing, product sorting (rather than straight table sorting)...

Is anyone looking at the popular libraries? I assume that discussions may
already going on with the guys and gals who are developing them, so
appreciate that this may be an unnecessary point to raise. But a mapping of
popular widget type to relevant IndieUI events and user contexts would be a
great way of approaching the document. Perhaps as an alternative structure?



Liam McGee
+(0)1373 813414
Received on Friday, 9 May 2014 15:20:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:35:27 UTC