{"id":{"repo_id":"uiuc","oai_identifier":"oai:www.ideals.illinois.edu:2142/22284"},"canonical_url":"https://search.dev.ndltd.org/etd/uiuc/oai:www.ideals.illinois.edu:2142/22284","repository":{"repo_id":"uiuc","name":"University of Illinois - Urbana-Champaign","base_url":"https://www.ideals.illinois.edu/oai-pmh"},"display":{"title":"Application-independent user interface design using an application exposure","abstract":"User interface (UI) software reuse requires separating the reusable UI elements from the elements that constitute the application semantics. A classic issue in user interface research is how to couple these two groups of elements effectively. This issue is particularly conspicuous when 3D applications are concerned. In our attempt to build a UI support system for 3D applications, we use a software layer called the application exposure (AE) for the coupling. The AE layer consists of two portions. The operation portion allows operations defined on application objects to be invoked from within the user interface various fashions. The representation portion exposes to the UI side the states of the application objects engaged in user interaction. This portion of the exposure allows the user to closely monitor the application objects that undergo interactive modification. The AE contributes to increased reusability in two major ways. First, on the application side, we feel that writing the methods that generate the exposure is easier than learning the internal construction of a UI framework and building subclasses from it. Moreover, with the exposure, rather than subclassing, as the coupling mechanism, it appears to us that the UI part imposes far less on the application part. Second, on the user interface side, the application exposure isolates the UI components from the particularities that exist across various application objects. As such, these components can be built to fulfill the desired UI functions rather than to cater to the particular application objects. The UI components so built are likely to be more reusable. We use two other abstractions, namely that of mediator and activator, to encapsulate such highly reusable UI components.","abstract_html":"User interface (UI) software reuse requires separating the reusable UI elements from the elements that constitute the application semantics. A classic issue in user interface research is how to couple these two groups of elements effectively. This issue is particularly conspicuous when 3D applications are concerned. In our attempt to build a UI support system for 3D applications, we use a software layer called the application exposure (AE) for the coupling. The AE layer consists of two portions. The operation portion allows operations defined on application objects to be invoked from within the user interface various fashions. The representation portion exposes to the UI side the states of the application objects engaged in user interaction. This portion of the exposure allows the user to closely monitor the application objects that undergo interactive modification. The AE contributes to increased reusability in two major ways. First, on the application side, we feel that writing the methods that generate the exposure is easier than learning the internal construction of a UI framework and building subclasses from it. Moreover, with the exposure, rather than subclassing, as the coupling mechanism, it appears to us that the UI part imposes far less on the application part. Second, on the user interface side, the application exposure isolates the UI components from the particularities that exist across various application objects. As such, these components can be built to fulfill the desired UI functions rather than to cater to the particular application objects. The UI components so built are likely to be more reusable. We use two other abstractions, namely that of mediator and activator, to encapsulate such highly reusable UI components.","abstract_has_math":false,"creators":["Zhou, Tom Zhong-Yu"],"institution":"University of Illinois at Urbana-Champaign","degree_name":"Ph.D.","degree_level":"Dissertation","degree_discipline":"Computer Science","degree_department":null,"school":null,"contributors":["Kubitz, William J."],"advisors":[],"committee_chairs":[],"committee_members":[],"year":2011,"date_issued":"2011-05-07T13:34:58Z","date_published":"2011-05-07T13:34:58Z","updated_at":"2026-07-22T22:25:19Z","subjects":["Computer Science"],"languages":["eng"],"rights":["Copyright 1993 Zhou, Tom Zhong-Yu"],"rights_urls":[],"identifier_entries":[{"key":"dc:identifier","label":"Identifier","values":["AAI9411834","(UMI)AAI9411834"],"render_values":[{"text":"AAI9411834","href":null,"code":true},{"text":"(UMI)AAI9411834","href":null,"code":true}]}]},"links":{"outbound_url":"http://hdl.handle.net/2142/22284","outbound_label":"Handle","outbound_source":"dc:identifier"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor","label":"Contributor","values":["Kubitz, William J."]},{"key":"dc:creator","label":"Author","values":["Zhou, Tom Zhong-Yu"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date","label":"Dc Date","values":["2011-05-07T13:34:58Z","10000-01-01","1993"]},{"key":"dc:type","label":"Dc Type","values":["text"]},{"key":"thesis:degree_discipline","label":"Discipline","values":["Computer Science"]},{"key":"thesis:degree_level","label":"Degree Level","values":["Dissertation"]},{"key":"thesis:degree_name","label":"Degree Name","values":["Ph.D."]},{"key":"thesis:institution_name","label":"Thesis Institution Name","values":["University of Illinois at Urbana-Champaign"]}]},{"id":"subjects_keywords","label":"Subjects and Keywords","entries":[{"key":"dc:subject","label":"Dc Subject","values":["Computer Science"]}]},{"id":"language_rights","label":"Language and Rights","entries":[{"key":"dc:language","label":"Dc Language","values":["eng"]},{"key":"dc:rights","label":"Dc Rights","values":["Copyright 1993 Zhou, Tom Zhong-Yu"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier","label":"Identifier","values":["AAI9411834","(UMI)AAI9411834","http://hdl.handle.net/2142/22284"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description","label":"Description","values":["User interface (UI) software reuse requires separating the reusable UI elements from the elements that constitute the application semantics. A classic issue in user interface research is how to couple these two groups of elements effectively. This issue is particularly conspicuous when 3D applications are concerned. In our attempt to build a UI support system for 3D applications, we use a software layer called the application exposure (AE) for the coupling. The AE layer consists of two portions. The operation portion allows operations defined on application objects to be invoked from within the user interface various fashions. The representation portion exposes to the UI side the states of the application objects engaged in user interaction. This portion of the exposure allows the user to closely monitor the application objects that undergo interactive modification. The AE contributes to increased reusability in two major ways. First, on the application side, we feel that writing the methods that generate the exposure is easier than learning the internal construction of a UI framework and building subclasses from it. Moreover, with the exposure, rather than subclassing, as the coupling mechanism, it appears to us that the UI part imposes far less on the application part. Second, on the user interface side, the application exposure isolates the UI components from the particularities that exist across various application objects. As such, these components can be built to fulfill the desired UI functions rather than to cater to the particular application objects. The UI components so built are likely to be more reusable. We use two other abstractions, namely that of mediator and activator, to encapsulate such highly reusable UI components.","Made available in DSpace on 2011-05-07T13:34:58Z (GMT). No. of bitstreams: 2 license.txt: 4922 bytes, checksum: 910b249b4beec47e7ab768910c8f966f (MD5) 9411834.pdf: 5245909 bytes, checksum: daf94e3833051f4b34973a52be152a32 (MD5) Previous issue date: 1993","Item marked as restricted to the 'UIUC Users [automated]' Group (id=2) by Howard Ding (hding2@illinois.edu) on 2011-05-07T14:56:34Z Item is restricted indefinitely.","Restriction data tranferred 2014-07-01T11:26:27-05:00 Original Data Group with Access UIUC Users [automated] Release Date: none Reason: ETDs are only available to UIUC Users without author permission","ETDs are only available to UIUC Users without author permission","U of I Only"]},{"key":"dc:title","label":"Title","values":["Application-independent user interface design using an application exposure"]}]}],"canonical_facts":{"dc:contributor":["Kubitz, William J."],"dc:creator":["Zhou, Tom Zhong-Yu"],"dc:date":["2011-05-07T13:34:58Z","10000-01-01","1993"],"dc:description":["User interface (UI) software reuse requires separating the reusable UI elements from the elements that constitute the application semantics. A classic issue in user interface research is how to couple these two groups of elements effectively. This issue is particularly conspicuous when 3D applications are concerned. In our attempt to build a UI support system for 3D applications, we use a software layer called the application exposure (AE) for the coupling. The AE layer consists of two portions. The operation portion allows operations defined on application objects to be invoked from within the user interface various fashions. The representation portion exposes to the UI side the states of the application objects engaged in user interaction. This portion of the exposure allows the user to closely monitor the application objects that undergo interactive modification. The AE contributes to increased reusability in two major ways. First, on the application side, we feel that writing the methods that generate the exposure is easier than learning the internal construction of a UI framework and building subclasses from it. Moreover, with the exposure, rather than subclassing, as the coupling mechanism, it appears to us that the UI part imposes far less on the application part. Second, on the user interface side, the application exposure isolates the UI components from the particularities that exist across various application objects. As such, these components can be built to fulfill the desired UI functions rather than to cater to the particular application objects. The UI components so built are likely to be more reusable. We use two other abstractions, namely that of mediator and activator, to encapsulate such highly reusable UI components.","Made available in DSpace on 2011-05-07T13:34:58Z (GMT). No. of bitstreams: 2 license.txt: 4922 bytes, checksum: 910b249b4beec47e7ab768910c8f966f (MD5) 9411834.pdf: 5245909 bytes, checksum: daf94e3833051f4b34973a52be152a32 (MD5) Previous issue date: 1993","Item marked as restricted to the 'UIUC Users [automated]' Group (id=2) by Howard Ding (hding2@illinois.edu) on 2011-05-07T14:56:34Z Item is restricted indefinitely.","Restriction data tranferred 2014-07-01T11:26:27-05:00 Original Data Group with Access UIUC Users [automated] Release Date: none Reason: ETDs are only available to UIUC Users without author permission","ETDs are only available to UIUC Users without author permission","U of I Only"],"dc:identifier":["AAI9411834","(UMI)AAI9411834","http://hdl.handle.net/2142/22284"],"dc:language":["eng"],"dc:rights":["Copyright 1993 Zhou, Tom Zhong-Yu"],"dc:subject":["Computer Science"],"dc:title":["Application-independent user interface design using an application exposure"],"dc:type":["text"],"thesis:degree_discipline":["Computer Science"],"thesis:degree_level":["Dissertation"],"thesis:degree_name":["Ph.D."],"thesis:institution_name":["University of Illinois at Urbana-Champaign"]},"updated_at":"2026-07-22T22:25:19Z"}