Julian Hall wrote:
>
> One possibility would be to require memory to be accessed via macros defined
> in the plugin.h or whatever plugins would use; this could combine the speed
> of direct memory access with the flexibility of using function calls?
Yeah, that sounds fine to me. It's the API that
counts, anyway.
> >I was thinking about actions that originate with the GUI
> >but have global impact, like shutting down if the user
> >clicks the close box, or rebooting if the user clicks the
> >reboot icon, etc. These commands will need to be signalled
> >back to the main app.
>
> I would also like to be able to do things like select the system to run,
> etc, through the GUI as well as on the command line, or in the
> configuration file.
Okay, I think the VMWare way of doing things is fine
here. The VMWare user monitor accepts configuration
data from stdin. The configuration files used by
VMWare contain something like
#!/usr/bin/vmware
at the top, so you can simply do chmod a+x on the
config file and execute !!! So all you need is
to have a Windows.fmw, Linux.fmw, BeOS.fmw, etc.
and you execute the config file. I like that.
-- Ramon
