Re: Standard toolkit
Pete Lomax wrote:
>
>
> On Fri, 01 Jul 2005 18:22:31 -0700, Jason Gade <jaygade at gmail.com>
> wrote:
>>Arwen is Windows-specific, isn't it?
<snip>
>>Just wondering because if a set of libraries is recommended as a
>>standard "user toolkit" it should be cross-platform. That's why I was
>
> Just because something is not xplat should not be a reason for
> refusing to recommending it. As a bad example, perhaps, I use dir
> (or Explorer) on Windows and ls (or Konqueror) on Linux. Depends.exe
> is strictly windows-only, since it examines .dll files, but should
> still feature somewhere on any recommended utility list. Sure, put
> these things lower down the list, but don't exclude them.
Okay. I was actually trying to avoid the gui library portion at this
point anyway and I wanted to concentrate on utility portions. There are
a lot of gui libraries available right now, both cross-platform and
platform specific. I think cklester's site covers the situation pretty good.
>
>
>>thinking that wxEuphoria would be a good recommendation for
>>gui/networking toolkit. I know that Win32Lib is much more mature but it
>>is Windows-specific (for now). I still think that it is probably a good
>>example of how a library *should* be written but I could be wrong since
>>I haven't examined it extensively either.
>
> Win32lib is indeed stable and feature rich. However I don't think
> anyone would actually say it should be used as an *example* of how a
> library *should* be written. That is not the same as saying there is
> no high-quality code in there, but *starting* a new library, I can't
> imagine a worse way than attempting to copy win32lib.
> (I may be talking at cross purposes here; the exposed API of win32lib
> is in general exceptional.)
>
> One of the things about well-written code is that it is highly
> subjective. In fact, the sole purpose of attempting to craft
> well-written code is that more people can readily understand it.
> I will be interested in reviewing whatever you finally declare is
> well-written.
Well, that's the problem. I'm not very good at reading source code.
Actually, I can usually understand small pieces of the puzzle but then
trying to take a step back and understanding the complete structure is
difficult. That's probably why I've never moved beyond beginning
programmer despite years of study.
But my current goal is to look at the OpenEU spec and kind of see what
can be written into a library instead of directly into the language,
what kinds of other utility routines are needed and/or regularly used by
the community, and what features other languages have either in their
libraries or core language that could be used in a Euphoria library.
I'm not even saying that I'll come up with something, I'm just surveying
the scene such as it is. I'm thinking of trying my hand at another
project but I've never written gui code, database code, or networking
code and the project would require all of that.
It looks like aku saya has come up with a library project that I want to
check out as well.
>
>>As per Christian Cuvier's suggestion I am kind of surveying what kind of
>>library routines are currently used by programmers in Euphoria. I think
>>that is a good start towards a user toolkit/recommended set of add-on
>>routines that everyone should have available.
>
>
> CK has a section on his web page devoted to this topic.
>
> Regards,
> Pete
>
--
==============================
Too many freaks, not enough circuses.
j.
|
Not Categorized, Please Help
|
|
