Re: Libraries API

Svatopluk Dedic wrote:

> A related question: in project resource system, a resource may be
> decorated by additional content types by independent modules (if they
> e.g. can convert the original type to their own). Is such data reuse
> supported in Libraries ?

You talk too abstract, sorry. I would appreciate an example.

>> Library's lookup content is propagated to project resource
>> ProjectMember's lookup. There is no problem at API leval AFAIK.
>> I see possible problem at UI side, currently library customizer
>> shows all registered volume providers' customizers. Too many
>> volume providers will mess all library customizers.
>> 
> Do you mean that the customizer lists all volume types in one list ?

Yes the library customizer lists them all. It needs to
be adressed if number of unreated types starts to grow.
It's know issue.

>> Do you maen the library lookup? :-)
>> 
> Possibly, what interfaces are supposed to be registered in the Lookup ?

See updated getDescriptor() JavaDoc. I abandoned original idea
that presentation related objects were registered in lookup.
Library lookup should contain only intepretation of the library
content.
 
  Cc.