| [platform-swt-dev] SWT-Design 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
Attachment:
signature.asc
Description: OpenPGP digital signature