On approximately 5/14/2004 9:19 AM, came the following characters from
the keyboard of Jez White:
Well, when I compare what I have in my old build area (downloaded
snapshot) to what I now see via CVS, they appear to be not there. It is
not clear to me where they would then be added from, or what technique
of "not there" was used other than deletion :)
Humm. I'm wrong then. I was under the assumption that the examples CVS
folder was a relatively new addition:)
Maybe the confusion stems from what was in the "release" distribution or
PPM, vs what was in the source distribution. It has been my thought
that the tutorials and samples should have historically been part of the
release distribution, but they weren't... they were part of the source
distribution.
Many previous examples (even the one's that work) use none
standard coding, which just cause confusion - for me anyway:)
I certainly have no objection to samples being modified to use standard
coding, but I'm not sure what non-standard coding was used that was
confusing.
Many of the smaller examples are ok, but the larger examples use code that
hacks into the internals (typically for functionality that now exists in
base code). A smaller problem is that all of the old examples use OEM.
Yes, OEM was pervasive! It was all there was! I think it is still OK
to have OEM samples, but maybe they should be clearly marked OEM
samples, and perhaps a nice new sample that shows how to convert from
OEM to NEM would be nice.
If there isn't time to update the sample to use better coding, one could
add some comments to it (no risk in adding comments) describing the
non-standard-ness of the coding, but leaving the sample for whatever
educational value it might have. ??? I learned a good bit of GUI
coding from those old samples, although I agree that I got a bit
confused by some of them, also.
Good idea. I guess it's more of a question to who will do it?:) I don't mind
doing a few, but perhaps someone should "own" the task and divide it out to
those who are willing?
Yeah, "Where are the warm bodies?" is always a problem. Like you, I
wouldn't mind doing a few, especially when I write some test code to
learn how something works... a few extra lines of documentation, and
presto, a new sample. But it is always hard to find time to go back and
fix the old stuff...
I will rework my test code for GetOpenFileName and contribute it for a
sample. As I find minutes, I will try to address some of old ones. But
I'm about to be on vacation for a couple weeks.
I like the idea of having simple examples for all
controls/core functionality, (say treeview1.pl, treeview2.pl, listview1.pl
etc), as well as more complete applications, such as win32::gui notepad,
paint, calculator etc. Again it would take someone to own, organise and dish
out the tasks.
Maybe a start would be to put the following content as a file
(readme.txt ?) in the samples directory:
Goals:
This file is meant to inspire contributions to the sample programs
collection in this directory. Below is a list of sample code that
someone would like to see, or feels that it would have been helpful to
the process of learning Win32::GUI.
If you find yourself writing small programs to figure out how something
works in Win32::GUI, consider spending a few extra minutes adding some
comments, and contributing it as a sample program, so that it will be
easier for the next person to figure out the details of how to do what
you are learning.
Organization:
This directory is a great place to put single file sample programs.
Pick a name different from other names, of course.
For samples that require a small number of auxiliary files, if you can
name the files with a common prefix, so that the are all sorted together
by directory listings, then they can also go in this directory.
If there are quite a files, or the names cannot be grouped, then create
a new subdirectory to contain all the files of the sample.
Desired sample programs:
Treeview
.
.
.
More complex sample program ideas:
Program like Notepad using Win32::GUI
Program like Paint using Win32::GUI
Calculator program using Win32::GUI
--
Glenn -- http://nevcal.com/
===========================
The best part about procrastination is that you are never bored,
because you have all kinds of things that you should be doing.
