web commit by hb

[git.ikiwiki.info.git] / doc / index / discussion.mdwn

diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
index ac4f32d2661076e4cb5ce4622dcd160a37f6d324..4374130fae46c949e087575c75b886f8533a601a 100644 (file)
--- a/doc/index/discussion.mdwn
+++ b/doc/index/discussion.mdwn
@@ -5,6 +5,8 @@ Do so here..
 Note that for more formal bug reports or todo items, you can also edit the
 [[bugs]] and [[todo]] pages.
 
 Note that for more formal bug reports or todo items, you can also edit the
 [[bugs]] and [[todo]] pages.
 

+[[toc ]]
+

 # Installation/Setup questions
 
 I have just installed ikiwiki and it works - at least I have the example index.mdwn page
 # Installation/Setup questions
 
 I have just installed ikiwiki and it works - at least I have the example index.mdwn page


@@ -85,40 +87,6 @@ easily, perl is possible (but I'm not strong in perl).
 
 ----
 
 
 ----
 

-# OpenID
-
-I just figured I'd edit something on the page with my OpenID, since you've implemented it! --*[Kyle](http://kitenet.net/~kyle/)*=
-
-> Kyle, If you like openid, I can switch your personal wiki over to use your openid. --[[Joey]]
-
----- 
-
-# ACL
-
-> Moved to [[todo/ACL]] --[[Joey]]
-
-----
-
-Some questions about the RecentChanges function. -- Ethan
-
-> (Moved to [[todo/recentchanges]] --[[Joey]])
-
-----
-
-Also, I'd like to request another template parameter which is just
-$config{url}. That way you won't have to hard-code the URL of the wiki into
-the template. -- Ethan
-
-> That's already available in the BASEURL parameter. --[[Joey]]
-
-----
-
-# Canonical feed location?
-
-Moved to [[todo/canonical_feed_location]] --[[Joey]]
-
-----
-

 # asciidoc or txt2tags ?
 
 Any plugins or support for using asciidoc or txt2tags as the wiki language and/or exporting to asciidoc or txt2tags?
 # asciidoc or txt2tags ?
 
 Any plugins or support for using asciidoc or txt2tags as the wiki language and/or exporting to asciidoc or txt2tags?


@@ -144,6 +112,8 @@ Any plugins or support for exporting to LaTeX?
 >>
 >> --JeremyReed
 
 >>
 >> --JeremyReed
 

+>>> Have a look at [pandoc](http://code.google.com/p/pandoc/).  It can make PDFs via pdflatex. --[[roktas]]
+

 ----
 
 # Using with CVS?
 ----
 
 # Using with CVS?


@@ -182,51 +152,87 @@ Any setting for limiting how many kilobytes can be submitted via the "edit" form
 
 ----
 
 
 ----
 

-# Disable sub-discussion pages?
+# Access Keys
+
+Would anyone else find this a valuable addition.  In oddmuse and instiki (the only other
+wiki engines I am currently using, the edit, home, and submit link tags have an
+accesskey attribute.  I find it nice not to have to resort to the mouse for those
+actions.  However, it may not be something everyone appreciates.  Any thoughts?
+--[Mazirian](http://mazirian.com)

 
 

-Moved to [[bugs]] -- [[Joey]]
+> Maybe, although it would need to take the critisism at
+> http://www.cs.tut.fi/~jkorpela/forms/accesskey.html into account.
+
+>> Thank you for that link. Given that the edit link is the first thing you tab to
+>> in the current layout, I guess it isn't all that necessary. I have had a 
+>> a user complaint recently that Alt-e in oddmuse was overriding his access
+>> to the browser menu.

 
 ----
 
 
 ----
 

-# wiki\_file\_regexp and RCS ,v files
+# Editing the style sheet.

 
 

-I have RCS ,v files in my source directory. But get many "skipping bad filename" warnings.
+It would be nice to be able to edit the stylesheet by means of the cgi.  Or is this possible?  I wasn't able to achieve it.
+Ok, that's my last 2 cents for a while. --[Mazirian](http://mazirian.com)

 
 

-Also I don't see wiki\_file\_regexp documented. Because it is used with $config{wiki\_file\_regexp} I assume it can be set in the ikiwiki.setup.
-I added a comma to it in my IkiWiki.pm in the defaultconfig(). But that was wrong (so I reverted back), because then the ,v files were copied to my www tree.
+> I don't support editing it, but if/when ikiwiki gets file upload support,
+> it'll be possible to upload a style sheet. (If .css is in the allowed
+> extensions list.. no idea how safe that would be, a style sheet is
+> probably a great place to put XSS attacks and evil javascript that would
+> be filtered out of any regular page in ikiwiki). --[[Joey]]

 
 

-What is the correct way to include ,v RCS revision files in my source tree without receiving the "bad" messages and without copying over to www tree?
+>> I hadn't thought of that at all.  It's a common feature and one I've
+>> relied on safely, because the wikis I am maintaining at the moment
+>> are all private and restricted to trusted users. Given that the whole
+>> point of ikiwiki is to be able to access and edit via the shell as
+>> well as the web, I suppose the features doesn't add a lot.  By the
+>> way, the w3m mode is brilliant.  I haven't tried it yet, but the idea
+>> is great.

 
 

--- [[JeremyReed]]
+----
+
+# RecentChanges should show path to wiki sub-pages?

 
 

-> Add the ,v to the $config{wiki_file_prune_regexps} array. This is how we
-> skip equivilant files from other revision control systems too.
-> --[[Joey]]]
+The RecentChanges only shows the final file name for the recently changes file,
+for example "discussion". It would be more useful to see "index/discussion"
+or the path to the sub-page. I think this is handled by the htmllink() routine.
+
+> Went ahead and did this, IMHO the display is ok as-is. --[[Joey]]

 
 ----
 
 
 ----
 

-# Textile Plugin
+# Should not create an existing page
+
+This might be a bug, but will discuss it here first.
+Clicking on an old "?" or going to a create link but new Markdown content exists, should not go into "create" mode, but should do a regular "edit".

 
 

-It was trivial, but I put together a plugin that uses the Textile markup
-language, which I find to be the most superior of the various options for
-that sort of thing.  Where or how do I submit it for inclusion?
+> I belive that currently it does a redirect to the new static web page.
+> At least that's the intent of the code. --[[Joey]]

 
 

-> You can post it to [[plugins/contrib]]. --[[Joey]]
+>> Try at your site: `?page=discussion&from=index&do=create`
+>> It brings up an empty textarea to start a new webpage -- even though it already exists here. --reed

 
 

->> Thanks.  I tried using the "Add new post" form there, but apparently made a [mess of things somehow](http://ikiwiki.kitenet.net/contrib/textile___40__third-party_plugin__41__.html).  Sorry about that.
+>>> Ah, right. Notice that the resulting form allows saving the page as
+>>> discussion, or users/discussion, but not index/discussion, since this
+>>> page already exists. If all the pages existed, it would do the redirect
+>>> thing. --[[Joey]]

 
 

->>> No problem, the contrib form had the wrong rootpage setting. I've fixed
->>> it up and moved it to the right place. A copyright statement would be
->>> nice.
+----

 
 

-> How does one go about making a markup language added by means of a plugin, the default markup language.  In other words, I would like the index page to be written in Textile.
-> If I include a index.txtl (where txtl is the extension I have assigned to be handled by the textile plugin), ikiwiki will ignore it and make a new index.mdwn.
+# Refreshing RecentChanges page

 
 

->> Sounds like a bug; it should be configurable via `default_pageext`, but
->> I suspect that currently if there are two competing files with different
->> extensions that make the same page, they fight it out and some random
->> one "wins" 
->> 
->> Until I fix that, you can avoid the one from the underlay directory by
->> setting `underlaydir` to point to an empty directory. --[[Joey]]
->>
+What do you think about refreshing RecentChanges page (via Meta Refresh Tag)?
+It can be useful for users like me which rather prefer watching the last changes
+in WWW browser tab than subscribing to page. --Pawel
+
+> Depends, if it were done the time period should be made configurable.
+> Unwanted server load due to refeshing could be a problem for some.
+> --[[Joey]]
+
+>> Yes, it should be configurable by ikiwiki admin. I believe he's not
+>> stupid and he will not set too short refresh period to kill his server :)
+>> I propose to add `recentchanges_refresh` variable in ikiwiki setup
+>> to setting refresh period. If it's not defined, then ikiwiki doesn't put
+>> refresh meta tag into `recentchanges.tmpl`. Do you like it? ;) --Pawel
+
+>>> Seems reasonable --[[Joey]]