mention plugins/contrib/trail
parent
2f573cf515
commit
c4c2683814
|
@ -1,11 +1,3 @@
|
|||
This sounds like a more general version of what I want for
|
||||
one-photo-per-page galleries, where each page has previous|up|next links
|
||||
(like this plugin) and the index page has a list or grid of thumbnails
|
||||
(\[[!inline]] with a specially modified template perhaps). I'll watch this
|
||||
with interest! --[[smcv]]
|
||||
|
||||
----
|
||||
|
||||
This is a nice idea, I do have my gripes about the imeplementation.
|
||||
|
||||
Assuming that the index's list is in mdwn format is not ideal. I guess the
|
||||
|
@ -81,5 +73,8 @@ hook to run *after* trail's, or perhaps by having trail's
|
|||
pagetemplate hook disable itself for pages that contain
|
||||
a \[[!trail]] directive.
|
||||
|
||||
Does this sound viable? Should I think about implementing it?
|
||||
--[[smcv]]
|
||||
I have now implemented this at [[plugins/contrib/trail]].
|
||||
What do you think? I'm still not sure how it would relate
|
||||
to [[plugins/contrib/album]], but if trail is reviewed
|
||||
and approved in principle, I'll try to adapt album as
|
||||
outlined above. --[[smcv]]
|
||||
|
|
Loading…
Reference in New Issue