Patterns in eclipse

Three rules of eclipse

plugin may not change screen,task and create objects unless user asks for it

1) User owns the screen

2) User owns the CPU

3) User owns the memory

--> Do not use singleton pattern.Memory allocation never goes away

Building the UI withoug loading plugins

Decoupling using adapters
--> dynamic implementation of an interface
--> class can be adapted to any interface
--> best example is the properties view

4) most of the items are implemented as services
Located,Scoped and Destroyed

5) Separation of concerns
same class should not do a,b,c,d,e
use handlers
6) scalable UI
browse instead of combo
filters instead of presenting a large set of info
always use group data in relevant sections
provide deselect /select all buttons
differentiate and place common buttons appropriately