Migrate escaped directives (\[[) in doc/todo to have \[[! prefix

[ikiwiki.git] / doc / todo / fileupload / soc-proposal / discussion.mdwn

diff --git a/doc/todo/fileupload/soc-proposal/discussion.mdwn b/doc/todo/fileupload/soc-proposal/discussion.mdwn
index 299dc4c565f908c7f2de1c87bd45edd32d08b2c3..f85a956dbc65e4a771de4da50d3be83f03b5f976 100644 (file)
--- a/doc/todo/fileupload/soc-proposal/discussion.mdwn
+++ b/doc/todo/fileupload/soc-proposal/discussion.mdwn
@@ -1,8 +1,8 @@
-There's nothing in [[fileupload]] that suggests putting the file upload limit in the body of a page. That would indeed be a strange choice. Ikiwiki already uses [[PageSpecs|PageSpec]] in the Preferences page (for specifying locked pages, banned users, and subscriptions), and I had envisioned putting the file upload controls there, and possibly subsuming some of those other controls into them.
+There's nothing in [[fileupload]] that suggests putting the file upload limit in the body of a page. That would indeed be a strange choice. Ikiwiki already uses [[PageSpecs|ikiwiki/PageSpec]] in the Preferences page (for specifying locked pages, banned users, and subscriptions), and I had envisioned putting the file upload controls there, and possibly subsuming some of those other controls into them.

 
 > Thanks for clarifying; I clearly misunderstood the original text. -- Ben
 
 
 > Thanks for clarifying; I clearly misunderstood the original text. -- Ben
 

-It's not clear to me that the concept of attaching files to a page fits ikiwiki very well; unlike most wikis, ikiwiki supports subdirectories and [[SubPages|SubPage]], which allows for hierarchical placement of uploaded files, which is a much more flexible concept than simple attachment. Futhermore, the idea of listing all attached files at the bottom of a page seems somewhat inflexible. What if I want to make a podcast, using inline's existing support for that -- I won't want a list of every "attached" file at the bottom of my podcast's page then.
+It's not clear to me that the concept of attaching files to a page fits ikiwiki very well; unlike most wikis, ikiwiki supports subdirectories and [[SubPages|ikiwiki/SubPage]], which allows for hierarchical placement of uploaded files, which is a much more flexible concept than simple attachment. Futhermore, the idea of listing all attached files at the bottom of a page seems somewhat inflexible. What if I want to make a podcast, using inline's existing support for that -- I won't want a list of every "attached" file at the bottom of my podcast's page then.

 
 > If a file was attached to _some-dir/some-page_, it would be stored in _some-dir/_ and linked from _some-page_. That would seem reasonably hierarchical to me. What do you suggest as an alternative? 
 
 
 > If a file was attached to _some-dir/some-page_, it would be stored in _some-dir/_ and linked from _some-page_. That would seem reasonably hierarchical to me. What do you suggest as an alternative? 
 


@@ -29,7 +29,7 @@ For images, videos, etc. it would be nice to have some kind of meta data file to
 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
 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
+\[[!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.
 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.


@@ -43,4 +43,4 @@ the image/video/file/... and a discussion page. Probably named image.mdwn and im
 
 > I did an proof of concept implementation of this idea [here](http://ng.l4x.org/brainstorm/gallery/) yesterday night, including the link to the source code. I'd really love to hear comments about this approach.
   (note1: I'm really not interested in any kind of http interface to that thing, just testing ways of storing the meta
 
 > I did an proof of concept implementation of this idea [here](http://ng.l4x.org/brainstorm/gallery/) yesterday night, including the link to the source code. I'd really love to hear comments about this approach.
   (note1: I'm really not interested in any kind of http interface to that thing, just testing ways of storing the meta

-   data, note2: I'm no perl programmer)
\ No newline at end of file
+   data, note2: I'm no perl programmer)