On Monday, October 22, 2012 at 2:34 PM, Cor Bosman wrote:
On Oct 22, 2012, at 2:31 PM, till <klimpong@gmail.com (mailto:klimpong@gmail.com)> wrote:
On Monday, October 22, 2012 at 2:20 PM, Cor Bosman wrote:
Hey Dominic,
composer doesn't require PHP 5.3 namespaces.
foo_blah works just as nice. I'm using both "at work".
Anyhow — I made good progress over the weekend. Hoping to publish something by Wednesday.
One thing im wondering about composer/packagist. Is there an API through which RC or a plugin can offer a plugin admin page inside roundcube. If not, I think that is a serious negative.
Whatever the plugin wants to do does not depend on the "installer"?
Or can you explain how the installer would need to be aware of it?
What I mean is, that if a roundcube installation admin logs into RC, they can see all plugins that are installed (similar to about page), but also see if new versions are available, and maybe even update right from roundcube. Similar to wordpress and other software. It would highly improve user experience for roundcube plugins.
This doesn't need to exist now, but it would really be cool if this is at least possible.
Cor
Hey,
this is *very* much possible.
This kind of feature would be a plugin itself – or could also be part of the RoundCube core.
The way it would work in a nutshell is this:
- check local .lock file from composer (= composer.lock) against installed versions
- compare against our packagist repository
I'm not a 100% sure if someone has done this before, but it's all there — or takes little effort to be build.
It's already possible to run something like that ./composer.phar update --dry-run, so I don't see why this couldn't be exposed to the web:
http://getcomposer.org/doc/03-cli.md#options-3
Till