Bad news for codeblocks.
Posted 05-20-2015 at 09:32 AM by rainbowsally
Updated 05-20-2015 at 10:01 AM by rainbowsally (added a ps.)
Updated 05-20-2015 at 10:01 AM by rainbowsally (added a ps.)
Bad news for codeblocks.
[kdevelop3 32 and 64 bit versions (binary installers using 'make' are included below). See for yourself. And scratch your head, wondering... Where did we go so wrong?]
Ok... About codeblocks.
What happened to the "open" part of "open source", anyway? I'm not just talking about source code, but the very philosophy of user involvement in programming.
Codeblocks does not let you override the system build with a sandbox build because it (for exmaple) uses the full path to wx-config which will not match a sandboxed version of wxwidgets installed anywhere else.
Also, it does something with stdout so that it's not possible to see what it's doing behind our backs... even with 'uncmake' (available here at linuxquestions.org).
Let's go a little futher here and talk just about the nuts and bolts of codeblocks for a second.
Codeblocks editor has BAD (did I actually say "bad"?) defaults for the colors. The comments are too light and the (almost useless) brace and paren pair highlighting is way-way too bright. The highlights almost conceal the position of the cursor.
What indeed are the developers thinking? That we're all blind, or can't match parens? (I often mess those up, by the way, but even I don't need a 1000 Watt laser to point out my mistakes.)
But the default colers is not a big problem. A big problem is that it doesn't indent intelligently. You can copy/paste something somewhere and end up with the braces all messed up. And to reformat it you need to open the plugins menu and hunt down the one and only C/C++ format that can be used... and it doesn't always do it right either.
Compared to kdevelop3 (kdevelop for kde4 sucks!) codeblocks is really a no-go showboat. It has tons and tons of highlightings available, but so does kdevelop3. And kdevelop3 does regex. And it will NOT override your LD_LIBRARY_PATH or your PATH, so you can run sandboxed installations without problems. In fact my kdevelop3 is basically in a sandbox. It's in /opt/kde3. But it only works on KDE systems.
We have two versions of it, and you can take them for a spin if you like. They are from an old old commercial SuSE 10.0. And they still work in kde... for now. But for how much longer, we don't know. The sources are no longer available, so this was ripped from the SuSE 10 rpms.
Here's our old 32 bit version, which has a lot of cruft in it you won't need.
http://rainbowsally.org/rainbowsally...i386-rs.tar.xz
And here's the 64 bit version.
http://rainbowsally.org/rainbowsally...-x86_64.tar.xz
Unpack and type 'sudo make install'. Then type 'kdevelop3' (it's the only file that goes into /usr/bin). Then type 'sudo make uninstall'... and when you're confident that you can install/uninstall this easily, think about it. What the hell's wrong with the developers? Why is technology that's almost a generation (a human generation) behind the bleeding edge kicking &ss?
If you click on the IDE.exec in the test folder, you'll see what I'm talking about... if you have kde which hasn't been dumbed down too much... yet.
I'm telling you, linux is getting stupider and stupider. Fancier but with less and less concern about how the tools work, more and more concern about bug reports and developers' egos. The solution would be to convince the developers to use the stuff they create. That would eliminate most feature requests and bug reports right there, because the developers would have an actual interest in what they are producing.
And Gnome? Do you HAVE to have a desktop icon just to launch an app? That eliminates quick and easy clickable scripts -- just like Windows... way too many steps for people that just want to play with their compiler or print out the sizeof(long long) to see how many bytes it is.
Look! I have a file manager. I can see my files. I need to be able to click on a script, have the script change to the directory where it was clicked (cd dirname $0), and run an application from there. Not asking too much. (That's all the IDE.exec in the test directory does.)
Enlightenment is better than Gnome in this regard. That's a sad thing to have to say.
Sorry.
Bad day at the lab, here. Back to kdevelop3 and mc2 for the Computer Mad Science Team, but we'll keep the (stupid) codeblocks thing for people that are... how shall I say. Easily misled by the hype? In a rush to find the (cutting) edge of the cliff?
:-(
Dear developers. Try using the tools you create. In short order the problem will be solved. Reduced bug reports. Fewer feature requests. Better Linux 'first cuts'.
PS. To codeblocks. The headers in wxKWIC are all lowercase. It will never work in linux.
The Computer MAD Sci3nce Team.
[kdevelop3 32 and 64 bit versions (binary installers using 'make' are included below). See for yourself. And scratch your head, wondering... Where did we go so wrong?]
Ok... About codeblocks.
What happened to the "open" part of "open source", anyway? I'm not just talking about source code, but the very philosophy of user involvement in programming.
Codeblocks does not let you override the system build with a sandbox build because it (for exmaple) uses the full path to wx-config which will not match a sandboxed version of wxwidgets installed anywhere else.
Also, it does something with stdout so that it's not possible to see what it's doing behind our backs... even with 'uncmake' (available here at linuxquestions.org).
Let's go a little futher here and talk just about the nuts and bolts of codeblocks for a second.
Codeblocks editor has BAD (did I actually say "bad"?) defaults for the colors. The comments are too light and the (almost useless) brace and paren pair highlighting is way-way too bright. The highlights almost conceal the position of the cursor.
What indeed are the developers thinking? That we're all blind, or can't match parens? (I often mess those up, by the way, but even I don't need a 1000 Watt laser to point out my mistakes.)
But the default colers is not a big problem. A big problem is that it doesn't indent intelligently. You can copy/paste something somewhere and end up with the braces all messed up. And to reformat it you need to open the plugins menu and hunt down the one and only C/C++ format that can be used... and it doesn't always do it right either.
Compared to kdevelop3 (kdevelop for kde4 sucks!) codeblocks is really a no-go showboat. It has tons and tons of highlightings available, but so does kdevelop3. And kdevelop3 does regex. And it will NOT override your LD_LIBRARY_PATH or your PATH, so you can run sandboxed installations without problems. In fact my kdevelop3 is basically in a sandbox. It's in /opt/kde3. But it only works on KDE systems.
We have two versions of it, and you can take them for a spin if you like. They are from an old old commercial SuSE 10.0. And they still work in kde... for now. But for how much longer, we don't know. The sources are no longer available, so this was ripped from the SuSE 10 rpms.
Here's our old 32 bit version, which has a lot of cruft in it you won't need.
http://rainbowsally.org/rainbowsally...i386-rs.tar.xz
And here's the 64 bit version.
http://rainbowsally.org/rainbowsally...-x86_64.tar.xz
Unpack and type 'sudo make install'. Then type 'kdevelop3' (it's the only file that goes into /usr/bin). Then type 'sudo make uninstall'... and when you're confident that you can install/uninstall this easily, think about it. What the hell's wrong with the developers? Why is technology that's almost a generation (a human generation) behind the bleeding edge kicking &ss?
If you click on the IDE.exec in the test folder, you'll see what I'm talking about... if you have kde which hasn't been dumbed down too much... yet.
I'm telling you, linux is getting stupider and stupider. Fancier but with less and less concern about how the tools work, more and more concern about bug reports and developers' egos. The solution would be to convince the developers to use the stuff they create. That would eliminate most feature requests and bug reports right there, because the developers would have an actual interest in what they are producing.
And Gnome? Do you HAVE to have a desktop icon just to launch an app? That eliminates quick and easy clickable scripts -- just like Windows... way too many steps for people that just want to play with their compiler or print out the sizeof(long long) to see how many bytes it is.
Look! I have a file manager. I can see my files. I need to be able to click on a script, have the script change to the directory where it was clicked (cd dirname $0), and run an application from there. Not asking too much. (That's all the IDE.exec in the test directory does.)
Enlightenment is better than Gnome in this regard. That's a sad thing to have to say.
Sorry.
Bad day at the lab, here. Back to kdevelop3 and mc2 for the Computer Mad Science Team, but we'll keep the (stupid) codeblocks thing for people that are... how shall I say. Easily misled by the hype? In a rush to find the (cutting) edge of the cliff?
:-(
Dear developers. Try using the tools you create. In short order the problem will be solved. Reduced bug reports. Fewer feature requests. Better Linux 'first cuts'.
PS. To codeblocks. The headers in wxKWIC are all lowercase. It will never work in linux.
The Computer MAD Sci3nce Team.
Total Comments 0
