Re: Re: Incompatible change in the Java Module

Tomas Zezula napsal(a):
> On Fri, 2003-08-22 at 16:22, Svata Dedic wrote:
> 
>>Tomas Zezula napsal(a):
>>
>>>Hi all,
>>>
>>>If your module adds looks into the srcmodel composite looks you have to
>>>move them into the folder Looks/Composites/org-openide-src/ on the
>>>layer.
>>
>>It seems then that all looks that make sense only when a project context 
>>is present have to check for getLookup().lookup(ProjectMember.class) != 
>>null in each their operation, correct ?
>>
>>-Svata
> 
> Yes, the ProjectMember is added to the Look's Lookup only if the Look
> displays Element which has a file representation in the project.
> Otherwise the Lookup.lookup (PM.class) returns null.
> But this behavior is the same as before change.

What I meant is that all project-aware looks must perform 
lookup(ProjectMember.class) != null testing. So if there's a Look that 
makes no sense without project, it must do such test in all its methods 
that produce output.
As formerly the Looks registry was in the project's nature, Looks 
registered in there could safely assume there is a project context.

For that it seemed much better to have two registries for Looks, one 
basic for the bare data type, and a registry built on top of the base 
one, which is used only when there's a project context hanging around.
I wanted to make sure that I correctly understand the new requirement 
for src hierarchy looks - to check for ProjectMember in all overriden 
methods.

-Svata