Re: Wiki for and at Euphoria
On Tue, 5 Sep 2006 12:20:23 -0500, Kat <kat12 at coosahs.net> wrote:
>Can you imagine the /wiki/win32lib.html in a couple years?
Umm. "Ask Derek" 
.
One thing that seems pretty clear to me is that a "win32lib" manual is
basically impractical. What I mean is that anyone who knows it really
can't write /anything/ that captures the whole enchilada....
There is obviously a reason I jumped ship from win32lib to arwen,
and we're close here. More I think that I felt I might be able to
understand the source of arwen rather than the documentation per se,
but now I am very intimate with arwen innards, I do look in horror at
the docs, not only because I realise it is not that great, if not to
be honest pretty awful for a novice to digest, but it is much the way
I would (still!) write it too!
Anyway, lets' not do that. Instead, let's answer:
"I want a treeview"
"I want a listview"
"I...
And put win32lib/arwen/direct api/... examples instead.
Of course all libraries would gain seeing how much easier it is in
something else, and/or the ones with more functions could hammer home
their benefits.
>Will it just point to the M$ SDK then?
imo there should definitely be "more" of that...
>Will RDS hire someone to maintain it for each windoze version?
.. but to files we have, like win32.hlp, rather than www.microsoft.XXX
- most links don't last 12 months in my experience[1]
There is no particular reason why it is down to RDS alone to document
future/backward incompatibilities, is there?
Regards,
Pete
[1] I would not struggle to find examples that are 8 years old, but I
recall it was a real pain last year, lot less since (that dead PC was
a bit of a cut-off point).
|
Not Categorized, Please Help
|
|
