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

[Request] Let Exploded and Cloned Groups Update Automatically #34

Open
drinfernoo opened this issue Jun 23, 2020 · 5 comments
Open

[Request] Let Exploded and Cloned Groups Update Automatically #34

drinfernoo opened this issue Jun 23, 2020 · 5 comments
Labels
enhancement New feature or request

Comments

@drinfernoo
Copy link
Owner

Basically, if a group consists of an exploded or cloned directory, let that group automatically update its paths with any items from the source path that have been added since the group was created.

@drinfernoo drinfernoo added the enhancement New feature or request label Jun 23, 2020
@drinfernoo drinfernoo added this to the 2.0 milestone Jun 23, 2020
@drinfernoo
Copy link
Owner Author

@drinfernoo
Copy link
Owner Author

For cloned groups, I want these to be created as a static shortcut group, to be edited as the user sees fit.

For exploded groups, I think the best course will be to have two options: synced or not. If the group is "synced", then it'll pull paths fresh every time. If not, then it'll act as the current exploded groups do.

@drinfernoo
Copy link
Owner Author

Thinking about this a bit more, I think even Widget Groups should work the way Shortcut ones do, since you can change the labels, content type, etc... for those as well 🤔

@djay
Copy link
Collaborator

djay commented Aug 24, 2022

@drinfernoo the current code tries to estimate how often a path changes.
Could impliment it like this

  • if a path inside an exploded group is requested (e.g. loaded into a widget) then evaluate the exploded group as if its also a path.
  • if the group path seems likely to have changed then do a queued refresh on it
  • after any path refresh then look up if that path is synced to an exploded group
  • run the exploding code again.
    • add new paths
    • remove missing paths.
    • maybe not changing name of paths that didn't change?

I don't think it's that bad to make exploded groups synced always as long as changing names is allowed. Maybe the only reason not to is if you want to setup a static path in teh group and syncing allows removing paths?

@hackmonker
Copy link

Does this syncing of exploded groups work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants