for goplan9 i think the differences can be hidden in Go files with proper build directives (i.e. +build plan9 or +build !plan9). i think once you go past the naming convention and how a 9p connection is posted or opened, things should be the same for plan9 and posix-ish environments.
On Fri, Jul 10, 2015 at 7:37 AM, Friedrich Psiorz <f.psi...@gmx.de> wrote: > Thanks! > > I still think a real port would be better, and probably not too hard. > But your post made me think … maybe it would be nice to separate the > front end from the back end, so devdraw would be one possibility, the > native file system another and possibly an imported > 9fans.net/go/plan9/client a third one. > > But for now, I think I will just hard-wire the native file system for > Plan 9 and devdraw for all other OSs. > > Am 10.07.2015 um 12:18 schrieb yy: > > On 9 July 2015 at 16:52, Friedrich Psiorz <f.psi...@gmx.de> wrote: > >> Hi! > >> > >> I'm currently writing a graphical application in Go that I would like to > >> be able to run both in Unix and Plan 9. Currently the 9fans.net/go/draw > >> library only works in Unix, by connecting to p9p devdraw. > > I am sorry I do not have answers to your questions. But here you have > > a devdraw version which, instead of using Xlib, connects to a wsys > > service using 9p: > > > > https://bitbucket.org/yiyus/devwsys-prev/src/tip/util/9p-srv.c > > > > I was using it from Unix, but porting to Plan 9 should be quite easy. > > Then, go/draw would work without many changes. Of course, this > > solution is far from optimal (the path will unnecessarily be go/draw > > -> devdraw.9p -> wsys), but it should get the ball rolling. > > > > > > >
