Code::Blocks Forums

User forums => General (but related to Code::Blocks) => Topic started by: pghtech on August 04, 2006, 08:57:44 pm

Title: Code::BLocks and other IDE's
Post by: pghtech on August 04, 2006, 08:57:44 pm
I figured this would be a good place to ask a general question of what you user's thoughts are on Code::Blocks as compared to other IDE's (i.e. Visual Studio)?

What are some of the things you can expect and not expect with Code::Blocks?
Title: Re: Code::BLocks and other IDE's
Post by: Pecan on August 04, 2006, 10:53:19 pm
Speed, efficiency, non-bloat, controllable, modifiable, pleasurable.

Title: Re: Code::BLocks and other IDE's
Post by: kidmosey on August 04, 2006, 11:15:41 pm
Speed, efficiency, non-bloat, controllable, modifiable, pleasurable.

pleasurable?  lol
Title: Re: Code::BLocks and other IDE's
Post by: Pecan on August 04, 2006, 11:27:10 pm
Speed, efficiency, non-bloat, controllable, modifiable, pleasurable.

pleasurable?  lol

Yes, it is pleasing to use. As opposed to annoying to use.
Title: Re: Code::BLocks and other IDE's
Post by: sethjackson on August 05, 2006, 12:19:07 am
Speed, efficiency, non-bloat, controllable, modifiable, pleasurable.

pleasurable?  lol

Yes, it is pleasing to use. As opposed to annoying to use.


Yes I agree.
Code::Blocks is cross-platform which is a must have in my eyes. :)
Title: Re: Code::BLocks and other IDE's
Post by: kidmosey on August 05, 2006, 12:43:03 am
Yes, it is pleasing to use. As opposed to annoying to use.

I understand... I just had strange ideas of a CB::Lube plugin when I saw "pleasurable" and had to laugh. :D

@sethjackson
I think the cross-platform is one of the major aspects of C::B... including the gdb front-end.

Also, I don't know if this could be filed under "modifiable", but how about extensible?  the primarily plugin-based design makes C::B infinately useful.
Title: Re: Code::BLocks and other IDE's
Post by: sethjackson on August 05, 2006, 02:51:18 am
Yes, it is pleasing to use. As opposed to annoying to use.

I understand... I just had strange ideas of a CB::Lube plugin when I saw "pleasurable" and had to laugh. :D

@sethjackson
I think the cross-platform is one of the major aspects of C::B... including the gdb front-end.

Also, I don't know if this could be filed under "modifiable", but how about extensible?  the primarily plugin-based design makes C::B infinately useful.

Right. Most other C++ IDE's aren't cross-platform AFAIK. Well Eclipse is, but it is written in Java IIRC. I think Ajunta may be also. Of course Dev-C++ (well it depends on how you look at it) VS, and XCode aren't cross-platform.
Title: Re: Code::BLocks and other IDE's
Post by: kagerato on August 05, 2006, 05:50:29 pm
Right. Most other C++ IDE's aren't cross-platform AFAIK. Well Eclipse is, but it is written in Java IIRC. I think Ajunta may be also. Of course Dev-C++ (well it depends on how you look at it) VS, and XCode aren't cross-platform.

You're right; Dev-C++ isn't cross platform.  It's VCL-based, and the VCL is a win32 wrapper.

As for Anjunta, it depends on too many gnome libraries.  You could get it running on Windows or Mac with some work, but the result would be about ten extra libraries all for one program.  At least you can easily re-use a gtk installation across several applications (gimp, gaim, and gnumeric).

Eclipse works well on Win, Mac, and Linux/GNU.  I've used it on all three and have been relatively impressed at how well the SWT integrates with each platform.  You need a 35+ MiB java runtime for it, though -- might be a problem if you're not building java applications.  Keep in mind that the IDE itself is around 100 MiB.
Title: Re: Code::BLocks and other IDE's
Post by: sethjackson on August 05, 2006, 06:08:24 pm
Right. Most other C++ IDE's aren't cross-platform AFAIK. Well Eclipse is, but it is written in Java IIRC. I think Ajunta may be also. Of course Dev-C++ (well it depends on how you look at it) VS, and XCode aren't cross-platform.
Eclipse works well on Win, Mac, and Linux/GNU.  I've used it on all three and have been relatively impressed at how well the SWT integrates with each platform.  You need a 35+ MiB java runtime for it, though -- might be a problem if you're not building java applications.  Keep in mind that the IDE itself is around 100 MiB.

That is why I never used Eclipse. I didn't want an IDE written in Java, and I didn't want to have the Java runtime either. Just my personal preference (I dislike Java to put it lightly). :)