Issue 294 in openwonderland: Additional Annotations to Make Modules More Modular

0 views
Skip to first unread message

openwon...@googlecode.com

unread,
Sep 4, 2012, 3:08:43 PM9/4/12
to openwonder...@googlegroups.com
Status: New
Owner: pympno...@gmail.com
Labels: Type-Enhancement Component-Client Usability

New issue 294 by pympno...@gmail.com: Additional Annotations to Make
Modules More Modular
http://code.google.com/p/openwonderland/issues/detail?id=294

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()


openwon...@googlecode.com

unread,
Oct 25, 2012, 10:28:31 AM10/25/12
to openwonder...@googlegroups.com
Updates:
Status: WontFix

Comment #1 on issue 294 by pympno...@gmail.com: Additional Annotations to
(No comment was entered for this change.)

Reply all
Reply to author
Forward
0 new messages