On 1/2/06, Denis Oliver Kropp <[EMAIL PROTECTED]> wrote: > Mike Emmel schrieb: > > Okay I went through fusion in detail. > > I don't see a reason why you can layer hessian on top but on the same > > hand I'm not sure its required right now. > > I've played with fusion a bit and I'm pretty happy with it. > > Only one question. > > > > Right now the way to get the fusion world is via knowing its index > > which is stored in a enviroment variable or given on the command line. > > I assume this is pretty much the only way so on the case of me adding > > a new shared world for application we simply need a new environment > > variable. > > Or we can easily connect intially to the main world to get the index > > of a secondary shared world. It would still need to be created in the > > master process ? > > As written in my last mail, such a world management should be added > to Fusion. One idea was to have a central Fusion Device for the stuff > outside of the worlds: creation, joining, discovering etc., but create > a new device on the fly when a world is created. >
Thats fine but I'd not put it into fusion directly. I'd first go find another meta manager that has nothing to do with fusion its job is to resolve url's and call right plugin to set up a service in this case a fusion service. If you make this split this same meta or service manger can be used to manage tons of different resources/services. Initally this can simply be a small process or thread in directfb with a url parsing library with a plugin to handle our fusion url. It should be designed allow non fusion plugins. Mike > -- > Best regards, > Denis Oliver Kropp > > .------------------------------------------. > | DirectFB - Hardware accelerated graphics | > | http://www.directfb.org/ | > "------------------------------------------" > _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
