9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Julius Schmidt <aiju@phicode.de>
To: 9front@9front.org
Subject: Re: [9front] proposal: move common code from md, nes, snes, gb, gba, c64 to a libemu
Date: Fri, 11 May 2018 11:57:44 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1805111137160.15422@phi> (raw)
In-Reply-To: <1A03ECBC8C7788122EB7EDF476A31EC9@wopr.sciops.net>

it's basically sound.

some thoughts:

> - (?) added toggling fullspeed emulation when audio is enabled
by dropping samples?

i don't like that this is enabled with space.
i would prefer some more remote key, like `.

personally i think this is a misfeature. in other emulators i always find 
myself using it too much.

> - (?) dynamic rescaling from x1 to x16 for larger screens;
>  removed -2, -3
i think i've stated before i don't like this very much.
but i'll accept it begrudgingly, i think :).

> - profiling: now toggled at runtime, removed -T
good

> - fix for speed up after pausing emulation with audio turned off
reliable control of emulator speed might need control theory...

> - emalloc, as often reproduced in the emulators;
>  might be better off in libc or nowhere
moving emalloc to libc has been discussed many times and vetoed every
time.
not sure what you mean by 'nowhere'.

> - the signed typedefs might be better placed in /$objtype/include/u.h
yes i would like that.
we've postponed doing this too many times already.

> - another hacky library
who cares.

> - clumsy; input bit vectors are semi-arbitrary and adaptation in some
>  emulators is fairly bad; worse examples: snes and md
> - regkeyfn is not very useful as is
i would like this to be fixed.
why not just register all keys?
something like
 	regkey("left", Kleft, 1);
to register it as bit 1 in the input bitvector.

> - snes hires and md intla are ignored when scaling
that seems like it might be too confusing with automatic scaling.

> - maybe user programs should never care about scaling, and the library
>  should instead do some turbooptimized duff's device on screen flush
not sure.

> - can we merge 2600 even if it's buggy?
yes.


  reply	other threads:[~2018-05-11  9:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11  7:39 qwx
2018-05-11  9:57 ` Julius Schmidt [this message]
2018-05-11 11:08 [9front] " qwx
2018-05-11 20:18 qwx
2018-05-12 18:00 cinap_lenrek
2018-05-12 18:19 cinap_lenrek
2018-05-12 19:49 qwx
2018-05-13  5:04 qwx

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=alpine.LNX.2.00.1805111137160.15422@phi \
    --to=aiju@phicode.de \
    --cc=9front@9front.org \
    /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).