1. RE: Confidence
Hey Euman,
If you've got the courage to write a win32 prog without the aid of
win32lib then you are just the type of person that should be helping the
win32lib team. I'm not an official member but I've sent plenty of
emails to David Cuny (way back whan) and Derek Parnell when I've found
issues. You don't need to know how to fix it, you just need to expose
the problems.
In the past, some of my inquiries and/or requests have gone unanswered
but I would imagine that these guys get tons of stuff in their boxes and
even less time to respond to them all (or remember to do so). But it's
difficult to know if your input is being heard when there are no new
releases. So Derek... what the heck is holding version 0.56?
The only way you can get feedback and bug reports is with frequent
releases. My feeling is that these should come out at least once a
month, even if it only fixes a few bugs. I know I've given you email
that fixes at least one bug and/or have given you at least one possible
addition to the lib.
Do I have to officially join the win32lib team to have my emails / bug
reports / input considered? If I join, do I get a copy of the 'bleeding
edge' every few weeks? Is the SourceForge site even being used anymore?
I could go on but I won't because I know what 'real life' is like. I
just wish we (users) could get some more betas. Personally, I have no
idea what might be fixed and what still needs fixing so I won't be
giving you further feedback on 0.55.1. I think there might be other
users who feel the same way...
I hope you know that I'm not afraid to 'dig in' and submit fixes when I
find the time but I don't want to waste my time with fixes that are
already covered...
Hope I'm not being too harsh here...
-- Brian
Euman wrote:
> Now now, I should've worded that differently.
>
> TRUTH:
> I kept running into bugs in *MY OWN CODE*
> simply because I dont have the understanding.
>
> TRUTH:
> Win32lib would be much faster if it were streamlined but it's not to
> retain
> that ease of use variable. .
>
> TRUTH:
> Yes, there are bugs associated with Win32lib but they are being
> addressed
> and eventually it will be a great library of very common and usefull
> utilities.
>
> TRUTH:
> When my abilities are at a level to contribute to the library I will but
> at this
> time Im just a puppy when it comes to Windows programming.
> If I can learn the particulars of the WinAPI, I will be of much better
> use
> with bug reports and with additions. Anyone can write a program in
> Win32lib but I dont want to be just anybody I want to know what my
> program is doing at all times.
>
> Im sorry Derek if you think Im letting you all down
>
> TRUTH:
> I have every belief in the Win32lib teams success.
> And Wish you every bit to boot.
>
>
> Euman
>
>
>
> > Thanks for the vote of confidence!
> >
> > -----------
> > cheers,
> > Derek Parnell
>
>
>
2. RE: Confidence
> -----Original Message-----
> From: Euman [mailto:euman at bellsouth.net]
> TRUTH:
> Win32lib would be much faster if it were streamlined but it's
> not to retain that ease of use variable. .
Yeah, it's a tough line to walk. I think that once we're able to split the
library up you might see some performance gains. It should also be a little
less intimidating for people to take a look at and find some optimizations.
> TRUTH:
> When my abilities are at a level to contribute to the library
> I will but at this
> time Im just a puppy when it comes to Windows programming.
> If I can learn the particulars of the WinAPI, I will be of
> much better use
> with bug reports and with additions. Anyone can write a program in
> Win32lib but I dont want to be just anybody I want to know what my
> program is doing at all times.
Good luck. :) But I think you're at least at the level (in terms of Windows
understanding) where I was when I started messing around in Win32Lib. I
found that most of the API works in a fairly similar manner, so once I
figured out one piece, the next chunk I tackled was that much easier. A lot
of it is understanding how C works, since that's what you're communicating
with.
Besides, there's still lots to do. IMHO, if you find something that you
think should be different, it's a good thing to bring that up, but it's a
great thing if you code a [partial] solution. That's how this project seems
to have grown since Dave started it. It's just too large any more for one
person to do everything.
> Im sorry Derek if you think Im letting you all down
I don't think so. Frankly, once you've played around in the API a bit, I
suspect you'll eventually come back to Win32Lib (for one, because you won't
want to duplicate the work that's been done) and have some great ideas,
along with the knowledge of how to implement them.
I think it's to be expected that people get a little testy when their
programs stop working like they used to, or when the documentation's not
clear enough or synchronized with the code. I know I've seen it since I
started working on Win32Lib (you know who you are :). Once you start
changing/adding things, you've assumed responsibility for this whole project
(I'm SO glad Derek stepped up to the plate on that one!), at least in the
eyes of the users.
I know I haven't always been very responsive to bug reports or feature
requests on the sections I've worked on, but like Derek, I do attempt to
keep up with them and address them all.
> TRUTH:
> I have every belief in the Win32lib teams success.
> And Wish you every bit to boot.
Thanks.
Matt Lewis
