Re: [dsdp-ercp-dev] New API for mobile package

[Mark Rogalski <rogalski@xxxxxxxxxx>]

True, Commands can be added by other
components not necessarily under the application's control. For instance,
the eWorkbench adds Commands and an application may wish to query these
Commands and their priority in order to insert the App's Commands within
the priority order. Would your new methods enable that?

Gorkem Ercan <gercan@xxxxxxx>
Sent by: dsdp-ercp-dev-bounces@xxxxxxxxxxx

02/20/2007 04:33 AM

Please respond to
DSDP ercp list <dsdp-ercp-dev@xxxxxxxxxxx>

To	DSDP ercp list <dsdp-ercp-dev@xxxxxxxxxxx>
cc
Subject	Re: [dsdp-ercp-dev] New API for mobile package

The original use case comes from the Commands, on some devices the 
DELETE type commands can be positioned to special clear 'C' key. Which
command actually goes to that key is determined by command type plus 
priority. The need is to set a correct priority relative to existing 
Commands so that the command we desire is actually triggered. In this 
scenario priority is something we can query with existing APIs but it is
not possible to query the command types.

The other changes I am proposed are for API consistency.
--
Gorkem

Mark Rogalski wrote:
>
> Initial thoughts are that I'm not enthused about adding getters for
> parameters that the programmer already supplied. That would be adding
> overhead to every class for something that is probably rarely used.
> And there are other ways for a program to keep this info if needed.
On 
> the other hand, the increase in size is very minimal, so if any one
> can show compelling use case(s), I would be more open to the idea.
>        
>                 Mark
>
>
>
>
> *Gorkem Ercan <gercan@xxxxxxx>*
> Sent by: dsdp-ercp-dev-bounces@xxxxxxxxxxx
>
> 02/19/2007 03:28 PM
> Please respond to
> DSDP ercp list <dsdp-ercp-dev@xxxxxxxxxxx>
>
>
>                  
> To
>                  DSDP
ercp list <dsdp-ercp-dev@xxxxxxxxxxx>
> cc
>                  
> Subject
>                  [dsdp-ercp-dev]
New API for mobile package
>
>
>
>                  
>
>
>
>
>
> I would like to propose an API change for some of the widgets in the
> mobile package.
> Some of the widgets in the mobile package have constructors that take
a
> third style parameter that determines the behavior of the widget.
> Unlike the SWT style, which can be queried with getStyle(), on most
> cases this third parameters can not be queried.
> The affected widgets and styles are
> Command: command type
> ConstrainedText: constraint type
> DateEditor: dateEditor style
> ListBox: layout style
> MobileShell:  status style
> QueryDialog: query type
> SortedList: mode style
> TextExtension: extension style
>
> Useful, not needed? Let's discuss these to be part of the 1.1 API
changes.
>
>
> _______________________________________________
> dsdp-ercp-dev mailing list
> dsdp-ercp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-ercp-dev
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> dsdp-ercp-dev mailing list
> dsdp-ercp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-ercp-dev
>   

_______________________________________________
dsdp-ercp-dev mailing list
dsdp-ercp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-ercp-dev