Re: Graphics mode 257 memory address(es)

new topic     » goto parent     » topic index » view thread      » older message » newer message

I have no argument that Neil is the best graphics engine implementation I have
seen for Eu, capable of most things.  It may not suit
everybody, though, for several reasons.

First is the bulk of such a library.  If I have a small demo that requires a
virtual screen and I want to send it to the list for
evaluation by all you out there, I'm sure most would prefer it to be as small as
possible.  This can also be significant during
downloads when one has a service provider as crappy as mine :)

Second is the inflexibility of the library, given by the very machine code
routines that make it so fast.  Any modifications to fit
a specific purpose usually mean begging off to the author.  Pete is a clever
programmer, and his code embodies concepts and
techniques whith which a user may not have enough familiarity to change.  This
goes for any such library that attempts to reach
beyond Eu for the hardware.

Third is the educational value of plugging in a ready made library.  Of course,
everybody's got a different agenda, and a ready
rolled high performance option should be made available, but nothing makes a
concept clear like doing it yourself.

Anyway, simply pointing out a graphics library to use isn't really answering the
question, is it?

I do agree that the available Eu libraries should be classified into groups, but
the defenition of 'best' from the user's point of
view might vary considerably.  Perhaps a classification more like 'beginner'
'intermediate' and 'advanced' would be more
appropriate, with beginner being 'example code', pure easy Eu where possible,
intermediate having hairy programming concepts or
calls to hardware, and advanced having assembler or mission-critical code.

One could then look to 'beginner' to learn how it's done, 'intermediate' to see
how others did it, or to 'advanced' for high
performance plug ins.

Just a thought....
Nick.

Ralf Nieuwenhuijsen wrote:

> Or he could just use Neil, and have the benefit of command lists using 100%
> machine code, without him having to worry about
> anything.
> I am confused, how little graphics demo's and game's use Neil. I assume most
> download all graphics libraries for Euphoria, so
> either half of the list are [.....], or they didn't understand it at all. Few
> demo's would be better of with the simplicity of
> specific hack to the VESA interface...
>
> And no, I didn't write Neil. But that's really not the point. It seems are
> re-inventing all wheels already available for
> Euphoria.
> Consider my EDOM, with Gabriel Boehme's binary print & get, there is no reason
> to even keep a copy of my EDOM routines, since
> his, almost do the same, but are a lot cleaner, faster, etc. That's logical
> and makes sense. I wouldn't suggest any one now to
> use those old bloated routines.
>
> Maybe we ought to make a package full of Euphoria libraries, the best of each
> section. (graphics-interface, win32 support,
> graphics-drawing/imaging, spell-checkers, database, etc. I mean its not about
> opinions, or anything, in each section one library
> really is better.
>
> Ralf

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu