Repository navigation
API for managing templates #343
Description
Activity
Considering this as part of Theme support, as it ties in nicely with the API required to save and sync templates with the file system.
Final changes to the API / callbacks are being made before setting them in stone. Watch this space.
Themes has landed. Are we close to wrapping this one up?
It's "Done" insofar as it works. Whether it's optimal and usable will be determined by the position of the callbacks, which I'll be finalising over the weekend. Should be able to close by Monday with luck.
Bump? Any news on this issue. Done?
Not yet. I started but @NicolasGraph is refactoring the Theme system to be less resource intensive behind the scenes. As soon as he's done (this week?) I'll do this. If I did it now, we'd both have a hell of a job to merge because the changes are quite invasive in terms of the way callbacks are referenced.
3 remaining items
This is done for themes, which encompass forms, pages and styles. We'll unify this in coming releases, so let's leave this here as a reminder, but push it back.
I'd definitely like to see some form of webhook to re-import an updated theme via a URL as well as the current way of through the panels. Just leaving this here for future consideration.
Re: webhook, yes, let's look at implementing that at some point early next release.
From jukka.m.svahn on December 13, 2012 03:05:16
Continuing the API work from Users and Prefs to templates. This would include functionality for creating, updating, renaming, removing, listing and validating forms, pages and styles.
Original issue: http://code.google.com/p/textpattern/issues/detail?id=339