9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Friedrich Psiorz <f.psiorz@gmx.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Porting 9front.net/go/draw to Plan 9
Date: Fri, 10 Jul 2015 16:37:16 +0200	[thread overview]
Message-ID: <559FD89C.4010700@gmx.de> (raw)
In-Reply-To: <CADErNDtEQweaODiL7PYDs7-iu8m2HGFbefaxC6-cjobPewij3g@mail.gmail.com>

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.psiorz@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.
>
>




  reply	other threads:[~2015-07-10 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 14:52 Friedrich Psiorz
2015-07-09 14:55 ` [9fans] Porting 9fans.net/go/draw " Friedrich Psiorz
2015-07-09 15:03   ` David du Colombier
2015-07-10 10:18 ` [9fans] Porting 9front.net/go/draw " yy
2015-07-10 14:37   ` Friedrich Psiorz [this message]
2015-07-10 15:09     ` Skip Tavakkolian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=559FD89C.4010700@gmx.de \
    --to=f.psiorz@gmx.de \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).