om

/me is actually working on his Sphere OS idea ( stunned *ghasp* ).

The current #1 problem is this: 

Many methods in Sphere's API require information from the thread itself
to learn what permissions and contexts the thread has access to.

The interface object(s) are instantiated for all "Spheres" in the OS...

The current attempted design has a syscall object which receives
messages. It then looks around the current context for an interface
object which implements that message. If it fails, it sends the message
up to its counterpart in the parent context. 

This interface object must be able to query the calling THREAD, to learn
its previous context... 

Allowing threads to call interface objects with an explicit context
parameter would be an exploitable vulnerability to spoofing.

I've created, for now, a "BogusProcess" class... The key being to be
able to link a message all the way back to its process information
block... Suggestions? 


Problem #2 is debugging...

I'm attempting to code my first GUI... I would like to have some method
browsers, container class views, a heavily modified CommandShell, and a
number of varrious other buttons. 

I've gotten it to open a SystemWindow in a fairly appropriate manner,
(or so it would seem) the problem now is setting up a frame layout and
then making sure all the panes and buttons communicate with each other
in the desired fassion... 

What tutorials/wiki pages should I go to in order to get my fix of
information on the "extensions" based layout engine? 


-- 
Windows 3.11: Almost exactly 10 years old,
     and -400% slower than windows XP. ;) 

http://users.rcn.com/alangrimes/