Re: [platform-swt-dev] Re: API consistency

[Steve Northover <Steve_Northover@xxxxxxxxxx>]

It was an e4 hack and should be a subclass
of Resource.

> the art
of the obvious... I figured that much. 

How could I possibly know that from
your message?

"Laurent M." <totolaricot@xxxxxxx>
Sent by: platform-swt-dev-bounces@xxxxxxxxxxx

07/09/2008 05:34 PM

Please respond to
"Eclipse Platform SWT component developers list."        <platform-swt-dev@xxxxxxxxxxx>

To	platform-swt-dev@xxxxxxxxxxx
cc
Subject	[platform-swt-dev] Re: API consistency

Steve Northover wrote:
> 
> It's part of the e4 prototype and not part of the SWT API.
> 
> 

the art of the obvious... I figured that much. my question was more 
along the lines of some technical rational for not making it a Resource
descendent, which would help me [might I add 'others'?] make better 
choices (read: fitting more closely with your design goals as the father
of SWT) for my swt extensions.


> 
> *"Laurent M." <totolaricot@xxxxxxx>*
> Sent by: platform-swt-dev-bounces@xxxxxxxxxxx
> 
> 07/09/2008 04:59 PM
> Please respond to
> "Eclipse Platform SWT component developers list."  
    
>  <platform-swt-dev@xxxxxxxxxxx>
> 
> 
>                  
> To
>                  platform-swt-dev@xxxxxxxxxxx
> cc
>                  
> Subject
>                  [platform-swt-dev]
API consistency
> 
> 
>                  
> 
> 
> 
> 
> 
> any specific reason for not making org.eclipse.swt.effects.Effect
more
> generic or Resource subclass?
> 
> _______________________________________________
> platform-swt-dev mailing list
> platform-swt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
> 

_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev