web commit by enodev
parent
74306c7f20
commit
97f9de14ba
|
@ -23,3 +23,14 @@ It's not clear to me that the concept of attaching files to a page fits ikiwiki
|
||||||
I don't understand why the file size would need to be stored in the index file; this information is available by statting the file, surely? Similarly, the mime type can be determined through inspection, unless there turns out to be a reason to need to cache it for speed.
|
I don't understand why the file size would need to be stored in the index file; this information is available by statting the file, surely? Similarly, the mime type can be determined through inspection, unless there turns out to be a reason to need to cache it for speed.
|
||||||
|
|
||||||
--[[Joey]]
|
--[[Joey]]
|
||||||
|
|
||||||
|
For images, videos, etc. it would be nice to have some kind of meta data file to go along with it
|
||||||
|
(eg. image.jpg.meta), to store information like creator, title, description, tags, length, width,
|
||||||
|
height, compression, etc. which could be initially created by 'ikiwiki --generate-meta-stuff'.
|
||||||
|
Then PageSpec should be
|
||||||
|
teached to use these. Galleries could then be generated by means of
|
||||||
|
\[[inline pages="type(image/*) and year(2007)" template="gallery"]]. It
|
||||||
|
should of course be possible to edit this information via ikiwiki.cgi and with any
|
||||||
|
text editor (Name: value). This should also allow for creations of default .html pages with
|
||||||
|
the image/video/file/... and a discussion page. Probably named image.mdwn and image/discussion.
|
||||||
|
I think that would fit nicely with the ikiwiki concept. Cons? --enodev
|
Loading…
Reference in New Issue