News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Development roadmap?

Started by rickg22, June 03, 2005, 01:50:04 AM

Previous topic - Next topic

rickg22

Which bugs /  features will have to be fixed/added before 1.0 Final (Or at least RC1) ?

tiwag

Quote from: rickg22bug features

Freudian slip ?

rickg22


Profic

Features:
Possibility to switch off smart Home key in editor?
Possibility to order files in opened-list (in Project tab) or tabs (in new tabbed interface)?

Bugs
Makefile generated by c::b when file belongs to more than one target generates itself warnings about dublicate definition of actions.

This is what I quickly remember after my final switch from Dev-C++ to c::b... Project with many files need too-o-o much time to begin compile....

ADDED:
Remove this orange (or whatever color it would be) highlight of error/warning line after first user action in editor, or by Ctrl+Click by line in "Compiler messages tab". Currently it's no so easy to read this line, as I prefer dark-red for error highlight and use some red for syntax also.

ADDED PS:
However, rickg22, I don't think it was perfect idea to begin this topic, this all should go to sf's bugtracker/feature requester :)
Not fear, nor tears can reach me now, the light seems so clear as the night fades away (c) Tristania - Beyond The Veil

David Perfors

Search in files would be very helpfull
OS: winXP
Compiler: mingw
IDE: Code::Blocks SVN WX: 2.8.4 Wish list: faster code completion, easier debugging, refactoring

Profic

Quote from: mispuntSearch in files would be very helpfull
AFAIR already implemented in CVS :)
Not fear, nor tears can reach me now, the light seems so clear as the night fades away (c) Tristania - Beyond The Veil

Urxae

Some button to close a tab, so I don't have to do File->Close or put my hands back on the keyboard would be nice. (When browsing code, I like to use my mouse instead of my keyboard)

takeshimiya

In order of importance to me:

- Change the behaviour of the click at the breakpoint margin
http://sourceforge.net/tracker/index.php?func=detail&aid=1201664&group_id=126998&atid=707419

- Customizable shortcuts (key bindings)
http://sourceforge.net/tracker/index.php?func=detail&aid=1201652&group_id=126998&atid=707419

- Go to function with CTRL+click ("Go to Definition" and "Go to declaration" in the context menu also.)
http://sourceforge.net/tracker/index.php?func=detail&aid=1212127&group_id=126998&atid=707419

- Some button to close a tab (I suggest doing it exactly like firefox does -an only one close button at the right of all tabs)

- Posibility to disable a key in the keyboard (In the "Customizable shortcuts editor" perhaps. Who uses the INSERT key for example?)

:D

Urxae

^^^ and what he said

Though:
Quote from: takeshimiyaWho uses the INSERT key for example?
I do :wink:. Comes in quite handy sometimes. If you want it disabled on your computer, I can understand that (I've pressed it by accident a couple times too), but it does have its uses :).

takeshimiya

Oh it's great, I thought that nobody uses the insert key other than to overwrite text by accident, you are the first I know then =)

rickg22

ACK! Erm, I meant which of the feature requests ALREDY submitted...
(Yiannis is going to kill me :cry: )

Ok here goes again

Which one of the bug reports or feature requests *ALREADY SUBMITTED* do you consider would have to be fixed/added before we release 1.0-Final?


My objective here is to have some kind of development roadmap so that *WE developers*  can start working on them and speed up the current C::B development.

No need for fancy explanations, just list them.

David Perfors

Quote from: rickg22ACK! Erm, I meant which of the feature requests ALREDY submitted...
(Yiannis is going to kill me :cry: )

Ok here goes again

Which one of the bug reports or feature requests *ALREADY SUBMITTED* do you consider would have to be fixed/added before we release 1.0-Final?


My objective here is to have some kind of development roadmap so that *WE developers*  can start working on them and speed up the current C::B development.

No need for fancy explanations, just list them.
Quote from: takeshimiyaIn order of importance to me:

- Change the behaviour of the click at the breakpoint margin
http://sourceforge.net/tracker/index.php?func=detail&aid=1201664&group_id=126998&atid=707419

- Customizable shortcuts (key bindings)
http://sourceforge.net/tracker/index.php?func=detail&aid=1201652&group_id=126998&atid=707419

- Go to function with CTRL+click ("Go to Definition" and "Go to declaration" in the context menu also.)
http://sourceforge.net/tracker/index.php?func=detail&aid=1212127&group_id=126998&atid=707419
:lol:
OS: winXP
Compiler: mingw
IDE: Code::Blocks SVN WX: 2.8.4 Wish list: faster code completion, easier debugging, refactoring

Anonymous

RC versions should be polished, so IMHO the highest priority should be given to bugs (especially those that can be reproduced everywhere or causes C::B to crash) or simple requests, that make useful tweaks of what already exists.

Btw. is it just me, or some among open bug submissions report that stability of C::B under various Linux systems suffers a bit?

Anonymous

Quote from: AnonymousRC versions should be polished, so IMHO the highest priority should be given to bugs (especially those that can be reproduced everywhere or causes C::B to die horrible death ;) ) or simple requests, that make useful tweaks of what already exists.

Btw. is it just me, or some among open bug submissions report that stability of C::B under various Linux systems suffers a bit?

Anonymous

Saparate C/C++ switchs or file-specific switchs.