1. Confidence
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
From: "Brian Broker" <bkb at cnw.com>
To: "EUforum" <EUforum at topica.com>
Subject: RE: Confidence
> You don't need to know how to fix it, you just need to expose
> the problems.
I'll second this.
> 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?
You are quite right. I apologise to everyone who cares about this. I've been
extremely busy in my paid job and have had to do lots of travelling. And I
really should answer every email too - at least just to acknowldge it. I do
keep them all and use them to update an "Issues Register".
I'm very close to releasing the next version - most likely in the next day
or two. I'll announce it on this list. A part of the new work is to make it
easier to maintain the code, especially working with a team. I've found lots
of tiny bugs in the process and I'm fixing them as I go. The fix is usually
simple but the testing is time consuming. I've also added lots more error
checking and assertions. These will be stripped out when the "compressed"
versions are released - after most of the bugs have been squashed.
> 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.
After this version, frequent patch releases will be a lot easier.
> 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?
No special joining is required. SourceForge is too slow for most people so
I'm not using it.
I'll keep submitting stable releases for the wider community but I'm not
likely to use it a development vehicle.
> 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...
Great, there too much reported anyhow 
> 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...
Fair enough.
> Hope I'm not being too harsh here...
Not at all. I encourage this feedback.
-----------
cheers
Derek Parnell
3. Re: Confidence
On Fri, 4 May 2001, Derek Parnell wrote:
> [ bunchuv stuff about win32lib ]
You can ignore my complaint some time ago about getTextExtent.
It mysteriously started working again, I guess after I rebooted.
Jerry Story
4. Re: Confidence
- Posted by jbrown105 at HotPOP.com
May 04, 2001
Some one who can create a better GUI file for Linux would be
appreciated too :)
jbrown
P.S. GraphApp is great for simple programs, but for something complex,
one needs something better, and the GTK.E file is improperly wrapped,
I believe, and thus unuseable, execpt for simple programs.
P.P.S. 2 examples: llama/gtk's MLE's set method fails, and
it's menubar is at the bottom, and not the top.
P.P.P.S. On this list, Irv once asked how David managed to get GTK.E to work,
I believe he opened a dll that the gtk main so file was dependant on.
P.P.P.P.S. Anyone have info on wrapping Xlib, or wraping something like
Qt for Eu?
TIA,
jbrown
On Fri, May 04, 2001 at 10:45:53PM +0000, Brian Broker wrote:
>
>
> 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
<snip>
>
>
Linux User:190064
Linux Machine:84163
http://jbrown105.1avenue.com
5. Re: Confidence
jbrown wrote:
> and the GTK.E file is improperly wrapped,
> I believe, and thus unuseable, except
> for simple programs.
It depends what you mean by 'improperly'. It worked for the version that it
was created for, but since then, it appears that the library has changed.
> P.P.S. 2 examples: llama/gtk's MLE's set
> method fails, and it's menubar is at the
> bottom, and not the top.
Sounds like some constant values were added to an enum list - so much for
being 'constant'. 
> On this list, Irv once asked how David managed
> to get GTK.E to work, I believe he opened a dll
> that the gtk main so file was dependant on.
Yes, it's dynamically linked. One of the problems with this is that if the
library underneath changes (such as constants or structs), code breaks. but
since we can't statically link the GTK library to Euphoria, it's the only
way to do it.
> Anyone have info on wrapping Xlib
I've done a bit of it; you can find the start of an XLib wrapper at:
http://www.lanset.com/dcuny/mwin.htm
> or wrapping something like Qt for Eu?
There is no pre-built wrapper for Qt available. You'll also have to create a
DLL; Qt is builds static library *after* running through the MOC
pre-processor. Keep in mind that Qt has some serious license restrictions
attached to it.
That said, there's a Qt wrapper for Perl that you might want to look at.
-- David Cuny
