Lark Fitzgerald wrote:
> NBM's update the underlying code but the palette should not change
> since it was not part of the update. If you want to see components
> that are not already there you need to import the complib. It will
> create a new palette section with all the components.
I don't think this user is talking about complib files. In Woodstock
there are NBMs that can be used to replace some of the built-in
components in NetBeans 5.5 (or later) with newer versions. These NBMs
should update the palette entries. Also, I'd suggest to install locally
and not globally so that the change can easily be backed out by
manipulating the userdir. Installing globally will wipe out the old
module and as I understand it, you cannot go back without reinstalling
Visual Web Pack. See
http://wiki.java.net/bin/view/Javatools/InstallingWoodstockComponentsInNetBeans
for more info.
-Edwin
>
> Hope that helps,
> Lark
>
> Sofiane Cherchalli wrote:
>> Hi All,
>>
>> I compiled and generated the NBM modules : com-sun-rave-webui-jsf-themes
>> -defaulttheme.nbm and com-sun-webui-jsf.nbm.
>>
>> I installed then as global modules but nothing changed in the
>> palette. I can't see Masthead and Mastfooter for instance.
>>
>> Did I do something wrong?
>>
>> Thanks for any help
>>
>> Regards,
>> Sofiane
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_woodstock.dev.java.net
> For additional commands, e-mail: users-help_at_woodstock.dev.java.net
>