-
Notifications
You must be signed in to change notification settings - Fork 333
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
Plugins #588
Comments
Evan mentioned the possibility of having a ./local directory where overrides (such as themes) could be dropped. |
This may work indeed. Would you be able to do some more complex stuff in it ? For instance I was thinking of an auto-refresh plugin like you have in StatusNet (or Twitter). Also if we add this kind of mechanism, we need to have something easy enough to share theses additions between each other. For instance put your changes in |
The web interface already has auto-refresh. Martin Trigaux notifications@github.com wrote:
Sent from my Android phone with K-9 Mail. Please excuse my brevity. |
Ok my bad for autorefresh :) |
There's rudimentary support for plugins in 0.3.x. I'm really dubious about them; I wouldn't count on continued support. |
Hello,
Is there plans to have some kind of plugins and theming mechanism ?
I know the idea of pump is to keep the core minimal and rely on external services to do stuff such as RSS, bridges & co but there is still things you will not be able to do as an external services.
For instance look at request #547, it shouldn't be in the core but still interesting. Same for the additions that jpope made (eg: this one) with no other choices than maintaining of fork of pump for theming and minor additions.
Also the problem of external services is that it works only per user vs per instance for theme and plugins (I think that both cases are useful).
Thanks
The text was updated successfully, but these errors were encountered: