Promoting Code::Blocks

[ironhead]

I'd like to start out by saying I've very much impressed by Code::Blocks, it's by far the best IDE I've ever used for MinGW.  It managed to convert me from using Vim as my IDE.  

I'd like to promote Code::Blocks on my site for the windows shell that I've written.  Beyond putting a blurb in the general about, I was wondering if there is a site button or something I should use?

Thanx again for Code::Blocks!

[rickg22]

No, there isn't a button yet. But I'm sure you can create one from the Logo that we have

[ironhead]

Hopefully this:

http://emergedesktop.org/e107_images/CodeBlocks.jpg

Is OK.

Cheers!

[Anonymous]

can you make that pic a bit larger ?
and I think all of us should also put some CB advertisement signature at our e-amail or login at other forums.

rob

[rickg22]

Um wouldn't that be spamming? Besides that would really skew search engines IMO. About the pic: I think that re-writing the text in the button should improve it.

[ironhead]

I'll do what I can with the text.  I'm not exactly a graphic artist.  

[rickg22]

Hey, I found that googling for "Free C++ IDE" and "Dev-C++" leads us to many forums (as we saw on the "how did you find out about Codeblocks" thread).

Why don't we google for these terms, subscribe to the appropriate forums, and recommend Code::Blocks in there? (Note: Don't make a sales pitch, just mention it and give your *HUMBLE* opinion).

[Yury Benesh (aka ybx)]

I think it's too early to advert C::B, it's pretty buggy and unstable and there's no support for separate debug/release/... configurations...

[Yury Benesh (aka ybx)]

Some people could be distracted...

[mandrav]

I think it's too early to advert C::B, it's pretty buggy and unstable and there's no support for separate debug/release/... configurations...

Huh?  :shock:
Are you sure you 're talking about Code::Blocks???
Buggy and unstable???
No debug/release configurations???

:roll:  :?:

Yiannis.

[David Perfors]

Some people could be distracted...

That could be true, but we need to get people who could tell us where the bugs are  :lol:
So let advertise

[rickg22]

I agree. If we wait until 1.0 to adverstise, what happens if someone finds a bug when it's too late?

[Yury Benesh (aka ybx)]

I think it's too early to advert C::B, it's pretty buggy and unstable and there's no support for separate debug/release/... configurations...

Huh?  :shock:
Are you sure you 're talking about Code::Blocks???
Buggy and unstable???
No debug/release configurations???

:roll:  :?:

Yiannis.

ooops! Did I just not find them??? Then, it's a reason to write a readme.txt at least. SO how to add different configurations to the same project, e.g. ANSI Debug, ANSI Release, UNICODE Debug, UNICODE Release and to run BATCH BUILD to produce only UNICODE Release and ANSI Release, for instance, like in MSVC++ ?

[rickg22]

Wait a second. When you say "debug/release", you mean for OTHER PROJECTS, right? :? (confused)

[mandrav]

ooops! Did I just not find them???

The "configurations" as they 're called in msvc, are the build targets in C::B. At least that's my understanding, not having used msvc. But since msvc projects are imported correctly, along with their "configurations", I 'm pretty sure it's the same thing.

it's pretty buggy and unstable

I still don't understand this assumption. I work with C::B all day, every day and I can tell immediately if it becomes unstable at some point in development. Also, immediately, I work on "stabilizing" it again...
I 'm not trying to say that it has no bugs whatsoever, but not the kind of bugs that would crash and burn it...

Yiannis.