[Github-comments] [geany/geany] YALSPADD - Yet Another Language Services Plugin API Design Discussion (#1458)

[elextr]

@kugel- can you explain what you mean by signals being too "heavy weight"?  Its the way existing events in Geany are notified to plugins and anyone else who is interested ("document-save" etc).  But signal data passing and return is poor.

@kugel- your point about making the facilities available to non-C plugins is good.

The problem I see with anything gobject based is it requires specialist knowledge for someone to contribute a change to Geany to make a function overridable/modifyable by a plugin.  I would suspect that few plugin devs will have that ability, so making changes to allow plugins to do stuff will bottleneck at the few internal project people who have that knowledge.  

It would be nice if there was a way that worked as simply as using signals, ie emit() and connect().  Then more people could contribute changes to Geany that let their plugin modify built-in behaviour.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1458#issuecomment-294348514
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20170416/2a14f833/attachment.html>