Additional Annotations to Make Modules More Modular

[GoogleCodeExporter]

Being able to annotate key pieces of wonderland functionality will allow 
developers to quickly develop faster without having to worry about internal 
boilerplate code.

* @MenuItem - for classes that wish to add a menu item to a particular menu in 
the menu bar
 A proposed SPI might include:
-- getMenuName()
-- getMenuItemName()
-- actionPerformed()
-- getAllowedGroups/getAllowedUsers/getAllowed*

* @HudWindow - for classes that wish to add window to the Head's Up Display
A proposed SPI might include:
-- HUDComponent open()

* @ClientConnection - for classes that wish to initiate a separate connection 
to the server
--- import to note that server-side @ConnectionHandler already exists
A proposed SPI exists in BaseClientConnection

* @JMERenderer - for fields in cell classes that wish to specify a particular 
3D renderer to use.
 An SPI exists as extension of BasicRenderer

* @FlatRenderer - for fields in cell classes that wish to specify a particular 
2D renderer to use.
An SPI exists as extension of CellRenderer

* @TextRenderer - for fields in cell classes that wish to specify a particular 
text-based renderer to use.
 A proposed SPI might include:
-- String draw()/paint()/render()

Original issue reported on code.google.com by pympno...@gmail.com on 4 Sep 2012 at 7:08

[GoogleCodeExporter]

Original comment by pympno...@gmail.com on 25 Oct 2012 at 2:24

• Changed state: WontFix