Re: [platform-swt-dev] No interfaces in SWT?

[David_Whiteman@xxxxxxx]

Someone correct me if I'm wrong, but aren't all methods marked "public" considered API?  And can't the public methods that appear in the JavaDoc serve as the "API Guide"?

David
--
David Whiteman
OTI Raleigh
david_whiteman@xxxxxxx

Greg Brown <gkb71@xxxxxxxxxxxx> Sent by: platform-swt-dev-admin@xxxxxxxxxxx 02/26/2002 10:05 AM Please respond to platform-swt-dev

To:        platform-swt-dev@xxxxxxxxxxx         cc:                 Subject:        [platform-swt-dev] No interfaces in SWT?

Hi all-

I have a question about the design of the SWT API: There does not appear 
to be any set of standard interfaces that SWT classes are required to 
implement. For example, the org.eclipse.swt.widgets.Button class does 
not implement any interface that dictates what methods a Button should 
have - it just extends Control. How does an SWT developer, either 
working on an SWT application or porting the SWT to a new platform, know 
which classes and methods should be available to applications on all 
platforms and which are implementation-specific? An API guide would be 
helpful, but is not as reliable as ensuring that a class implements an 
interface. What is the design rationale for not using interfaces? Am I 
missing something?

If there is an API guide, could someone please point me to it? Thanks!

Greg

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