Re: Introductions

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

1->> Enthousiasm

>My current direction with Euphoria is to make more stereo toys for the
>headset, as well as trying to create more desktop style applications.
>Eventually, I'd like to have a small computing environment that allows
>me to take advantage of the 3-D capabilities of the headset, allowing
>a 'surround environment' as well as stereovision. With Euphoria, I
>can disregard a lot of the overhead, and get right to the application. I
>love that!!


Way to go Euphoria... VR helmet Programming in Euphoria sounds pretty
cool...

2-->> More suggestions (I just keep spitting these suggestions out)

A new data type called routine. That's what I want. It's value can be
printed and stuff like an integer, but the use can be so much faster since
the checking and actual pointing to the routine can be done when a value is
assigned to this.

Also it looks a lot better.

    procedure MCGA_Pixel (object x, sequence pos)
        .. code ..
    end procedure

constant routine my_pixel = routine_id ("MCGA_Pixel")

my_pixel ({3,3,4}, {100,100})
    instead of:
call_proc(my_pixel, {{3,3,4},{100,100}})

And it has to be faster.. (which should be possible using a special data
type.
Also it would be nice if we could call built-in routines also.

Please Robert (or any1 else), if you disagree, please specify why not..

Ralf

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

Search



Quick Links

User menu

Not signed in.

Misc Menu