From mboxrd@z Thu Jan 1 00:00:00 1970 References: <201204181609.q3IG9mv9009569@freefriends.org> From: Francisco J Ballesteros Content-Type: text/plain; charset=us-ascii In-Reply-To: Message-Id: Date: Wed, 18 Apr 2012 18:35:46 +0200 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: [9fans] nix at lsub Topicbox-Message-UUID: 7808dca4-ead7-11e9-9d60-3106f5b1d025 If you consider a set of abstract widgets, reasonable enough, you could map t= hem to native implementations in -a browser -cocoa -gnome -add your one here. then, there could be a portable shared component speaking to those and gatew= aying to your favorite protocol (9p, ix), and you could have a clean interface and= reasonable bindings for it. cocoa was going to be my first move here, btw. didn't even start, though. -- using ipad keyboard. excuse any typos. On Apr 18, 2012, at 6:28 PM, Charles Forsyth wro= te: > i thought the easiest way to begin and be cross-platform would be to talk t= o a component running in a browser, > similar in principle to a viewer in Octopus. > a browser client will be needed anyway, and there is a browser on many thi= ngs (often only a browser); thus > your first step won't be your last, but it would cover a big distance. > it might also make it quicker to experiment. >=20