Re: [Figleaf-developer] Need for a ViewRegistry

[Greg S. <ste...@on...>]

sam...@ma... wrote:

>Quoting Greg Steckman <ste...@on...>:
>
>
>  
>
>>>Well I don't think it can hurt to have this as a seperate class which
>>>      
>>>
>>different
>>    
>>
>>>UI mechanisms can reuse - I'll take your code as a base and write one with
>>>      
>>>
>>full
>>    
>>
>>>test coverage so we can work out any little kinks that might exist.
>>>
>>>
>>>sam
>>>http://www.magpiebrain.com/
>>>      
>>>
>
>  
>
>>I'll break it out. I was just getting started on the tests.
>>
>>Greg
>>    
>>
>
>OK, cool - I'd started a little bit of work on this but it sounds like you've
>got it all in hand. What do we need next?
>
>sam
>http://www.magpiebrain.com/
>
>
>  
>
I haven't had a chance to look at your introspection stuff yet, but now 
it will proxy both superinterfaces of Informative? The next thing might 
be to put the validatable interface back in as a super of Informative. 
The other thing would be to cover the case where a class implements some 
but not all of the superinterfaces of Informaive. For example, I 
implement ClassDescriptor but not Observable. Then have the proxy just 
do its magic for Observable and defer ClassDescriptor calls to the real 
object.

Greg