Re: Java module separations

Sorry for that,
the thing is that after the API split, another split will come.
Java nature will be divided into generic java nature and j2se nature,
the looks are going to be a part of generic java nature, but we haven't
decided yet where the nature should be located, probably in the 
java-projects module.

Tomas

Rochelle Raccah wrote:

>But no one has mentioned which of the new java modules would contain this
>behavior....
>
>Rochelle
>
>Tomas Zezula wrote:
>  
>
>>Rochelle Raccah wrote:
>>
>>    
>>
>>>Thanks, Svata.  Like I said, I'm not up to date on the projects branch.  I
>>>assume there is a Java Look which is extensible?  If so, which of the submodules
>>>will that be?
>>>
>>>Thanks,
>>>Rochelle
>>>
>>>      
>>>
>>Hi Rochelle,
>>you are right, there are looks for JavaDataObject and for all the
>>sourcemodel Elemets (ClassElement, FieldElement, ...).
>> These Looks are composite and allow other modules to easily extend the
>>default look by adding your new look instance file
>>into the context folder of the composite look. Your look can add new
>>properties, actions,  things into Lookup, ...
>>
>>The context folders for these composite looks are defined in the
>>java-nature (java/src/org/netbeans/modules/java/resources/java-nature.xml)
>>
>>Here is an example how to use them (adding look for ClassElement):
>>
>>In your module nature just add:
>>
>><Looks>
>>    <Composites>
>>       <ClassElement>
>>          <file name="myNewLook.instance">
>>                <attr name="instanceCreate"
>>methodvalue="org.netbeans.modules.mymodule.ui.looks.MyLook.create"/>
>>                <attr name="instanceClass"
>>stringvalue="org.netbeans.modules.mymodule.ui.looks.MyLook"/>
>>                <attr name="instanceOf"
>>stringvalue="org.netbeans.api.looks.Look"/>
>>          </file>
>>       </ClassElement>
>>    </Composites>
>></Looks>
>>
>>This will add the o.n.m.mymodule.ui.looks.MyLook into ClassElement's
>>composite look.
>>The base looks will be in the java.jar (the core module), but the API is
>>fully declarative,
>>so you don't need to define a dependency on this module.
>>
>>Tomas
>>
>>    
>>
>>>Svata Dedic wrote:
>>>
>>>
>>>      
>>>
>>>>Rochelle Raccah wrote:
>>>>
>>>>
>>>>        
>>>>
>>>>>I'm not sure if this still exists in projects, but where would the new
>>>>>incarnation of data loader, data object, nodes, etc. be?
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>Ideally, you should not be using DataLoader or DataObjects. Rather use
>>>>other extensibility mechanisms (e.g. ProjectEnvironmentProvider).
>>>>Nodes are already superseded by Looks.
>>>>
>>>>-Svata
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: [email protected]
>>>>For additional commands, e-mail: [email protected]
>>>>
>>>>
>>>>        
>>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: [email protected]
>>>For additional commands, e-mail: [email protected]
>>>
>>>
>>>
>>>      
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [email protected]
>>For additional commands, e-mail: [email protected]
>>    
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>
>  
>