Get rid of the @PlaceInstance annotation

[GoogleCodeExporter]

A much better way to do this is to:
1) Ask the user to create an interface for each of its custom places. These 
interfaces should extend Place.
2) Have the user create an implementation class for this custom place 
interface.
3) Have the user bind the interface with the implementation in the gin 
module, and add the corresponding provider function in the ginjector.
4) Have the user mark the proxy as inheriting from its custom place 
interface (instead of place)
5) When generating the custom ProxyPlace, create an instance of the custom 
place implementation using the ginjector. (We will have to look for the 
right method.)
6) In the generated ProxyPlace forward calls to all methods defined in the 
custom Place to the implementation.

use dependency injection (through the ginjector) 

Original issue reported on code.google.com by philippe.beaudoin on 1 Apr 2010 at 6:35

[GoogleCodeExporter]

Bumping up, preparing for release 0.2.

Original comment by philippe.beaudoin on 13 May 2010 at 9:49

• Added labels: Milestone-V1.0-3
• Removed labels: Milestone-V1.0-2

[GoogleCodeExporter]

This is now handled by Issue 101.

Original comment by philippe.beaudoin on 21 Jun 2010 at 5:18

• Changed state: WontFix
• Added labels: ****
• Removed labels: ****