[Figleaf-developer] Re: current state of Introspector

[<sam...@ma...>]

I think we need to get this sorted properly. With that in mind, I'm going to
write some integration tests for my validation work, check it in and move back
to this - we can pick up the validation/changeset stuff later. The integration
tests can act as a proof of concept so we can come back to it when we have a
better idea as to how a developer will define figleaf applications.

For the introspector this is my overview of how things stand:

1. We have a two interfaces that have to be implemented by an object in order
for it to be useable in figleaf:
-- ClassDescriptor
-- Observable
Which together make Informative
2. If an object implements Informative, no action is taken
3. If an object implements one required interface but not the other, then we
look on the classpath for the other, e.g. it implements ClassDescriptor but not
Observable, then we look for Observable
4. If a required interface cannot be located on the classpath, we create a
default implementation

All of this is hidden behind the existing InformativeFactory code - the changes
will be completelty transparent to your GUI code.

Sound ok?

sam