Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: 280Z28 on December 13, 2005, 10:29:33 am
-
I think it'd be a good idea to have a list of features proposed and/or under active development, along with the milestone they will hopefully be released with. An example is the new binding/event architecture will almost surely be going in, but will not be released until the 2.0 release series. "Simple" profiles will are also being developed and should go in 1.0 (AFAIK).
By the way, this is for core features, not plugins.
Edit: I know I arbitrarily assigned targets to these even though I'm not a project leader. For features I want to get in later versions, esp. 2.0, there is plenty of time to talk about them later. :)
I'll start with what I'm working on or interested in:
Topic: Rectangular (block) selection operations in wxScintilla.
Status: Completely broken in SVN head (1499), patch available for some of the operations.
Target milestone: 1.0 final
Topic: Compiler options (edit: this is a plugin so it can happen anytime...)
Status: Pretty complete as is, some advanced options to go
Target: 1.1 (first minor update after 1.0)
Topic: New advanced options in project files
Status: I haven't even posted details of what I mean
Target: 2.0
Topic: Completely revamped bindings/events architecture (not just the key binding plugin)
Status: A few discussions on the forum
Target: 2.0
-
Topic: Editor virtual space
Status: I don't see evidence of support in either wxScintilla or the Scintilla base
Target: 1.1
-
I wonder what a virtual space is...
-
I wonder what a virtual space is...
Allows cursor positioning after the end of a line but does not insert the trailing spaces leading to that position unless you type something.
-
I think this feature should be disengageable by the user. The reason? Well, I really hate such a behaviour from the editor and I don't believe that I am the only one with that opinion. :wink:
-
I think this feature should be disengageable by the user. The reason? Well, I really hate such a behaviour from the editor and I don't believe that I am the only one with that opinion. :wink:
I've never seen it not as an option or turned on by default.
-
Ah, yes, I hate that functionality too :twisted:
But sometimes it can be usefull.
-
"Simple" profiles will are also being developed and should go in 1.0 (AFAIK).
What's that supposed to be?
Topic: Rectangular (block) selection operations in wxScintilla.
Status: Completely broken in SVN head (1499), patch available for some of the operations.
Not true. I am working with that release, and although I see no serious use for that feature, I just tried cut/copy/paste on a rectangular selection, and it works without any problems.
Topic: Compiler options (edit: this is a plugin so it can happen anytime...)
Status: Pretty complete as is, some advanced options to go
Target: 1.1 (first minor update after 1.0)
Compiler redesign is scheduled for 2.0. To my knowledge, a 1.1 release is not planned. The fact that something is a plugin does not necessarily mean that it can be changed any time. In particular the compiler plugin has non-trivial interdependencies.
Topic: Editor virtual space
If wxScintilla does not support it, then Code::Blocks will not support it. Rewriting wxScintilla for our own needs is not reasonable because that particular module is updated very frequently. If we cook our own curry, we get into trouble merging the changes with the official releases. Also, I am with Der Meister as far as this particular feature is concerned. Not knowing where a line ends is revision control horror - I'd never want to use that.
-
virtual space : don't like it. This is indeed a living nightmare
-
Now that I remember, the virtual space thing is usefull to those who are used to vi/vim navigation-command mode, where you look at the code.
But regardless, I also remember stopping using a text editor because it always had virtual space activate.
-
"Simple" profiles will are also being developed and should go in 1.0 (AFAIK).
What's that supposed to be?
Topic: Rectangular (block) selection operations in wxScintilla.
Status: Completely broken in SVN head (1499), patch available for some of the operations.
Not true. I am working with that release, and although I see no serious use for that feature, I just tried cut/copy/paste on a rectangular selection, and it works without any problems.
Topic: Compiler options (edit: this is a plugin so it can happen anytime...)
Status: Pretty complete as is, some advanced options to go
Target: 1.1 (first minor update after 1.0)
Compiler redesign is scheduled for 2.0. To my knowledge, a 1.1 release is not planned. The fact that something is a plugin does not necessarily mean that it can be changed any time. In particular the compiler plugin has non-trivial interdependencies.
Topic: Editor virtual space
If wxScintilla does not support it, then Code::Blocks will not support it. Rewriting wxScintilla for our own needs is not reasonable because that particular module is updated very frequently. If we cook our own curry, we get into trouble merging the changes with the official releases. Also, I am with Der Meister as far as this particular feature is concerned. Not knowing where a line ends is revision control horror - I'd never want to use that.
Simple profiles are profiles that are in there. I'll go more into features I was to see in profiles but aren't there now, later.
Use my patch in svn forum to see how block copy/paste is supposed to work.
I call "1.1" the first release after 1.0 that isn't just a quick bug fix or security issue.
We're going to have to modify wxScintilla later (by 2.0) for other reasons anyway. Plenty of time to go into that later.
-
Virtual space is useful to me, and I'm going to implement it as a non-default option. :shrug: Of course, you don't have to check it in, but why stop a feature option that some people are used to? I'm sure I'm not the only one that uses it.
-
Virtual space is useful to me... I'm sure I'm not the only one that uses it.
i use i too sometimes when i want to edit some tables - normally i use TextPad as default editor and there is an editor option called (bind cursor to text) for this.
-
Y'all jacked my thread... :?
Someone else post what they are working on and when they hope to finish it
-
OK um... so far...
um... :( I don't know.
But youknow, you do have a point. We need a good roadmap to orient users so they can't complain if some feature is ready.
And this is specially true, because RC3 hasn't been released yet, and I bet it'll be about a month before all the recent bugs are removed.
Anyway, 280Z28, remember that the "Feature requests" at Sourceforge are still there.
-
Hint: Most OSS projects have a roadmap entry in the WiKi. :)