Re: XInfo vs Spice metadata

On Mon, 2003-10-27 at 21:13, peter royal wrote:
> 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 

I would definitely like to do that too. In the printing/pub industry FTP
is widely used (don't ask me why) and I would like to use the FTP server
in the incubator without changing the sources. I already have to get it
running in plexus but I would like to use it as is.

Is there anything about the FTP server that would prevent it from being
run as a component in Plexus as long as the Loom lifecycle was obeyed?

> (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
> 
> _______________________________________________
> jcontainer-interest mailing list
> jcontainer-interest-81qHHgoATdGxIXFVlbCvtR2eb7JE58TQ@public.gmane.org
> http://lists.codehaus.org/mailman/listinfo/jcontainer-interest
-- 
jvz.

Jason van Zyl
[email protected]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society