My only experience with NPE is installing it to build flite. I don't know much about its internal workings. From my understanding, APE and NPE just provide functions that behave like the Unix counterparts.
If you have a simple program as an example, I might look into it. Having talked to the 9front devs, I will say that no one wants to maintain APE. Most advice is to take the opportunity to refactor and clean up to do it in Plan9 way, or just find a new way to do what the old program does.
@@adventuresin9 I'd love to see a guide on how to port SDL software, that'd be great, even a demo is fine, there aren't any resources online on how to port stuff to Plan 9
To a certain extent, there isn't much need for porting details, because most Plan9 interaction is just done through open(), read(), write(), close(). There isn't some special API to deal with. Like, reading the mouse is just opening and reading the mouse file. Playing sound is just opening /dev/audio and dumping PCM data into it.
Pure gold!
Hopefully this presentation helps more drivers to appear in plan9
Thanks, this is useful
Will you make a video explaining how to port stuff using NPE? It'd be great! Thanks for the awesome work you're currently doing btw!
My only experience with NPE is installing it to build flite. I don't know much about its internal workings. From my understanding, APE and NPE just provide functions that behave like the Unix counterparts.
@adventuresin9 Yeah, but I'm interested in any sort of porting guide, think it'd be a very valuable "lesson" :)
If you have a simple program as an example, I might look into it. Having talked to the 9front devs, I will say that no one wants to maintain APE. Most advice is to take the opportunity to refactor and clean up to do it in Plan9 way, or just find a new way to do what the old program does.
@@adventuresin9 I'd love to see a guide on how to port SDL software, that'd be great, even a demo is fine, there aren't any resources online on how to port stuff to Plan 9
To a certain extent, there isn't much need for porting details, because most Plan9 interaction is just done through open(), read(), write(), close(). There isn't some special API to deal with. Like, reading the mouse is just opening and reading the mouse file. Playing sound is just opening /dev/audio and dumping PCM data into it.