Re: Standard Euphoria Library Project
Mike The Spike wrote:
> Wha?
> You like that scheme?
> Well, it's better than SeqLib.e, GFX.e and StrTok.e or
> some shit like that.
>
> I think if we wanna do something usefull with this
> project, we shouldn't all provide a sequence routine
> library or some lame shit like that.
> We could take advantage of this oppurtunity to
> actually code all those libraries we wanted for such a
> long time, but weren't able to code on our own.
>
> A multiplatform GUI would finally give our Euphoria
> programs a uniform look on all platforms.
> Maybe a LLama/Win32lib hybrid?
>
> And Mic and Jiri could spew out some fast 3D graphics
> rotuines so Euphoria games don't look like mode 13h
> Space Invaders clones.
> The games I saw in Euphoria were mostly clones from
> old arcade games.
> But that's not fair, since those arcade games were a
> few K in size and coded in ASM back in the 70s.
> Like this latest RPG is saw, what was it, you know,
> that RPG with the .bat file that points to something
> wrong, well, that's a 320*200*256 game written in a
> 32-Bit high performance programming language, with
> optimising compiler support.
> If it was a 160*144*256 game, it could be running on
> the damned Gameboy (in HighColor mode).
> When are we gonna see some Quake clones in Eu?
> The reason why we aren't seeing any right now, is
> because of a lack of multimedia libraries in Euphoria.
> C, for example, has access to OpenGL, Direct X,
> Allegro, etc. automagically. Just include a few files
> and you're set.
>
> Mike The Spike
A cross-platform GUI library would be quite nice, as would a
cross-platform sockets library etc. Perhaps we could build that into ESL
(Euphoria Standard Library) at some time. However, I think that the
"lame" sequence routines are a must, since they are one of the major
reasons behind this library. Since these simple routines are used so
frequently, they are the primary cause for namespace conflicts and
re-writing code. Few people would re-write win32lib every time they
wrote a Windows program, but people frequently rewrite these simple
routines. This is especially a problem in include files, many of which
define the same routines as globals, which can cause namespace
conflicts. While these more complex libraries you speak of would be very
useful, I'm not sure they are in the scope of ESL, as they are such big
projects. Perhaps such libraries should be included in ESL, but we
should at least establish some basic coding guidelines and frequently
used routines first.
Jeff Fielding
|
Not Categorized, Please Help
|
|
