Feature | BCB 6 | CB 5274 | Importance | Remark for CB |
Included framework libs | yes | NO | ** | WxWidgets should be included and compiled (As Mingw is). |
Separated window for edited Dialog. | yes | NO | *** | Most programs need big windows as their main dialog. CB editor does not allow a plain view of the edited window, only included in the small part of the tabbed edition window. That is not enough. |
Integrated framework help | yes | NO | **** | In BCB, when you select a component property, a component declaration or implementation, or select a resource, and press F1 (help), the help is opened directly on the component (or function, or property)'s description. That is essential, and makes work very efficient and quick. CB should provide that kind of help as a priority, and integrate closely the WxWidgets help. On addition, CB could provide a limited help using the function (or component, or property) declaration (through F1). |
Choose alternative keyboard shortcuts sets. For example Visual Studio shortcuts, Borland shortcuts, etc.. | yes | NO | * | I know the possibility to modify the shortcuts one-by-one, but it would be easier to select a complete set. |
While debugging, passing above a variable displays its value. | yes | partly | **** | CB does it, but only partly: Many local variable or function parameters are not displayed. The informations are often incomplete, forcing the use of the Watch window, which does not display global variables (why???) For example, the very used WxString is frequently not displayed as a string, but as a byte table. It is not constant. The mouse-over often displays different information from the Watch window. In Watch, classes are not always displayed as it. For example, a button if displayed in one line: “Button1 = (struct wxButton*) 0x12345678. And I try to dereference it, I obtain: “*Button1 = <incomplete type>. I suggest a tough work at checking and improving this feature, as an essential feature. By the way, BCB proposes two windows: Watch and Evaluate. Evaluate displays a variable (or class) with details and forget everything when closed (unlike Watch). It is very useful to see more information than the mouse-over, and also to modify a value. Under BCB, I use it very much more often than the Watch window, as it is limited to one variable at a time (a small, quick and efficient window). |
Integrated environment | yes | partly | *** | Basically, you install BCB and obtain a complete environment. Nothing to add or configure, everything is made to work together and is integrated. CB is partly integrated, but: WxWidgets is not included. Plugins are available, but it is difficult at first to know what which of them will do, and if there are bad interactions between them. I suggest to integrate as many things as possible in CB by default, including the plugins (AFAIR, they are not checked at install by default). And improve CB as a complete set, well integrated. For example, the Help plugin is not well integrated. I'm sorry to say that it appears clearly to be an added tool, not an integrated component of the IDE. |
I agree with wxWidgets integration (should be optional), since you have wxSmith. But I really doubt about more libraries.
Choose alternative keyboard shortcuts sets. For example Visual Studio shortcuts, Borland shortcuts, etc.. yes NO * I know the possibility to modify the shortcuts one-by-one, but it would be easier to select a complete set.
Choose alternative keyboard shortcuts sets...
Already exists.
Settings/Editor/KeyBoard Shortcuts/KeyProfile/Add new
The problem has always been which wxWidget Library to integrate and is it worth the band width.
I say what we need is an replacement of DevPak that works better with Code::Blocks. And use it to download the desired type of wxWidgets.
I prefer CB way because it provide me flexibility to use wxWidgets build that I want, that is, version and static/dynamic libraries, wich can be difficult with integrated framework libs.A possibility is to integrate by default the last version of WxWidgets and let the option of choosing another (personal) build. Isn't it ?
At first, I also miss the complete window in wxSmith (with menus and the border) but I see it is something usual in wxWidgets dialog editors. At least, in wxSmith you have a button that allow you to see the entire window without building the project.Yes, there is a preview button. But my problem is to build a big window, so to work (edit) its (big) components, which is obviously impossible with the preview.
I really miss integrated help before I found throw this forum a way to integrate linux wxWidgets help with yelp in CB with a simple bash script. Now I have that script a little bit modified to obtain wxWidgets help of the svn version from the web.I understand there are "tricks", but I believe it is very important to have an integrated environment.
I personally don't think, that BCB is something to look at...Each point of view is interesting, but I insist: this thread is not really about BCB6, in the way of a competition (or worst, a fight).
VCL is horrible.I won't troll about that and the rest, in my point of view there are defaults, bugs, and bad design in all frameworks. I read the documentation of WxWidgets, and I noticed it has a very old design, not really using C++ technicals. Win32 is old and complex too, dot.net seems to be a bit more modern, but I guess it joined the design of VCL (same designer, as I read), GTK and QT are not native (draw components, not using the O.S. ones), etc..
A possibility is to integrate by default the last version of WxWidgets and let the option of choosing another (personal) build. Isn't it ?This is a quite old issue. Read this thread: http://forums.codeblocks.org/index.php/topic,8752.0.html
I really miss integrated help before I found throw this forum a way to integrate linux wxWidgets help with yelp in CB with a simple bash script. Now I have that script a little bit modified to obtain wxWidgets help of the svn version from the web. Despite that, I really want to see integrated help in CB, it will be a very good improvement, maybe someday.True! When I select a class name and press F1, wxWidgets help runs, but I very often have to perform a search to get into class description. It's a pain in the neck!
While debugging, passing above a variable displays its value.Debugger limitations are THE thing that prevents me from dropping VC++. wxSmith limitations don't bother be. A better integration between gdb and C::B (like the one in Eclipse/CDT for example) is probably difficult and long to achieve. Let's be patient.
Under Windows, I personally think C::B should be packaged in two ways: "single" package (only C::B) and "out-of-the-box-GUI-dev" package (C::B + minGW + wxWidgets lib release and debug).I agree with the idea of linking MinGW and WxWidgets.
When I select a class name and press F1, wxWidgets help runs, but I very often have to perform a search to get into class description.Personaly, though I installed CB with all plugins, more WxWidgets, Nothing happen when I press F1! :(
Let's be patient.Yes, but my question is: what is really important to users ?
Another possibility is to develop a true package tool in CB.Yes, this would be very nice. But a all-in-one setup has an advantage: it could allow to set all the relevant paths (toolchain, help... see below) and also to make sure all components work well together (toolchain, C::B, wxWidgets) ; there are sometime various compatibility issues.
As in ReactOS or Ubuntu, after installation the tool could list additionnal software. One click = A quick installation (and configuration).
And something similar to firefox plugins manager: the ability to update packages with ease.
That would solve problem of the official releases of CB, which are very rare.Another old complaint. For example, read http://forums.codeblocks.org/index.php/topic,7772.0.html
Personaly, though I installed CB with all plugins, more WxWidgets, Nothing happen when I press F1!Go in menu Settings>Environment, browse icons and select the "Help files" icon, then press the "Add" button to add the path to your wxWidgets help file. A "F1" press will yield wxWidgets help opening.
I mean users opinion should lead CB development.I'm not sure CB team completely agrees with this statement (see above) :).
I believe things could be different than just waiting new features with hope.We are in open-source world : if you think something should be done, then develop it yourself !
I have no time to do it myself (time is THE problem !)
LOL, thats true, I started developing a plugin named codepacks to solve library problems since it was going to work like synaptic downloading libraries from repositories and giving you the option of configuring your current project with a given configuration from the library, but then i stopped programming it because of lack of time. First started working on the downloader and analysis and banggg!!!!!!! no more, but I still want to do it, just not in the time i would like it to be.I hope you'll find some time to complete this plugin soon!
But it seems it could solve some of the problems here like the wxwidgets one!
C::B guys obviously are the masters and manage the project as they please !Of course. :)
a all-in-one setup has an advantage: it could allow to set all the relevant paths (toolchain, help... see below) and also to make sure all components work well together (toolchain, C::B, wxWidgets)Yes, that's true.
Go in menu Settings>Environment, browse icons and select the "Help files" iconThank you! :)
I'm not sure CB team completely agrees with this statement (see above). I'm not sure, that practically it always happens like this in FOSS projects in generalThat world is not perfect. But we can help it. ;)
No troll inside
if you think something should be done, then develop it yourself !Precisely! :)
I have no time to do it myself (time is THE problem !)
I started developing a plugin named codepacks to solve library problems since it was going to work like synaptic downloading libraries from repositoriesBravo! :)
Alexis:I see: So you want us to do what you suppose to develop, right? Is that how democracy works? Sure not.QuoteC::B guys obviously are the masters and manage the project as they please !Of course. :)
I see: So you want us to do what you suppose to develop, right? Is that how democracy works? Sure not.I could tell you "Democracy is not telling the others to shut up", but I won't troll about your reply (as I did not for another one in the same thread).
Stop spamming our forum.I presume (but you don't say) you are talking about my web site below. I changed my 'signature' to avoid misunderstandings.
We in the dev team are *all* real life persons. We have family we have work and we (especially these days) work very hard. But we still find the time to continue development of C::B. What about you?
I did not expect such an aggressive reply from anybody.
To MortenMacFly:
From your lack of submitting patches can I assume you have no plans to submit patches in the future?Well, as you can read in my posts, my intention in this thread is to discuss about design decisions about C::B. Decisions take place before implementation; I cannot tell you what I could program before knowing what to program precisely. No need to do assumptions.
Personally, I am interested in replies proposing constructive things, in the theme of this thread: suggestions about the overall design of C::B.
I did not expect such an aggressive reply from anybody.This was not meant to be aggressive. I just wanted to make myself clear: