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

Version control lack is a complete showstopper for C::B

<< < (2/2)

jarod42:
Some VCS do need integration to be workable.
For example, with Perforce, files are in read-only mode until we "edit" them
(so tools which edit the file must tell to Perforce to edit the file :-/ )
but as soon we don't need a "auto-lock"/auto-edit feature, I prefer to use dedicated VCS tool.

"Correct" VCS doesn't need integration.

nelson777:
"In the end - what version control system should we support? There are many - CVS, SVN, GIT, HG, Perforce, SourceSafe an so on... what shall we support? All of them? No way." - Morten
"What would you tell to people claiming they are missing version control integration if you were in our position? " - Morten

Morten... I understand your position. Really. But it's kinda like I understand hunger in today's world. There are reasons for it, maybe even good reasons. There are very understandable factors that lead to that. But people continue to die and it's absolutely unnaceptable no matter what.
As for C::B I was reading what you wrote, understanding, tried to see by your eyes, but as I was doing that I have my Eclipse CDT open with my project in it (you now, the one I started in C::B and imported to Eclipse because I need good version control support), with perfect version control integration for ALL major version control systems, file comparation, history (local and remote), author identification for code modifications, code refactoring, automatic make file creation, a fully customizable interface, many different code views and code filters, better code editing facilities and for the final kill the exceptional Mylyn plug-in that allows me to mantain an history of code modifications for a certain task.... case closed. And I'm sure you know I only mentioned some of the features.
I will end this post and get back to it. For now Eclipse CDT is absolutely the IDE king... and as the americans say... it's hard to beat the king.
Finally, I really wish you guys can make C::B a better IDE, but it really has to rise up to the challenges it faces.

-Nelson

MortenMacFly:

--- Quote from: nelson777 on April 10, 2012, 06:38:57 pm ---For now Eclipse CDT is absolutely the IDE king... and as the americans say... it's hard to beat the king.
--- End quote ---
You luckily have the freedom to chose, don't you? Before I came to C::B I was using Eclipse and I still have to use it for some projects. Everybody has its own priorities and needs. Yours are different so C::B is not for you. That's fine.

However, if people are not willing to take part in a community developing alternatives they have to stick to whatever the are used to use. You cannot really compare Eclipse to C::B in terms of development team and time used to develop. In Eclipse, you have WAY more developers, a strong financial background and a long-term history. If you were really looking for alternatives to that and are not happy with C::B I don't wonder. And to make sure you don't waste our time again: C::B will never reach the level of functionality like Eclipse in many areas, but it has enough other strong benefits that make it my favourite IDE over Eclipse (and I am only talking for myself).

Bye!

Navigation

[0] Message Index

[*] Previous page