Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Altering the Plugin Template
Yes, I noticed. I haven’t used composer yet and as I said in my previous message:
What Jukka does with his plugins and Composer is interesting. I wonder how well that integrates with the way users typically install plugins (via the TXP admin interface).
Offline
Re: Altering the Plugin Template
ruud wrote #294694:
The benefit of keeping it all contained in a single file for one version of a plugin is that you can generate all the other suggested files from that single file instead of having to maintain separate files manually.
And I like this approach. Although I’ve not got round to finishing it yet, I was planning to make myself a glue shell script for releasing a plugin. It’d take the plugin’s .php template file —slightly modified from its current format — and:
- split it into code and docs segments;
- squirt the docs into a separate
.textilefile (or at a push, funnel it through Pandoc to make github-flavoured markdown); - extract the history info and make a changelog file;
- extract meta data including the licence version, grab the relevant licence wording in .txt format from the GNU website and make a licence file for the repo if necessary;
- compile the plugin into .txt and .txt.zip files;
- bundle the lot up into a commit;
- commit;
- tag with the version number;
- push to github;
- release;
- upload to my website;
- make toast.
Quite how things like Composer and the central repo would factor in I don’t know, but for my own sanity, having a single file that acts as a master from which the various pieces can be extracted and farmed out to wherever they are needed makes a lot of sense to me, with my developer hat on.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: Altering the Plugin Template
In reply to ruud #294698:
Sorry about that Ruud. I thought I had read the whole message, but overlooked that part on Jukka.
When I first saw Composer, and read about it, I thought “nice in theory, but one more complicated thing to learn. I don’t see most people installing composer in order to install a plugin.” That said, perhaps that is a rash judgement and it is not complicated once I take a bit of time to learn it.
Perhaps it would require a Composer plugin that then allows the rest of the plugins to be installed? Jukka might have that very plugin – I saw something that sounds like it might do that, but haven’t had the chance to try it out.
Offline
Re: Altering the Plugin Template
maverick wrote #294701:
Sorry about that Ruud. I thought I had read the whole message, but overlooked that part on Jukka.
Oh no. I suspect your message was written while I was editing my post (I often do that instead of creating a new one if nobody responded yet).
Offline