Re: [Phpwiki-talk] AppendTextPlugin revision 1.3

[Reini U. <ru...@x-...>]

Pascal Giard (QC/EMC) schrieb:
i also added the "redirect" parameter.
> at the moment, it's boolean, but maybe it'd be smarter to make it 
> support the destination page as a value ?
> 
> That might be interesting if you modify a page from another one and want 
> to come back to the modificator.

What I really want is the following as default:

If the current page and the target page (the page argument) are the 
same, display after the successful AppendText action the changed page 
directly, and an AppendText notification at the top of the page. As on 
SearchHighlight and

No link to the changed page, the page directly.

Only if the basepage is different, display the link to the changed page.

> a comment on the copyrights, i don't necessarly want to be the copyright 
> holder. I don't mind if the phpwiki team is the copyright holder and 
> that i'm cited as a contributor.

Ok.

> PS: do you plan to add the snippets you pasted me in the standard edit 
> page ?

Something like this, just better. The AddCategory button is already 
there, the plugin part not yet.
What is missing is that the popup window on the AddCategory button 
should generate an extra request to get those pages. A category "popup 
on demand".
Currently the traversal is done on each edit request, which I want to 
avoid, cause edit already is slow enough. The user can wait a bit to get 
the matching categories and plugins to insert into, after pressing the icon.

And the plugin part needs some prefix and suffix.

<?plugin WikiFormRich action=AppendText buttontext="AddPlugin"
    pulldown[] name=text value="<?plugin <!plugin-list BackLinks 
page=WikiPlugin !> ?">
    ?>
would be cool, but probably too hard.

<?plugin WikiFormRich action=AppendText buttontext="AddCategory"
   pulldown[] name=text value=<!plugin-list TitleSearch s=Category !>
   ?>

Of course you can change the editpage.tmpl to add these pulldowns on 
every edit request, but I prefer a js generated button. Just don't know 
if MacOSX Safari has still a problem with those generated js buttons and 
how to overcome.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/