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

Restructure cocoa crate #496

Open
komi1230 opened this issue Jan 22, 2022 · 0 comments
Open

Restructure cocoa crate #496

komi1230 opened this issue Jan 22, 2022 · 0 comments

Comments

@komi1230
Copy link

In the future, directory structure should be like below:

src
├── appkit
│   ├── text.rs
│   ├── view.rs
│   └── etc...
├── swiftui
│   ├── text.rs
│   ├── view.rs
│   └── etc...
├── uikit
│   ├── text.rs
│   ├── view.rs
│   └── etc...
├── util
│   ├── base.rs
│   ├── foundation.rs
│   └── etc...
├── appkit.rs
├── swiftui.rs
├── uikit.rs
├── util.rs
├── lib.rs
├── macros.rs
└── quartzcore.rs

But current cocoa dir structure is like below:

src
├── appkit.rs
├── base.rs
├── foundation.rs
├── lib.rs
├── macros.rs
└── quartzcore.rs

These days I'm developing Winit to improve experience in IME. And I have found current cocoa crate has many points to be improved.
I want to contribute this crate with adding some class or protocol which is still not to be implemented, like NSTextInputClient or etc.
But there are too many class and protocol to be implemented. That's why I propose cocoa crate should be structured to be scalable to implement more features.
And also I propose to add swiftui/ and uikit/.
This structure can endure other issues about SwiftUI.

How do you think about this ?

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