Feature request: Add a way to "archive" grains

sandstorm-io / sandstorm

Sandstorm is a self-hostable web productivity suite. It's implemented as a security-hardened web app package manager.

https://sandstorm.io

Other

6.76k stars 707 forks source link

Feature request: Add a way to "archive" grains #1113

Open paulproteus opened 9 years ago

paulproteus commented 9 years ago

In the many months I've been using Sandstorm, I have created a lot of grains.

I love the new Grains list, but it is now cluttered with many things I don't care about.

I'd like to make some of them "archived" so that even if I click them, they don't move to the top of the grains list. This is basically the same as "Deleted" except I'm a digital packrat so I don't ever want to delete anything.

zeigerpuppy commented 8 years ago

good idea, archiving may be good, or even dividing into "projects" this could be achieved with grain "tags" and filters. So I may have, for example a text file grain, and a photo library tagged "flower_project" and then also tag it "archived" the default filter could be to hide archived grains. This mechanism would also be useful for sharing a whole project at once, made up of multiple grains.

ocdtrekkie commented 4 years ago

The new UI design issue, #1915 actually specified archived grains as an expectation, but it was never built. This is one I think would be really really nice. If I write a document (which I do almost exclusively on Sandstorm now), I tend to keep it. But I don't need most old grains on my UI most of the time. I also probably would archive/hide grains that belong to a Collection, for grain list cleanliness purposes.

So I'd like a "Hide" function, maybe so it can cover both those cases, and a tab to view/unhide them. The UI could be not unlike trash, but archived grains should still run if you open them, and they won't be deleted.

ocdtrekkie commented 2 years ago

I have been playing with a lot of things lately which make me want this even more. Specifically, I now have a bunch of grains that may trigger from outside actions, which I don't necessarily want to push to the top of my grain list all the time.

My home automation apps sync to a grain a couple times an hour. It fights with my news reader for the top spot on the grain list usually.
I prefer to access my news reader almost exclusively through the Windows and iOS client apps, and don't really need it on the top of my grain list either, even though I access it daily.
I host a few websites on my server, and I unfortunately expect to host one or two using StandaloneDomains, so they may "launch" in some cases when accessed.
I just tested out an action which syncs my GitHub repo to a GitWeb grain so I have local archived copies. However, I am now worried this will swamp my other grains.

zenhack commented 2 years ago

Hm, maybe we should change the way the sorting works, so that it only "counts" if a grain is opened via the UI. Do we have an open issue for that already?

ocdtrekkie commented 2 years ago

I think the choice to update the updated date when the API was hit was intentional, and I think I still probably think it should? (I'm generally assuming grains which have not changed their updated date have not changed state since last updated.)