This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 151722 - Enable/disable project properties categories regarding the type of project
Summary: Enable/disable project properties categories regarding the type of project
Status: NEW
Alias: None
Product: javame
Classification: Unclassified
Component: Build System (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks: 162137
  Show dependency tree
 
Reported: 2008-10-29 14:15 UTC by Radko Najman
Modified: 2012-04-16 12:22 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Radko Najman 2008-10-29 14:16:35 UTC 
Allow to enable/disable the project properties categories regarding the type of project (MIDP, CDC, BD-J).

There are project properties categories which are valid only for some types of projects. For other project types they
should be hidden but it is not possible to do it with the current implementation. Currently they can be enabled/disabled
for all project types only. E.g. obfuscation is not implemented for BD-J projects so Obfuscating category should be
hidden for these projects.
Comment 1 _ tboudreau 2008-11-12 16:21:52 UTC 
According to Petr S. there is some ability to disable functionality already in place and more features just need to be added to the ones this functionality 
supports
Comment 2 _ tboudreau 2008-11-17 23:15:58 UTC 
Petr, if you could fill in what ability to disable functionality you were talking about, that would be a big help. 
Wouldn't be hard to craft something from scratch if necessary.  Just some enum of node names and mask in
project.properties or similar.
Comment 3 Petr Suchomel 2008-11-18 09:46:27 UTC 
Basically, we are talking about project customizer
mobility.project\src\org\netbeans\modules\mobility\project\ui\resources\layer.xml 

    <folder name="Customizer">
        <folder name="org.netbeans.modules.kjava.j2meproject">
            <folder name="general">

The question is, if each project support should say, which categories are valid/visible for its own.
Comment 4 _ tboudreau 2008-12-02 17:33:29 UTC 
Moving target to M2 since we are already in the stabilization phase of M1, but I should be able to attach a patch here soon
Comment 5 _ tboudreau 2009-02-03 14:52:34 UTC 
Well, any preference for the following three possible approaches:
1.  Separate folders for different specifications (i.e. CDC, etc. have their own SFS categories for their customizers)
2.  Some <attr name="excludeFrom" stringvalue="CDC,XYZ"/> on individual elements
3.  Some programmatic accept (String specification) method on the customizer panel factory (worse from performance
perspective but probably simplest to implement)
Comment 6 _ tboudreau 2011-05-26 01:59:26 UTC 
Reassigning a bunch of bugs still assigned to me - I haven't worked for Oracle in almost a year.