From d8f2fb5eff8c61320a4151d4b82f0692592da0b2 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Nov 2007 03:30:32 -0500 Subject: web commit by JoshTriplett: pdfshare plugin --- doc/todo/pdfshare_plugin.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/todo/pdfshare_plugin.mdwn diff --git a/doc/todo/pdfshare_plugin.mdwn b/doc/todo/pdfshare_plugin.mdwn new file mode 100644 index 000000000..40a162bfd --- /dev/null +++ b/doc/todo/pdfshare_plugin.mdwn @@ -0,0 +1 @@ +Given an ikiwiki with a PDF checked into it, how about a plugin that uses [pdfshare](http://ejohn.org/blog/easy-pdf-sharing/) to embed a version of the PDF that uses images and Javascript navigation? Great for presentations, or any other PDF you want to provide an easy preview of. The pdfshare plugin should regenerate the images and navigation if you update the PDF. --[[JoshTriplett]] \ No newline at end of file -- cgit v1.2.3 From 67f83da07da20189f4bee99b05f2a54fede4bfc6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Nov 2007 04:36:32 -0500 Subject: web commit by http://ptecza.myopenid.com/: * More dynamic rootpage parameter? --- doc/blog/discussion.mdwn | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/doc/blog/discussion.mdwn b/doc/blog/discussion.mdwn index 40e8c8f77..2682799bd 100644 --- a/doc/blog/discussion.mdwn +++ b/doc/blog/discussion.mdwn @@ -1,4 +1,4 @@ -How do you provide the per post discussion links in your own blog? +## How do you provide the per post discussion links in your own blog? > That's configured by the "actions" parameter to the inline directive. See > docs in [[plugins/inline]]. --[[Joey]] @@ -13,3 +13,23 @@ take it as far as implementing "replies" to other comments. > See [[todo/discussion_page_as_blog]] for some of my own thoughts on this > --[[Joey]] + +--- + +## More dynamic `rootpage` parameter? + +I prefer to use a current year, month and day to archive my blog posts, for example +`post/2007/11/12/foo-bar-baz` path is better for me then `post/foo-bar-baz`. +Unfortunately it seems that `rootpage` parameter is very static. Is it a chance +to make it more dynamic? Now I have to use `svn mkdir` command to create +appropriate subdirectories by hand. + +I think that you could add builtin functions or variables, for example `current_year()` +or `$CURRENT_YEAR` to usage inside `rootpage` parameter. Something like for Manoj's +calendar plugin. Then my `rootpage` parameter could be like +`rootpage="post/current_year()/current_month()/current_day()"`. Another good hints +are welcomed ;) + +What's your opinion, Joey? I hope it's also useful for another ikiwiki lovers :) + +--[[Paweł|ptecza]] -- cgit v1.2.3 From 99cc46ec641853346e0f371d1a6cad2429569d76 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Nov 2007 04:38:47 -0500 Subject: web commit by http://ptecza.myopenid.com/: * rootpage is a parameter of inline plugin --- doc/blog/discussion.mdwn | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/blog/discussion.mdwn b/doc/blog/discussion.mdwn index 2682799bd..fb643bf23 100644 --- a/doc/blog/discussion.mdwn +++ b/doc/blog/discussion.mdwn @@ -16,13 +16,13 @@ take it as far as implementing "replies" to other comments. --- -## More dynamic `rootpage` parameter? +## More dynamic `rootpage` parameter of inline plugin? I prefer to use a current year, month and day to archive my blog posts, for example `post/2007/11/12/foo-bar-baz` path is better for me then `post/foo-bar-baz`. -Unfortunately it seems that `rootpage` parameter is very static. Is it a chance -to make it more dynamic? Now I have to use `svn mkdir` command to create -appropriate subdirectories by hand. +Unfortunately it seems that `rootpage` parameter of inline plugin is very static. +Is it a chance to make it more dynamic? Now I have to use `svn mkdir` command +to create appropriate subdirectories by hand. I think that you could add builtin functions or variables, for example `current_year()` or `$CURRENT_YEAR` to usage inside `rootpage` parameter. Something like for Manoj's -- cgit v1.2.3 From b4f768db713be367d5abf09fba464ee1a5adb711 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Nov 2007 05:07:00 -0500 Subject: web commit by http://ptecza.myopenid.com/: * Comment --- doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn b/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn index e5e65a7f3..2947dc70f 100644 --- a/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn +++ b/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn @@ -1,4 +1,10 @@ [[tag wishlist]] [[tag patch]] -In our team internal wiki, we wish to impose a policy that all edits must have a comment. Patch in [[debbug 450620]]. \ No newline at end of file +In our team internal wiki, we wish to impose a policy that all edits must have a comment. Patch in [[debbug 450620]]. + +> Good idea! I also hate empty commit comments, but I know that it's also a matter +> of human mentality. Of course, you can forbid users to commit empty comments, +> but then they can commit so worthless comments like "\*" or "\* blah". +> +> --[[Paweł|ptecza]] \ No newline at end of file -- cgit v1.2.3 From dee093bb9178450ec2975daed172a5ba0573b93e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Nov 2007 05:10:06 -0500 Subject: web commit by http://ptecza.myopenid.com/: * Fix signature --- doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn b/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn index 2947dc70f..76f62b68a 100644 --- a/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn +++ b/doc/todo/Allow_web_edit_form_comment_field_to_be_mandatory.mdwn @@ -5,6 +5,4 @@ In our team internal wiki, we wish to impose a policy that all edits must have a > Good idea! I also hate empty commit comments, but I know that it's also a matter > of human mentality. Of course, you can forbid users to commit empty comments, -> but then they can commit so worthless comments like "\*" or "\* blah". -> -> --[[Paweł|ptecza]] \ No newline at end of file +> but then they can commit so worthless comments like "\*" or "\* blah". --[[Paweł|ptecza]] \ No newline at end of file -- cgit v1.2.3 From a5e27e4c54f3236de7c768536e5e08140b6f3ddc Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Nov 2007 09:14:36 -0500 Subject: web commit by tschwinge: *forward*ing functionality for the meta plugin. --- ...__forward__42__ing_functionality_for_the_meta_plugin.mdwn | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/todo/__42__forward__42__ing_functionality_for_the_meta_plugin.mdwn 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 new file mode 100644 index 000000000..f740d75e3 --- /dev/null +++ b/doc/todo/__42__forward__42__ing_functionality_for_the_meta_plugin.mdwn @@ -0,0 +1,12 @@ +Here is a patch [[tag patch]] to add a *forward*ing functionality +to the [[`meta`_plugin|plugins/meta]]. + +Find the most recent version at +. + +I can't use `scrub(...)`, as that will strip out the forwarding HTML command. +How to deal with that? + +I can also submit a Git patch, if desired. + +--[[tschwinge]] -- cgit v1.2.3 From 38df3288a72ec263f85297294649fe455bf56934 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Nov 2007 09:27:56 -0500 Subject: web commit by tschwinge: Should perhaps explain the syntax. Done that extra-extensively now. ;-) --- ...forward__42__ing_functionality_for_the_meta_plugin.mdwn | 14 ++++++++++++++ 1 file changed, 14 insertions(+) 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 f740d75e3..30bcbd58f 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 @@ -9,4 +9,18 @@ How to deal with that? I can also submit a Git patch, if desired. + +*Syntax:* + +**URL** = http://some.nice/place/ (*etc.*) + +**WHITHER** = \[\[**[[wikilink]]**]] | **URL** + +**D** = natural number (*meaning seconds*) + +**OPT_DELAY** = delay=**D** | empty (*immediatelly*) + +\[[meta forward="*WHITHER*" *OPT_DELAY*]] + + --[[tschwinge]] -- cgit v1.2.3 From e589b2aa6122420fd974a258411bdfb537eabc73 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Nov 2007 12:11:31 -0500 Subject: web commit by http://joey.kitenet.net/: test --- doc/sandbox.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/sandbox.mdwn b/doc/sandbox.mdwn index 04c71446a..ab1d91d89 100644 --- a/doc/sandbox.mdwn +++ b/doc/sandbox.mdwn @@ -1,7 +1,7 @@ This is the SandBox, a page anyone can edit to try out ikiwiki. ---- -Do re me fa so la te... git! +Do re me fa so la te... git? i see. i see. lalala hmmmmmmmm. -- cgit v1.2.3