User forums > Using Code::Blocks

My pretty Qt!

<< < (4/5) > >>

eranif:
Mm, 1700$? maybe for one platform...

I just purchased 4 Qt licenses for my team - the console edition (no GUI), costs us around 3300$ (!!) per developer (If we needed only 1 platform we would have used the OS API directly and not Qt)

Eran

incorrect user:

--- Quote from: JGM on September 19, 2007, 03:17:45 pm ---Hope you got another point of view!

--- End quote ---

Sorry, i didn't understand. You mean i need to learn more about wx and be sure that for some purposes it's better? I've understood that it's better to write the commercial software with wxWidgets. But C::B is free!
You see, i can't get the idea of mandrav: why it is not permitted to use not native events exchange code and widgets' drawing for cross-platform applications (in particulary C::B)??

P.S. No problem, i see that it's almost impossible to convert C::B for Qt, so, let it be so... :)

Biplab:

--- Quote from: incorrect user on September 20, 2007, 09:27:25 am ---Sorry, i didn't understand. You mean i need to learn more about wx and be sure that for some purposes it's better?

--- End quote ---

There are a large number of developers who uses wxWidgets. Don't assume they are morons. wxWidgets has been developed for last 15 years and it's a good alternative. It may not be the best toolkit in the world but definitely it's not a Toy toolkit to write only Hello-World applications.

You may like Qt. It's your choice. But that doesn't mean other toolkits are useless.


--- Quote from: incorrect user on September 20, 2007, 09:27:25 am ---I've understood that it's better to write the commercial software with wxWidgets. But C::B is free!

--- End quote ---

Neither we did say that you should start writing commercial apps with wxWidgets nor we said that all Free apps should be written with Qt. It's a choice of the devs and C::B devs prefer wxWidgets.


--- Quote from: incorrect user on September 20, 2007, 09:27:25 am ---You see, i can't get the idea of mandrav: why it is not permitted to use not native events exchange code and widgets' drawing for cross-platform applications (in particulary C::B)??

--- End quote ---

Because Qt has it's own event management system.


--- Quote from: incorrect user on September 20, 2007, 09:27:25 am ---P.S. No problem, i see that it's almost impossible to convert C::B for Qt, so, let it be so... :)

--- End quote ---

Yes, I said it earlier. We'll not change it to Qt.

incorrect user:
Sorry, maybe i'm incorrect, but i really wonder about this:


--- Quote from: Biplab on September 20, 2007, 09:56:27 am ---Because Qt has it's own event management system.

--- End quote ---

So what?? How does it hinder the IDE? Maybe it would be just more slow, but i believe it isn't noticeable...


Biplab:

--- Quote from: incorrect user on September 20, 2007, 11:00:22 am ---
--- Quote from: Biplab on September 20, 2007, 09:56:27 am ---Because Qt has it's own event management system.

--- End quote ---
So what?? How does it hinder the IDE?

--- End quote ---

Sorry, it was not the reply that you wanted.

Anyway, Non-native toolkits possesses Non-native look. This is not what we want. An Windows app looks more acceptable if it uses the Windows look'n-feel with which people are used to. Apart from that drawing a non-native control adds an extra processing overhead (Though unnoticeable for most common apps) on CPUs.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version