NetBeans Forums

 FAQFAQ   SearchSearch   MemberlistMemberlist   RegisterRegister   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
  

Your wishes for next release of CND
Goto page 1, 2, 3  Next
 
Post new topic   This topic is locked: you cannot edit posts or make replies.    NetBeans Forums -> C/C++ Users
View previous topic :: View next topic  
Author Message
vladimirvv



Joined: 17 Aug 2008
Posts: 2
Location: St. Petersburg

PostPosted: Tue Jun 15, 2010 6:31 am    Post subject: Your wishes for next release of CND Reply with quote

Dear CND Users,

We are approaching the end of 6.9 development cycle and we hope you will enjoy the new release that will be available soon.

In the same time it is a right moment for CND development team to start planning our next, after 6.9, release. We will be glad to hear from you what is your take on features, enhancements that CND is lacking and which could make your work with CND more productive.

We, CND Team, would like to ask you to review the list of enhancement requests (https://netbeans.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=STARTED&bug_status=REOPENED&bugidtype=include&cf_bug_type=ENHANCEMENT&columnlist=priority%2Cbug_status%2Cvotes%2Cshort_desc&product=cnd) against C/C++/Fortran support and vote for those of them that you feel are important.

You are also very welcome to submit a new request (https://netbeans.org/bugzilla/enter_bug.cgi?product=cnd&cf_bug_type=ENHANCEMENT) if you haven't found anything similar already filed.

Thank you very much for using our product and for your help in moving it forward.
CND Development Team.
Back to top
rmartins



Joined: 16 Jun 2010
Posts: 4

PostPosted: Wed Jun 16, 2010 3:50 pm    Post subject: Reply with quote

Hello to all,
my wishes for the next release focus on speed and usability in a production environment (listed with a decreasing order of importance):
1) Support for incremental+partial parsing (https://netbeans.org/bugzilla/show_bug.cgi?id=187567)

2) Template unresolved identifier (https://netbeans.org/bugzilla/show_bug.cgi?id=158692)

3) Further memory usage reduction & better parsing speed for large projects (https://netbeans.org/bugzilla/show_bug.cgi?id=186765)

4)*xRef* improve performance of xRef repository implementation (https://netbeans.org/bugzilla/show_bug.cgi?id=109495)

Keep up the good work,
Rolando Martins
Back to top
Nikolay Molchanov
Posted via mailing list.





PostPosted: Wed Jun 16, 2010 6:18 pm    Post subject: Your wishes for next release of CND Reply with quote

I would like to support Rolando's requests/wishes. Currently parsing is
a big problem -
it takes too long, and makes the IDE very slow. I think ideally parsing
should be done
on a separate process (another jvm). In this case it would not affect
the IDE at all,
and several projects can be parsed in parallel. Also I think there is a
big room for
performance improvement and memory usage reduction.

Thanks.
Nik

rmartins wrote:
Quote:
Hello to all,
my wishes for the next release focus on speed and usability in a production environment (listed with a decreasing order of importance):
1) Support for incremental+partial parsing (https://netbeans.org/bugzilla/show_bug.cgi?id=187567)

2) Template unresolved identifier (https://netbeans.org/bugzilla/show_bug.cgi?id=158692)

3) Further memory usage reduction & better parsing speed for large projects (https://netbeans.org/bugzilla/show_bug.cgi?id=186765)

4)*xRef* improve performance of xRef repository implementation (https://netbeans.org/bugzilla/show_bug.cgi?id=109495)

Keep up the good work,
Rolando Martins




Back to top
XVilka



Joined: 28 May 2010
Posts: 6
Location: Moscow

PostPosted: Wed Jun 23, 2010 9:35 am    Post subject: Reply with quote

My wishes is:

1) better support of assembler highlites and support for navigating:
show labels, functions, macroses and datas as for C/C++ sources

2) better support of assembler include files (*.inc) and if C/C++ project active handle them as not PHP files, but as ASM inculde files.

3) support for fasm syntax and integration when compiling.
4) when implementing this - please see RadASM as example http://www.oby.ro/rad_asm/

5) if possible - add support for some gui editor
Back to top
Nikolay Molchanov
Posted via mailing list.





PostPosted: Wed Jun 23, 2010 4:29 pm    Post subject: Your wishes for next release of CND Reply with quote

Hello CND team,

I think NB 6.9 is a great step ahead, but I still miss 3 things:

1. "Send To ..." action in context menu for a selected file.
- This action should invoke specified command and pass file name as a
parameter.

2. SCCS support.
- This means at least 4 actions in context menu:
-- Checkout
-- Checkin
-- Diffs (enabled for checked out files)
-- Uncheckout

3. "Terminal" action in context menu.
- This action should open terminal window in selected directory.

Here is some explanation. We use Netbeans IDE or Sun Studio IDE (which
is based on Netbeans)
on Solaris and Linux systems, and sometimes it is necessary to perform
some action with a file (like
run "ls -l" to see its size, timestamp, or to run "chmod ...", or to
open it in a special viewer/editor, ...).
In this case we have to open a terminal window, change directory to the
project directory, and run
these commands, which is somewhat inconvenient, especially navigation to
the project directory.

I understand that SCCS support is a difficult task. I'll be happy if
"Send To .." is implemented, so
I can easy implement SCCS support with a set of scripts.

Thanks.
Nik


Leonid Lenyashin wrote:
Quote:
Dear CND Users,

We are approaching the end of 6.9 development cycle and we hope you
will enjoy the new release that will be available soon.

In the same time it is a right moment for CND development team to
start planning our next, after 6.9, release. We will be glad to hear
from you what is your take on features, enhancements that CND is
lacking and which could make your work with CND more productive.

We, CND Team, would like to ask you to review the list on enhancement
requests against C/C++/Fortran support and vote for those of them that
you feel are important.

List of enhancements:
https://netbeans.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=STARTED&bug_status=REOPENED&bugidtype=include&cf_bug_type=ENHANCEMENT&columnlist=priority%2Cbug_status%2Cvotes%2Cshort_desc&product=cnd


You are also very welcome to submit a new request if you haven't found
anything similar already filed:
https://netbeans.org/bugzilla/enter_bug.cgi?product=cnd&cf_bug_type=ENHANCEMENT


Thank you very much for using our product and for your help in moving
it forward.
CND Development Team.
Back to top
Ivan Soleimanipour
Posted via mailing list.





PostPosted: Wed Jun 23, 2010 11:26 pm    Post subject: Your wishes for next release of CND Reply with quote

On 06/23/10 09:29, Nikolay Molchanov wrote:
Quote:
Hello CND team,

I think NB 6.9 is a great step ahead, but I still miss 3 things:

1. "Send To ..." action in context menu for a selected file.
- This action should invoke specified command and pass file name as a
parameter.

2. SCCS support.
- This means at least 4 actions in context menu:
-- Checkout
-- Checkin
-- Diffs (enabled for checked out files)
-- Uncheckout


I'm not sure these will be enough by themselves.
There needs to be intregration with the project system so that if any file
that needs to be adjusted by the IDE is modified it is automatically
checked out.
Back to top
Nikolay.Molchanov@Oracle.
Posted via mailing list.





PostPosted: Thu Jun 24, 2010 1:00 am    Post subject: Your wishes for next release of CND Reply with quote

Ivan Soleimanipour wrote:
Quote:
On 06/23/10 09:29, Nikolay Molchanov wrote:

Quote:
Hello CND team,

I think NB 6.9 is a great step ahead, but I still miss 3 things:

1. "Send To ..." action in context menu for a selected file.
- This action should invoke specified command and pass file name as a
parameter.

2. SCCS support.
- This means at least 4 actions in context menu:
-- Checkout
-- Checkin
-- Diffs (enabled for checked out files)
-- Uncheckout


I'm not sure these will be enough by themselves.
There needs to be intregration with the project system so that if any file
that needs to be adjusted by the IDE is modified it is automatically
checked out.

Yes, that's right, and there is a lot of work related to error handling,
icons, parsing 'sccs diffs' output and so on. That's why I said that
I understand that SCCS support is a difficult task. But I'll be happy
if "Send To .." is implemented, so I can easy implement SCCS support
with a set of scripts.

Thanks.
Nik
Back to top
charlls



Joined: 27 Jan 2009
Posts: 44

PostPosted: Sat Jun 26, 2010 3:16 am    Post subject: Reply with quote

i endorse rmartins suggested priorities, separate threads for parsing sounds like an absolute must, thanks for all the amazing work! Very Happy
Back to top
naboko



Joined: 26 Jun 2010
Posts: 5

PostPosted: Mon Jul 05, 2010 2:47 pm    Post subject: Reply with quote

I support and recommend rmartins suggested priorities.

>Performance improvements, as usual.

>Bug fixes, little things, as usual.


>Global compiler options panel with as extensive and rich as the one from Code::Blocks.

Code::Blocks has a very rich Global Compiler Options panel.
I use it to configure the compiler globally to my taste.
Would be very handy to have in NetBeans.
For pictures how it looks: http://atutility.com/content/setup-c-development-using-mingw-codeblocks-windows-vista
Code::Blocks: http://www.codeblocks.org/home
(It's accessed by going to the menu and then Settings>Compiler and debugger.)


>Smarter handling of console applications exit.

Without adding an extra keyboard action, console applications just flash by. However it is possible to do something slightly more intelligent than always requiring a lasts keyboard stroke. The tools could check if the last thing a console application does is requiring a user interaction. Excluding a few things such as the return statement and other common things such as e.g. closing brackets. If there is: not adding extra interaction because the application won't flash by. If there is not: add the extra interaction because the application will flash by. This will work for most applications. There might be some cases where it's desirable to do something else before exciting. This will prompt, just as now the case is, an extra user interaction.


>If there is NOT, adding an RAD GUI tool API.

I don't know if this is or is not present, or worked out enough to do the described situation which follows.

It would be nice to be able to use rad GUI tools nicely integrated into NetBeans. Especially be able to use glade: http://glade.gnome.org/ within NetBeans.
Back to top
Titus von Boxberg
Posted via mailing list.





PostPosted: Fri Jul 09, 2010 5:48 am    Post subject: Your wishes for next release of CND Reply with quote

Am 05.07.2010 um 16:47 schrieb naboko:
Quote:
Quote:
Global compiler options panel with as extensive and rich as the one from Code::Blocks.

Code::Blocks has a very rich Global Compiler Options panel.
I use it to configure the compiler globally to my taste.
Would be very handy to have in NetBeans.
For pictures how it looks: http://atutility.com/content/setup-c-development-using-mingw-codeblocks-windows-vista
Code::Blocks: http://www.codeblocks.org/home
(It's accessed by going to the menu and then Settings>Compiler and debugger.)
I'd like to endorse this feature request.
I'm trying to use cnd for projects that get compiled for
six architectures/target systems, each with Debug/Release,
so I have twelve targets. Since each workspace consists of about
ten projects (1 exe, 9 lib dependencies), I have 120 configurations to maintain.

Cnd's configuration for such projects just gives pain in the a..
because the settings for the tools are not organized hierachically / tree like
where each leaf (particular project+configuration tool option set)
would inherit from its preceding nodes.
So each and every setting has to be repeated in every project and configuration
it pertains to...

To get that topic more specific than just "have a look at C::B or CodeLite or VS"
here a rough first idea of what could be nice.

- provide the same tool options per tool chain and per language (C, C++)
as are defined in the project settings, at least where creating a union of them
makes sense.

- provide the same definitions globally for all tool chains (this would
be the root of the "options" tree.

- provide variable definitions per tool chain.
Then, tool chain specific definitions that are not covered by the tools' global
options can be referenced in multiple configurations of a project
in the same way, eliminating repetitive per-project-configuration-entries.

- for the each of the project's tool options, create a default setting
<use global settings> which just copies the options.
- when setting a configuration specific project option, create a union set
of the project / configuration specific options with the global options.

- Establish the same principle within the project's settings for
"All Configurations/Multiple Configurations" vs. a single configuration,
like e.g. in VS
This would at least require that entering "xxx Compiler" options
would work for "All/Multiple Configurations" which now it does not.

- for a workspace with lib projects as dependencies:
in the "Required Projects" settings -> Projects selection dialog:
Provide in the "Configuration" column / combobox a value
<same configuration as requiring project> which would get the value
${CONF}, not the contents of ${CONF}, which is not existent for
"All Configurations".
This should even be the default. Goal is use this dialog for
"All Configurations" because usually a dependency lib is required
for "all configurations", and usually it is desirable to compile it
with the same configuration name than the requiring project.

- in general: Stop storing the value of configuration specific variables
inside project's configuration.xml:
e.g. do not store the path ...dist/GNUMacOS-X/Debug/... but
store .../${CONF}/...
Then the project configuration file can be edited by people on different
machines / architectures and remain valid.
Simple rule could be: When the value entered by the user is the value
of a variable, store the name of the variable.

Can this be an interesting goal for CND?

Regards
Titus
Back to top
Mike Riley
Posted via mailing list.





PostPosted: Fri Jul 16, 2010 7:38 am    Post subject: Your wishes for next release of CND Reply with quote

On 06/23/10 02:35, XVilka wrote:
Quote:
My wishes is:

1) better support of assembler highlites and support for navigating:
show labels, functions, macroses and datas as for C/C++ sources

+1 - I am using Netbeans to edit and manage my sources for a project that uses a very old Visual
C++ compiler. It is far superior in how it handles C++, but it chokes when it sees some inline
assembly code and reports it as an error. I still use the Visual C++ to build with, because I
have to use the files it generates for this embedded platform.
Back to top
dmitchell



Joined: 10 Aug 2010
Posts: 4

PostPosted: Tue Aug 10, 2010 9:23 pm    Post subject: Reply with quote

My wish is that you start incorporating C++0x awareness into the editor. Variadic templates, lambda functions, rvalue references, templates closed with >>... none of this can be parsed. I have entire source files marked as errors, breaking features like code completion.
Back to top
rmartins



Joined: 16 Jun 2010
Posts: 4

PostPosted: Fri Aug 13, 2010 10:57 am    Post subject: Reply with quote

dmitchell wrote:
My wish is that you start incorporating C++0x awareness into the editor. Variadic templates, lambda functions, rvalue references, templates closed with >>... none of this can be parsed. I have entire source files marked as errors, breaking features like code completion.


Hi dmitchell,
C++0x has mentioned in the ongoing effort to better support templates:
https://netbeans.org/bugzilla/show_bug.cgi?id=158692
The issue is marked for 6.10 release but still isn't assigned to anyone...

Rolando
Back to top
theunstoppableprogrammer



Joined: 29 Aug 2010
Posts: 3

PostPosted: Sun Aug 29, 2010 1:48 pm    Post subject: built in mingw compiler ... Reply with quote

how about providing this together with netbeans
built in mingw compiler and tools.
access to code analysis refactoring anc call tree dunctions without ewen creating a project.
Back to top
Valeriano Cossu
Posted via mailing list.





PostPosted: Sun Aug 29, 2010 2:02 pm    Post subject: Your wishes for next release of CND Reply with quote

What?

On Sun, Aug 29, 2010 at 3:48 PM, theunstoppableprogrammer <address-removed ([email]address-removed[/email])> wrote:
Quote:
how about providing this together with netbeans
built in mingw compiler and tools.
access to code analysis refactoring anc call tree dunctions without ewen creating a project.







--
Cordiali saluti,
Valeriano Cossu

Regards,
Valeriano Cossu

ph: (0039) 346 2187419
skype: valerianocossu
http://www.valerianocossu.net
Back to top
Display posts from previous:   
Post new topic   This topic is locked: you cannot edit posts or make replies.    NetBeans Forums -> C/C++ Users All times are GMT
Goto page 1, 2, 3  Next
Page 1 of 3

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo