diff options
Diffstat (limited to 'doc/todo')
| -rw-r--r-- | doc/todo/__42__forward__42__ing_functionality_for_the_meta_plugin.mdwn | 4 | ||||
| -rw-r--r-- | doc/todo/__47___should_point_to_top-level_index.mdwn | 2 | ||||
| -rw-r--r-- | doc/todo/fileupload/soc-proposal/discussion.mdwn | 6 | ||||
| -rw-r--r-- | doc/todo/format_escape.mdwn | 2 | ||||
| -rw-r--r-- | doc/todo/linktitle.mdwn | 4 | ||||
| -rw-r--r-- | doc/todo/mailnotification/discussion.mdwn | 2 |
6 files changed, 10 insertions, 10 deletions
diff --git a/doc/todo/__42__forward__42__ing_functionality_for_the_meta_plugin.mdwn b/doc/todo/__42__forward__42__ing_functionality_for_the_meta_plugin.mdwn index b584341c6..842c87e2d 100644 --- a/doc/todo/__42__forward__42__ing_functionality_for_the_meta_plugin.mdwn +++ b/doc/todo/__42__forward__42__ing_functionality_for_the_meta_plugin.mdwn @@ -16,7 +16,7 @@ I can also submit a Git patch, if desired. **URL** = http://some.nice/place/ (*etc.*) -**WHITHER** = \[\[**[[wikilink]]**]] | **URL** +**WHITHER** = \[\[**[[ikiwiki/wikilink]]**]] | **URL** **D** = natural number (*meaning seconds*) @@ -49,7 +49,7 @@ the forwarding statement also to the referred-to page. >> (How to qualify a valid target address?) >> What is a *cyclic meta refresh loop*? Two pages in turn forwarding to each other? >> I think it would be possible to implement such a guard when only in-wiki links ->> ([[wikilink]]s) are being used, but how to do so for external links? --[[tschwinge]] +>> ([[ikiwiki/wikilink]]s) are being used, but how to do so for external links? --[[tschwinge]] >>> This seems a lot more securely to do for in-wiki links, since we know >>> that a link generated by a wikilink is safe, and can avoid cycles. diff --git a/doc/todo/__47___should_point_to_top-level_index.mdwn b/doc/todo/__47___should_point_to_top-level_index.mdwn index 88199d5de..60cb763e1 100644 --- a/doc/todo/__47___should_point_to_top-level_index.mdwn +++ b/doc/todo/__47___should_point_to_top-level_index.mdwn @@ -1,3 +1,3 @@ -Since `/` now works in [[WikiLink]]s to anchor links to the root of the site +Since `/` now works in [[ikiwiki/WikiLink]]s to anchor links to the root of the site (for instance, `\[[/index]]`), `/` alone should work as a reference to the top-level index page (for instance, `\[[Home|/]]`). --[[JoshTriplett]] diff --git a/doc/todo/fileupload/soc-proposal/discussion.mdwn b/doc/todo/fileupload/soc-proposal/discussion.mdwn index 299dc4c56..1ce52f0ca 100644 --- 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 -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? @@ -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 - data, note2: I'm no perl programmer)
\ No newline at end of file + data, note2: I'm no perl programmer) diff --git a/doc/todo/format_escape.mdwn b/doc/todo/format_escape.mdwn index 0f5859b3e..45002f0c6 100644 --- a/doc/todo/format_escape.mdwn +++ b/doc/todo/format_escape.mdwn @@ -218,7 +218,7 @@ Index: doc/plugins/rst.mdwn -* reStructuredText does not allow raw html to be inserted into - documents, but ikiwiki does so in many cases, including -- [[WikiLinks|WikiLink]] and many +- [[WikiLinks|ikiwiki/WikiLink]] and many - [[PreprocessorDirectives|ikiwiki/PreprocessorDirective]]. +* Some bits of ikiwiki may still assume that markdown is used or embed html + in ways that break reStructuredText. (Report bugs if you find any.) diff --git a/doc/todo/linktitle.mdwn b/doc/todo/linktitle.mdwn index 8d6ce3c1f..d5b53e082 100644 --- a/doc/todo/linktitle.mdwn +++ b/doc/todo/linktitle.mdwn @@ -1,6 +1,6 @@ Pages could have a `linktitle` (perhaps via [[plugins/meta]]), and -[[wikilinks|wikilink]] could use that title by default when linking to the -page. That would allow pages to have a simple, easily linkable name +[[wikilinks|ikiwiki/wikilink]] could use that title by default when linking +to the page. That would allow pages to have a simple, easily linkable name (without spaces, for instance), but use the proper title for links. For example, [[ikiwiki/PreprocessorDirective]] could use the `linktitle` "preprocessor directive", and pages for [[users]] could have `linktitle`s diff --git a/doc/todo/mailnotification/discussion.mdwn b/doc/todo/mailnotification/discussion.mdwn index 29421d321..b8af29f05 100644 --- a/doc/todo/mailnotification/discussion.mdwn +++ b/doc/todo/mailnotification/discussion.mdwn @@ -10,5 +10,5 @@ Mail notifications are probably not required. For example I get lots of comments Perhaps a powerful little UNDO feature on RecentChanges is all that is needed. > Um, if you'll look at the [[mailnotification]] page, ikiwiki has -> supported mail notifications for > 1 year, with a powerful [[PageSpec]] +> supported mail notifications for > 1 year, with a powerful [[ikiwiki/PageSpec]] > to allow chosing which pages you want to be notified about. --[[Joey]] |