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

Share fragments / scripts among note types #23

Open
hgiesel opened this issue Mar 30, 2021 · 1 comment
Open

Share fragments / scripts among note types #23

hgiesel opened this issue Mar 30, 2021 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@hgiesel
Copy link
Owner

hgiesel commented Mar 30, 2021

We'd probably need a new area for fragments / scripts for All note types, from the fragment can be shared to individual note types.

Fragments / script would need a new field for backreference, whether they were originally implemented directly on the note type, or shared from "all note types".

@hgiesel hgiesel added enhancement New feature or request help wanted Extra attention is needed labels Mar 30, 2021
@jthulhu
Copy link

jthulhu commented Aug 24, 2021

I suggest that you rework entirely how this addon works. Instead of giving assets "owners" (ie. binding an asset to a particular note type), I think assets should be created independently, and then for each asset you could check-in every note that should have that one.

For instance, you could have add a button to the tools menu with "Manage assets", which would show the full list of assets, with approximately the same interface that we have now. Then, you could click on one asset to manage it. This would open a window with all the settings. On this window, one button would allow you to edit the asset. An other button would allow you to open the list of all the notes, with a checkbox next to it. When you click on "Confirm", it closes this window, and updates the notes so that the asset is loaded for every note that was checked.

With this setup, there is no need for a backreference. All the assets could be saved in the media collection, as standalones.

This approach would be the most flexible.

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

No branches or pull requests

2 participants