1 Very nice! There are some rough spots yes, but this looks exactly as I'd
2 hoped it would, and seems close to being ready for merging.
4 A few observations, in approximate order of priority:
6 * What's the copyright and license of showdown? Please include that from
8 * What happens if there are concurrent edits? The CGI.pm modification to
9 save an edited wikiwyg part doesn't seem to check if the source file has
10 changed in the meantime, so if the part has moved around, it might
11 replace the wrong part on saving. I've not tested this.
12 * The stuff you have in destdir now really belongs in basewiki so it's
13 copied over to any destdir.
14 * Personally, I'm not sure if I need double-click to edit a section in my
15 wiki, but I'd love it if the edit form in the cgi could use wikiwyg. Seems
16 like both of these could be independent options. Doable, I'm sure?
17 * It would be good to move as much as possible of the inlined javascript in
18 wikiwyg.tmpl out to a separate .js file to save space in the rendered
20 * Both this plugin and the [[Gallery_Plugin_for_Ikiwiki]] are turning out
21 to need to add a bunch of pages to the basewiki. I wonder what would be a
22 good way to do this, without bloating the basewiki when the plugins arn't
23 used. Perhaps the underlaydir concept needs to be expanded so it's a set
24 of directories, which plugins can add to. Perhaps you should work with
25 arpitjain on this so both plugins can benefit. (The smiley plugin would
26 also benefit from this..)
27 * Is there any way of only loading enough of wikiwyg by default to catch
28 the section double-clicks, and have it load the rest on the fly? I'm
29 thinking about initial page load time when visiting a wikiwyg-using wiki
30 for the first time. I count 230k or so of data that a browser downloads