Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Compile single file

<< < (3/5) > >>

tiwag:

--- Quote from: kjliew ---...Single file project is overkilled in using an IDE. I would rather use "gcc -o Hello Hello.cpp" to build ...
--- End quote ---


that's my opinion too

Ceniza:
Well, that's something I liked of Dev-C++, and believe me, I've made a lot of little tests, well 133 non-wxWidgets related tests, and it's really handy to be able to compile them and run them from the IDE.

Code::Blocks has showed to be pretty nice to use with projects, workspaces and different targets, but why not to give the simple functionality too? I'm pretty sure it'll be nice for newbies and, once again, handy.

squizzz:
It sounds like it's useless option, BUT... it gives a nice feeling that IDE is lightweight and ready to go right after it starts. I agree that it's mostly valuable for newbies, who usually try dozen of book examples without even knowing what workspace/project/target is. Sometimes I do also find this useful, when I quickly have to try if some snippet works - guess what am I doing then? - yup, launching my old fellow Dev-C++ :)
Well, the fact that Dev-C++ does have it is IMHO good enough itself to have it too. Which IDE will newbies find easier to use (at least as an initial feeling) if they can't simply hit compile button and have their "hello world" program running?

I think it would be nice to have "Compile file" option, that compiles source file as a simple console application with default compiler, and eventually have the possibility to upgrade it to a project (*.cbp with this very file already included). Even if I'm not going to use it often. :)

David Perfors:
I agree that this functionality should be included. I think that we should make Code::Blocks usefull for a wide range of users including "example newbies" :lol:

tiwag:
i think the better approach is to give newbies the information WHAT they are doing actually
and not to make it as easy as possible to compile a few code-fragments without tinking about
what they're doing. In long term this strategy leads to a lot of "Bug reports" about
* cannot link, unresolved external xyz ,...
You just have to look, what's happening in the devcpp forums, most of the questions there
could be answered by themselves, if they had a few lines of documentation, how the
devcpp is working. Even more worse is the situation with wx-devcpp.
They glued together MingW and wxWidgets libraries and Includefiles in a completely
brainless way - obviously someone without knowledge of the power of several built-versions
of wxWidgets has done this - what leads to a terrible situation especially for "neewbies", if they
eventually want to try compiling some wx-widgets-supplied samples.
They can't then rely on the wxWidgets documentation and for all the devcpp's - with or without wx -
doesn't exist any relyable documentation. That is really confusing for newbies.

My opinion is, in general "newbies" are willing to learn - we have to give them proper documentation.

this is opposed to : "Do it like it works with our sample projects - or do it not ... live or die, basta"

Navigation

[0] Message Index

[#] Next page

[*] Previous page