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

Allow saving custom AI purpose #97

Closed
PaRaD1SE98 opened this issue Apr 26, 2023 · 5 comments
Closed

Allow saving custom AI purpose #97

PaRaD1SE98 opened this issue Apr 26, 2023 · 5 comments

Comments

@PaRaD1SE98
Copy link

It would be nice if we can save custom purpose.

@enricoros
Copy link
Owner

How do you envision the UX to be? Asking because there are many ways to do it, and only want to do it right.

@PaRaD1SE98
Copy link
Author

PaRaD1SE98 commented Apr 27, 2023

I think a suitable example is the home page of google chrome. The current layout is already close.

image

I think we can modify the current 'edit-show' feature to a 'pin' feature.

We can have an 'options' button on the top right of every purpose item like this. (On hover show 'options' button)

image

Inside the options we can have :

  • 'pin' or something like 'stay on top',
  • 'modify' to adjust icon and prompt
  • 'delete' to delete the item

May be we also need a bulk delete button somewhere.

Instead of an 'edit' button here, we can have a 'Show <More/Less>...' button.(Or put it on the bottom right...)
Always keep the 'Custom' on the last 'pinned' purpose items.
(Or don't use 'Custom purpose item' but add an 'add' button somewhere)
Maybe add a scroll bar to keep the ui clean.
image

For the save purpose feature, it could be like this:
image
on save, add the feature to the first 'pinned' feature.

Can also add a save button here.
image

@enricoros
Copy link
Owner

Thanks for the great guidance - very appreciated your diagrams - very clear.
I will consider it. Need to figure out how to overlay:

  • user edited > source-edits (people that customize this app) > default options.

Right now the "Purposes" system is very hardcoded, so people edit them in the code and then deploy their own. But it should be editable after deployment by each user, that's for sure.

@enricoros
Copy link
Owner

#35

@enricoros
Copy link
Owner

Duplicate of: #35

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

2 participants