1 This is an idea from [[JoshTriplett]]. --[[Joey]]
3 Some uses of ikiwiki, such as for a bug-tracking system (BTS), move a bit away from the wiki end
4 of the spectrum, and toward storing structured data about a page or instead
7 For example, in a bug report you might want to choose a severity from a
8 list, enter a version number, and have a bug submitter or owner recorded,
9 etc. When editing online, it would be nice if these were separate fields on
10 the form, rather than the data being edited in the big edit form.
12 There's a tension here between remaining a wiki with human-editable source
13 files, containing freeform markup, and more structured data storage. I
14 think that it would be best to include the structured data in the page,
15 using a directive. Something like:
18 \[[data yaml="<arbitrary yaml here>"]]
21 As long as the position of the directive is not significant, it could be
22 stripped out when web editing, the yaml used to generate/populate form fields,
23 and then on save, the directive regenerated and inserted at top/bottom of
26 Josh thinks that yaml is probably a good choice, but the source could be a
27 `.yaml` file that contains no directives, and just yaml. An addition
28 complication in this scenario is, if the yaml included wiki page formatted content,
29 ikiwiki would have to guess or be told what markup language it used.
31 Either way, the yaml on the page would encode fields and their current content.
32 Information about data types would be encoded elsewhere, probably on a
33 parent page (using a separate directive). That way, all child pages could
34 be forced to have the same fields.
36 There would be some simple types like select, boolean, multiselect, string, wiki markup.
37 Probably lists of these (ie, list of strings). Possibly more complex data
40 It should also be possible for plugins to define new types, and the type
41 definitions should include validation of entered data, and how to prompt
42 the user for the data.
44 This seems conceptually straightforward, if possibly quite internally
45 complex to handle the more complicated types and validation.
47 One implementation wrinkle is how to build the html form. The editpage.tmpl
48 currently overrides the standard [[!cpan CGI::FormBuilder]] generated form,
49 which was done to make the edit page be laid out in a nice way. This,
50 however, means that new fields cannot be easily added to it using
51 [[!cpan CGI::FormBuilder]]. The attachment plugin uses the hack of bouilding
52 up html by hand and dumping it into the form via a template variable.
54 It would be nice if the type implementation code could just use
55 FormBuilder, since its automatic form generation, and nice field validation
56 model is a perfect match for structured data. But this problem with
57 editpage.tmpl would have to be sorted out to allow that.
61 * Pagespecs that can select pages with a field with a given value, etc.
62 This should use a pagespec function like field(fieldname, value). The
63 semantics of this will depend on the type of the field; text fields will
64 match value against the text, and link fields will check for a link
65 matching the pagespec value.
66 * The search plugin could allow searching for specific fields with specific
67 content. (xapian term search is a good fit).
71 [[tracking_bugs_with_dependencies]]
73 > I was also thinking about this for bug tracking. I'm not sure what
74 > sort of structured data is wanted in a page, so I decided to brainstorm
77 > * You just want the page to be pretty.
78 > * You want to access the data from another page. This would be almost like
79 > like a database lookup, or the OpenOffice Calc [VLookup](http://wiki.services.openoffice.org/wiki/Documentation/How_Tos/Calc:_VLOOKUP_function) function.
80 > * You want to make a pagespec depend upon the data. This could be used
81 > for dependancy tracking - you could match against pages listed as dependencies,
82 > rather than all pages linked from a given page.
84 >The first use case is handled by having a template in the page creation. You could
85 >have some type of form to edit the data, but that's just sugar on top of the template.
86 >If you were going to have a web form to edit the data, I can imagine a few ways to do it:
88 > * Have a special page type which gets compiled into the form. The page type would
89 > need to define the form as well as hold the stored data.
90 > * Have special directives that allow you to insert form elements into a normal page.
92 >I'm happy with template based page creation as a first pass...
94 >The second use case could be handled by a regular expression directive. eg:
96 > \[[regex spec="myBug" regex="Depends: ([^\s]+)"]]
98 > The directive would be replaced with the match from the regex on the 'myBug' page... or something.
100 >The third use case requires a pagespec function. One that matched a regex in the page might work.
101 >Otherwise, another option would be to annotate links with a type, and then check the type of links in
102 >a pagespec. e.g. you could have `depends` links and normal links.
104 >Anyway, I just wanted to list the thoughts. In none of these use cases is straight yaml or json the
105 >obvious answer. -- [[Will]]
107 >> Okie. I've had a play with this. A 'form' plugin is included inline below, but it is only a rough first pass to
108 >> get a feel for the design space.
110 >> The current design defines a new type of page - a 'form'. The type of page holds YAML data
111 >> defining a FormBuilder form. For example, if we add a file to the wiki source `test.form`:
116 comment: This is a test
120 >> The YAML content is a series of nested hashes. The outer hash is currently checked for two keys:
121 >> 'template', which specifies a parameter to pass to the FromBuilder as the template for the
122 >> form, and 'fields', which specifies the data for the fields on the form.
123 >> each 'field' is itself a hash. The keys and values are arguments to the formbuilder form method.
124 >> The most important one is 'value', which specifies the value of that field.
126 >> Using this, the plugin below can output a form when asked to generate HTML. The Formbuilder
127 >> arguments are sanitized (need a thorough security audit here - I'm sure I've missed a bunch of
128 >> holes). The form is generated with default values as supplied in the YAML data. It also has an
129 >> 'Update Form' button at the bottom.
131 >> The 'Update Form' button in the generated HTML submits changed values back to IkiWiki. The
132 >> plugin captures these new values, updates the YAML and writes it out again. The form is
133 >> validated when edited using this method. This method can only edit the values in the form.
134 >> You cannot add new fields this way.
136 >> It is still possible to edit the YAML directly using the 'edit' button. This allows adding new fields
137 >> to the form, or adding other formbuilder data to change how the form is displayed.
139 >> One final part of the plugin is a new pagespec function. `form_eq()` is a pagespec function that
140 >> takes two arguments (separated by a ','). The first argument is a field name, the second argument
141 >> a value for that field. The function matches forms (and not other page types) where the named
142 >> field exists and holds the value given in the second argument. For example:
144 \[[!inline pages="form_eq(age,15)" archive="yes"]]
146 >> will include a link to the page generated above.
148 >>> Okie, I've just made another plugin to try and do things in a different way.
149 >>> This approach adds a 'data' directive. There are two arguments, `key` and `value`.
150 >>> The directive is replaced by the value. There is also a match function, which is similar
151 >>> to the one above. It also takes two arguments, a key and a value. It returns true if the
152 >>> page has that key/value pair in a data directive. e.g.:
154 \[[!data key="age" value="15"]]
156 >>> then, in another page:
158 \[[!inline pages="data_eq(age,15)" archive="yes"]]
160 >>> I expect that we could have more match functions for each type of structured data,
161 >>> I just wanted to implement a rough prototype to get a feel for how it behaves. -- [[Will]]
163 >> Anyway, here are the plugins. As noted above these are only preliminary, exploratory, attempts. -- [[Will]]
165 >>>> I've just updated the second of the two patches below. The two patches are not mutually
166 >>>> exclusive, but I'm leaning towards the second as more useful (for the things I'm doing). -- [[Will]]
169 # Interpret YAML data to make a web form
170 package IkiWiki::Plugin::form;
174 use CGI::FormBuilder;
178 hook(type => "getsetup", id => "form", call => \&getsetup);
179 hook(type => "htmlize", id => "form", call => \&htmlize);
180 hook(type => "sessioncgi", id => "form", call => \&cgi_submit);
183 sub getsetup () { #{{{
187 rebuild => 1, # format plugin
191 sub makeFormFromYAML ($$$) { #{{{
193 my $YAMLString = shift;
198 eval q{use CGI::FormBuilder};
201 my ($dataHashRef) = YAML::Load($YAMLString);
203 my @fields = keys %{ $dataHashRef->{fields} };
205 unshift(@fields, 'do');
206 unshift(@fields, 'page');
207 unshift(@fields, 'rcsinfo');
209 # print STDERR "Fields: @fields\n";
213 $submittedPage = $q->param('page') if defined $q;
215 if (defined $q && defined $submittedPage && ! ($submittedPage eq $page)) {
216 error("Submitted page doensn't match current page: $page, $submittedPage");
219 error("Page not backed by file") unless defined $pagesources{$page};
220 my $file = $pagesources{$page};
224 if (defined $dataHashRef->{template}) {
225 $template = $dataHashRef->{template};
227 $template = "form.tmpl";
230 my $form = CGI::FormBuilder->new(
234 required => [qw{page}],
236 action => $config{cgiurl},
237 template => scalar IkiWiki::template_params($template),
238 wikiname => $config{wikiname},
245 $form->field(name => 'do', value => 'Update Form', required => 1, force => 1, type => 'hidden');
246 $form->field(name => 'page', value => $page, required => 1, force => 1, type => 'hidden');
247 $form->field(name => 'rcsinfo', value => IkiWiki::rcs_prepedit($file), required => 1, force => 0, type => 'hidden');
250 foreach my $x (qw{label type multiple value fieldset growable message other required validate cleanopts columns comment disabled linebreaks class}) {
254 while ( my ($name, $data) = each(%{ $dataHashRef->{fields} }) ) {
255 next if $name eq 'page';
256 next if $name eq 'rcsinfo';
258 while ( my ($key, $value) = each(%{ $data }) ) {
259 next unless $validkey{$key};
260 next if $key eq 'validate' && !($value =~ /^[\w\s]+$/);
262 # print STDERR "Adding to field $name: $key => $value\n";
263 $form->field(name => $name, $key => $value);
267 # IkiWiki::decode_form_utf8($form);
272 sub htmlize (@) { #{{{
274 my $content = $params{content};
275 my $page = $params{page};
277 my $form = makeFormFromYAML($page, $content, undef);
279 return $form->render(submit => 'Update Form');
282 sub cgi_submit ($$) { #{{{
286 my $do=$q->param('do');
287 return unless $do eq 'Update Form';
288 IkiWiki::decode_cgi_utf8($q);
292 eval q{use CGI::FormBuilder};
295 my $page = $q->param('page');
297 return unless exists $pagesources{$page};
299 return unless $pagesources{$page} =~ m/\.form$/ ;
301 return unless IkiWiki::check_canedit($page, $q, $session);
303 my $file = $pagesources{$page};
304 my $YAMLString = readfile(IkiWiki::srcfile($file));
305 my $form = makeFormFromYAML($page, $YAMLString, $q);
307 my ($dataHashRef) = YAML::Load($YAMLString);
309 if ($form->submitted eq 'Update Form' && $form->validate) {
311 #first update our data structure
313 while ( my ($name, $data) = each(%{ $dataHashRef->{fields} }) ) {
314 next if $name eq 'page';
315 next if $name eq 'rcs-data';
317 if (defined $q->param($name)) {
318 $data->{value} = $q->param($name);
322 # now write / commit the data
324 writefile($file, $config{srcdir}, YAML::Dump($dataHashRef));
326 my $message = "Web form submission";
328 IkiWiki::disable_commit_hook();
329 my $conflict=IkiWiki::rcs_commit($file, $message,
330 $form->field("rcsinfo"),
331 $session->param("name"), $ENV{REMOTE_ADDR});
332 IkiWiki::enable_commit_hook();
333 IkiWiki::rcs_update();
335 require IkiWiki::Render;
338 IkiWiki::redirect($q, "$config{url}/".htmlpage($page)."?updated");
341 error("Invalid data!");
347 package IkiWiki::PageSpec;
349 sub match_form_eq ($$;@) { #{{{
352 my @args=split(/,/, $argSet);
353 my $field=shift @args;
354 my $value=shift @args;
356 my $file = $IkiWiki::pagesources{$page};
358 if ($file !~ m/\.form$/) {
359 return IkiWiki::FailReason->new("page is not a form");
362 my $YAMLString = IkiWiki::readfile(IkiWiki::srcfile($file));
367 my ($dataHashRef) = YAML::Load($YAMLString);
369 if (! defined $dataHashRef->{fields}->{$field}) {
370 return IkiWiki::FailReason->new("field '$field' not defined in page");
373 my $formVal = $dataHashRef->{fields}->{$field}->{value};
375 if ($formVal eq $value) {
376 return IkiWiki::SuccessReason->new("field value matches");
378 return IkiWiki::FailReason->new("field value does not match");
387 # Allow data embedded in a page to be checked for
388 package IkiWiki::Plugin::data;
397 hook(type => "getsetup", id => "data", call => \&getsetup);
398 hook(type => "needsbuild", id => "data", call => \&needsbuild);
399 hook(type => "preprocess", id => "data", call => \&preprocess, scan => 1);
400 hook(type => "preprocess", id => "datatable", call => \&preprocess_table, scan => 1); # does this need scan?
403 sub getsetup () { #{{{
407 rebuild => 1, # format plugin
411 sub needsbuild (@) { #{{{
412 my $needsbuild=shift;
413 foreach my $page (keys %pagestate) {
414 if (exists $pagestate{$page}{data}) {
415 if (exists $pagesources{$page} &&
416 grep { $_ eq $pagesources{$page} } @$needsbuild) {
417 # remove state, it will be re-added
418 # if the preprocessor directive is still
419 # there during the rebuild
420 delete $pagestate{$page}{data};
426 sub preprocess (@) { #{{{
428 my %params=@argslist;
431 my $class = defined $params{class}
432 ? 'class="'.$params{class}.'"'
436 $html = "<th $class >$params{key}:</th><td $class >";
438 $html = "<span $class >$params{key}:";
441 while (scalar(@argslist) > 1) {
442 my $type = shift @argslist;
443 my $data = shift @argslist;
444 if ($type eq 'link') {
446 $pagestate{$params{page}}{data}{$params{key}}{link}{$data} = 1;
447 my $link=IkiWiki::linkpage($data);
448 add_depends($params{page}, $link);
449 $html .= ' ' . htmllink($params{page}, $params{destpage}, $link);
450 } elsif ($type eq 'data') {
451 $data = IkiWiki::preprocess($params{page}, $params{destpage},
452 IkiWiki::filter($params{page}, $params{destpage}, $data));
453 $html .= ' ' . $data;
454 # store data after processing - allows pagecounts to be stored, etc.
455 $pagestate{$params{page}}{data}{$params{key}}{data}{$data} = 1;
468 sub preprocess_table (@) { #{{{
472 push @lines, defined $params{class}
473 ? "<table class=\"".$params{class}.'">'
478 foreach my $line (split(/\n/, $params{datalist})) {
479 push @lines, "<tr>" . IkiWiki::preprocess($params{page}, $params{destpage},
480 IkiWiki::filter($params{page}, $params{destpage}, $line)) . "</tr>";
485 push @lines, '</table>';
487 return join("\n", @lines);
490 package IkiWiki::PageSpec;
492 sub match_data_eq ($$;@) { #{{{
495 my @args=split(/,/, $argSet);
497 my $value=shift @args;
499 if (! exists $IkiWiki::pagestate{$page}{data}) {
500 return IkiWiki::FailReason->new("page does not contain any data directives");
503 if (! exists $IkiWiki::pagestate{$page}{data}{$key}) {
504 return IkiWiki::FailReason->new("page does not contain data key '$key'");
507 if ($IkiWiki::pagestate{$page}{data}{$key}{data}{$value}) {
508 return IkiWiki::SuccessReason->new("value matches");
510 return IkiWiki::FailReason->new("value does not match");
514 sub match_data_link ($$;@) { #{{{
518 my @args=split(/,/, $argSet);
520 my $value=shift @args;
522 if (! exists $IkiWiki::pagestate{$page}{data}) {
523 return IkiWiki::FailReason->new("page $page does not contain any data directives and so cannot match a link");
526 if (! exists $IkiWiki::pagestate{$page}{data}{$key}) {
527 return IkiWiki::FailReason->new("page $page does not contain data key '$key'");
530 foreach my $link (keys %{ $IkiWiki::pagestate{$page}{data}{$key}{link} }) {
531 # print STDERR "Checking if $link matches glob $value\n";
532 if (match_glob($link, $value, @params)) {
533 return IkiWiki::SuccessReason->new("Data link on page $page with key $key matches glob $value: $link");
537 return IkiWiki::FailReason->new("No data link on page $page with key $key matches glob $value");