[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-swt-dev] SWT-Design Decisions

Not to mention, one of the requirements for SWT was that the class
hierarchy could fit on a single PowerPoint slide using a font size Steve
could still see.

-Randy



                                                                           
             Steve Northover                                               
             <Steve_Northover@                                             
             ca.ibm.com>                                                To 
             Sent by:                  "Eclipse Platform SWT component     
             platform-swt-dev-         developers list."                   
             bounces@xxxxxxxxx         <platform-swt-dev@xxxxxxxxxxx>      
             rg                                                         cc 
                                                                           
                                                                   Subject 
             09/27/2006 11:27          Re: [platform-swt-dev] SWT-Design   
             AM                        Decisions                           
                                                                           
                                                                           
             Please respond to                                             
             "Eclipse Platform                                             
               SWT component                                               
             developers list."                                             
             <platform-swt-dev                                             
               @eclipse.org>                                               
                                                                           
                                                                           





Hi Tom,

These questions have been asked before.

1) Interfaces have various advantages and drawbacks.  Defining them for the
purposes of Javadoc is not in keeping with the small side of the toolkit.
What's an "SWT-Binding writer"?
2) There could be abstact classes but that would introduce a layer,
increase the size of the toolkit and make things slower, and possibly
harder to debug and maintain.
3) The idea was to minimize the number of constants in the toolkit.  Read
the Javadoc for class SWT.

Steve

                                                                           
 Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>                                 
 Sent by:                                                                  
 platform-swt-dev-bounces@xxxxxxxxxxx                                   To 
                                                       SWT development     
                                                       <platform-swt-dev@e 
 09/27/2006 05:44 AM                                   clipse.org>         
                                                                        cc 
                                                                           
              Please respond to                                    Subject 
       "Eclipse Platform SWT component                 [platform-swt-dev]  
              developers list."                        SWT-Design          
       <platform-swt-dev@xxxxxxxxxxx>                  Decisions           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           





Hi,

Last night I browsed the SWT-Source and asked myself some questions:

1. Why are there no interface definitions like IWidget, IComposite, ...?
  This would make life of SWT-Binding writers easier to stay in sync
  with the SWT-API, wouldn't it? Another pro is that the javadoc is
  stored in the interface and not duplicated in the real
  implementation as it is now.

2. Why are the no AbstractClasses used to extract platform-independent
  code parts of Widgets?

3. Looking back was it really a good decision to put all constants into
  SWT class?

Thanks for your thoughts.

Tom

--
B e s t S o l u t i o n . a t                        EDV Systemhaus GmbH
------------------------------------------------------------------------
tom schindl    leiter softwareentwicklung/CSE   mobile  ++43 676 3232147
------------------------------------------------------------------------
eduard-bodem-gasse 8/3    A-6020 innsbruck      fax      ++43 512 935833
http://www.bestsolution.at                      phone    ++43 512 935834

_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
(See attached file: signature.asc)
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev

Attachment: signature.asc
Description: Binary data