User forums > General (but related to Code::Blocks)

Why did you choose Code::Blocks?

<< < (2/3) > >>

nenin:

--- Quote from: SashaGT on June 06, 2023, 09:57:03 am ---Why did you download a start using Code::Blocks?

--- End quote ---
70% the same as Miguel Gimenez.

1. I had to migrate to open source from Borland (many years ago).
1. Also I have to keep in mind multiplatform possibility.
1. For some time I used Dev-Cpp, but it was abandoned de-facto. Also it was underdeveloped.
1. There were some alternatives, but not good.
1. C::B was already operable with non-crucial issues. It also supported Fortran, which I need from time to time.

cacb:
I come from a background where the company I worked for developed and delivered software for VAX/VMS and a number of Unix platforms. So cross platform was always my perspective. Then in the 1990s, Windows took over and development became more and more MSVS centric with GUIs using MFC, and cross platform kind of faded away, which I did not really enjoy.

I was looking for a good solution for cross platform GUI and found that wxWidgets was the best answer, it is native on all platforms which I think is the right approach. Code::Blocks supports wxWidgets development via the simply excellent and very important wxSmith plugin. wxSmith is a major reason for choosing Code::Blocks.

Also, Code::Blocks has its own build system that works the same on Windows and Linux (the platforms that matter to me). You can use GCC everywhere like most people do, or you can do what I do: Within one and the same project I have build targets for the MSVC compiler (used on Windows) and also for GCC (used for linux). This is as good as it gets for my use, the software is native everywhere and I can update the project files everywhere and use git to synchronize between platforms.

I have used Code::Blocks more or less this way since about 2008 and I enjoy it. I use the Nightly Builds of C::B on Windows and I build from source on Linux. I have a git mirror repository that is automatically updated every day from the SourceForge SVN original https://github.com/arnholm/codeblocks_sfmirror

Many thanks to the developers and maintainers of Code::Blocks!

SashaGT:

--- Quote from: cacb on June 08, 2023, 09:07:15 am ---Code::Blocks supports wxWidgets development via the simply excellent and very important wxSmith plugin.

--- End quote ---

Yes! I've not much experience with wxWidgets but I've known about it and the plugin for some time now. I really ought to invest some time into learning more about it. I typically create an empty project and link everything I need manually via the build options but I recognize there's quiet a few templates that exist packaged with C::B. I've seen the wxWidgets template a few times but haven't had the time to investigate it.

Oh, I've also been reminded (just today) via the C::B splash screen that it's open source... likely another reason I was drawn to it!

speedreadersteve:
It's simple to pick up and start coding with, which is good for a beginner like me.  It also has enough power to it that I don't have to hop over to visual studio in order to create something like a project.

Butter-Swimming Butterfly:
1. For Windows users, the other primary IDE option has been Visual C++ during the past couple decades. Visual C++ just had more annoyances during the last times I've tried it.
  ~ For example, Code::Block's debugging (GDB) graphical user interface is superior to what Visual C++ (and other C++ IDEs which are available for Windows users) offered last time I tried. VC++ had an inconvenient command-heavy interface if I remember right.
  ~ Visual C++'s solution/project configuration system was stupid (and it might still be).
  ~ Also, Code::Blocks was designed to work with GCC (and MinGW). MSVC doesn't really support the C++ standard as completely as GCC. GCC is a good compiler suite for C++ programmers.
2. Code::Blocks has a graphic style that is tightly-fitted, mostly uniform (non-messy spacing between layout content), and adequately colorful. I think it looks sharp, so I like it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page