*.h

ok, say i hate windows and windows API and I want to use none of the VC++ .h file or VC++ at all and I am going to use some free C++ compiler today what *.h files could I get/find/use to make windows and do allot of the stuff Win32 API does for me? and what if what if i go crazy and want to write software for Win32, Linux, Mac, Unix, Solaris and have it all in one *.exe file, how would i do this?

Thanks

you want to write your own api?????

Quote:

---

Originally posted by ZanM
ok, say i hate windows and windows API and I want to use none of the VC++ .h file or VC++ at all and I am going to use some free C++ compiler today what *.h files could I get/find/use to make windows and do allot of the stuff Win32 API does for me? and what if what if i go crazy and want to write software for Win32, Linux, Mac, Unix, Solaris and have it all in one *.exe file, how would i do this?

Thanks

---

Do you want to write your own functions (API) to create and work with different windows(a bunch of pixels)?
You need to know asm for access and working with the BIOS video memory. Even when you draw pixels on the screen, you, sometime, use DOS interrupt(s) in the asm, which will not work on any other OS.

BTW, you can't directly call interrupts in VC++:D

no I was just curious to see if anybody thought it could be done without the API I had assumed it could not. as far a Pset type stuff goes yeah i would do it and I'm learning asm right now along with c++. i have this crazy nothin of making my resume in to a OS that runs on cd

i.e. they put in the cd or floppy and it boots to a gui with my resume and a bunch of sample applications and so on......

just curious, whats wrong with the API?

i love it (when it works right) I have been using it to make vb a better tool for years but sometimes I wake up in the middle of the night in a cold sweet because I had that dream about Bill pointing and laughing and saying I own you hahahahaha I own the world

so maybe i never had that dream but who says you didn't :o

Quote:

---

Originally posted by ZanM
i love it (when it works right) I have been using it to make vb a better tool for years but sometimes I wake up in the middle of the night in a cold sweet because I had that dream about Bill pointing and laughing and saying I own you hahahahaha I own the world

so maybe i never had that dream but who says you didn't :o

---

So, basically, you'll have to write everything API, that runs on all OSs, yourself.
Draw everything pixel by pixel, and create fancy windows so you are not using any OS API.

Quote:

---

Originally posted by ZanM
i love it (when it works right) I have been using it to make vb a better tool for years but sometimes I wake up in the middle of the night in a cold sweet because I had that dream about Bill pointing and laughing and saying I own you hahahahaha I own the world

so maybe i never had that dream but who says you didn't :o

---

thats not as scary as all the code you would have to write.

i can use routines already defined if i really wanted to linux is open source i could pick through it and find what o need and mod it a little then use it

like i'll every get the time anyway i have a wife and a kid and my wife hates it when i program at home :)

You can't program windows without the API. You simply can't. At least not unless you know the source code of windows and understand it thoroughly. And even then it's damn hard.
I don't know where to get instructions what is possible with linux, but I am sure there is one somewhere in the internet. There also should be APIs for things like KDE, window maker, WAPI (a linux emulation of the WIN API) etc. But it is the same here: you nearly can't avoid the API.