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 167508 - Project properties for cnd.
Summary: Project properties for cnd.
Status: NEW
Alias: None
Product: cnd
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@cnd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-23 08:23 UTC by Thomas Preisler
Modified: 2014-04-14 14:31 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Preisler 2009-06-23 08:23:37 UTC
All,

We are trying to work through some additions we need under project options. There are a few questions and thoughts we would like to share and hopefully get feedback.

 

We are currently creating our projects using the cnd Project maker.

In our compilers we have additional options and features which extend what the current cnd projects can manage. We also do not provide a Fortran compiler.

 

Is it possible to remove some of the property nodes based on a project type? For example a generic C project or an embedded project. The issue here is we use the cnd to create our projects.

 

 

Is it possible to change the sheets based on the tool type?

 

Change sheet elements
 

Tool Type
 

If we can do this we might be able to customize some of the existing dialogs more easily.

 

 

 

The best solution we would like to go for is this.

We would like to provide settings that are completely data driven. So the sections and field names are populated from the xml file as well as the possible values that they can contain. Even 
interaction between fields would be able to be handled from the data stored in the xml file. There would not be ANY code particular to the section shown below (all of this would be created and its 
operation controlled from a data file):

However I am not sure how this would impact the cnd group and Sun Studio for backward compatibility.

 

 

 

If we do not do the whole dialog then currently we can see us doing this in 2 ways.

   1. Create our own node MPLAB which underneath we have the same build->Compiler, build->Assembler, build->linker as in the generic sections plus specific embedded nodes for environment-
>H/W Tools etc. We could create sheets for these nodes that would be purely data driven and could read xml files of our creation. However I do not like the idea of having 2 build sections at 
different depths.







   2. Another thought would be to extend the personality files and adapt the reader to be able to pass these additional entities. We would then use the section below the current settings to allow 
anyone to add their own specific data driven entries into the sheets.
   3. Would a scroll bar appear if the entries became to large for the sheet?
Comment 1 Thomas Preisler 2009-06-23 08:27:42 UTC
See also http://www.netbeans.org/issues/show_bug.cgi?id=125855