Closed GoogleCodeExporter closed 8 years ago
Regarding 1)
Pro dumping:
In its current form the idea is flawed, as there is no simple way to
distinguish and query various objects of the same class. While
getPlugin(Interface.class) works fine for multiple implementations that can be
further identified using capabilities, sub-interfaces (or through suppression),
several instances of the same class are too similar.
Contra dumping
On the other hand, we could introduce some @Identifier(id="x") method /
variable tag. Pluglet authors could it to tag methods that return some value
based on the pluglets status or initialization value. These could then be
queried like
plugletManager.getPluglet(Interface.class, "x", "y")
so that the Pluglet is returned that implements Interface and has an ID label
'x' returning the value 'y'.
Original comment by r.biedert
on 16 Nov 2010 at 10:04
Fixed priority.
Original comment by r.biedert
on 16 Nov 2010 at 6:06
4. Should be dumped. Adds complexity, we don't use it anymore, and has
unresolved problems with complex return types.
Original comment by r.biedert
on 17 Nov 2010 at 11:03
Closing the whole issue. While 1., 3. and 4. appear to be valid, I think that
2. takes lots of time and will not result in the benefits anticipated (e.g.,
simpler flow of code) due to the then necessary inter-plugin dependencies.
Instead, we should focus on clearing up the innards of the .base. package.
Original comment by r.biedert
on 17 Nov 2010 at 11:08
Original issue reported on code.google.com by
r.biedert
on 16 Nov 2010 at 9:41