[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FreeAES

 >> How about combining efforts and calling it FreeAES ?
 >
 >I think internally they are quite different - Craig Graham (XaAES main
 >author) had some interesting ideas using pipes (and he always suggested
 >changing to sockets, but that never got done). 

Yes, /pipe allows it to work cleanly under memory protection, AFAIR.

Thought:
There should be a tutorial about the usage of pipes and shared memory.
Using those in applications would improve safety of memory protection,
since they're MEANT to be shared zones.

 >> Generally, I like XaAES's idea of a loadable GUI, à la X, which is
 >> definitely welcome within a multi-user MiNTOS environment.  
 >
 >Both XaAES and oAESis implemented a few things that aren't in AES 4.1,
 >and I dont think are in N.AES:  XaAES has windowed alerts that only 
 >blocked the affected app. 

This is really cool. Making all alerts into non-modal windows
should have been done in all AES already. I wonder why others 
(N.AES and Magic) haven't done it; it's one of those things I
think are definitely needed as an AES upgrade.

 >> XaAES and Win95 both derivate from X (window gadgets, etc.), AFAIR.
 >> However, if these GUI are RSC-based, this can be easily customized.

I actually like the idea of XaAES having X look (gadgets, etc.) and
features (ie: loadable through networking), but still being an AES 
(ie: GUI that can run TOS software).

I guess it's pretty correct, if I state that many people on this list 
dream of an X clone that happens to be an AES able to run GEM apps,
especially if it becomes portable for Linux 68k, don't you think?


----------------------------------------------------------------
 Martin-Eric Racine           The Atari TT030 Homepage with FAQ
 FUNKYWARE CREATIONS inc.     http://members.tripod.com/~TT030/
----------------------------------------------------------------