User:Mulehollandaise/Interpreters TODO

From IFWiki

Following this thread, this is an attempt to list some of the work that needs to be done on some interpreters. This encompasses bugs, features, and even ideas for new projects.

Gargoyle

Project page: [1] Issues list: [2]

Reviving the project

- Need an official maintainer (is there one?)

  • Skills : C, time

- Report bugs

  • Skills : none?

Bugs that need to be fixed

- Fix bugs on the list of issues

  • Skills : C

- Fix bugs in Glulxe: "Fix the scrolling delays that have been reported?" (from zarf's list)

- Wade: people have hacked Gargoyle just to get a popular game to run (eg Counterfeit Monkey)

- Wade: sound on Mac (are we talking about the Glulx terp?) have bugs, not longer up to date, out of date with glk

- I think the Linux version of the frotz in Gargoyle has a bug where some one-letter commands are not recognized, but I could be wrong (todo: test and see)

Supporting more formats

- Support TADS games with version > 3.1

  • dddddd needs help with adapting his Linux code to multiplatform: [3]
  • Skills: Multiplatform C/C++ and jam required. Bonus if TADS and gargoyle codebases familiarity.

- TADS webui support

  • I think this means support HTML TADS ?

- Support ADRFIT 5 games?

- Use the "very latest" Alan interpreter

  • Robert DeFord's Onaar (IFComp2015) patched Gargoyle so that it used the latest Alan interpreter
  • Skills: see with Robert DeFord

Other

- Add "Preferences" UI


Parchment

Project page: [4] Issues list: [5]

- allow CSS stylesheets to be passed in URLs, implement timed effects, autosave system, etc.

  • Skills : JavaScript, Z-Machine knowledge

- Is the buglist on GoogleCode still relevant?

Zeugma

- Detailed instructions on how to use this

  • Skills: C64 and multi-function cartridges (like 1541 Ultimate)

- Accents are not displayed yet

  • Skills: being awesome at C64 programming

- perf improvements? (Inform 7 games are way too slow)

  • I doubt it's possible since the author seems pretty awesome at C64 stuff
  • Skills: being awesome at C64 programming

Glulx/Glk Spec

Look at Zarf's list and help him!

- Glk 2.0 (integrate HTML and CSS) + change interpreters to fit the spec (see the post)

  • Skills: don't know

Quixe

Project page: [6] Issues list: [7]

- Implement sounds

  • Skills : JavaScript, Glulx knowledge

- Implement style hints? Or wait until the CSS-style stuff is implemented?

- Detailed instructions / documentation? (kind of like that

  • Skills : fiddling with zarf's tools until you get it right, clear writing

Glulx-TypeScript

- Implement Templates

  • TypeScript, JavaScript, HTML, CSS, Design, Inform 7 (story and extensions)

iOSGlk

- Graphics and sound - Merge data-import/export from iOSGlulxe to iOSFizmo (ability for interpreter to import and export save files)

Twisty (Android)

  • Skills : Android/Java, Z-machine

Releasing games

- Write a tutorial on how to release a standalone-app of your interactive fiction (Inform, in particular)

  • Some people use NSIS to create bundle; others say "rename WinFrotz.exe or Gargoyle.exe so it has the name of your game and it'll start it automagically"
  • Skills: writing a clear tutorial for multiple platforms and formats

- How do you do it on mobile?

  • iOS: is there a good tutorial for iOSfizmo?
  • Android: is there *any* way to do it?


Other

- Mobile interpreters? (on Android, iPhone, etc)

  • Skills: unknown yet

- A Choosatron-style interpreter (that prints the output on 'receipt'-sized thermal paper) would be amazing

  • Maybe we can use a Rasberry Pi for that (frotz is available on it + some people (see http://frederickvandenbosch.be/?p=1297 ) interface raspPi (and its touch screen) and thermal printers
  • Skills: Arduino, code, etc.
Retrieved from "https://www.ifwiki.org/index.php?title=User:Mulehollandaise/Interpreters_TODO&oldid=72854"