Skip to content

Implement Auto Splitters#27

Closed
CryZe wants to merge 1 commit intomasterfrom
auto-splitting
Closed

Implement Auto Splitters#27
CryZe wants to merge 1 commit intomasterfrom
auto-splitting

Conversation

@CryZe
Copy link
Copy Markdown
Collaborator

@CryZe CryZe commented May 24, 2017

This implements Auto Splitters. This is still a huge Work in Progress as it's still entirely unclear which scripting language to use. These are the options:

  • Lua: This is probably one of the most viable options. Unfortunately it adds a C Dependency which can cause compilation / linking issues. I can't compile it on my Windows machine apparently, at least with the GNU Toolchain, which I definitely need to fix, in order to choose Lua. However I might also be able to just use the MSVC Toolchain from now on with livesplit-core. If that works, we probably want Lua. The bindings I would use would either be hlua, which I've used before, or the new rlua bindings.

  • Dyon: This seems to be the most viable scripting language written in Rust. It should be able to compile anywhere, but its target audience is game development, so it has a very specific style to it and doesn't have any 64-bit integers or hexadecimal literals, which is extremely bad for our purpose. Also it doesn't come with any standard library, so we would need to provide functions for basic things like working with strings, files, network, ...

  • Rhai: Yeah no. This one doesn't seem to have progressed enough to even be usable in any usecase for anybody, so this seems very much not like an option.

  • gluon: This is written in Rust and comes with its own standard library. The only problem is that its heavily functional, which might be too hard for most people writing the ASL scripts, so I'm not too sure about this one.

  • ketos: Seems kind of nice, but is a Lisp Dialect, so it looks pretty ugly to use. I'd prefer gluon's functional style over this.


Operating System Support:

  • Windows
  • Linux
  • macOS

@CryZe CryZe force-pushed the auto-splitting branch from a1e3f77 to 3f9cc01 Compare May 28, 2017 20:19
@CryZe CryZe force-pushed the master branch 3 times, most recently from beaab97 to 963b475 Compare June 8, 2017 13:09
@CryZe
Copy link
Copy Markdown
Collaborator Author

CryZe commented Jun 25, 2017

I should consider building it on top of this library: https://github.com/luser/read-process-memory

@CryZe
Copy link
Copy Markdown
Collaborator Author

CryZe commented Aug 15, 2017

Wren may also be a good scripting language to use.

@CryZe
Copy link
Copy Markdown
Collaborator Author

CryZe commented Sep 10, 2018

Considering we are going for a totally different approach now, I'm going to close this.

@CryZe CryZe closed this Sep 10, 2018
@CryZe CryZe deleted the auto-splitting branch February 13, 2019 03:31
@CryZe CryZe mentioned this pull request Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant