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

Premade tutorial project #172

Open
nightblade9 opened this issue Jun 11, 2022 · 3 comments
Open

Premade tutorial project #172

nightblade9 opened this issue Jun 11, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@nightblade9
Copy link

I looked through the installation instructions. A lot of them mention copying things from the core folder into a new folder. It looks like a lot of steps.

Is there any way you can create a premade project that you can just clone/unzip and go? It sounds like you can include any older version of the framework, and users can upgrade by getting the latest version and copying over core.

@db0
Copy link
Owner

db0 commented Jun 12, 2022

I've actually had an idea of making a script file which would do the quick-start steps automatically for someone who wants to not bother, but the point of the quickstart is to also introduce some concepts to new players, so that they understand the components. Technically one can simply use the custom folder directly without any copying.

@db0 db0 added the enhancement New feature or request label Jun 12, 2022
@nightblade9
Copy link
Author

I see; that makes sense. Maybe I can explain my suggestion with context: I'm looking to prototype a card game with your framework, and I'm looking for the easiest possible solution to get it running quickly. For me, a template/script would be ideal. (I read through all the manual steps in depth and looked at some of the code to make sure I understand how things work.)

Thanks for the hint about being able to use custom without copying. I actually thought the right approach is to extend (not copy) core classes, so that you can upgrade them later and get the benefits of upgrading (does that work if you copy them?)

@db0
Copy link
Owner

db0 commented Jun 14, 2022

I actually thought the right approach is to extend (not copy) core classes, so that you can upgrade them later and get the benefits of upgrading (does that work if you copy them?)

That is correct. You should always be extending classes or inheriting scenes from the core/ folder, if you want the framework to remain upgradable.

For a quick prototype, keeping the custom/ folder as is and adjusting it from there should work just fine. The scenes and classes in it are already extending/inheriting as needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants