Hello,
I was wondering if the idea of editing directly its extension in the application would not be interesting?
I have some extensions that I had made for me, well it’s more shortcuts, and finally if I need to change the shortcut in the extension I have to go find the extension or redo it etc …
Whereas if I could just edit directly, it would be easier.
And I even think it shouldn’t be complicated to do, but I’m not a dev, so I have to say anything ^^.
Thank you.
I’ve just discovered that you can access the source directly. So my idea fell through. 
Hey, I do love this idea. I like the idea of making the extensions easier to edit.
In the new PopClip, extensions are now stored in a database instead of just being stored on the disk. This supports the new features like action duplication and iCloud sync.
And yes, we now have View Source for every extension. 
It’s quite basic, just showing you a folder with the files, but it’s a starting point.
I want to take this further in future versions, perhaps with an in-built viewer to view the source and let you export as a .popclipext package or copy as a snippet.
Direct editing is also a great idea.
But of course, as you know, I will talk about ideas, but I can’t say if or when these will be implemented.
Beta Build 6007 now has a simple read-only source viewer with Export… (as .popclipext) and Copy Snippet (where the source is a valid snippet).
Ahah
You say :
But of course, as you know, I will talk about ideas, but I can’t say if or when these will be implemented.
You’re super reactive, I love it!
Do you think editing in this window would be complicated?
Yes! 
The actual text editing itself, not too difficult if I just use the macOS standard text editor controls, but then we would probably want to have syntax highlighting, word wrap, auto-complete, maybe find and replace, all stuff like that that coders are used to in their editors.
And then there are other questions, like what if you make an edit and there’s an error?
What about Undo? Should we keep old versions around so you can revert in case you made a mistake? (maybe “revert to original” button as well)
Then there’s the question of what if you’re editing a signed extension? Now it won’t be signed anymore, so need to think about how to deal with that. Perhaps also the editor should force you to change the extension ID before letting you save a “com.pilotmoon…” extension…
A whole lot of complications. None of which are insurmountable, but it’s a larger project.
So I think it’s better for now to keep it simple and then you can use your existing text/code editor tools to make and edit extensions. I don’t want to find myself developing a whole code editor as well as PopClip
I totally understand. It’s true that I haven’t considered all the issues raised, and probably others as well. It’s all worth thinking about.
The idea is this:
Thanks for listening!
