Re: XInfo vs Spice metadata

On Oct 27, 2003, at 9:05 PM, peter-4lf8KW9E9MLMqX/[email protected] wrote:
> Just FYI there exists a copy of a BlockInfoReader in CVS history that 
> reads
> the .xinfo file and generates an equivelent MetaClass ClassDescriptor. 
> I
> started to implement it but could not be bothered finishing the job 
> (which
> is writing unit tests and supporting MXInfo aswell). I didn't think it 
> was
> worth it at the time but you are more than welcome to revive it from 
> the
> history and finish it off.

Ya, I think that is what Ryan is working with.. we were just going to 
do .xinfo, not the MXInfo.. mainly to support existing Avalon 
components out-of-the-box without the need to re-process source (plus, 
I can lobby for the continued inclusion of .xinfo in avalon's CVS since 
it is the LCD wrt metadata at the moment)
-pete