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

Plugins #588

Open
mart-e opened this issue May 5, 2013 · 5 comments
Open

Plugins #588

mart-e opened this issue May 5, 2013 · 5 comments
Milestone

Comments

@mart-e
Copy link

mart-e commented May 5, 2013

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

@jpope777
Copy link
Contributor

jpope777 commented May 5, 2013

Evan mentioned the possibility of having a ./local directory where overrides (such as themes) could be dropped.

@mart-e
Copy link
Author

mart-e commented May 5, 2013

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 ./local/my-changes/templates/layout.utml to be able to share only the my-changes/ directory. Of course, the problem would them be how to manage conflicts...

@evanp
Copy link
Contributor

evanp commented May 5, 2013

The web interface already has auto-refresh.

Martin Trigaux notifications@github.com wrote:

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 ./local/my-changes/templates/layout.utml to be able to
share only the repository. Of course, the problem would them be how to
manage conflicts...


Reply to this email directly or view it on GitHub:
#588 (comment)

Sent from my Android phone with K-9 Mail. Please excuse my brevity.

@mart-e
Copy link
Author

mart-e commented May 5, 2013

Ok my bad for autorefresh :)

@evanp
Copy link
Contributor

evanp commented Jun 23, 2013

There's rudimentary support for plugins in 0.3.x. I'm really dubious about them; I wouldn't count on continued support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants