Selecting operations in an object-oriented user interface
A user can select actions in a user interface. An action can be selected by one or more "views" - for example, a "Print" action may be selected by selecting Print on a File menu, clicking on an icon of a printer, or pressing control-P. An action object defines, for each possible...
Gespeichert in:
Hauptverfasser: | , |
---|---|
Format: | Patent |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | |
---|---|
container_issue | |
container_start_page | |
container_title | |
container_volume | |
creator | RAYMOND TRAINER VANESSA DONNELLY |
description | A user can select actions in a user interface. An action can be selected by one or more "views" - for example, a "Print" action may be selected by selecting Print on a File menu, clicking on an icon of a printer, or pressing control-P. An action object defines, for each possible view representing the action, the attributes required to provide that view, and also an identifier to identify the operation to be invoked when the action is selected. The system identifies when a user selects a view and informs the action object of this. The action object then generates a command to invoke the desired operation. This mechanism achieves single event generation from multiple views, and therefore the application does not need to concern itself with how the user generated the call. The action views query the attributes of the action object directly, all the necessary data is held in one place, and with automatic view concurrency, the application developer no longer has to worry about keeping action views synchronised with each other. |
format | Patent |
fullrecord | <record><control><sourceid>epo_EVB</sourceid><recordid>TN_cdi_epo_espacenet_GB2315139A</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>GB2315139A</sourcerecordid><originalsourceid>FETCH-epo_espacenet_GB2315139A3</originalsourceid><addsrcrecordid>eNrjZLAMTs1JTS7JzEtXyC9ILUosyczPK1bIzFNIzFPIT8oCSunmF2Wm5pWkpiiUFqcWAaVKUovSEpNTeRhY0xJzilN5oTQ3g7yba4izh25qQX58anEBUEleakm8u5ORsaGpobGlozFhFQCekC3y</addsrcrecordid><sourcetype>Open Access Repository</sourcetype><iscdi>true</iscdi><recordtype>patent</recordtype></control><display><type>patent</type><title>Selecting operations in an object-oriented user interface</title><source>esp@cenet</source><creator>RAYMOND TRAINER ; VANESSA DONNELLY</creator><creatorcontrib>RAYMOND TRAINER ; VANESSA DONNELLY</creatorcontrib><description>A user can select actions in a user interface. An action can be selected by one or more "views" - for example, a "Print" action may be selected by selecting Print on a File menu, clicking on an icon of a printer, or pressing control-P. An action object defines, for each possible view representing the action, the attributes required to provide that view, and also an identifier to identify the operation to be invoked when the action is selected. The system identifies when a user selects a view and informs the action object of this. The action object then generates a command to invoke the desired operation. This mechanism achieves single event generation from multiple views, and therefore the application does not need to concern itself with how the user generated the call. The action views query the attributes of the action object directly, all the necessary data is held in one place, and with automatic view concurrency, the application developer no longer has to worry about keeping action views synchronised with each other.</description><edition>6</edition><language>eng</language><subject>CALCULATING ; COMPUTING ; COUNTING ; ELECTRIC DIGITAL DATA PROCESSING ; PHYSICS</subject><creationdate>1998</creationdate><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://worldwide.espacenet.com/publicationDetails/biblio?FT=D&date=19980121&DB=EPODOC&CC=GB&NR=2315139A$$EHTML$$P50$$Gepo$$Hfree_for_read</linktohtml><link.rule.ids>230,308,780,885,25562,76317</link.rule.ids><linktorsrc>$$Uhttps://worldwide.espacenet.com/publicationDetails/biblio?FT=D&date=19980121&DB=EPODOC&CC=GB&NR=2315139A$$EView_record_in_European_Patent_Office$$FView_record_in_$$GEuropean_Patent_Office$$Hfree_for_read</linktorsrc></links><search><creatorcontrib>RAYMOND TRAINER</creatorcontrib><creatorcontrib>VANESSA DONNELLY</creatorcontrib><title>Selecting operations in an object-oriented user interface</title><description>A user can select actions in a user interface. An action can be selected by one or more "views" - for example, a "Print" action may be selected by selecting Print on a File menu, clicking on an icon of a printer, or pressing control-P. An action object defines, for each possible view representing the action, the attributes required to provide that view, and also an identifier to identify the operation to be invoked when the action is selected. The system identifies when a user selects a view and informs the action object of this. The action object then generates a command to invoke the desired operation. This mechanism achieves single event generation from multiple views, and therefore the application does not need to concern itself with how the user generated the call. The action views query the attributes of the action object directly, all the necessary data is held in one place, and with automatic view concurrency, the application developer no longer has to worry about keeping action views synchronised with each other.</description><subject>CALCULATING</subject><subject>COMPUTING</subject><subject>COUNTING</subject><subject>ELECTRIC DIGITAL DATA PROCESSING</subject><subject>PHYSICS</subject><fulltext>true</fulltext><rsrctype>patent</rsrctype><creationdate>1998</creationdate><recordtype>patent</recordtype><sourceid>EVB</sourceid><recordid>eNrjZLAMTs1JTS7JzEtXyC9ILUosyczPK1bIzFNIzFPIT8oCSunmF2Wm5pWkpiiUFqcWAaVKUovSEpNTeRhY0xJzilN5oTQ3g7yba4izh25qQX58anEBUEleakm8u5ORsaGpobGlozFhFQCekC3y</recordid><startdate>19980121</startdate><enddate>19980121</enddate><creator>RAYMOND TRAINER</creator><creator>VANESSA DONNELLY</creator><scope>EVB</scope></search><sort><creationdate>19980121</creationdate><title>Selecting operations in an object-oriented user interface</title><author>RAYMOND TRAINER ; VANESSA DONNELLY</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-epo_espacenet_GB2315139A3</frbrgroupid><rsrctype>patents</rsrctype><prefilter>patents</prefilter><language>eng</language><creationdate>1998</creationdate><topic>CALCULATING</topic><topic>COMPUTING</topic><topic>COUNTING</topic><topic>ELECTRIC DIGITAL DATA PROCESSING</topic><topic>PHYSICS</topic><toplevel>online_resources</toplevel><creatorcontrib>RAYMOND TRAINER</creatorcontrib><creatorcontrib>VANESSA DONNELLY</creatorcontrib><collection>esp@cenet</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>RAYMOND TRAINER</au><au>VANESSA DONNELLY</au><format>patent</format><genre>patent</genre><ristype>GEN</ristype><title>Selecting operations in an object-oriented user interface</title><date>1998-01-21</date><risdate>1998</risdate><abstract>A user can select actions in a user interface. An action can be selected by one or more "views" - for example, a "Print" action may be selected by selecting Print on a File menu, clicking on an icon of a printer, or pressing control-P. An action object defines, for each possible view representing the action, the attributes required to provide that view, and also an identifier to identify the operation to be invoked when the action is selected. The system identifies when a user selects a view and informs the action object of this. The action object then generates a command to invoke the desired operation. This mechanism achieves single event generation from multiple views, and therefore the application does not need to concern itself with how the user generated the call. The action views query the attributes of the action object directly, all the necessary data is held in one place, and with automatic view concurrency, the application developer no longer has to worry about keeping action views synchronised with each other.</abstract><edition>6</edition><oa>free_for_read</oa></addata></record> |
fulltext | fulltext_linktorsrc |
identifier | |
ispartof | |
issn | |
language | eng |
recordid | cdi_epo_espacenet_GB2315139A |
source | esp@cenet |
subjects | CALCULATING COMPUTING COUNTING ELECTRIC DIGITAL DATA PROCESSING PHYSICS |
title | Selecting operations in an object-oriented user interface |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-14T01%3A46%3A30IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-epo_EVB&rft_val_fmt=info:ofi/fmt:kev:mtx:patent&rft.genre=patent&rft.au=RAYMOND%20TRAINER&rft.date=1998-01-21&rft_id=info:doi/&rft_dat=%3Cepo_EVB%3EGB2315139A%3C/epo_EVB%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rfr_iscdi=true |