-
Notifications
You must be signed in to change notification settings - Fork 23
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
Build UI Library Available for Extensions #9
Comments
austincondiff
changed the title
Build CodeEdit UI for Extensions
Build UI Library Available for Extensions
Nov 22, 2022
In my experiment over here, I use the following structures for "primative" ui elements (VStack, HStack, Text, Button):
{
"viewType": "vstack", // or hstack
"content": [/*other json representations of UI elements*/]
}
{
"viewType": "text",
"content": "content here"
}
{
"viewType": "button",
"onClick": "name of callback function",
"content": { /*other json representation of a UI element*/ }
} All views need a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should allow extension developers to use a library of standardized UI components so that we can ensure a consistent visual design throughout CodeEdit and it's extensions.
The following UI components will need to be available for extensions to use for views in the navigator, inspector, and debug areas:
Possible UI elements (need further elaboration):
Note: some of these are standard to SwiftUI however depending on our architecture we may need to expose these through CodeEditKit.
Other considerations:
We should also keep in mind what we plan to allow developers to extend. This might include:
The text was updated successfully, but these errors were encountered: