🚀 go-pugleaf

Dennis Jones wrote:

> I don't know anything about Python, but I don't think your problems are
> language-specific.  I think you just need a little more experience with the
> Win32 API.  Switching to Python might simplify some programming tasks, but
> you will still (presumably) be using Windows, which means you will always
> need a good grasp of the Win32 API.  Don't get me wrong though...I'm not
> saying you shouldn't learn Python...knowing several languages can only help
> you in the long run.


Well, I need to do some server side scripts and I *think* python is more 
C/C++ like than PHP or perl.  In the last couple of hours I wrote a 
script that enumerates all the .txt files in a folder and saves the 
names, sizes, and creation dates as tuples in a specialized python file 
- my first python script.  It's the basis that I'll build on for a 
script that I need that will compare the files in the folder now to 
those there the last time it was run and generate a web page to inform 
the user that a new file(s) is available.  But I think I *really* need 
to read the tutorial before I do any more! :-)

I do need more experience with the Win32 API and I do have the reference 
text - at my office.  I started in 1975 with FORTRAN, then basic, 6502 
assembly, Pascal, PLI, C, C++, and a tiny bit of Delphi on CDC, IBM, DG, 
Sun UNIX, and Windows PCs.  I've always used Borland compilers on my own 
computers and now my work Windows machines. My programming is to support 
the research group that I'm in so the code is specialized and has few 
users, sometimes only one.  I'm an ecologist (officially) and aircraft 
manager, too... So I don't work anywhere near full time programming, 
some of my knowledge is shallow, but I'm always learning.  I'd rather be 
programming than doing some of my other duties.  At least I'm allowed to 
work at home when I want to.

Our beta site: http://www.fireimaging.com