9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Russ Cox <russcox@gmail.com>
Cc: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9port libdraw
Date: Wed, 12 Jan 2005 21:08:49 -0800	[thread overview]
Message-ID: <3e1162e6050112210876644305@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a0501122105156aafc9@mail.gmail.com>

> Note that keyboard.c and mouse.c aren't actually
> compiled.  They're just reference copies of the Plan 9
> versions.

I figured as much when looking at the duplicate functions.

> 
> > I was a decent SDL programmer a few years back but I never
> > really did much with X11. :)
> >
> > Hopefully this will be more educational than frustrating.
> 
> If what you say about SDL being somewhat model-independent
> is true, then it shouldn't be too bad.  The only files you'll need
> to provide are equivalents to the x11-*.c in libdraw.
> Some you can stub out (like x11-cload.c, where you
> can just remove the if and its body), some will translate
> fairly directly (like x11-mouse.c and x11-keyboard.c),
> and others should have the non-X-dependent pieces split
> out of them (like x11-init.c).  In all, though, it's only 2,500
> lines of code, so it shouldn't be too bad.  And you definitely
> don't need to understand X.
> 

I guess what I need to know is what is expected in and out of some
of these functions and the best description I get is the existing X code.

Sometimes the data in  is just a void * like in the _ioproc function for 
keyboard.c... It's immediately handled through a Keyboardctl pointer though
so that's not so bad.

I've already done a copy of all the x11-*.c to sdl-*.c and am working on those.

> If you have questions, feel free to ask.

I certainly will :)


Dave

> 
> Russ
>


  reply	other threads:[~2005-01-13  5:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 21:13 David Leimbach
2005-01-12 21:23 ` William Josephson
2005-01-12 21:38 ` Russ Cox
2005-01-13  0:12   ` David Leimbach
2005-01-13  2:24     ` William K. Josephson
2005-01-13 21:21       ` David Leimbach
2005-01-13  4:52   ` David Leimbach
2005-01-13  5:05     ` Russ Cox
2005-01-13  5:08       ` David Leimbach [this message]
2005-01-12 22:40 ` Charles Forsyth
2005-01-13  0:16   ` David Leimbach
2005-01-13  0:39     ` Charles Forsyth
2005-01-13 17:33   ` [9fans] SDL on Plan9 was " Joel Salomon
2005-01-13 18:22     ` Steve Simon
     [not found] <200501131459.j0DExSMn023614@skeeve.com>
     [not found] ` <3e1162e6050113132167c99ec2@mail.gmail.com>
2005-01-15 19:18   ` [9fans] " David Leimbach
2005-01-15 20:00     ` David Leimbach

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=3e1162e6050112210876644305@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@cse.psu.edu \
    --cc=russcox@gmail.com \
    /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).