Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

App structure #1

Open
MatusGuy opened this issue Oct 6, 2023 · 0 comments
Open

App structure #1

MatusGuy opened this issue Oct 6, 2023 · 0 comments
Assignees

Comments

@MatusGuy
Copy link
Owner

MatusGuy commented Oct 6, 2023

Damn. I messed up. But I think I have an idea on how to fix all of this.

Perhaps I can label every level/folder/addon as a "project" and make a special QAbstractItemModel for such thing. Every model index there will have a type and content. A type is like a filetype, but stored as an enum value declared in C++ and exposed to QML. And content is for the actual content of the item that's selected. For example a script item will have the type "SCRIPT" and the content print("hello world")

In JS I will create a giant switch case with to select the right editor for each filetype using the filetype enum I exposed

@MatusGuy MatusGuy self-assigned this Oct 6, 2023
MatusGuy added a commit that referenced this issue Oct 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant