On Sep 18, 2008, at 10:57 PM, Chris Meller wrote:
>
>
> On Thu, Sep 18, 2008 at 10:52 PM, Owen Winkler <[EMAIL PROTECTED]>
> wrote:
>
> <snip>
>
> Maybe this feature could be part of the String class:
>
> String::add_format('out', 'fn_autop');
> String::add_format('out', 'fn_fancypants');
> function filter_format_fn_autop($value) { return autop($value); }
> function filter_format_fn_fancypants($value, $quotestyle) {
> return fancy_quoted_thing($value, $quotestyle);
> }
> echo $foo->out(array('fn_fancypants'=>FP_UBER_FANCY));
>
> Or something?
>
> Sounds good to me.
>
> I dunno. I'm wondering if anyone's happy with the current
> arrangement.
>
> I have no opinion on it one way or another really.
>
> We should also consider how to handle pre-caching on post content;
> content input filtering. We have a field for storing it. I can't
> think
> of a good reason for applying all of these filters at runtime.
>
> I've never understood how anyone could envision something like this.
> The post content we store should be totally raw, because my whims
> change at random. If I get sick of the stupid fancypants formatting,
> I want it to go away on everything dynamically - I think that's half
> the point of having a plugin filtering system.
I would assume that we would have a system which clears the cached
content whenever filters are changed (plugin deactivation/activation).
--~--~---------~--~----~------------~-------~--~----~
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/habari-dev
-~----------~----~----~----~------~----~------~--~---
