Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
1Activity
0 of .
Results for:
No results containing your search query
P. 1
Dashboard for Controls Design Reference

Dashboard for Controls Design Reference

Ratings: (0)|Views: 205|Likes:
Published by Andrew
Design for dashboard and visualizations.
Design for dashboard and visualizations.

More info:

Categories:Topics, Art & Design
Published by: Andrew on Aug 02, 2013
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

01/26/2014

pdf

text

original

 
Dashboardfor Controls
 info
Comm
I N T E R N A T I O N A L
®
ACompanion to theDashboard for ControlsDesign Guide for theCreation of TouchpanelControl Interfaces
Design Reference
 
Acknowledgements
Participants of the DashboardSteering Committee
Greg Bronson, CTS-D, SteeringCommittee ChairTim Cape, CTS-D Andrew Faunce, CTSGreg Maderic
Foreword
 April 30, 2005
The content in this document has been developed
byindustry volunteer experts working on behalf of InfoCommInternational
®
,in support of the “Dashboard for Controls”effort. While the “Dashboard” is about making AV controlseasier to use for the individual user, the process leading to itscreation is about individuals working together for a commoncause. I hope you’ll find that cause, the Dashboard forControls and its various elements, to be of benefit to your workand the industry as a whole.More than 50 InfoComm member volunteers have contributedto the project since it began in the spring of 2001. Be itconcept development, critical review,peer dialog or simplymonitoring our activities, we owe thanks to all for the many,many contributions along the way. Space prevents listing allcontributors; but perhaps you areone of those whocontributed. If so, I (and the Dashboard for Controls SteeringCommittee) thank you. I’d offer that you should takesatisfaction on those elements you can identify as “your own”and further consider those with which you may have takenexception. You’ll be in good company.Special thanks, and credit, go to dedicated individuals whoover the last year have given extra, as steering committeemembers, in the sprint to the “finish line.” Indulge me while Itell a few stories. Andrew Faunce was at the InfoComm EndUser Summit in March of 2002 when we first conceived of theDashboard project. At key points
 
i
INFOCOMM DASHBOARD FOR CONTROLS DESIGN REFERENCE|FOREWORD
Acknowledgments
Participants of the DashboardSteering Committee
Greg Bronson, CTS-D, SteeringCommittee ChairTim Cape, CTS-D Andrew Faunce, CTSGreg MadericRichard Nimtz, Jr., CTSHoward NunesRem Remington, CTSDavid Silberstein, CTS
Participating Councils and Committee
ICAT CouncilIndependent Programmers CouncilManufacturers CouncilTechnology Managers CouncilDashboard for Controls Committee
 
ii
INFOCOMM DASHBOARD FOR CONTROLS DESIGN REFERENCE|FOREW0RD
since then, he has continued to thoughtfully consider andcontribute to shaping the Dashboard. Rick Nimtz and RemRemington “raised their hands” when the InfoComm End User(Technology Manager) Council looked for sub-committeemembers to work on the Dashboard at our annual meeting.They’ve hung in there for years; and may think twice next timewe’re looking for hands (just kidding)! Tim Cape and DaveSilberstein “returned my calls” in the summer of 2002 when Iasked for their participation in the then newly developed“cross-council” work group for Dashboard. Sometimesadvocates, sometimes voices of reason, they’ve been therethroughout, contributing with the wealth of knowledge theyhave on this topic. Last, but not least, areGreg Maderic andHoward Nunes, both of whom participated as representativesof the fledgling InfoComm Programmers Council. Starting“cold” on the project in fall of 2004, they immediatelyimmersed into “all things Dashboard.” Writing, and editing, theDashboard Reference, they lent their expertise to add adimension to the project that I hadn’t let myself dream wouldbe achievable.Thanks go to InfoComm , and its skilled staff, for providing aplatform for this work to occur and shepherding the volunteereffort. If you believe there are errors or omissions in this work,or simply want to help further develop the concepts, pleasecontact the InfoComm membership department. Wewelcomeyour input.
Greg Bronson, CTS-DChair, Dashboard for Controls Working GroupClassroom Technology Project Leader, Cornell University

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->