Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Further Development Direction? #13

Open
kexoth opened this issue Aug 14, 2017 · 0 comments
Open

Further Development Direction? #13

kexoth opened this issue Aug 14, 2017 · 0 comments

Comments

@kexoth
Copy link

kexoth commented Aug 14, 2017

As I saw in your examples you have 2 approaches:

  • Using Console.boot which actually is not that useful because:
    • Cannot subscribe to additional effects;
    • Cannot be an interactive part of the update because you only update Model -> Model which means you cannot intercept additional messages;
    • Cannot do additional customizations over the view outside the draw commands;
  • Using the functions for creating the assets, scene, sprites, display, keyboard events, etc.
    • This is also broken at this moment because those modules are not exposed in your elm-package.json.

About the first approach it seems to be easier to start developing & I tried to make a more convenient wrapping such as Navigation.
My idea was to have all the functions for a Html.program wrapped & further exposed for the developer to leverage them. This is a sample wrapped Elm program which does what I had intended .
I tried to implement that in your existing codebase but had issues over which couldn't surpass. This is my rework so far on Console.elm.

In my opinion it's better to continue in the second approach but to wrap most of the setup for the game-engine's state inside a module such as Console.

Great job so far! 🥇

@kexoth kexoth changed the title Further Development? Further Development Direction? Aug 14, 2017
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

No branches or pull requests

1 participant