Source: http://patents.com/us-9864612.html
Timestamp: 2018-10-21 08:32:07
Document Index: 524678856

Matched Legal Cases: ['Application No. 201110436306', 'Application No. 201110436635', 'Application No. 201110443291', 'Application No. 201110436635', 'Application No. 201110443291', 'Application No. 201110436593', 'Application No. 200980131157', 'Application No. 09803312', 'Application No. 200980131157', 'Application No. 200980131157', 'Application No. 200980131157', 'Application No. 201110436306', 'Application No. 201110436306', 'Application No. 201110436593', 'Application No. 201110436635', 'Application No. 2011103151', 'Application No. 201110436593', 'Application No. 201110436306', 'Application No. 201110436593', 'Application No. 201110436635', 'Application No. 201110443291', 'Application No. 201110443291', 'Application No. 201110443291', 'Application No. 201210376181', 'Application No. 201210376206', 'Application No. 201210376181', 'Application No. 201210376181', 'Application No. 201210376206', 'Application No. 200980131157', 'Application No. 201110436635', 'Application No. 201110436635', 'Application No. 201110436635', 'Application No. 201110436635', 'Application No. 200980131157', 'Application No. 09803312', 'Application No. 201210376206', 'Application No. 201210376181', 'Application No. 201110436635']

US Patent # 9,864,612. Techniques to customize a user interface for different displays - Patents.com
United States Patent 9,864,612
Friend , et al. January 9, 2018
Techniques to customize a user interface for different displays are described. An apparatus such as an electronic device with a processing system may implement a custom user interface system that when executed by a processor is operative to adapt a user interface view of an application for presentation by one or more displays. The custom user interface system may comprise, among other elements, a user interface adaptation component operative to receive as input a user interface view of the application for presentation on a first display and an adaptation parameter, and modify the user interface view for presentation on a second display based on the adaptation parameter. A presentation component is operative to present the customized user interface view on the second display. Other embodiments are described and claimed.
Friend; Joseph (Bothell, WA), Fish; Nathan (Redmond, WA), Berg; Jeffrey (Seattle, WA), Lee; Joo-Young (Redmond, WA), Hans; Derek (Redmond, WA), Karnawat; Kuldeep (Redmond, WA), Santy; Jeremy (Redmond, WA)
Friend; Joseph
Fish; Nathan
Berg; Jeffrey
Lee; Joo-Young
Hans; Derek
Karnawat; Kuldeep
Santy; Jeremy
Family ID: 1000003051686
12/978,308
US 20120166985 A1 Jun 28, 2012
Current CPC Class: G06F 9/4448 (20130101)
Field of Search: ;715/765,761
5337407 August 1994 Bates et al.
5339389 August 1994 Bates et al.
6049334 April 2000 Bates et al.
6119147 September 2000 Toomey et al.
6564246 May 2003 Varma et al.
6633315 October 2003 Sobeski
7228492 June 2007 Graham
7257769 August 2007 Caspi
7401300 July 2008 Nurmi
7447713 November 2008 Berkheimerm
7451183 November 2008 Romero et al.
7478129 January 2009 Chemtob et al.
7512906 March 2009 Baier
7590941 September 2009 Wee et al.
7764247 July 2010 Blanco
8150719 April 2012 Perrella et al.
8667401 March 2014 Lozben
8826117 September 2014 Junee
9118612 August 2015 Fish et al.
9383888 July 2016 Fish
2003/0046296 March 2003 Doss
2003/0220973 November 2003 Zhu et al.
2004/0194033 September 2004 Holzwarth et al.
2004/0250201 December 2004 Caspi
2005/0246642 November 2005 Valderas
2005/0285845 December 2005 Dehlin
2006/0010197 January 2006 Ovenden
2006/0094441 May 2006 Beckmann et al.
2006/0143064 June 2006 Mock et al.
2006/0244734 November 2006 Hill
2007/0011231 January 2007 Manion
2007/0100937 May 2007 Burtner, IV et al.
2007/0109939 May 2007 Shimizu et al.
2007/0186171 August 2007 Junuzovic et al.
2007/0226032 September 2007 White et al.
2007/0245238 October 2007 Fuggitt et al.
2007/0300185 December 2007 Macbeth
2008/0001717 January 2008 Fiatal
2008/0005235 January 2008 Hegde et al.
2008/0109406 May 2008 Krishnasamy et al.
2008/0141126 June 2008 Johnson et al.
2008/0147790 June 2008 Malaney et al.
2008/0244442 October 2008 Veselova et al.
2008/0263010 October 2008 Roychoudhuri et al.
2008/0307322 December 2008 Stochosky et al.
2009/0006980 January 2009 Hawley et al.
2009/0007014 January 2009 Corner et al.
2009/0055739 February 2009 Murillo
2009/0089055 April 2009 Caspi et al.
2009/0109180 April 2009 Do et al.
2009/0119604 May 2009 Simard et al.
2009/0183095 July 2009 Deitsch
2009/0204465 August 2009 Pradhan
2009/0210822 August 2009 Schindler
2009/0313125 December 2009 Roh
2009/0319562 December 2009 Holm-Petersen et al.
2009/0327019 December 2009 Addae et al.
2009/0327425 December 2009 Gudipaty
2010/0079467 April 2010 Boss et al.
2011/0022967 January 2011 Vijayakumar
2011/0153612 June 2011 Paul
2011/0154192 June 2011 Yang et al.
2011/0161130 June 2011 Whalin
2011/0282871 November 2011 Seefeld et al.
2011/0289142 November 2011 Whalin
2012/0159347 June 2012 Fish et al.
2012/0159355 June 2012 Fish et al.
2012/0179980 July 2012 Whalin
2012/0179981 July 2012 Whalin
2013/0125051 May 2013 Kelley et al.
2013/0211980 August 2013 Heiferman
2013/0212494 August 2013 Heiferman
2013/0263020 October 2013 Heiferman
1886977 Dec 2006 CN
101198976 Jun 2008 CN
101363739 Feb 2009 CN
101364886 Feb 2009 CN
101515226 Aug 2009 CN
101789871 Jul 2010 CN
1517260 Mar 2005 EP
04257046 Sep 1992 JP
2010176320 Aug 2010 JP
WO 02061682 Aug 2002 WO
2006/100475 Jun 2006 WO
WO-2007092470 Aug 2007 WO
Bell, David et al., "Sensory Semantic User Interfaces (SenSUI)" Fluidity Research Group, Oct. 20, 2009. cited by applicant .
Zenghong, Wu et al. "Context Awareness and Modeling in Self-Adaptive Geo-Information Visualization" Retrieved on Aug. 30, 2010. cited by applicant .
Mitrovic, Nikola et al. "Adaptive User Interface for Mobile Devices" Published 2002. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/473,206, filed (Dec. 7, 2011), 36 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/486,762, filed (Oct. 14, 2011), 24 pages. cited by applicant .
"Online Calendar & Group Scheduling", MOSAIC Technologies, retrieved from <http://www.webexone.com/Brandded/ID.asp?brandid=2348&pg=%20AppCalenda- r> on Apr. 24, 2009, 4 pages. cited by applicant .
Ju, Wendy et al., "Where the Wild Things Work: Capturing Shared Physical Design Workspaces", Stanford University, CSCW '04, (Nov. 6, 2010), pp. 533-541. cited by applicant .
"Adobe Connect", Retrieved from: <http://www.adobe.com/acom/connectnow/> on Oct. 11, 2010, (Sep. 16, 2010),3 pages. cited by applicant .
"Adobe ConnectNow", Retrieved from: <http://www.adobe.com/acom/connectnow/> on Oct. 13, 2010, (2010),6 pages. cited by applicant .
"Cisco Context-Aware Mobility Solution: Presence Applications", retrieved from https://www.cisco.com/en/US/solutions/collateral/ns340/ns394/ns348/n- s788/brochure.sub.--c22-497557.html on Sep. 7, 2010, 5 pages. cited by applicant .
"Description for SharePoint Meeting Manager", Retrieved from: <http://www.softpicks.net/software/Business/Project-Management/SharePo- int-Meeting-Manager-47146.htm> on Oct. 11, 2010, (Jul. 27, 2009),2 pages. cited by applicant .
"GoToMeeting", Retrieved from: <http://www.gotomeeting.com/fec/online.sub.--meeting> on Oct. 11, 2010, 1 page. cited by applicant .
"Meet mimio--The Digital Meeting Assistant", Mayflower Business Systems Limited; http://www.kda.co.uk/mimio1/whitepaper.html, (May 1999),10 pages. cited by applicant .
"Meeting Center, Using Video in Your Meetings", retrieved from http://www.oucs.ox.ac.uk/webex/Windows/Video.pdf on May 13, 2009; Cisco webex, 2 pages. cited by applicant .
"Meeting Management Software", Retrieved from: <http://workingsmarter.typepad.com/my.sub.--weblog/2004/12/meeting.sub- .--managem.html> on Oct. 11, 2010, (Dec. 10, 2004),2 pages. cited by applicant .
"Microsoft Office Communicator 2007 Getting Started Guide", retrieved from http://www.ittdublin.ie/media/Media,22233,en.pdf, (Jul. 2007),77 pages. cited by applicant .
"Microsoft.RTM. Office Live Meeting Feature Guide", Microsoft Corporation, Available at <http://download.microsoft.com/download/8/0/3/803f9ba6-5e12-4b40-84d9-- d8a91073e3dc/LiveMeeting.doc>,(Jan. 2005),pp. 1-17. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/473,206, filed (May 19, 2011),28 pages. cited by applicant .
Adams, Lia et al., "Distributed Research Teams: Meeting Asynchronously in Virtual Space", Institute of Electrical and Electronics Engineers, (1999),17 pages. cited by applicant .
Bunzel, Tom "Using Quindi Meeting Capture", retrieved from http://www.informit.com/guides/content.aspx?g=msoffice&seqNum=220, (Sep. 1, 2006),3 pages. cited by applicant .
Fruchter, Renate "Brick & Bits & Interaction (BBI)", http://www.ii.ist.i.kyoto-u.ac.jp/sid/sid2001/papers/positions/bricksbits- interaction.pdf, (2001),4 pages. cited by applicant .
Ionescu, Arna et al., "Workspace Navigator: Tools for Capture, Recall and Reuse using Spatial Cues in an Interactive Workspace", Stanford Technical Report TR2002-04, http://bcj.stanford.edu/research/wkspcNavTR.pdf, (2002),16 pages. cited by applicant .
Karlson, Amy et al., "Courier: A Collaborative Phone-Based File Exchange System", Technical Report; MSR-TR-2008-05; Microsoft Research, (Jan. 2008),17 pages. cited by applicant .
Kim, Hyun H., et al., "SmartMeeting: CMPT 481/811 Automatic Meeting Recording System", http://www.cs.usask.ca/grads/hyk564/homePage/811/CMPT%20811%20final.doc, (2004),7 pages. cited by applicant .
Peddemors, A.J.H. et al., "Presence, Location and Instant Messaging in a Context-Aware Application Framework", retrieved from htt://citeseerx.ist.psu.edu/viewdoc/download?doi=10.11.1.98.3321&rep=rep1- &type=pdf; 4th International Conference on Mobile Data Management, MDM, (2003),6 pages. cited by applicant .
Rudnicky, Alexander I., et al., "Intelligently Integrating Information from Speech and Vision to Perform Light-weight Meeting Understanding", retrieved from http://citesseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.126.1733&rep=re- p1&type=pdf, (Oct. 2005),6 pages. cited by applicant .
Watson, Richard "What is Mobile Presence?", Retrieved from http://reseller.tmcnet.com/topics/unified-communications/articles/54033-w- hat-mobile-presence.htm, (Apr. 10, 2009),4 pages. cited by applicant .
Werle, Patrik et al., "Active Documents Supporting Teamwork in a Ubiquitous Computing Environment", The Research Group on Ubiquitous Computing; Department of Computer and Systems Sciences; KTH Center for Wireless Systems; retrieved from http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.157.4661, (2001),4 pages. cited by applicant .
Yu, Shoou-Jong et al., "Who Said What When? Capturing Important Moments of a Meeting", retrieved from http://repository.cmu.edu/cgi/viewcontent.cgi?article=1003&context=silico- n.sub.--valley; Technical Report, (Apr. 10-15, 2010),7 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/486,762, filed (Feb. 8, 2012),28 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/965,965, filed (Nov. 8, 2012), 12 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/965,965, filed (Jun. 4, 2012), 12 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/968,332, filed (Jul. 23, 2012), 19 pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110436306.8, Nov. 15, 2014, 6 pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110436635.2, Nov. 27, 2014, 11 pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110443291.8, Nov. 21, 2014, 8 Pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/968,332, filed Oct. 9, 2014, 23 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/473,206, filed Oct. 8, 2015, 39 pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110436635.2, Oct. 20, 2015, 12 Pages. cited by applicant .
"Notice on Reexamination", CN Application No. 201110443291.8, Aug. 24, 2015, 9 pages. cited by applicant .
"CSS Max-width Property", Retrieved From: http://web.archive.org/web/20070608101036/http://www.w3schools.com/, 2007, 1 page. cited by applicant .
"Create Treemaps Using Easy Drag-and-drop Interactions", Retrieved From: http://www.magnaview.nl/treemap/, 2010, 1 page. cited by applicant .
"GeoTime", Retrieved at: https://web.archive.org/web/20101219085705/http://www.geotime.com/Product- /GeoTime-%281%29/Features--Benefits.aspx, 2009, 10 pages. cited by applicant .
"The Beginner's Guide to Data Visualization", Retrieved From: http://www.tableausoftware.com/beginners-data-visualization, 2010, 10 Pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110436593.2, Jan. 6, 2014, 11 Pages. cited by applicant .
"Collaboration within the Telepresence Experience", Retrieved From: http://www.wrplatinum.com/downloads/11056.aspx, Jan. 2010, 11 Pages. cited by applicant .
"Foreign Office Action", CN Application No. 200980131157.5, Nov. 21, 2013, 11 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/965,965, filed Jun. 4, 2012, 12 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 13/253,886, filed Apr. 11, 2013, 13 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 11/260,515, filed Feb. 24, 2011, 14 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 13/272,832, filed Aug. 12, 2013, 15 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/472,101, filed Oct. 5, 2011, 15 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/184,174, filed Feb. 4, 2011, 16 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 11/260,515, filed Mar. 3, 2009, 16 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/472,101, filed Mar. 28, 2012, 16 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/184,174, filed Sep. 25, 2013, 16 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/965,965, filed Dec. 20, 2013, 16 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 11/260,515, filed Sep. 30, 2010, 17 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 13/272,832, filed Dec. 30, 2013, 18 Pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/184,174, filed Mar. 13, 2012, 19 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 11/260,515, filed Dec. 11, 2009, 19 pages. cited by applicant .
"Meeting Center Using Video in Your Meetings", Retrieved From: http://www.oucs.ox.ac.uk/webex/Windows/Video.pdf, May 13, 2009, 2 Pages. cited by applicant .
"Mindshift Innovation", Retrieved From: http://mindshiftinnovation.blogspot.com/2007/09/seadragon.html, Oct. 4, 2007, 2 Pages. cited by applicant .
"Datapoint version 1.1", Retrieved From: http://www.filedudes.com/DataPoint-download-20853.html, 1997-2007, 2 Pages. cited by applicant .
"FREE PhotoMesa 3.1.2 (Windows)", Retrieved From: https://web.archive.org/web/20071209231951/http://www.windsorinterfaces.c- om/photomesa.shtml, 2007, 2 Pages. cited by applicant .
"ZuiPrezi Nonlinear Presentation Editor", ZuiPrezi Ltd., http://zuiprezi.kibu.hu/, 2007, 2 pages. cited by applicant .
"ProShow Producer Feature Overview", Photodex Corporation: http://www.photodex.com/products/producer/features.html, 2008, 2 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/184,174, filed Sep. 6, 2011, 20 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/184,174, filed Nov. 20, 2012, 20 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/967,497, filed Dec. 3, 2013, 20 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/968,332, filed Dec. 5, 2013, 20 pages. cited by applicant .
"An Overview of Aabel 3Features", Retrieved From: http://www.gigawiz.com/aabel3.html, Aug. 9, 2011, 21 pages. cited by applicant .
"CounterPoint User Manual", Retrieved From: http://www.cs.umd.edu/hcil/counterpoint/, 2005, 21 pages. cited by applicant .
"Human and Technical Factors of Distributed Group Drawing Tools", Retrieved From: http://grouplab.cpsc.ucalgary.ca/grouplab/uploads/Publications/Publicatio- ns/1992-HumanTech.IWC.pdf, 1992, 29 Pages. cited by applicant .
"CounterPoint: A Zooming Presentation Tool", Retrieved From: http://web.archive.org/web/20050205082738/www.cs.umd.edu/hcil/counterpoin- t/, Feb. 5, 2005, 3 Pages. cited by applicant .
"FREEPATH-EDU Nonlinear Presentation Software", Grass Roots Software, 2008, 3 pages. cited by applicant .
"Aquatic Sugar: The Children's Interface, Translated for Adults", Retrieved From: http://www.olpcnews.com/software/operating.sub.--system/aquatic.sub.--sug- ar.sub.--childrens.sub.--interface.html, Nov. 7, 2007, 5 Pages. cited by applicant .
"Extended European Search Report", EP Application No. 09803312.9, Jul. 7, 2011, 6 pages. cited by applicant .
"Foreign Office Action", CN Application No. 200980131157.5, Jan. 30, 2013, 7 pages. cited by applicant .
"Foreign Office Action", CN Application No. 200980131157.5, Aug. 31, 2012, 7 pages. cited by applicant .
"Visualize and Map SalesForce Leads with SpatiaiKey", Retrieved From: http://web.archive.org/web/20101120170237/http://www.spatialkey.com/suppo- rt/tutorials/visualize-and-map-salesforce-leads-with-spatialkey-part-ii, 2010, 7 Pages. cited by applicant .
"Foreign Office Action", CN Application No. 200980131157.5, Jul. 23, 2013, 8 pages. cited by applicant .
et al.,' "International Search Report and Written Opinion", Application No. PCT/US2009/046529, Nov. 30, 2009, 11 Pages. cited by applicant .
Derthick, et al.,' "An Interactive Visualization Environment for Data Exploration", Retrieved From: http://www.cs.cmu.edu/.about.sage/KDD97.html, Aug. 1997, 10 Pages. cited by applicant .
Fernando, et al.,' "Narrowcasting Attributes for Presence Awareness in Collaborative Virtual Environments pdf", http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4019930, 2006, 6 pages. cited by applicant .
Geyer, et al.,' "Activity Explorer: Activity-centric Collaboration from Research to Product", IBM Systems Journal, IBM.RTM. Retrieved From: http://www.research.ibm.com/journal/sj/454/geyer.html., 2006, 26 Pages. cited by applicant .
Good, et al.,' "CounterPoint: Creating Jazzy Interactive Presentations", Retrieved From: http://drum.lib.umd.edu/bitstream/1903/1121/2/CS-TR-4225.pdf, 2001-2003, 9 Pages. cited by applicant .
Hewagamage, "Interactive Visualization of Spatiotemporal Patterns Using Spirals on a Geographical Map", Proc. IEEE Symp. Visual Languages, 1999, 8 pages. cited by applicant .
Hupfer, "Introducing Collaboration into an Application Development Environment", Retrieved From: http://pnexpert.com/files/IBM.sub.--Contextual.sub.--Collaboration.pdf, Nov. 6-10, 2004, 4 Pages. cited by applicant .
Izadi, et al.,' "Dynamo: A public interactive surface supporting the cooperative sharing and exchange of media", Retrieved From: http://research.microsoft.com/pubs/132613/p159-izadi.pdf, 2003, 10 Pages. cited by applicant .
Little, "High-End Business Intelligence with Data Visualization for WPF 4", Retrieved From: http://www.codeproject.com/Articles/90591/High-End-Business-Intelligence-- with-Data-Visualization, Jun. 29, 2010, 7 Pages. cited by applicant .
Moran, et al.,' "Tailorable Domain Objects as Meeting Tools for an Electronic Whiteboard", Retrieved From: http://pdf.aminer.org/000/121/871/tailorable.sub.--domain.sub.--objects.s- ub.--as.sub.--meeting.sub.--tools.sub.--for.sub.--an.sub.--electronic.sub.- --whiteboard.pdf, 1998, 10 Pages. cited by applicant .
Nelson, "Just Around the Corner: Visual Fusion 4.5", Retrieved From: http://www.idvsolutions.com/Company/Newsletters/2009/Q3/Vfx45Silverlight.- aspx, Sep. 30, 2009, 6 Pages. cited by applicant .
Shaw, "Create Pan andd Zoom Effects in PowerPoint", Retrieved From: http://office.microsoft.com/en-us/powerpoint-help/create-pan-and-zoom-eff- ects-in-powerpoint-HA010232631.aspx, 2007, 13 Pages. cited by applicant .
Thomas, et al.,' "Through-Walls Collaboration", Retrieved From: http://www.tinmith.net/papers/piekarski-pervasive-2009.pdf, 2009, 8 Pages. cited by applicant .
Wempen, "PowerPoint 2007 Bible", John Wiley & Sons, Feb. 27, 2007, 27 pages. cited by applicant .
Weverka, "PowerPoint 2007 All-in-One Desk Reference for Dummies", Published by Wiley Publishing, Jan. 2007, 8 pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110436306.8, Feb. 8, 2014, 13 Pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/968,287, filed Mar. 27, 2014, 18 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/486,762, filed (Feb. 14, 2013), 29 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/965,965, filed Mar. 11, 2015, 17 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/968,287, filed Jun. 5, 2015, 21 pages. cited by applicant .
"Foreign Notice of Allowance", CN Application No. 201110436306.8, Apr. 1, 2015, 4 Pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110436593.2, Mar. 16, 2015, 7 Pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110436635.2, May 18, 2015, 14 Pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/473,206, filed Apr. 9, 2015, 55 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/967,497, filed Mar. 13, 2015, 21 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/968,287, filed Mar. 27, 2015, 18 pages. cited by applicant .
"Notice of Allowance", U.S. Appl. No. 12/968,332, filed Apr. 10, 2015, 15 pages. cited by applicant .
Pash,"Google Docs Updates with a Drawing Editor, Real-Time Collaboration, and Speed", Retrieved from <http://lifehacker.com/5513760/google-docs-updates-with-a-drawing-edit- or-real-time-collaboration-and-speed> on Jun. 8, 2015, Jun. 5, 2015, 17 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 13/253,886, filed Feb. 14, 2014, 26 Pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/965,965, filed Jun. 5, 2014, 13 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/968,287, filed Jun. 6, 2014, 19 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/968,332, filed Jul. 17, 2014, 23 pages. cited by applicant .
"Foreign Notice of Allowance", RU Application No. 2011103151, Sep. 4, 2013, 18 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/967,497, filed Jul. 2, 2015, 24 pages. cited by applicant .
"Foreign Notice of Allowance", CN Application No. 201110436593.2, Jun. 4, 2015, 6 Pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/486,762, filed (Jun. 20, 2013), 42 pages. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/968,332, filed (Aug. 1, 2013),19 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/967,497, filed (Jun. 20, 2013),19 pages. cited by applicant .
Bergmann, et al., "Automated Assistance for the Telemeeting Lifecycle", Proceedings of the ACM conference on Computer supported cooperative work, (Oct. 1994), pp. 373-384. cited by applicant .
"Final Office Action", U.S. Appl. No. 12/184,174, filed Aug. 11, 2014, 18 pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110436306.8, Sep. 17, 2014, 7 Pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110436593.2, Sep. 12, 2014, 12 Pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110436635.2, May 27, 2014, 14 pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110443291.8, Jan. 24, 2014, 12 Pages. cited by applicant .
"Foreign Office Action", CN Application No. 201110443291.8, Jul. 24, 2014, 10 Pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/472,101, filed Sep. 16, 2014, 10 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/473,206, filed Jul. 31, 2014, 41 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/965,965, filed Oct. 2, 2014, 14 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 13/253,886, filed Aug. 14, 2014, 15 pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 14/225,234, filed Jul. 18, 2014, 5 pages. cited by applicant .
"Notice on Reexamination", CN Application No. 201110443291.8, Jan. 4, 2016, 10 Pages. cited by applicant .
"Non-Final Office Action", U.S. Appl. No. 12/968,287, filed Nov. 20, 2015, 22 pages. cited by applicant .
"Office Action Issued in Chinese Patent Application No. 201210376181.9", dated Aug. 17, 2016, 12 Pages. cited by applicant .
"Office Action Issued in Chinese Patent Application No. 201210376206.5", dated Mar. 9, 2016, 9 Pages. cited by applicant .
Chinese Decision on Reexamination dated Dec. 5, 2016, in Application 201210376181.9, 17 pages. (No English Translation). cited by applicant .
Chinese Final Rejection Received for Chinese Patent Application No. 201210376181.9, dated Jan. 20, 2016, 14 Pages. cited by applicant .
Chinese Notice of Reexamination dated Dec. 7, 2016, in Appln. No. 201210376206.5, 10 pages. cited by applicant .
Chinese Office Action dated Apr. 3, 2015 in Appln No. 201210376206.5, 15 pgs. cited by applicant .
Chinese Second Office Action Issued in Patent Application No. 201210376181.9, dated Jul. 13, 2015, 13 Pages. cited by applicant .
Chinese Second Office Action Issued in Patent Application No. 201210376206.5, dated Jun. 10, 2015, 10 Pages. cited by applicant .
Chinese Sixth Office Action Received for Chinese Patent Application No. 200980131157.5, dated Dec. 11, 2014, 9 Pages. cited by applicant .
Chinese Third Office Action dated Oct. 28, 2015 in Appln No. 201210376206.5, 3 pgs. cited by applicant .
Office Action Issued in Chinese Patent Application No. 201110436635.2, dated Apr. 1, 2016, 9 Pages. cited by applicant .
Office Action Issued in Chinese Patent Application No. 201110436635.2, dated Jul. 28, 2016, 9 Pages. cited by applicant .
Office Action Issued in Chinese Patent Application No. 201110436635.2, dated May 18, 2015, 13 Pages. cited by applicant .
Office Action Issued in Chinese Patent Application No. 201110436635.2, dated Oct. 20, 2015, 10 Pages. cited by applicant .
Office Action Received for Chinese Patent Application No. 200980131157.5, dated Jul. 6, 2015, 9 Pages. cited by applicant .
"Microsoft Word's Click and Type Feature", published by SnipTools, Nov. 12, 2003 downloaded Jun. 28, 2015 from http://sniptools.com/vault/microsoft-words-click-and-type-feature; 2 pgs. cited by applicant .
"The Platinum Experience of Collaboration--CollaboratorHYPERMAX", Retrieved Date: Jul. 16, 2010, http://www.businessoctane.com/group.sub.--telepresence.php, 7 pgs. cited by applicant .
"The Screen Capture Tool" by Help and Manual, archived Mar. 13, 1006 by the Internet Wayback Machine, downloaded Nov. 28, 2016, 3 pages, from https://web.archive.org/web/20060313150929/http://www.helpandmanual.com/h- elp/help.sub.--toc.html?hm.sub.--advanced.sub.--tools.sub.--capture. cited by applicant .
Gallegos, D., et al. "CounterPoint User Manual" class project for Charles Paine at the University of New Mexico, Downloaded from Archive. Org 2005 capture, http://web.archive.org/web/20050205082738/www.cs.umd.edu/hcil/co- unterpoint/, 21 pgs. cited by applicant .
Rudnicky, Alexander I., et al., "Intelligently Integrating Information from Speech and Vision to Perform Light-weight Meeting Understanding", retrieved from http://citesseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.126.1733&rep=re- p1 &type=pdf. (Oct. 2005), 6 pages. cited by applicant .
Office Action dated Oct. 4, 2016, in U.S. Appl. No. 13/272,832, 22 pgs. cited by applicant .
Notice of Allowance dated Aug. 10, 2016, in U.S. Appl. No. 13/253,886, 22 pgs. cited by applicant .
Notice of Allowance dated Mar. 1, 2016, in U.S. Appl. No. 12/968,287, 13 pgs. cited by applicant .
Office Action dated Apr. 10, 2015, in U.S. Appl. No. 12/472,101, 14 pgs. cited by applicant .
Office Action dated Apr. 20, 2015, in U.S. Appl. No. 13/272,832, 18 pgs. cited by applicant .
Office Action dated Apr. 20, 2016, in U.S. Appl. No. 13/271,148, 19 pgs. cited by applicant .
Office Action dated Dec. 1, 2016, in U.S. Appl. No. 12/184,174, 17 pages. cited by applicant .
Office Action dated Dec. 20, 2013, in U.S. Appl. No. 12/965,965, 19 pages. cited by applicant .
Office Action dated Sep. 30, 2010, in U.S. Appl. No. 11/260,515 18 pages. cited by applicant .
Office Action dated Jan. 6, 2015, in U.S. Appl. No. 13/253,886, 43 pgs. cited by applicant .
Office Action dated Jul. 17, 2015, in U.S. Appl. No. 13/271,148, 18 pgs. cited by applicant .
Office Action dated Jul. 18, 2014, in U.S. Appl. No. 14/225,234, 25 pgs. cited by applicant .
Office Action dated Jul. 7, 2015, in U.S. Appl. No. 12/184,174, 17 pgs. cited by applicant .
Office Action dated Jul. 9, 2015, in U.S. Appl. No. 13/253,886, 13 pgs. cited by applicant .
Office Action dated Jun. 17, 2016, in U.S. Appl. No. 14/225,234, 11 pgs. cited by applicant .
Office Action dated Mar. 10, 2015, in U.S. Appl. No. 14/225,234, 10 pgs. cited by applicant .
Office Action dated Oct. 31, 2014, in U.S. Appl. No. 13/272,832, 17 pgs. cited by applicant .
Office Action dated Mar. 13, 2012, in U.S. Appl. No. 12/184,174, 20 pages. cited by applicant .
Office Action dated Mar. 21, 2016, in U.S. Appl. No. 12/472,101, 14 pgs. cited by applicant .
Office Action dated Mar. 3, 2016, in U.S. Appl. No. 12/184,174, 16 pgs. cited by applicant .
Office Action dated Mar. 4, 2016, in U.S. Appl. No. 13/272,832, 27 pgs. cited by applicant .
Office Action dated Oct. 6, 2016, in U.S. Appl. No. 14/225,234, 11 pgs. cited by applicant .
Office Action dated Oct. 8, 2015, in U.S. Appl. No. 14/225,234, 11 pgs. cited by applicant .
Office Action dated Sep. 16, 2015, in U.S. Appl. No. 13/272,832, 17 pgs. cited by applicant .
Office Action dated Sep. 22, 2015, in U.S. Appl. No. 12/472,101, 9 pgs. cited by applicant .
Office Action dated Mar. 10, 2017, in U.S. Appl. No. 13/272,832, 18 pgs. cited by applicant .
Advisory Action dated Feb. 7, 2017, in U.S. Appl. No. 14/225,234, 3 pgs. cited by applicant .
Office Action dated Feb. 27, 2017, in U.S. Appl. No. 12/967,497, 26 pgs. cited by applicant .
Office Action Issued in European Patent Application No. 09803312.9, dated Feb. 17, 7 pages. cited by applicant .
Decision on Reexamination Issued in Chinese Patent Application No. 201210376206.5, dated Jun. 1, 2017, 18 pages. cited by applicant .
Notice of Allowace Issued in Chinese Patent Application No. 201210376181.9, dated Mar. 1, 2017, 4 pages. cited by applicant .
Notification of Reexamination Issued in Chinese Patent Application No. 201110436635.2, dated Apr. 27, 2017, 14 pages. cited by applicant .
Office Action dated Jun. 5, 2017, in U.S. Appl. No. 14,225,234, 11 pages. cited by applicant .
Office Action dated Sep. 12, 2017, in U.S. Appl. No. 13/271,148, 18 pages. cited by applicant .
Office Action dated Oct. 6, 2017, in U.S. Appl. No. 14/225,234, 12 pages. cited by applicant.
Primary Examiner: Parker; Jeanette J
1. A computer-implemented method, comprising: displaying a user interface view of an application on a first display of a device, the user interface view having a first set of user interface control elements and a content of the application; detecting a second display of the device, wherein the second display has a first area including a first side of the second display and a second area including a second side of the second display, where the first area and the second area of the second displayed do not overlap; customizing the user interface view of the application on the first display by generating a customized interface view based on an adaptation parameter, the customized user interface view having a second set of user interface control elements and the content of the application, wherein the second set of user interface control elements are different from the first set of user interface control elements, and wherein the user interface control elements are enabled to control operations of the application; displaying the customized user interface view of the application on the second display of the device at a same time as displaying the user interface view of the application on the first display of the device; receiving another adaptation parameter indicating that a user's location is closer to the second area than the first area of the second display; and in response to receiving the another adaptation parameter, modifying the customized user interface view by moving at least one of the user interface control elements of the second set of user interface control elements from a first location within the first area of the second display to a second location within the second area of the second display, where in the second location is closer to the user then the first location, while the content of the application is displayed on the first display and the second display and the location of the first set of user interface control elements on the first display remain unchanged; and displaying the modified customized user interface on the second display.
2. The computer-implemented method of claim 1, wherein customizing the user interface view further comprises adding an additional user interface control element to the user interface view.
3. The computer-implemented method of claim 1, wherein customizing the user interface view further comprises removing an additional user interface control element from the user interface view.
4. The computer-implemented method of claim 1, wherein customizing the user interface view further comprises modifying at least one of the user interface control elements of the user interface view.
5. The computer-implemented method of claim 1, wherein the adaptation parameter corresponds to a physical characteristic of the second display.
6. The computer-implemented method of claim 1, wherein the adaptation parameter corresponds to a control directive from the user.
7. The computer-implemented method of claim 1, wherein the adaptation parameter corresponds to an additional location of the user relative to the second display.
8. The computer-implemented method of claim 1, wherein the another adaptation parameter is generated by a motion sensor.
9. A computer storage hardware device containing instructions that, when executed by a processor, perform a method comprising: displaying a user interface view of an application on a first display of a device, the first user interface view having a first set of user interface elements and a content of the application; detecting a second display of the device, wherein the second display has a first area including a first side of the second display and a second area including a second side of the second display, where the first area and the second area of the second displayed do not overlap; customizing the user interface view of the application on the first display by generating a customized interface view based on an adaptation parameter, the customized user interface view having a second set of user interface control elements and the content of the application, wherein the second set of user interface control elements are different from the first set of user interface control elements, and wherein the user interface control elements are enabled to control operations of the application; displaying the customized user interface view of the application on the second display of the device at a same time as presenting the user interface view of the application on the first display of the device; receiving another adaptation parameter indicating that a user's location is closer to the second area than the first area of the second display; and in response to receiving the another adaptation parameter, modifying the customized user interface view by moving at least one of the user interface control elements of the second set of user interface control elements from a first location within the first area of the second display to a second location within the second area of the second display, where in the second location is closer to the user then the first location, while the content of the application is displayed on the first display and the second display and the location of the first set of user interface control elements on the first display remain unchanged; and displaying the modified customized user interface on the second display.
10. The computer storage device of claim 9, further comprising instructions that when executed by the processor perform a method further comprising generating the first and second user interface views based on properties of the first and second displays.
11. The computer storage device of claim 9, further comprising instructions that when executed by the processor perform a method further comprising modifying the first or second user interface view based on control directives received from the user.
12. The computer storage device of claim 9, wherein the second set of user interface elements comprises a modified user interface element of the first set of user interface elements.
13. The computer storage device of claim 9, wherein the adaptation parameter indicating the user's location is received from a location component, and wherein the location component determines the location of a user relative to the second display based on video information, audio information, or motion information.
14. An apparatus, comprising: a processor; multiple displays coupled to the processor; and a memory coupled to the processor, the memory storing a custom user interface system that, when executed by the processor, is configured to adapt a user interface view of an application for presentation by one or more displays, the custom user interface system comprising: a user interface adaptation component configured to receive as input a first user interface view of the application for presentation on a first display and an adaptation parameter, and generate a second user interface view by customizing the first user interface view of the application on the first display based on the first user interface view for presentation on a second display based on the adaptation parameter, wherein the first user interface view comprises a first set of user interface control elements and a content of the application, and wherein the second user interface view comprises a second set of user interface control elements that are different from the first set of user interface control elements and the content of the application, where in the user interface control elements are enabled to control operations of the application; and a presentation component configured to displaying the first user interface view of an application on a first display of a device, detect a second display of the device, wherein the second display has a first area including a first side of the second display and a second area including a second side of the second display, where the first area and the second area of the second displayed do not overlap, display the second user interface view on the second display of the device at a same time as presenting the first user interface view of the application on the first display of the device, the presentation component further configured to receive another adaptation parameter indicating a user's location is closer to the second area than the first area of the second display, and in response to receiving the another adaptation parameter, modifying the second user interface view by moving at least one of the user interface control elements of the second set of user interface control elements from a first location within the first area of the second display to a second location within the second area of the second display, where in the second location is closer to the user then the first location, while the content of the application is displayed on the first display and the second display and the location of the first set of user interface control elements on the first display remain unchanged; and displaying the modified second user interface on the second display.
15. The apparatus of claim 14, wherein generating the second user interface view further comprises modifying at least one user interface control element of the first set of user interface control elements.
16. The apparatus of claim 14, wherein the adaptation parameter represents a physical characteristic of the second display or a control directive of the user.
17. The apparatus of claim 14, wherein the custom user interface system further comprises a location component configured to determine the location of a user relative to the second display based on video information, audio information, or motion information.
18. The apparatus of claim 14, wherein the second display includes one or more additional input components.
A software application typically utilizes a user interface specifically designed to allow a human user to interface with the software application. A user interface may generate one or more user interface views to present information from the software application for viewing by a user on an output device such as a display, and also to receive control directives or commands from a user via an input device to control, navigate and interact with various features provided by the software application. In some cases, a device may be attached to multiple output devices, such as a laptop computer with a laptop screen and external monitor, a personal computer with dual-monitors, or a conferencing server with connected devices each having a different display. In such cases, an application may generate a single user interface view for presentation on the multiple displays, which is typically duplicated on each additional display. However, a single user interface may not necessarily be appropriate for each display. It is with respect to these and other considerations that the present improvements have been needed.
Various embodiments are generally directed to techniques to custom user interfaces for different displays. Some embodiments are particularly directed to enhanced techniques for generating and presenting customized user interface views for providing interoperability with a software application, with each customized user interface view specifically designed for a given display. In other words, a single software application may present different customized user interface views with different user interface elements on different displays, either at a same time or different times.
In one embodiment, for example, an apparatus such as an electronic device with a processing system may implement a custom user interface system that when executed by a processor is operative to adapt a user interface view of an application for presentation by one or more displays, and in some cases, potentially across multiple computing devices. The custom user interface system may comprise, among other elements, a user interface adaptation component operative to receive as input a user interface view of the application for presentation on a first display and an adaptation parameter, and modify the user interface view for presentation on a second display based on the adaptation parameter. A presentation component is operative to present the customized user interface view on the second display. Other embodiments are described and claimed.
FIG. 1 illustrates an embodiment of a custom user interface system.
FIG. 2 illustrates an embodiment of a custom user interface system as shown in FIG. 1 with additional elements.
FIG. 3 illustrates an embodiment of a system implementing a custom user interface system as shown in FIGS. 1, 2 with simultaneous presentations.
FIG. 4A illustrates an embodiment of a system implementing a user interface component as shown in FIGS. 1, 2 with a single display.
FIG. 4B illustrates an embodiment of a system implementing a custom user interface system as shown in FIGS. 1, 2 with a single display.
FIG. 5A illustrates an embodiment of a user interface view.
FIG. 5B illustrates an embodiment of a first customized user interface view.
FIG. 5C illustrates an embodiment of a second customized user interface view.
FIG. 5D illustrates an embodiment of another user interface view.
FIG. 5E illustrates an embodiment of another customized user interface view.
Conventional techniques allow an application to generate a single user interface view for presentation on multiple displays, with the single user interface view corrected for varying physical characteristics of a display, such as size, color, resolution, and so forth. For instance, assume a first display has a smaller dimension than a second display. An application may generate a single user interface view that is scaled for both displays, with a smaller version for the smaller display and a larger version for the larger display. In both cases, the user interface elements used to construct the user interface view remain the same. However, each display may be used for different purposes. For instance, during a meeting, a smaller display may be used to read a document while a larger display is to present the same document to a number of meeting participants. In such cases, having a scaled version of a same user interface view may not be useful for both purposes. Various user interface elements, such as a toolbar, may be useful on a smaller display to allow a presenter to manipulate a document, but may be a distraction to viewers when presented on the larger display. As such, multiple displays presenting scaled versions of a single user interface view may not be desirable for all potential scenarios.
To solve these and other problems, various embodiments are directed to enhanced techniques for automatically generating, modifying and presenting customized user interface views useful for providing interoperability with a software application, with each customized user interface view specifically designed for a given display. In other words, a single software application may present different customized user interface views with different user interface elements on different displays, either at a same time or different times. Further, the different customized user interface views may be automatically generated based on various adaptation parameters, such as a location of a user, among other adaptation parameters discussed more fully below.
In one embodiment, this may be accomplished using a custom user interface system. The custom user interface system may be implemented as part of an application program (e.g., a word processor, spreadsheet, etc.) or a system program (e.g., an operating system). Additionally or alternatively, the custom user interface system may be designed as a standalone software component interoperable with an application program or a system program. The custom interface component may receive content to be displayed by a user interface view for an application program, and generates customized user interface views to display the received content based on one or more adaptation parameters suitable for one or more displays used with the application. The user interface view and each customized user interface view may utilize different sets of user interface elements suitable for a given display. For instance, each set of user interface elements may have one or more mutually exclusive user interface elements. It may be appreciated, however, that in some cases different user interface views may share a certain number of user interface elements in common that are needed for all the user interface views.
In one embodiment, an apparatus such as an electronic device with a processing system may implement a custom user interface system that is operative to adapt a user interface view of an application for presentation by a display. The custom user interface system may comprise a user interface adaptation component operative to receive as input a user interface view of an application for a first display, and one or more adaptation parameters. The custom user interface system may generate one or more customized user interface view (e.g., versions of the user interface view) for the application for presentation on a second display. The user interface view may have a first set of user interface elements, and the customized user interface may have a second set of user interface elements selected based on one or more adaptation parameters. The second set of user interface elements may be different from the first set of user interface elements. The custom user interface system may further comprise a presentation component operative to present the user interface view and the customized user interface view for the application on the respective first and second displays. Other embodiments are described and claimed.
FIG. 1 illustrates a block diagram for a custom user interface system 100. In one embodiment, for example, the custom user interface system 100 may comprise a computer-implemented component having multiple components 110, 130. As used herein the terms "system" and "component" are intended to refer to a computer-related entity, comprising either hardware, a combination of hardware and software, software, or software in execution. For example, a component can be implemented as a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers as desired for a given implementation. The embodiments are not limited in this context.
In the illustrated embodiment shown in FIG. 1, the custom user interface system 100 may be implemented as part of an electronic device. Examples of an electronic device may include without limitation a mobile device, a personal digital assistant, a mobile computing device, a smart phone, a cellular telephone, a handset, a one-way pager, a two-way pager, a messaging device, a computer, a personal computer (PC), a desktop computer, a laptop computer, a notebook computer, a handheld computer, a tablet computer, a server, a server array or server farm, a web server, a network server, an Internet server, a work station, a mini-computer, a main frame computer, a supercomputer, a network appliance, a web appliance, a gaming device, a distributed computing system, multiprocessor systems, processor-based systems, consumer electronics, programmable consumer electronics, television, digital television, set top box, wireless access point, base station, subscriber station, mobile subscriber center, radio network controller, router, hub, gateway, bridge, switch, machine, or combination thereof. Although the custom user interface system 100 as shown in FIG. 1 has a limited number of elements in a certain topology, it may be appreciated that the custom user interface system 100 may include more or less elements in alternate topologies as desired for a given implementation.
In one embodiment, an apparatus such as an electronic device with a processing system may implement a custom user interface system 100 generally arranged to dynamically and automatically modify, adapt or customize content for a user interface view 102 of an application for presentation by a display, with each customized user interface view 120-b specifically designed for a given display. In this manner, a single software application may present different customized user interface views 120-b each having a different set of user interface elements on different displays. The different customized user interface views 120-b may be presented at either a same time or different times with the user interface view 102 or each other.
In the illustrated embodiment shown in FIG. 1, the custom user interface system 100 may comprise a user interface adaptation component 110 and a presentation component 130. The custom user interface system 100 may be generally arranged to generate various customized user interface views 120-b. The presentation component 130 may be generally arranged to present the user interface view 102 and any customized user interface views 120-b on various electronic displays, with each customized user interface view 120-b customized for a corresponding display.
The user interface adaptation component 110 may receive as input a user interface view 102 for a software program, such as an application program or a system program. The user interface view 102 may comprise various user interface elements specifically arranged to provide interoperability with a given software program. For instance, a user interface view 102 may include a toolbar, icons, control buttons, drop down menus, a document, multimedia information, and so forth. A user may use various input devices to interact with the user interface view 102 and control various aspects and operations of the software application. The user interface view 102 may be a user interface view built and ready for presentation by a display. Alternatively, the user interface view 102 may be a user interface view that is already presented by a display.
The user interface adaptation component 110 may also receive as input one or more adaptation parameters 104-a. The adaptation parameters 104-a may comprise values used to modify the user interface view 102 for a given display. In one embodiment, an adaptation parameter 104-1 may represent a physical characteristic of a display. Examples of physical characteristics of a display may include screen resolution, screen size, screen shape, operating frequency, refresh rate, and so forth. In one embodiment, an adaptation parameter 104-2 may represent a control directive of a user. Examples of control directives may include signals received from an input device (e.g., a keyboard, pointer, touch screen, etc.) initiated by a user. For instance, a user may manually change one or more user interface elements for the user interface view 102 (e.g., remove a toolbar). In one embodiment, an adaptation parameter 104-3 may represent a location of a user. For instance, measurements of a distance between a user location and a display may be made on a periodic, aperiodic or continuous basis. It may be appreciated that these are merely a few examples of adaptation parameters 104-a, and others may be used for alternative implementations. The embodiments are not limited in this context.
It is worthy to note that "a" and "b" and "c" and similar designators as used herein are intended to be variables representing any positive integer. Thus, for example, if an implementation sets a value for a=5, then a complete set of adaptation parameters 104-a may include adaptation parameters 104-1, 104-2, 104-3, 104-4 and 105-5. The embodiments are not limited in this context.
In operation, the custom user interface system 100 may receive as input a user interface view 102 of an application for presentation on a first display and one or more adaptation parameters 104-a. The custom user interface system 100 may modify or customize the user interface view 102 to create a customized user interface view 120-b suitable for presentation on a second display based on the adaptation parameters 104-a.
In various embodiments, a customized user interface view 120-b may have different user interface elements from those used by a given user interface view 102. In one embodiment, a user interface view 102 may have a first set of user interface elements, while a customized user interface view 120-1 may have a second set of user interface elements different from the first set of user interface elements. For instance, assume a user interface view 102 comprises a user interface for a word processing application, and has a first set of user interface elements that includes a document that is ready for editing, a toolbar, a page count, a word count, and a zoom control. The customized user interface view 120-1 may comprise a second set of user interface elements that includes all of the first set of user interface elements, with the addition of a ruler. Alternatively, the customized user interface view 120-1 may comprise only a document and a zoom control. It is worthy to note that the first and second sets of user interface elements do not need to have completely different user interface elements, but rather only a single user interface element needs to be different between the two sets.
The user interface adaptation component 110 may generate one or more custom user interface views 120-b for a given user interface view 102 as needed for different displays based on adaptation parameters 104-a. The user interface adaptation component 110 may receive a different set of adaptation parameters 104-a for each customized user interface view 120-b.
In one embodiment, the user interface adaptation component 110 may receive an adaptation parameter 104-1 comprising a value representing a property for a display, such as a physical characteristic of a display. Examples of physical characteristics of a display may include screen resolution, screen size, screen shape, operating frequency, refresh rate, and so forth. For example, assume the adaptation parameter 104-1 is a value representing a height and/or width of a display. The user interface adaptation component 110 may compare the adaptation parameter 104-1 for a secondary display with stored height and/or width values associated with a primary display used for a user interface view 102 (or read in real time from the primary display or display adapter). The user interface adaptation component 110 may determine that the secondary display is larger than the primary display based on the comparison. Rather than simply scaling a size for the user interface view 102, the user interface adaptation component 110 may modify various user interface elements from the user interface view 102 specifically for a larger display, such as those user interface elements suitable for viewers rather than those user interface elements suitable for a presenter. For instance, the user interface adaptation component 110 may increase font size beyond a scaled version of the original font size in the user interface view 102, to make text on a document more visually readable by a viewer at a distance. Similarly, the user interface adaptation component 110 may change a background color and text color to provide more contrast to enhance viewing of text on a document. The user interface adaptation component 110 may also remove user interface elements from the user interface view 102 that are not particularly useful or relevant to viewing rather than presenting, such as control user interface elements. In this manner, a user may use a laptop with a user interface view 102 with a document and editing user interface elements displayed on the laptop display, while a large touch display for a conference room attached to the laptop may have a customized user interface view 120-b with just the document and not any of the editing user interface elements. The customized user interface view 120-b may even enlarge the document for easier viewing at a distance by any meeting attendees in a conference room.
In one embodiment, the user interface adaptation component 110 may receive an adaptation parameter 104-2 comprising a value representing a control directive of a user. Examples of control directives may include signals received from an input device (e.g., a keyboard, pointer, touch screen, etc.) initiated by a user. For instance, rather than having the user interface adaptation component 110 automatically generate user interface elements for the customized user interface view 120-b, a user may manually select and change one or more user interface elements for the user interface view 102. Continuing with the previous example, a user may select editing user interface elements for the user interface view 102 on a laptop display, thereby allowing the user to edit a document during a meeting. The user may further deselect the editing user interface elements for the customized user interface view 120-b of a large touch display to enhance distance viewing by meeting participants in a conference room.
In one embodiment, the user interface adaptation component 110 may receive an adaptation parameter 104-3 comprising a value representing a location of a user relative to a display. For instance, measurements of a distance between a user location and a display may be made on a periodic, aperiodic or continuous basis. The measurements may be used to determine which user interface elements of a user interface view 102 are appropriate for a display proximate to the user. Continuing with the previous example, the user interface adaptation component 110 may receive an adaptation parameter 104-3 on a periodic basis indicating a distance between the user and the display. The user interface adaptation component 110 may select one set of user interface elements for a customized user interface view 120-b of large touch display based on the distance. For instance, user interface elements for editing tools may appear as a user moves closer to a display, and disappear as a user moves away from a display. In another example, user interface elements for editing tools may move from one side of a display to another side of a display based on which side the user is closer to a given moment in time.
In one embodiment, the user interface adaptation component 110 may receive an adaptation parameter 104-4 comprising a value representing components for a display. A display device may have one or more components providing additional capabilities beyond a display screen, such as a video camera, array microphone, touch sensors, motion sensors, speakers, and so forth. A computing device may typically access such capabilities, for example, via a USB interface or similar interface. The presence of such components could also influence displayed functionality and use of the display. For instance, the user interface adaptation component 110 may detect touch sensors implemented for a display, and generate a customized user interface view 120-b with user interface control elements for the touch sensor.
The presentation component 130 may present the customized user interface view 120-b on the second display. In one embodiment, the presentation component 130 may present the customized user interface view 120-b of the application on the second display at a same time as the user interface view 102 of the application is presented on the first display. In one embodiment, the presentation component 130 may present the customized user interface view 120-b of the application on the second display at a different time as the user interface view 102 of the application is presented on the first display. The presentation component 130 may be implemented as part of a main processing system for a computing device, or in a dedicated processing system such as a display adapter for one or more displays used with the main processing system of the computing device.
FIG. 2 illustrates a more detailed block diagram of the user interface adaptation component 110. In the illustrated embodiment shown in FIG. 2, the user interface adaptation component 110 may further comprise a data store 232 and a location component 234. The location component 234 may be coupled to various input devices, including a video camera 240, a microphone 242, and a motion detector 244. It may be appreciated that the user interface adaptation component 110 may include more or less elements as desired for a given implementation. For instance, other input devices may include various biometric sensors for a human. The embodiments are not limited in this context.
The datastore 232 may comprise a database storing information for the custom user interface system 100. The datastore 232 may comprise a local datastore implemented on a same device as the custom user interface system 100, or a remote datastore implemented on a different device from a device executing the custom user interface system 100. The datastore 232 may store information useful for the custom user interface system 100, such as information associated with a given application, a given computing system, a given display, a given display adapter, user interface elements, user interface templates, customized user interface templates, historical information, movement patterns, user preferences, user profiles, customization rules, and so forth. For instance, the datastore 232 may store specifications for each display attached to a device, such as screen size or resolution. Alternatively, some devices natively share capabilities, such as when attaching a device via a digital visual interface (DVI) cable, or attaching a USB monitor with cameras or sensors. In such cases, the datastore 232 may be an optional component.
The location component 234 may be arranged to determine a location of a user relative to a display, and encode the location as an adaptation parameter 104-3. The location component 234 may determine a location for a user based on information received from the video camera 240, the microphone 242 and/or the motion detector 244. Additionally or alternatively, the location component 234 may track a location for a user based on a device carried by the user, such as a smart phone. In this case, the location component 234 may automatically retrieve location information from a GPS device, cellular tower triangulation, wireless data network node detection, or similar location detection techniques. In addition to location of a user, the location component 234 may specifically be arranged to identify location of various body parts of a user, such as a user's arms, for motion capture gestures and other motion-based user interfaces.
The location component 234 may determine a location by analyzing video information received from the video camera 240. For instance, the video camera 240 may provide continuous video or periodic images to the location component 234 having images of a user and a display device. The location component 234 may measure a distance between the user and the display device, and encode the measured distance as the adaptation parameter 104-3. Additionally or alternatively, the location of a display device or other furniture and equipment within a conference room may be stored in the datastore 232, and the location component 234 may estimate distance of a user from a display device based on proximity to known locations within the conference room.
The location component 234 may determine a location by analyzing audio information received from the microphone 242. For instance, the microphone 242 may record sounds from the user, and use acoustic location techniques to determine a distance and direction for a user relative to a display device.
The location component 234 may determine a location by analyzing motion information received from the motion detector 244. For instance, the motion detector 244 may scan for movement of a user, and use motion detection techniques to determine a distance and direction for a user relative to a display device.
The user interface adaptation component 110 may receive an adaptation parameter 104-3 from the location component 234, and generate a customized user interface view 120-b based on the received adaptation parameter 104-3. For instance, assume a display is a large touch display with touch sensors. The user interface adaptation component 110 may adjust various control user interface elements of a user interface view 102 based on proximity to one side or another side of the large touch display to make it more convenient for a user to control an application. In another example, the user interface adaptation component 110 may adjust font size as a user moves away from the large touch display to allow the user to better see a document on the user interface view 102. In yet another example, the user interface adaptation component 110 may remove control user interface elements completely as a user moves away from the large touch display since the user will not be capable of using the touch screen.
FIG. 3 illustrates a block diagram of a system 300. The system 300 may comprise a computing device 302 communicatively coupled to multiple displays 308-c arranged to perform various operations in accordance with the described embodiments. For example, the computing device 302 may implement the custom user interface system 100 to generate customized user interface views 120-b for each of the displays 308-c.
The computing device 302 may include without limitation any of the electronic devices as described with reference to FIG. 1 having a processing system. In the illustrated embodiment shown in FIG. 3, the computing device 302 may comprise an application 304, the custom user interface system 100, and a display adapter 306. It may be appreciated that the computing device 302 may comprise more or less elements as desired for a given implementation.
The multiple displays 308-c may each comprise any electronic display for presentation of visual, tactile or auditive information. Examples for a display 308-c may include without limitation a cathode ray tube (CRT), bistable display, electronic paper, nixie tube, vector display, a flat panel display, a vacuum fluorescent display, a light-emitting diode (LED) display, electroluminescent (ELD) display, a plasma display panel (PDP), a liquid crystal display (LCD), a thin-film transistor (TFT) display, an organic light-emitting diode (OLED) display, a surface-conduction electron-emitter display (SED), a laser television, carbon nanotubes, nanocrystal displays, a head-mounted display, and so any other displays consistent with the described embodiments. In one embodiment, a display 308-c may be implemented as a touchscreen display. A touchscreen display is an electronic visual display that can detect the presence and location of a touch within the display area. The touch may be from a finger, hand, stylus, light pen, and so forth. The embodiments are not limited in this context.
The custom user interface system 100 may generate customized user interface views 120-b for one or more of the displays 308-c. As shown, the presentation component 130 may present a customized user interface view 120-1 of the application 304 on a display 308-2 at a same time as the user interface view 102 of the application 304 is presented on a display 308-1. As previously described, the user interface view 102 may be a current user interface view for an application rendered for a primary display, while the customized user interface view 120-1 may be an adapted version of the user interface view 102 specifically customized for a secondary display. While the user interface view 102 and the customized user interface view 120-1 may share some user interface elements in common, each will have at least one different user interface element from the other (e.g., an added UI element, a removed UI element, a modified UI element, etc.). It may be appreciated that the custom user interface system 100 may generate any number of customized interface views 120-b for any number of displays 308-c. The embodiments are not limited in this context.
FIGS. 4A, 4B illustrate a block diagram of a system 400. The system 400 may comprise a computing device 402 communicatively coupled to multiple displays 408-d arranged to perform various operations in accordance with the described embodiments. For example, the computing device 402 may implement the custom user interface system 100 to generate customized user interface views 120-b for each of the displays 408-d. The computing device 402 and the multiple displays 408-d may be similar to corresponding computing device 302 and multiple displays 308-c as described with reference to FIG. 3.
The custom user interface system 100 may generate customized user interface views 120-b for one or more of the displays 408-d. In one embodiment, the presentation component 130 may present a customized user interface view 120-b of an application 404 on a display 408-2 at a different time as a user interface view 102 of the application 404 is presented on a first display 408-1. As shown in FIG. 4A, the presentation component 130 may present a user interface view 102 of the application 404 on a display 408-1, while the display 408-2 is blank or turned off. As shown in FIG. 4B, the presentation component 130 may present a customized user interface view 120 of the application 404 on the display 408-2, while the display 408-1 is blank or turned off.
By way of example, assume a user has two different displays attached to a device, with each display on opposite sides of a conference room. When the user moves towards the display 408-1, the presentation component 130 may turn on the display 408-1 and present the user interface view 102. The presentation component 130 may turn off the display 408-2 to converse power or improve audience focus. As the user moves toward the display 408-2, the presentation component 130 may turn off the display 408-1, and turn on the display 408-2 and present the customized user interface view 120.
FIG. 5A illustrates an exemplary customized a user interface view 102. FIG. 5A illustrates a display 308-2 having a motion sensor 560 to display a user interface view 102-1 for an application program 304, 404. Assume the application program 304 comprises a word processing application, and user interface view 102-1 comprises a specific user interface view for the word processing application. As shown, the user interface view 102 comprises various user interface elements, including a document 502, a control bar 504, and a status bar 506. Further assume the user interface view 102-1 is presented on the display 308-1, which is a display for a laptop computer.
FIG. 5B illustrates an exemplary customized user interface view 120-1. FIG. 5B illustrates the user interface view 102-1 after adaptation by the user interface adaptation component 110 to generate a customized user interface view 120-1 of the user interface view 102-1. Assume the customized user interface view 120-1 is presented on the display 308-2, which is a large touch display with cameras and touch sensors in a conference room. Further assume the display 308-2 has a motion sensor 560 to detect motion of a user, including a user's body parts, such as hand waving for gesture based control of the customized user interface view 120-1. Since the display 308-2 is a large touch display designed for viewing by various attendees of a meeting in the conference room, the customized user interface view 120-1 maintains the main focus user interface elements of the document 502 and the control bar 504. However, the customized user interface view 120-1 removes the status bar 506 to further enlarge the document 502 and enhance focus on the document 502, and does this based on detected properties and capabilities of the display 308-2. Note that the customized user interface view 120-1 is not simply a scaled larger version of the user interface view 102, but rather is an enlarged user interface view with different user interface elements suitable for the display 308-2. Hence, removal of the status bar 506 from the customized user interface view 120-1 is appropriate in this context.
Further assume the user interface adaptation component 110 receives an adaptation parameter 104-3 generated by the motion sensor 560 indicating that a user location is near a side 508 of the display 308-2. The user interface adaptation component 110 may generate the customized user interface view 120-1 of the user interface view 102-1 such that the control bar 504 is presented towards the side 508 of the display 308-2. This allows a presenter to more easily reach and utilize the touch sensors for managing the document 502 of the application 304.
FIG. 5C illustrates an exemplary customized user interface view 120-2. As with the customized user interface view 120-1, the customized user interface view 120-2 is customized for the display 308-1. However, sometime during a presentation the presenter moves towards the side 510 of the display 308-2, as detected by the motion sensor 560. The user interface adaptation component 110 receives an adaptation parameter 104-3 indicating that a user location is near a side 510 of the display 308-2 from the location component 234. The user interface adaptation component 110 may generate the customized user interface view 120-2 of the user interface view 102 such that the control bar 504 is presented towards the side 510 of the display 308-2. This allows a presenter to more easily reach and utilize the touch sensors for managing the document 502 of the application 304.
FIG. 5D illustrates an exemplary user interface view 120-2. FIG. 5D illustrates the user interface view 102-2 before adaptation by the user interface adaptation component 110. Since the display 308-2 is a large touch display designed for viewing by various attendees of a meeting in the conference room, the user interface view 102-2 maintains the main focus user interface element of only the document 502 when an adaptation parameter 104-3 generated by the motion sensor 560 indicates a user is beyond a defined distance from the display 308-2. This scenario allows for an example of adding user interface elements to the user interface view 102-2.
FIG. 5E illustrates an exemplary customized user interface view 120-3. FIG. 5E illustrates the user interface view 102-2 after adaptation by the user interface adaptation component 110. Assume the user interface adaptation component 110 receives an adaptation parameter 104-3 generated by the motion sensor 560 indicating that a user location is within a defined distance of the display 308-2, and further, is near the side 510 of the display 308-2. The user interface adaptation component 110 may generate a customized user interface view 120-3 of the user interface view 102-2 such that multiple control elements 512-1, 512-2 and 512-3 are presented towards the side 510 of the display 308-2. This allows a presenter to interact with the document 502 with a set of controls within easy reach of the user.
FIG. 6 illustrates one embodiment of a logic flow 600. The logic flow 600 may be representative of some or all of the operations executed by one or more embodiments described herein, such as the user interface adaptation component 110 of the custom user interface system 100, for example.
In the illustrated embodiment shown in FIG. 6, the logic flow 600 may present a user interface view of an application on a first display for a device at block 602. For example, the presentation component 130 of the custom user interface system 100 may present a user interface view 102 of an application 304 on a first display 308-1 for a computing device 302.
The logic flow 600 may detect a second display for the device at block 604. For example, the display adapter 306 of the computing device 302 may detect a presence of additional displays available for the computing devices 302, such as the displays 308-2 through 308-c.
The logic flow 600 may customize the user interface view based on an adaptation parameter at block 606. For example, the user interface adaptation component 110 of the custom user interface system 100 may receive the user interface view 102 and one or more adaptation parameters 104-a, and customize the user interface view 102 based on the one or more adaptation parameters 104-a. In one embodiment, for example, the user interface adaptation component 110 may add, remove, modify, or move a user interface element of the user interface view 102 to generate a customized user interface view 120-b.
The logic flow 600 may present the customized user interface view on the second display at block 608. For example, the presentation component 130 may present a customized user interface view 120-1 on the second display 308-2 of the computing device 302.
In the various embodiments, it may be appreciated that a single device utilizing a single application may utilize multiple displays to present multiple user interface views, with the user interface views comprising different versions of a single user interface view. This is a significant improvement over other conventional computing systems utilizing multiple displays, where an application may generate a single user interface view for presentation on each of the multiple displays, with a user interface view scaled in size for a given display. In other words, each display has different user interface views synchronized across different display devices, rather than a tethering mode where a user interface view and any changes to a user interface view are simply replicated across all displays. The embodiments are not limited in this context.
The drives and associated computer-readable media provide volatile and/or nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For example, a number of program modules can be stored in the drives and memory units 710, 712, including an operating system 730, one or more application programs 732, other program modules 734, and program data 736. The one or more application programs 732, other program modules 734, and program data 736 can include, for example, the custom user interface system 100, the user interface adaptation component 110, the customized user interface views 120-b, the presentation component 130, the datastore 232, and the location component 234.
One or more monitors 744 or other type of display devices are also connected to the system bus 708 via an interface, such as a video adaptor 746. In addition to the monitor 744, a computer typically includes other peripheral output devices, such as speakers, printers, and so forth. One or more monitors 745 may also be connected to the system bus 708 via an input device interface 742 and/or a hub, such as USB hub 743. The monitors 745 may comprise various components, such as a video camera, array microphone, touch sensors, motion sensors, speakers, and so forth. The components may be connected to the input device interface 742 via the USB hub 743.
Some embodiments may comprise an article of manufacture. An article of manufacture may comprise a computer-readable storage medium arranged to store logic. Examples of a computer-readable storage media include any storage medium capable of storing electronic data, including volatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of the logic may include various software elements, such as software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. In one embodiment, for example, an article of manufacture may store executable computer program instructions that, when executed by a computer, cause the computer to perform methods and/or operations in accordance with the described embodiments. The executable computer program instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The executable computer program instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a computer to perform a certain function. The instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language.
Previous Patent US 9,864,611 | Next Patent US 9,864,613