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

[DOCS] Add a tutorial series on translating between engine and script code. #29

Open
willnationsdev opened this issue Feb 21, 2019 · 2 comments

Comments

@willnationsdev
Copy link
Owner

Go through an example of taking a complex Engine class (or set of classes) and walk through how to change it into script code. Illustrates relationship between engine/script code and teaches people how to build their own complex objects. Going to use EditorInspector to teach people how to build their own editor (slightly).

Go through an example of taking a scene one has built in the editor and converting it into an engine module. Scene -> Script -> C++ class.

@willnationsdev
Copy link
Owner Author

In the process of creating these docs, I will have created a script-based foundation for a user's own Inspector. Once this foundation is in place and integrated into godot-next, contributors can then begin creating specific Property GUI implementations, like EditorProperty, but not tied directly to the editor.

@willnationsdev
Copy link
Owner Author

This proved to be very involved so I have the branch, but I will likely be focusing (for now anyway) on other tasks.

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