PuReWidgets toolkit


Published on

Presentation of the PuReWidgets toolkit (http://purewidgets.org) at the Interactive Art group of CITAR. Nov 26, 2012

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

PuReWidgets toolkit

  1. 1. The PuReWidgets toolkit for interactive public display applications Jorge Cardoso jorgecardoso@ieee.org! 26 Nov 2012!
  2. 2. Interactive display
  3. 3. MotivationInteraction in Public Displays•  Every display uses its own approach•  Wasted development effort•  Users face inconsistent interaction modelsWe can learn from the desktop platform•  GUIs faced similar problems 3
  4. 4. RequirementsThe toolkit should support•  Multiple, extensible, PD-specific controls•  Various input mechanisms and modalities•  Concurrent interaction•  Asynchronous interaction•  Graphical representations
  5. 5. PD-specific controlsInteraction with publicdisplays is differentfrom desktopWe need specificcontrols for publicdisplays
  6. 6. Various input mechanisms
  7. 7. Concurrent/shared interaction•  Multiple users•  No single user controlling the display
  8. 8. Asynchronous interaction•  Supports interaction even if an application is off-screen
  9. 9. PuReWidgetsWidget-based toolkit for supportinginteractions in public displays•  For web-based PD applications•  A widget represents an interactive feature. –  Is represented by a class in an object-oriented programming model. –  Applications instantiate widgets and receive interaction events via a callback function 9
  10. 10. Features•  Various types of controls –  Action, Options, Text entry, Download, Upload, Check-in•  Supports various input mechanisms –  SMS, Bluetooth naming, QR codes, email, touch (with limitations)•  Automatically generates GUIs for desktop and mobile devices•  User identification in input events•  Asynchronous events•  Graphical representations for widgets•  Client and server application models
  11. 11. PuReWidgets Architecture 11
  12. 12. PuReWidgets Implementation•  Google Appengine (server)•  Google Web Toolkit – GWT (client)•  Takes advantage of well-known development environment, and user base 12
  13. 13. Initial development•  Continuous refinement cycle – Develop interactive PD applications – Gain insight – Refine the toolkit – Refactor the applications 13
  14. 14. Evaluation•  Threefold –  Personal experience in developing 3 applications –  Programmers’ evaluation of the toolkit –  Audience users’ perception of the interaction/ application model on a real world deployment 14
  15. 15. ConclusionWe have now a complete interaction system forpublic display applications•  Web-based –  “Easy” development•  Various widgets –  Supporting diverse interactions•  Multi-user –  Supporting simultaneous, shared interactions•  Multiple input mechanisms –  From web-based, QR codes, to SMS•  Async input –  To support offline interactions and various application models 15
  16. 16. Future work/Ideas Toolkit developmentJavascript/jQuery libraryOutput widgets for PDRemote, Direct manipulation widgets“Native” apps with phonegapThird-party check-insMore flexible application scheduling 16
  17. 17. Future work/Ideas Other ideasInteractive narratives for public displaysApplication coordination between displaysAndroid/iOS “Open-in”/”Share to” Public display near youPD App: users upload content that they can later request thedisplay to showInteractive marketingHow to effectively communicate interactivityGuidelines for content creationWordpress plugin for content creation“Place” representationsWho’s around app 17
  18. 18. The  PuReWidgets  toolkit  for   interactive  public  display   applications   Jorge  Cardoso     jorgecardoso@ieee.org! Photo credits: Bluetooth photo: creative commons (Flickr user ‘dhaun’) | Touch-screen: creative commons (Flickr user ‘Happydog’)Locamoda app: creative commons (Flickr user ‘gumption’) | Widgets panel: GFDL (http://en.wikipedia.org/wiki/File:Widgets.png)