On Oct 5, 7:56 pm, The Editor <[email protected]> wrote:
> All right. I'll look into this. I suppose we could pass an array back
> from the custom function--one with content and two with a flag to
> return or continue processing. This would allow you to either return
> immediately, or continue on through the rest of the function.
this would be a step forward. it would allow to inject some custom
code before the standard function, but not after unfortunately.
> Or
> perhaps we could have an array of functions called in some order, by
> default including the core page save routine, but not necessarily.
> This could really open things up--which I like! Can you remember how
> PmWiki did this? I never got to that point in understanding its inner
> workings.
the PmWiki way it reminds the array $BOLTstartupProcess which is a
list of functions to be called at a certain point. the difference
being that the order of the list is very important.
eg. (the functions are just an example)
$EditFunctions = array
('Stamp','Diff','ReplaceOnSave','SaveData','SavePage');
all the functions take the same args (pagename, content, etc) which
are passed from one to the other and it is like a pipe through which
the page goes when saving, with the benefit that you could customize
(or even disable, let's say) a specific part of the whole process, or
inject some custom code at a specific point.
blues
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
