Re: Re: project conversion questions

Svata Dedic wrote:

>On Thu, 2003-07-31 at 08:23, Tomas Zezula wrote:
>  
>
>>The content of CookieSet or Lookup (which is now preferred) should be
>>described in the documentation.
>>    
>>
>
>If it helps, not only NetBeans has this problem. I am now working with
>Eclipse - and they put implement IAdaptable interface (a subset of
>Lookup.Provider - no change notifications, or multiplicity) on a number
>of classes. One never knows what are all options - and they vary
>depending on what plugins are in the system. This, for example, is the
>doc for IEditorInput.getAdapter() API method:
>"Editor input must implement the IAdaptable interface; extensions are
>managed by the platform's adapter manager."
>
>:-(
>
>The problem is that the range of adapters (cookies) cannot be documented
>in doc of the class that contains getCookie() - it is not known for that
>class (otherwise there should be getters, anyway), they are add-on
>services.
>
>Any idea how to organize documentation, so that you can find what
>cookies are injected by various subsystems to a particular class' Lookup
>?
>  
>
IMO the arch documents could help us here. We can add the arch-question 
like: "Do you extend Lookup of any object -- which object and what do 
you put in its Lookup?". Since the arch questions/answer are in XML and 
the actuall documentation is generated for some product (group of 
modules) it's possible to generate the list of things which are added to 
the Lookup of various objects.

I think there are similar Lookup-related questions in Nb 3.5 arch 
documents, but they deal with global Lookup only (Services folder). This 
should be extended for Lookups on particular objects.

-vita