wxWidgets vs Windows API
 

I've been waiting to try a GUI toolkit since I learned Windows API. For those that have used it: How is it? What can you do with it? What can't it do that API can? Is it worth abandoning API to learn? Since I found a GUI designer for it, I've been thinking about trying it. My major problem with tring it is: Will I not be able to do something in wxWidgets that I can do in API? Also, does it make programs too big? Because I also want to keep my programs as small as possible.

I can not answear your question; but I think you should learn what an API is. It might not be what you think it is, as I interpreted it when I read your post.
Take a look here: http://en.wikipedia.org/wiki/API

I'm talking about windows API (Application Programming Interface) I know what it is. I have programmed in Assembly for Several platforms. API is a compilation of calls that an operating system provides. For instance a restart call on a TI-83 Plus would qualify as an API call. Or the B_CALL macro(a restart call at 0028 followed by a double word) on the 83+.

I understood that you was talking about the Windows API, and I also know what an API is. There is a lot of beginners on this forum, and the post was written as you thought that API has something to do with the Windows API. Never mind then. ;)

/Klarre

I can see why. I'm just asking how good this tool kit is. I heard it's cross platform which is very nice. But the problem with Toolkits vs any API is that they lack some things. My major concern is that wxWidgets would be lacking something important. That and the hard disk space it will consume.

If your API wrapper doesn't cover what you need, just use the unwrapped stuff. Have you browsed or searched the forum for "wxWidgets"? Have you visited the site?

Yes... I have. It looks good. Says it's cross platform, uses object oriented code. But I can't find too much in depth documentation, besides I would really have to go in-depth with it to find out what's missing. I need a toolkit and fast. Currently, I use the api and am able to quickly create great and small apps quickly with the templates I created. I was just wondering if this would be any quicker. I do like api, but it's not the quickest thing.

EDIT:
I just read the wxWidgets wiki. It says that MFC has smaller exe size then it does. That's not good. MFC exes are bigger compared to exes made with Windows API... That just leaves one question, how much bigger are wxWidgets exes?

Generally speaking, the more advanced a toolkit is, the faster it is to develop in, and the more benefits it provides. This invariably comes at a cost of file size.

As with most things, it's a tradeoff. I personally subscribe to the notion that developers should laden as much work as possible upon the computer, as developer time is frequently more expensive than CPU cycles, RAM or disk space. You may have different views on this, though, and that's fine.

As an aside, APIs are not proper nouns, so it's "the Windows API" or "a device API", rather than just "Windows API". Also, the term API is more general than you seem think it is. When you access wxWidgets, for example, you'll be accessing it through an API.

I thought that you people were done attacking my useage of a simple term. So what, I used improperly, I thought you'd be smart enough to assume that I meant Windows API when I posted API.

It's funny, you say this when you just took time pointing out stupid semantics. :p In all seriousness though, I do have different views. All of those things are important. Wow, programming has indeed changed, if you view time more important than efficiency. I think that a program should be fast, consume as few resources as possible and be as small as the developer can get it with the resources at hand. I don't see why you wouldn't agree. If you think time is sooooo important, you shouldn't be wasting it on a forum, talking to an 18 year old kid about how API is not a pronoun.

This is not a very smart statement; it's plain stupid. You don't need to tell me how important machine efficiency can be, since I've been developing embedded systems since the advent of the microprocessor as a commercially feasible device. I have also been responsible for the development of multi-million dollar projects employing the services of many programmers, hardware engineers, and mechanical engineers. The success of any endeavor depends upon the health of the bottom line. As a mere boy, you obviously have no inkling of reality.