From 57db80bccd430cd44b7fb1dbdf9359d2feb02f93 Mon Sep 17 00:00:00 2001 From: joey Date: Sat, 28 Apr 2007 18:55:19 +0000 Subject: web commit by enodev --- doc/todo/fileupload/soc-proposal/discussion.mdwn | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/todo/fileupload/soc-proposal/discussion.mdwn b/doc/todo/fileupload/soc-proposal/discussion.mdwn index 0ff6c6ce5..02eaf5693 100644 --- a/doc/todo/fileupload/soc-proposal/discussion.mdwn +++ b/doc/todo/fileupload/soc-proposal/discussion.mdwn @@ -33,4 +33,10 @@ teached to use these. Galleries could then be generated by means of 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 \ No newline at end of file + I think that would fit nicely with the ikiwiki concept. Comments? --enodev + +> Replying to myself. Just appending .meta gives problems when \$usedirs is enabled as the original file and the directory containing the html file will have the same name. Taking away the original extensions has problems with filenames having different extensions and the same basename. So something like 'about-image.jpg.meta'? That would require no changes to the core to support it and is reasonably easy to the eye. + +> I also pondered about putting this info in the rcs log, but that is problematic when you just 'cp'/'mv'/whatever the directory. Same goes for using something like svn properties, which git does not even support. Storing this info in the index file is problematic, because that isn't versioned. Major problem I see with this approach would be the disconnected nature of having two files. Posix extended attributes? ;-( + +> This could also be used to specify the license of the file. \ No newline at end of file -- cgit v1.2.3