Re: WIN32LIB
Gentlemen,
What you are discussing here is exactly what I had in mind when I tried to
write a "Win32Lib Tutorial". My main goal was also to learn Win32
programming by writing down what I ran into, and what solutions there could
be found. After posting a few of these "lessons", Wolfgang Fritz offered to
help me, translating things into HTML and putting together a nice user
interface.
Not too long after that, I discovered that Wolfgang was a better learner
than I am, his contributions increased and mine decreased. So now you can
call it his project, but he always is trying to encourage people to join in.
Maybe this is where you can jump in and write an introduction to Win32
programming, that can become part of the "Tutorial Project". Maybe it could
even be incorporated into the recent Win32Lib coding project?
Ad Rienks
----- Oorspronkelijk bericht -----
Van: David Alan Gay <moggie at INTERLOG.COM>
Aan: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Verzonden: zaterdag 12 augustus 2000 17:58
Onderwerp: Re: WIN32LIB
> > Does anyone have a suggestion for a place to start? Would a good
> > "introduction to basic concepts of windows programming" be the
appropriate
> > place to start?
> >
>
> That's the best place to start, John. Everything that WIN32LIB uses to
> function...controls, parent-child window relationships, events...is
derived
> from the Windows environment. What would be best for starters is a
> comparison between DOS programming (which everyone here has done and has
> control programming control over) and Windows programming (which a few
have
> done and rely on Windows API to meet their requests). I can already give
you
> one difference from my own experiences: DOS programs have a mainline you
can
> control, and are procedure-driven...Windows programs have no definable
> mainline and are dependent on triggered events.
>
> It should not be done in the manner Charles Petzold of Windows 95
> programming fame had done (with all due respect and apologies to his fans
> here in the group). Charles put too much time explaining how to do it
using
> a specific language and very little time explaining the "why". He didn't
> explain how the Windows environment actually worked and what all of the
> parts were. He just basically said "register this window, and do it using
> Visual C++ and you will do fine!". It's like saying to a budding
sailboater,
> "Just unfurl the sail and go" without explaining about the dynamics of
> sailboating, the parts of a sailboat, and the tricks and dangers of
> sailboating.
>
> David Gay
|
Not Categorized, Please Help
|
|
