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

Isolated Examples or Game Templates? #519

Open
Swivelgames opened this issue Sep 3, 2023 · 8 comments
Open

Isolated Examples or Game Templates? #519

Swivelgames opened this issue Sep 3, 2023 · 8 comments

Comments

@Swivelgames
Copy link

It'd be an awesome way to jump start new users into the game engine if the examples were isolated, or if there were "Game Templates" that provided some pre-implemented game mechanics like the examples show.

Primary motivation here is that the format that the examples are in, and the format that the init script produces, don't immediately parallel.

It would be super helpful if each of the examples were isolated, potentially following a similar layout to fyrox-template init. Although, that could potentially result in duplication of a lot of code.

A bigger ask would be to add an option to fyrox-template init like --example x that would initialize the project with the example implemented in it. That would make it incredibly easy to dive right in and start tweaking different things, while following the layout that init implements.

Summary

  • examples/ dir does not parallel fyrox-template init layout, potentially making it difficult for newcomers to understand how the examples apply.

Possible Solutions

  • Add fyrox-template init --name x --example y to initialize a new Fyrox project with the specified example already implemented
  • Update examples/ to follow fyrox-template init project layout
@mrDIMAS
Copy link
Member

mrDIMAS commented Sep 3, 2023

You absolutely right. I though about this many times, but postponed it since I was quite busy in real life and had forces only to implement engine's must-have functionality. I also thought about adding a standard modules, such as character controller etc. to have the most common parts ready to be used right away. Now I have more free time and could start implementing all of this.

@mrDIMAS
Copy link
Member

mrDIMAS commented Sep 13, 2023

So, I created a separate repo for the demo projects - https://github.com/FyroxEngine/Fyrox-demo-projects. Now I'll gradually add more and more projects to it and when there will be at least few medium sized demos, I'll delete all the outdated examples from ./examples directory of the engine.

@Swivelgames
Copy link
Author

Nice! I like it! This is great. There are so many good examples in ./examples, but having them mirror the layout of fyrox-template init will be super helpful.

@mrDIMAS
Copy link
Member

mrDIMAS commented Sep 17, 2023

Yeah, I'm currently transferring some of them. However, some of them are kinda useless now, because they were made when there was no editor and the stuff the code does in the examples can be replaced by doing the same in the editor.

@mrDIMAS
Copy link
Member

mrDIMAS commented Sep 17, 2023

Also, I'll try to add web versions of examples (WASM-based) to the website, because right now the examples there are... not good to say the least. This will take some time though, since I'm fixing bugs in parallel with this. I'm keep finding small issues here and there 😕

@Swivelgames
Copy link
Author

@mrDIMAS Nice! That's good, though. Doesn't make for fast pace, but definitely adds to the stability of the engine, I imagine.

@Riddhiman007
Copy link
Contributor

@mrDIMAS I can update it for you.

@Riddhiman007
Copy link
Contributor

I'll make one --template arg after somedays

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

3 participants