hacker.org

I have some problem of WiniAPI codes,maybe you could leave your E-mail,and fsher@isbase.net,its mine.thanks.

FSHer wrote:I have some problem of WiniAPI codes,maybe you could leave your E-mail,and fsher@isbase.net,its mine.thanks.

You need to understand the structure of the language you're using completely before you use the WinAPI. Because it gives more power than you have in your language you're using and that doesn't means it easy to control.

If you do understand the language you're doing then please send a private message to me about your issue.

Try using .NET

Allosentient wrote:Try using .NET

Insanity.. You recommend people to use a .NET-language that's depending on microsoft and their filthy systems?

.NET dosen't give the user freedom to choose system. Kapitalistic populistic bullshit. That's what .NET is about.

WhiteKnight wrote:

FSHer wrote:I have some problem of WiniAPI codes,maybe you could leave your E-mail,and fsher@isbase.net,its mine.thanks.

You need to understand the structure of the language you're using completely before you use the WinAPI. Because it gives more power than you have in your language you're using and that doesn't means it easy to control.

If you do understand the language you're doing then please send a private message to me about your issue.

Y,I know what you mean,but i think i've master the basic API programming and have done some simple projects i know how to use APIs and what should happen when the fn returns,but don't know how it works.Maybe i need to learn something of NT's kernel.but it's really hard.so if something unexpected appears i don't know how to deal with. i know MSDN,but sometimes it's useless.

FSHer wrote:

WhiteKnight wrote:

FSHer wrote:I have some problem of WiniAPI codes,maybe you could leave your E-mail,and fsher@isbase.net,its mine.thanks.

You need to understand the structure of the language you're using completely before you use the WinAPI. Because it gives more power than you have in your language you're using and that doesn't means it easy to control.

If you do understand the language you're doing then please send a private message to me about your issue.

Y,I know what you mean,but i think i've master the basic API programming and have done some simple projects i know how to use APIs and what should happen when the fn returns,but don't know how it works.Maybe i need to learn something of NT's kernel.but it's really hard.so if something unexpected appears i don't know how to deal with. i know MSDN,but sometimes it's useless.

Because usually the WinAPI is the last resort, because it seems to be a threat to security for whoever using your program. Maybe... send the key logged information of that user to you.

WhiteKnight wrote:

FSHer wrote:I have some problem of WiniAPI codes,maybe you could leave your E-mail,and fsher@isbase.net,its mine.thanks.

You need to understand the structure of the language you're using completely before you use the WinAPI. Because it gives more power than you have in your language you're using and that doesn't means it easy to control.

If you do understand the language you're doing then please send a private message to me about your issue.

well,I read your msg back again,I'm sorry but i deem that maybe you don't know what winAPI exactly is,you talked about the lauguage,you mean winAPI is a programming lauguage? Do you have the choice of lauguage when you use winAPI's msg-mechanism to program codes?
Expecting more warm-hearted persons could give me a hand^_^

FSHer wrote:

WhiteKnight wrote:

FSHer wrote:I have some problem of WiniAPI codes,maybe you could leave your E-mail,and fsher@isbase.net,its mine.thanks.

You need to understand the structure of the language you're using completely before you use the WinAPI. Because it gives more power than you have in your language you're using and that doesn't means it easy to control.

If you do understand the language you're doing then please send a private message to me about your issue.

well,I read your msg back again,I'm sorry but i deem that maybe you don't what winAPI exactly is,you talked about the lauguage,you mean winAPI is a programming lauguage? Do you have the choice of lauguage when you use winAPI's msg-mechanism to program codes?
Expecting more warm-hearted persons could give me a hand^_^

The Windows API is the set of functions Microsoft provides to programmers to do things on a Windows operating system.

It comes from Microsoft and is therefore shitty. You shouldn't use it.

I'll elaborate on precisely why it's shitty. The documentation is poor, the API itself is poorly designed and overly complex, and Microsoft is liable to change it at the drop of a hat.

`Well, how do i program on windows, then?' you might ask.

Use a cross platform wrapper around the Windows API. It'll handle all the hairy, WinAPI stuff for you and you have the added benefits of a more stable, easier to understand API as well as the ability to port what you write.

canine wrote:The Windows API is the set of functions Microsoft provides to programmers to do things on a Windows operating system.

It comes from Microsoft and is therefore shitty. You shouldn't use it.

I'll elaborate on precisely why it's shitty. The documentation is poor, the API itself is poorly designed and overly complex, and Microsoft is liable to change it at the drop of a hat.

`Well, how do i program on windows, then?' you might ask.

Use a cross platform wrapper around the Windows API. It'll handle all the hairy, WinAPI stuff for you and you have the added benefits of a more stable, easier to understand API as well as the ability to port what you write.

Thanks for your advise,it's reasonable.,but WinAPI is really charming for me^_^ There are 70 percents people all over the world use MS's OS after all .Unix,linux are powerful,but is just suit for few people.

FSHer wrote:Thanks for your advise,it's reasonable.,but WinAPI is really charming for me^_^ There are 70 percents people all over the world use MS's OS after all .Unix,linux are powerful,but is just suit for few people.

Well, I think they're for everyone. Not everyone uses them and I recognize that and what I'm suggesting is that you use something that wraps the Windows API.

So if you write a long, complex program using it, you're stuck there.To use it on another operating system you'd have to rewrite it. Hell, you'd need to rewrite it if Microsoft changed the API on a whim.

What specifically are you thinking of doing with the Windows API?

canine wrote: So if you write a long, complex program using it, you're stuck there.To use it on another operating system you'd have to rewrite it. Hell, you'd need to rewrite it if Microsoft changed the API on a whim.

What specifically are you thinking of doing with the Windows API?

Just like Hook

FSHer wrote:

canine wrote: So if you write a long, complex program using it, you're stuck there.To use it on another operating system you'd have to rewrite it. Hell, you'd need to rewrite it if Microsoft changed the API on a whim.

What specifically are you thinking of doing with the Windows API?

Just like Hook

Hook?

canine wrote:

FSHer wrote:

canine wrote: So if you write a long, complex program using it, you're stuck there.To use it on another operating system you'd have to rewrite it. Hell, you'd need to rewrite it if Microsoft changed the API on a whim.

What specifically are you thinking of doing with the Windows API?

Just like Hook

Hook?

SetWindowsHookEx,CALLBACK HookProc

FSHer wrote:SetWindowsHookEx,CALLBACK HookProc

I'm not particularly familiar with the Windows API. What would you use SetWindowsHookEx to do?

Watch keyboard/mouse input?

Also, what language are you using?

Grand_Master wrote:

Allosentient wrote:Try using .NET

Insanity.. You recommend people to use a .NET-language that's depending on microsoft and their filthy systems?

.NET dosen't give the user freedom to choose system. Kapitalistic populistic bullshit. That's what .NET is about.

Eh? It is a superior tool for working with Windows. I did the challenges on this very website by using almost nothing except .NET. If anybody cared about Linux, there would be more people working on the Linux version of .NET (Mono), but I guess you guys will be stuck using tools developed in the 70's and 80's (and next time come up with a better argument as to why the technology is better, ad hominem against Microsoft is not an argument).