Open ReconVirus opened 1 year ago
Hey! I admit I don't immediately grasp the idea of your project. Feel free to open a pull request solving the issues in Supercharged Links that conflict with yours.
what my plugin does is turn a code block into a rendered icon. What im tryng to do is use that code block within Supercharged links, but instead of seeing a code block, the actual icon is render instead. thats being appened or deppended to the link. .
You can probably achieve something with this by generating a CSS file. See this https://github.com/mdelobelle/obsidian_supercharged_links#css-custom-properties-css-variables link for examples. Just make sure you assign the right properties to the yaml, I guess.
https://github.com/ReconVirus/Monstrology
Hello, I am the developer of Monstrology and I would appreciate your interest in collaborating with me. Your project Super Chargerd Links looks very impressive and I think it could enhance the functionality of my plugin. I would be happy to explain to you how my plugin works and how we can make it compatible with yours.
My plugin ihas a unique feature that lets users turn a code block into a element or monster icon, Simply as using something like
ele:FIre
ormon:Beast
The problem is that when I try to use my plugin alongside your's, it seems to interfere with the monster icon feature. The icons do not render properly, leave just the
mon;Beast
. I think this is because your plugin modifies the code block’s HTML structure and attributes, which affects how my plugin recognizes and transforms the code block into an icon.To solve this problem, I think we need to do two things:
First, we need to make sure that your plugin does not alter the code block’s original content or metadata, such as its id, class, or style. This way, my plugin can still identify and process the code block correctly. Second, we need to make sure that your plugin does not overlap or conflict with the monster icon’s HTML elements, such as its div, img, or svg tags. This way, the icon can still display and function properly.
I hope this explanation helps you understand how my plugin works and what we need to do to make it work with yours. If you have any questions or suggestions, please let me know. I look forward to hearing from you and working with you on this exciting project. Thank you for your time and cooperation.