Closed scottux closed 11 years ago
Totally agree 110%. Then we update the plugin installer to clone right off of github instead of installing a zip. We could make a list of available plugins right on the plugin installer page of the framework and the user can just click install and the framework handles it. Then we could get rid of all of the install scripts that need to be dealt with.
I'm in the middle of taking a closer look at this, and it looks like if we set up each plugin as a submodule, we can use composer to pull them in as external dependencies... I think. @vakopian is this along the lines of what you were thinking?
I've already started this on my fork and it appears to be working fantastically. I need to move all of the plugin repos over to qcubed, but I should have all of this done by the end of the day.
I've moved the plugins over, I just need to update the submodule list to point to the qcubed/ repos instead of the jamescmunro/ repos. I'll do that tonight and we can close this issue.
OMG! so many repos in a qcubed root! (https://github.com/qcubed) Can it be grouped under a plugins "subdirectory"?
It's just a list of our public repositories, not a file structure. There is no way that I'm aware of to group repositories on github.
ok it looks not very attractive, but is a workable approach.
I know it's ugly, but I'm not sure there's anything we can do about it. The good thing is that we should be able to use composer now to pull them in and get rid of the shell scripts and zipping the files etc.
If we need to zip them or we feel like operating on them after they're merged, we can use Travis CI.
sounds good!
What are the changes to plugin creation? Please fix up the plugin creation documentation.
@spekary #5
We need to investigate how to break this repo down into individual plugins.