GB2480646A

GB2480646A - Relinquishing screen space for another application

Info

Publication number: GB2480646A
Application number: GB1008791A
Authority: GB
Inventors: Martin Yagi
Original assignee: NEC Casio Mobile Communications Ltd
Current assignee: NEC Casio Mobile Communications Ltd
Priority date: 2010-05-26
Filing date: 2010-05-26
Publication date: 2011-11-30
Also published as: GB201008791D0

Abstract

A data processing device has a user interface resource, such as a screen. A first program 26 accesses the resource. The first program indicates 32 that it will relinquish part of the resource, such as an area of the screen, to be used by a second program 30. The first program may also indicate for how long a time it relinquishes the resource. A management program 22, such as a window manager, looks in a database of programs 24 to find a program which can execute using the part of the resource relinquished by the first program. It then executes 34 the program it found using the relinquished resource. If the first program indicates 34 that it needs the resource again, the second program may be terminated 38. The invention is particularly suitable for use in handheld computing devices with small screens, such as mobile phones.

Description

USER INTERFACE MANAGEMENT

The present invention provides for a method of managing use of a User Interface, and to a data processing device arranged to employ the same and also to computer program products and elements for use therein.

A wide variety of data processing devices such as, for example, communications.

organiser, and media-player devices, and combinations thereof, are available and are commonly required to support multiple and simultaneous execution of software and programs such as, for example, various specific applications. Generally the physical limitations of such devices require that the User Interface be shared by the various programs and in view of the possible simultaneous execution of such programs, conflict resolution for access to the User Interface is required. For this purpose, a User Interface management entity is commonly employed to select one of the programs for access to the User Interface dependent upon priority levels/rules set for the competing programs.

However, the management of the User Interface resource and related conflict resolution by means solely of priority levels/rules is found to be disadvantageously inflexible and complex. Such disadvantages and limitations are particularly evident when a wide variety of programs is available for execution on the data processing device and wherein some of which might have been downloaded, or otherwise have originated, from third parties.

The present invention seeks to provide for a method 01 managing use of a User Interface, and to related data processing devices and computer program products and elements having advantages over known such methods, devices and program products/elements.

In particular, the present invention seeks to provide for such methods, devices and programs/elements which can be used in place of, or complementary to, known User Interface management arrangements.

It should be appreciated that the present invention can be employed in relation to any appropriate data processing devices employing a User Interface resource and, one particular example of such devices, comprises a mobile communications User Equipment (UE) such as a mobile phone handset.

Such handsets comprise data processing devices that are arranged to offer a wide variety of ftinctions beyond simple telephony such as organising and media-playing functionality. Use of the handset therefore no longer comprises a short goal-focussed activity such as simply starting and ending a telephone call when required. Since such handsets can support a wide variety of program applications, some of which might be required for relatively long periods of time, there might be frequent requirements for simultaneous use of a plurality of applications requiring access to the User Interface resource.

Even though such handsets can also offer a variety of User Interface resources such as for example graphical, textual, auditory, vibratory and haptics feedback resources, conflicts for use of such resources can readily arise when, for example. a user might be browsing the Internet and an incoming call is received.

As noted above, management of such shared User Interface resources is currently achieved by means of reference to priority levels/rules, and also through controlled termination of particular applications when not required.

Current mobile phone handsets also comprise examples of data processing devices that are likely to access and download a wide variety of programs/applications from third parties. This further increases the requirement for managed access to the shared User Interface resource.

According to a first aspect of the present invention there is provided a data processing device including a User Interface resource and having a first program arranged when executing to access the User Interface resource, and to provide an indication of the degree to which the said first program will relinquish use of at least part of the said User Interface resource for use by a second program.

The invention proves advantageous insofar as an alternative, or complementary, arrangement can be provided for allowing the managed sharing of User Interface resources in a readily flexible and simple manner which need not be either wholly. or partly, dependent upon priority levels/rules.

The device and/or the said first program can be arranged simply and advantageously to indicate how much of the User Interface resource it wishes to relinquish. Although as an alternative, and more indirect indication, the device and/or said first program could indicate how much, if at all, of the resource it wishes to retain access to. In any case, that portion of the resource that is no longer required by the first program is liberated for access by a second program having requirements that match the available resource.

Of course, some form of further selectability can be provided should a plurality of second programs be available for use with the relinquished User Interface resource.

Advantageously, the data processing device includes a resource control/management entity and which can be arranged to receive notification of the degree to which the primary program will relinquish use of the User Interface resource.

Examples of such a control/management entity comprise a window manager and/or audio manager etc. Within the scope of the present invention, the degree to which the first program will relinquish use of the said User Interface resource can comprise any appropriate percentage of the resource, or indeed an absolute amount thereof, and/or a time period for which exclusive access to the resource will not be required or will be required on reduced basis.

Yet further, the control/management entity can be arranged to select between one or more possible second programs and which, dependent upon the degree to which the primary program element relinquishes access to the User Interface resource, can include a series application of the said plurality of second programs.

Advantageously, the control/management entity is arranged to access stored data relating to each of the second programs as part of the selection process.

As a further advantage, the second program can be associated with metadata serving to identify requirements of the said second program.

Advantageously, the aforesaid elements of metadata can be added to the program package information.

Yet further, the identity of the program as a second program can also be included within the said metadata.

Still further, the device can also be arranged to confirm for the second program the degree to which the first program relinquishes use of the User Interface resource such that execution of the second program can proceed in an appropriate manner on the basis of the available relinquished" resources.

As of course should be appreciated, the said first and second programs, which can comprise, primary and secondary programs, can each comprise different program applications for the device and the said device itself can comprise a mobile radio communications device.

It should be appreciated that, in different circumstances, one and the same program can comprise either the said first, or the said second, programs of the invention as defined above.

The said User Interface resource can comprise any one or more of a screen, keypad and/or audio interface.

Further, the second program can comprise, or operate as, a generally short-lived and therefore temporary, program.

Further, the device can be arranged such that use of the second program of the User Interface resource can be cancelled upon request initiated by way of the first program.

If the said first program is allotted a higher priority than the second program, such a hierarchy can be readily employed to enforce the said cancellation.

With regard to the possible further cancellation scenarios relating to the second program's access to the resource, the invention can allow for the provision of a time-frame specified to allow the second application to perform, for example, a specific final action. The control entity can monitor for such final action and if it is determined that this final action has not occurred within the specified time-frame, the fbrced cancellation of access by the second program to the resource can be initiated. Yet further, details of, or the identity of, such second programs not executing within the allotted time-frame can be retained so as to control whether, or how, that particular second application is permitted future access to the resource.

Further, the device can be arranged such that the relinquishing of at least partial use of the User Interface resource for use by the second program can include enablement of the actual execution of the second program.

According to another aspect of the present invention there is provided a method of User Interface resource management in a data processing device and wherein a first

D

program, when executing, uses the User Interface resource and further including the step of providing an indication of the degree to which the first program will relinquish use of the said User Interface resource for use by a second program.

As noted above the invention proves advantageous insofar as an alternative, or complementary, method is provided for allowing the managed sharing of User Interface resources in a readily flexible and simple manner which is not necessarily either wholly, or partly, dependent upon priority levels/rules.

An indication of how much the primary program will relinquish access to the resource, or as a possible alternative how much the first program wishes to retain access to the User Interface resource can be provided. The unused portion of the resource is then available for access by a second program having requirements that match the available resource.

The indication of the degree to which the first program will relinquish use of the User Interface resource can be provided either as an indication of the remaining requirement of the first program, or an indication of the actual portion of the resource not currently required. As above, some form of further selectability can be provided should a plurality of second programs be available for use with the relinquished User Interface resource.

The method can further provide notification of the degree to which the first program will relinquish use of the User Interface resource to a resource control/management entity Within the scope of the method of the present invention, the degree to which the tirst program element will relinquish use of the said User Interface resource can comprise any appropriate percentage of the resource, or indeed an absolute amount thereo1 and/or a time period and/or magnitude of a time period for which access to the resource will not be required or will be required on a reduced basis.

Advantageously, a control/management entity can be arranged to provide a step of selecting between one or more possible second programs and which, dependent upon the degree to which the first program element relinquishes access to the User Interface resource, can include controlling a series application of each of the said plurality of second programs.

The said selection process can include the step of a control/management entity accessing stored data relating to each of the second programs.

The step of selecting can include searching metadata that can be found in the program package information, and which serves to identify requirements of the said second program.

Of course, the actual identity of the program as a second program can also be found within the said metadata.

The method can further include the step of indicating, for execution of the second program, the degree to which the first program will relinquish use of the User Interface resource such that execution of the second program can proceed having regard to the available "relinquished" resources and preferably optimizing such relinquished resources.

As noted the second program can comprise, or operate as, a generally short-lived, and therefore temporary, program, also referred to herein as a "Casual Application", and the method can include the step of terminating use by the second program of the User Interface resource responsive to a request initiated by way of the first program.

The method can also include enablement of the actual execution of the first program upon relinquishing of use of the User Interface resource for use by the second program.

Yet further, the invention can provide for a first program element which, when executing in a data processing device, is arranged to access a User Interface resource, and further can include an indication of the degree to which it will relinquish use of the said User Interface resource for use by a second program element.

Preferably, the aforesaid first program element is arranged for use within a data processing device and/or method as outlined above.

Still further, the invention can provide for a second program element arranged to execute in a data processing device and accessing a User Interface resource also accessed by a first program element, the second program element being arranged to access the User Interface resource responsive to at least partial relinquishing of the said resource by the first program element and to execute subject to the relinquished resource.

Within the context of the present invention, it should be appreciated the aforementioned first program need not be executing exclusively within the device. That is, the said first program could comprise either of two simultaneously executing programs each only accessing their respective portion of the said resource but wherein at least one is arranged to relinquish some of the said respective portion for use by a second program. In genera!, it is considered that the said first program will be executed by user action, system bootup, or in response to a specific event.

The second program e!ement can be arranged for use within a device and/or method as outlined above.

The present invention can also provide for a computer program product or computer readable medium comprising instructions for carrying out a method as outlined above.

The invention is described further hereinafter, by way of example only, with reference to the accompanying drawings in which: Fig. 1 is a schematic representation of a mobile phone handset according to an embodiment of the present invention; Fig. 2 is a schematic diagram illustrating operation of the handset of Fig. 1 in accordance with an embodiment of the present invention; Fig. 3 is a signalling timing diagram for signalling arising in accordance with an embodiment of the present invention; and Fig. 4 is a flow diagram serving to illustrate User Interface management according to an embodiment of the present invention.

Turning first to Fig. 1 there is provided an illustration of a mobile phone handset 10 including a standard communications interface comprising an antenna 12 and transceiver functionality 14 and along with processing 16 and storage 1 8 functionality.

Also provided is a User Interface resource 20 for providing a user interface by way of a touch-screen (not shown) incorporated within the handset 10.

In accordance with this particular embodiment of the present invention, the processing functionality 16 includes a User Interface controller 22 arranged for determining which of a potential plurality of second applications, hereinafter referred to as secondary or casual applications can have (temporary) access to the User Interface resource 20 and having regard to the resource-requirement relinquished by a first application hereinafter referred to as a primary application.

Having identified the degree to which the primary application will relinquish use of the User Interface resource 20, the User Interface control entity 22 is arranged to access a database arrangement 24 within the storage functionality 18. In this embodiment, metadata is stored in the database arrangement 24 is stored relating to each of the potential secondary applications. Such data serves to identify which of those secondary applications has requirements that match, or fall within the scope of the relinquished, and therefore now available, portion of the User Interface resource.

As will be appreciated from the introductory passages of this application, and for the further discussion below, the "resource" can comprise any appropriate characteristic of the User Interface such as a period of time for availability and/or a percentage of the total area of the touch screen (not shown in the drawings), available for the secondary application.

The User Interface control entity 22 within the processing functionality 16 can therefore provide for the managed control of access to the User Interface resource 20 between two or more applications in an advantageously adaptable and simple manner and without necessarily requiring use of priority levels/rules.

While a wide variety of potentially competing applications may be available, an illustrative example comprises a primary weather-monitoring application which can be arranged to indicate that part of the touch-screen area currently employed can in fact he relinquished for use by a secondary application such as, for example, an advertising application. The advertising application can then be developed independently of the weather application and so can be simultaneously presented to the user within that part of the touch screen that has been relinquished by the primary application. The User Interface control entity 22 can readily match the requirement of a secondary application to the amount of the resource "relinquished" by the primary application so as to avoid any actual conflict between the respective applications. That is, when an application is willing to relinquish some of its resources, it can indicate the resource information, such as screen area coordinates, vibrate requirement and likely timeframe etc., to the User Interface control entity 22 which, as noted, can comprise a window manager, audio manager etc. The control entity then selects a suitable application for execution using information from the applications database 24 containing data such as the minimum screen size required and/or minimum activity time required by the said secondary application. Such secondary applications are generally expected to be short-lived and so control is returned to the primary application either upon completion of execution of the secondary application, or on demand from the primary application.

Turning now to Fig. 2, there is provided an operational diagram illustrating use of the handset device 10 of Fig. I in accordance with an embodiment of the present invention.

In the illustration, the handset 10 is executing an application such as a music player 26 which, at STEP I provides an indication that simultaneous use of the secondary application can be tolerated/permitted and further confirms the maximum properties such as screen area etc., available to the secondary program. Such data is delivered to the User Interface control entity 22 which, by way of the secondary application selection functionality 28, accesses at STEP 2 the secondary application database 24 which stores at least an indication of the relevant properties/requirements of each of the secondary applications.

A secondary application having requirements which match or at least do not exceed those made available by the primary application is then selected and invoked by way of STEP 3. The secondary application which, in the aforesaid example, can comprise the display of a particular advertisement then executes at 30.

It should of course be appreciated that the invention is in no way limited to the nature of the secondary applications that might be simultaneously employed along with the primary application in accordance with the present invention.

As non-limiting examples, and in addition to the advertisement noted, the secondary application could comprise any one or more of an upgrade manager, mind-training mini games, non-scheduled reminders, incoming messages, handset status changes (rather than just updating the icon in the status tray), and RSS feed changes etc. The illustrated embodiment of the present invention takes account of the fact that applications that are installed on mobile devices in particular, and especially downloaded third-party applications, typically include related metadata. This can include data such as application name, version number and/or date of creation etc. The invention advantageously allows for such metadata to be extended to include information relating to the functional requirements of the operation as a secondary application and, indeed, information serving to indicate whether or not the application would in fact qualify as a "suitable secondary application" i.e. an application having a relatively short lifespan and not exceeding the "relinquished" resources indicated as being available. Also, requirements such as minimum display size, whether audio is required, whether vibratory action is required and the minimum execution/display time required etc., can also be provided within this data. Further, such metadata information can be stored in such a manner that it is readily accessible by way of the selection functionality 28 of the User Interface control entity 22.

It should be appreciated that the implementation of the messaging originating from the primary application will depend upon the operating system, window system and Window Manager for example. That is, with an X Window-based solution, a new Window Manager Hints Protocol (http://standards. freedesktop. org\wn-spec\wn-spec-I.4.html) message could be employed.

Of course, it should be appreciated that the primary application may at some stage again require sole access to the User Interface resource and so can, if required, revoke the previous relinquishing of the portion of the User Interface resource.

Such a possibility is illustrated and discussed further below with reference to Fig. 3.

Fig. 3 comprises a signalling diagram relating to signalling arising between a primary application, a User Interface control entity and a secondary application such as those previously discussed in relation to Figs. I and 2.

In Fig. 3, the primary application 26 initiates an initial signalling message 32 indicating a portion of the required User interface resource to be relinquished and which can comprise an indication of the time, screen area etc., that is relinquished. This signalling message 32 is delivered to the User Interface control entity 22 which, in this embodiment, comprises a Window Manager. The Window Manager 22 interrogates the database 24 seeking to identify which one or more of a plurality of possible secondary applications has requirements that fall within the bounds set by the relinquished portion as indicated by the data within the message 32.

Having identified a secondary application, the Window Manager 22 then issues a signalling message 34 invoking the identified secondary application 30 which then starts to run, accessing the available portion of the User Interface resource until such time as the running of the secondary application is complete, or a further message 36 is delivered from the primary application 26 to the Window Manager 22 revoking the availability of the portion of the User Interface resource. Should such a revocation signal 36 be received by the Window Manager 22, and prior to completion of execution of the secondary application 30, a quit signal 38 is delivered from the Window Manager 22 to the secondary application 30.

It should of course be appreciated that Fig. 3 provides an indication olvarious signalling stages that need not necessarily arise. For example, signalling messages 34 will not arise if the Window Manager 22 was not able to select a suitable secondary application when interrogating the database 24. Further, the quit signal 38 need not arise if the previously selected secondary application has already completed and no further follow-up secondary application has been scheduled by the Window Manager 22.

Turning lastly to Fig. 4 there is provided a flow diagram as a further illustration of an embodiment of the present invention. I,., L)

The procedure indicated commences at 40 with the identification of a primary application which also indicates that it could relinquish at least a portion of its requirements for the User Interface resource. In one example, in which the shared resource is to comprise a portion of a device screen, the signal from the first application could, for example, contain information such as the identity of the primary program such as in the form of application name application ID and/or process name: time frame of the availability for the secondary application; height of screen area to be made available in pixels; width of screen area to be made available in pixels: and the X and Y location of the screen area to be made available which is typically in the leftmost.

and the rightmost pixel respectively. The particular characteristics of the properties of the User Interface resource relinquished are identified at 42 and saved at step 44 for future reference. The saving of such characteristics can prove important and if the secondary application is particularly shortlived such that a further "secondary application" might execute within the given constraints. In further detail, these signal parameters can be coded, for example using XML for subsequent extraction/decoding for analysis. Such analysis can comprise determining whether or not the application is currently visible/raised such that the signal could be ignored; or whether or not the screen area released is insufficient for any secondary applications requirements in which case the signal can again be ignored.

If, as noted, an initial secondary program (i.e. casual application) is relatively short lived such that a further secondary program could be selected, then any previously saved properties of the primary application such as timestamp, time duration, height, width and root values are readily available to assist with such further selection.

At step 46, the database 24 storing the relevant properties of each of the secondary programs is interrogated so as to identify the existence of any suitable secondary applications and which have requirements falling within the constraints set by the primary application. For example, a secondary program can be determined as "suitable" on the basis of a comparison of elements such as minimum time frame available and related height/width parameters to assess whether the secondary application exhibits requirements falling within those of the relinquished portion of the resource.

At step 48, an appropriate secondary application is selected although it should be appreciated that, if a plurality of appropriate secondary applications exist, selection policies as stored within a further database 50 can be accessed in order to discriminate between the available secondary applications. If, at step 46 it is determined that there is a choice of possible secondary applications, the application selection may be determined by one, or possibly a combination, of a random selection; selection based on most frequently, or most recently, executed; related revenue generation for example due to advertisement display; or level of importance it should be appreciated that this list illustrates only some of the possible examples and is non-limiting.

Finally, at 52 it is determined whether or not a suitable secondary application is found.

If it is, then at step 54 the secondary application is invoked, If not, the procedure simply terminates at step 56 with the primary application continuing on its own. As noted, in relation to step 54, data related to the selected application may be modified and stored as required. Merely as examples, such data can comprise the last time an application executed and/or the number of times it has executed and such information can be employed in subsequent selection procedures -for example of an algorithm arrange to select the most-recently executed Application or otherwise.

As an alternative to employing selection policies such as those stored in the database 50, the selection of one of a plurality of secondary applications can simply comprise a random act if required.

Also, at the time of seeking to invoke the selected secondary application at step 54, the constraints set by the primary application are delivered for control of the secondary application, for example as command-line arguments, so as to enable the secondary application to execute in an appropriate manner to the constraints, such as time and size constraints, set by the primary application. The actual manner of execution of the

IS

secondary application then proceeds in the most appropriate manner having regard to the available share of the resources of the User Interface.

With regard to steps 60 and 62, it should be appreciated that these can be invoked if a particular second programme completes well within the timeframe of availability allotted to it. The control entity can then select a further second, or socalled casual, application for execution with access to the relinquished portion of the resource. Also, properties of the second application, such as total execution time, can be reviewed and updated at this stage so as to ensure the ongoing accuracy of the data stored.

As should therefore be appreciated, three particular aspects are embodied within the present invention. These serve to provide for an advantageous solution to the problems faced by the present invention and which can offer an enhancement to display systems allowing multiplication of overlapping Windows such as, for example, X Window based systems. That is, the invention advantageously employs messaging between relevant entities, particularly from the initiating primary application in order to allow for cooperative display management. Also, the invention can provide for an enhanced Window Manager serving to allow for an enhanced application selection and function mechanism and also secondary applications that are able to run on a short time basis, and within certain constraints utilizing the relinquished resources. These can be efficiently and advantageously employed and, as required, simply and reliably identified by means of metadata included with the application package information.

The invention therefore proves advantageous in improving the User Interface and user experience of simultaneous applications through the relinquishing of unnecessary resources that can be readily employed within the aforementioned simultaneous operation.

While it should be appreciated that the present invention can be adapted for use in relation to any appropriate device employing a User Interface, it is found that the invention is particularly advantageous when used in relation to devices employing User Interfaces exhibiting physical limitations such as devices with rclatively small screens, or limited input mechanisms such as keypads etc.

Claims

CLAIMS: 1. A data processing device including a User Interface resource and having a first program arranged, when executing, to access the User Interface resource, and to provide an indication of the degree to which the first program will relinquish use of the said User Interface resource for use by a second program.
2. A data processing device as claimed in Claim 1 and including a resource control/management entity arranged to receive notification of the degree to which the first program will relinquish use of the User Interface resource.
3. A data processing device as claimed in Claim 2 wherein the control/management entity is arranged to access stored data relating to the second program as part of the process or enabling use of the said resource by the second program.
4. A data processing device as claimed in Claim 2 or 3, wherein the said control/management entity comprises a window manager and/or audio manager.
5. A data processing device as claimed in Claim I, 2, 3 or 4, wherein the degree to which the first program will relinquish use of the said User Interface resource comprises any appropriate percentage of the resource, or an absolute amount thereof, and/or a time period for which access to the resource will not be required or will be required on a reduced basis.
6. A data processing device as claimed in any one or more of the preceding claims and arranged to select between one or more possible second programs.
7. A data processing device as claimed in any one or more of the preceding claims wherein the second program is associated with metadata serving to identify requirements of the said second program, and optionally wherein a control/management entity is arranged to access a database of such metadata.
8. A data processing device as claimed in any one or more of the preceding claims and arranged to confirm for the second program the degree to which the first program relinquishes use of the User Interface resource such that execution of the second program can proceed having regard to the available resource.
9. A data processing device as claimed in any one or more of the preceding claims and comprising a mobile radio communications device.
10. A data processing device as claimed in any one or more of the preceding claims wherein the said User Interface resource comprises any one or more of a screen, keypad, visual, tactile and vibratory and/or audio interface.
ii. A method of User Interface resource management in a data processing device and wherein a first program, when executing, accesses the User Interface resource and further including the step of providing an indication of the degree to which the first program will relinquish use of the said User Interface resource for use by a second program.
12. A method as claimed in Claim 11 and including the step of indicating how much, if at all, the first program requires access to the User Interface resource to assist with relinquishing the remainder of the resource for access by a second program having requirements that can be met by the available resource.
13. A method as claimed in Claim ii or 12, and including the step of selecting between a plurality of second programs available for use with the relinquished User Interface resource.
14. A method as claimed in Claim ii, 12 or 13, and including the step of providing notification of the degree to which the first program will relinquish use of the User Interface resource to resource control/management entity.
15. A method as claimed in Claim 14 and including selecting at the control/management entity between one or more possible second programs and which, dependent upon the degree to which the first program element relinquishes access to the User Interface resource, can include a controlled series execution of each of the said plurality of second programs.
16. A method as claimed in Claim 14 or 15 and including the step of accessing, by way of the control/management entity, stored data relating to each of the second programs as part of the selection process.
17. A method as claimed in Claim 16 and including the step of accessing metadata serving to identify requirements of the said second program.
18. A method as claimed in any one or more of Claims 11 to 17 and including, for assisting execution of the second program, the step of indicating the degree to which the first program will relinquish use of the User Interface resource such that execution of the second program can proceed having regard to the relinquished resources.
19. A method as claimed in any one or more of Claims 11 to 1 8 and including the step of terminating use by the second program of the User Interface resource responsive to a request initiated by way of the first program.
20. A method as claimed in any one or more of Claims 11 to 19, and including the step of enabling execution of the second program with the relinquishing of use of the User Interface resource by the first program.
21. A program element which, when executing in a data processing device, is arranged to access a User Interface resource, and the further including an indication of the degree to which it will relinquish use of the said User Interface resource for use by a second program element.
22. A program element as claimed in Claim 21, and arranged for use within a method as claimed in any one or more of Claims 11 to 20.
23. A second program element arranged to execute in a data processing device and accessing a User Interface resource previously accessed by a first program element, the second program element arranged to access the User Interface resource subject to at least partial relinquishing of the said resource by the first program element and to execute responsive to the relinquished resource.
24. A second program element as claimed in Claims 23 and arranged to execute within control constraints established by the first program element and/or responsive to a cancellation signal established by the first program element.
25. A second program element as claimed in Claim 24 and arranged to suffer subsequent operational limitation responsive to a breach of the control conditions established by the first program element.
26. A second program element as claimed in Claim 23, 24 or 25, and arranged for use in the method of any one or more of Claims 11 to 20.
27. A computer program product or computer readable medium comprising instructions for carrying out a method as claimed in any one or more of Claims 11 to 20.
28. A data processing device substantially as hereinbefore described with reference to, and as illustrated in, the accompanying drawings. 2!29. A method of User Interface resource management substantially as hereinbefore described with reference to, and as illustrated in, the accompanying drawings.30. A program element substantially as hereinbefore described with reference to the accompanying drawings.