Why I choose SDK over anything else

[Patrice Terrier]

Because

• SDK is the only way to have direct access to the core Windows API.
• It doesn't use a propriatary syntax nor it hides you what is going on behind the hood.
• It is the only common denominator understood by all compilers including DotNET.
• It keeps your code small and fast.
• It allows you to write procedural code that is not harder to learn than OOP.
• It allows you to use ALL the Windows controls.
• It is easy to use with third party DLL, because DLL are the core meat of SDK.
• It handles ALL the Windows message and structures.
• It is not a dead end, because Microsoft despite what they say is always enhancing it.
• You are no tied to anybody else to write your own controls when you need them.
• There are literally millions of SDK source code examples over the NET.

And last, but not the least, ask you why third party addon providers are only SDK coders.

Patrice Terrier
www.zapsolution.com

[Eros Olmi]

You convinced me to go with SDK and abandon DDT.

What about few simple code for SDK UI dummies like me?
Maybe a specific forum for SDK beginners using PB ...?

Ciao
Eros

[José Roca]

 
You can start with the Hello World programs here:
http://www.jose.it-berater.org/smfforum/index.php?topic=72.0

And then follow with the Charles Petzold examples:
http://www.jose.it-berater.org/smfforum/index.php?board=5.0

[Patrice Terrier]

Eros

Do yourself a favor put your hand on Charles Petzold Windows programming book at Microsoft Press.
And I would grant you for the fifth edition if it is still available.

Everything is explained there, with a bunch of C examples, very easy to translate to PB because they are plain SDK, thus the syntax is the same!!!!

Portability is my keyword, avoid propriatary syntax like the plague or accept to become the hostage of somebody else

[Eros Olmi]

Patrice,

I have in front of me, exactly Fifth Edition. I was just "ironic" with "dummies like me"

In any case your indication is the best one. Many new users will come here in future and for what it is in my possibility I will driven all people approaching PB to José forum.

Ciao
Eros

[Paul Squires]

The single biggest improvement to my programming skills was to learn SDK programming. It was at times a pretty slow process because my knowledge of C was limited at best. I got the Petzold book, Rector & Newcomer, etc... It has taken me several years to finally understand enough of it to beome somewhat proficient. Everyday I browse through chapters in the books and find new things that I didn't know.

The whole process of learning SDK can be overwelming at first - extremely overwhelming. A lot of people don't have the time or patience to learn it in pieces - they want to know it all immediately. My advice, learn the basics about messages and controls, but save the more indepth topics like GDI (DC's, drawing, graphics) for later. It wasn't until I had to write some custom controls or enhance FireFly itself that I really needed to learn GDI stuff.

DDT is very limiting for all but the basic type of applications. Sure, you can get a program up and running quite quickly but when the time comes to do something out of the ordinary (and that time WILL come) then you are usually stuck by a DDT limitation.

The one thing that really bugs me are the people who fear monger that SDK style programming is difficult and should be avoided like the plague.    The SDK is simply a set of functions pre-built into Windows itself. Why wouldn't anyone want to tap into that? I see many times where people struggle trying to do a simple task using BASIC constructs only to later find out that one or two Win API functions could have replaced their whole code. Don't get me wrong, there are also many examples of BASIC functions that are awkward to code in WinAPI, but unless you are exposed to both types of programming then you can never decide what the best option to choose is.

Bottom line: If you are serious about being a programmer and want to progress your skills then you have to learn SDK style programming (WinAPI). You are limiting yourself if you don't. It will take time, you'll be frustrated as hell, but in the end you'll notice the difference - big time.

[Patrice Terrier]

Many SDK examples have been posted in 1997-1999 and they are still available in the archive forum, or in POFF.
and POFF is also one of the most valuable place to learn from.

I have for myself provided many SDK examples either on the forum or with the different trial version that can be downloaded from my web site.

However since most new comers were biased with DDT, I stopped posting new SDK examples.

Perhaps we could exhume some good plain SDK examples and post them here in a dedicated SDK section.

Patrice Terrier
www.zapsolution.com

[Donald Darden]

Sounds like a good idea to me.  Why don't you consider it, and tell us what you need or how you want to do it?

[Kent Sarikaya]

I am confused here a bit. MS Vista was delayed because it was totally rewritten as noted after the inner battles between the old school and new school guys at microsoft. Is all that OS  work a layer above the windows api that has been there all along then?

[Patrice Terrier]

Fortunatly the good old API (name it FLAT API) is still there, buried low in the Windows root.

A good example of that is my GDImage (written with PB) that works like a charm with DotNET applications.

[Patrice Terrier]

Don

Sounds like a good idea to me.  Why don't you consider it, and tell us what you need or how you want to do it?

That would require a "SDK source code only" dedicated section, and a short explaination to tel us how to upload code there.

[Kent Sarikaya]

I guess time to learn api programming then if it will be here for time to come. That is good to know! Thanks.

[Paul Squires]

I am more than willing to help with SDK examples.

If we can get Dominic on board as well then we would have a great knowledge base to work from.

[Patrice Terrier]

I have exhumed 2 of my SDK examples to post them here,
when a dedicated "Only SDK source code" section become available.
Also I would like to know what to do, to upload the files there?

Patrice Terrier
www.zapsolution.com

[James Klutho]

For the people who choose the SDK approach, how do you incorporate dialog boxes?  Do you use DlgEdit etc? Do you use windows with their own message pumps (like Firefly)? Other variations?  Having to deal with the 2 "Window Types" in a typical application has always been a turn off for me in SDK programming.  Though DDT has it's short comings, it's simplicity is a nice.

Do people use SDK for the main loop and DDT for dialogs?