Plan editor architecture - Githubissues

potatoengine / potato

Hobby C++ game engine

MIT License

38 stars 2 forks source link

Plan editor architecture #226

Open seanmiddleditch opened 3 years ago

seanmiddleditch commented 3 years ago

The current shell/editor is a hodge-podge of hacks and ideas and is not particularly well-planned out.

We need a solid design for the core architecture of the editor, including:

[ ] How does the editor interact with recon/content?
[ ] How does the editor manage documents?
[ ] How does the editor manage editor panels and the workspace?
[ ] What is the data model used in the editor?
[ ] What is the command architecture?
[ ] How can scripting extend the editor for designer or tech-art purposes?
[ ] How will core user features like undo/redo work?
[ ] Selection, multi-select, and multi-edit?
[ ] Document to asset conversion?
[ ] Play mode?
[ ] Editor settings?
[ ] Multi-process model?