[dev] Notifications and embedded hyperlinks
Jan Schneider
jan at horde.org
Fri Mar 5 00:58:21 PST 2004
Zitat von Jon Parise <jon at horde.org>:
> On Thu, Mar 04, 2004 at 11:39:34PM -0500, Chuck Hagenbuch wrote:
>
>> >As a compromise, I'd like to go ahead and add the $flags parameter.
>> >Then, we could have the following flags:
>> >
>> > NOTIFICATION_RAW - don't peform any encoding / conversions
>> > NOTIFICATION_WIKI - perform Wiki-style translations
>> > ...
>> >
>> >That will give us the flexibility to try different implementations in
>> >the future without modifying the API. Suggestions on better flag
>> >names (or additional flags) are welcome.
>>
>> That's fine with me. Two suggestions - how about using strings for
>> the flags, like we use strings for the message types (just for
>> consistency, mainly). So 'markup.raw' (default), 'markup.wiki', etc.
>> Also, then non-markup flags could have a different prefix. It's a
>> namespace! ;)
>
> How would you combine flags from multiple namespaces?
With an array of flags?
>> Second, how about a markup.html type, since that'd be much lighter
>> weight than wiki markup and also simple for things like the
>> Horde_Mobile listener to strip.
>
> Okay. For consistency, I'd suggest:
>
> markup.raw No encoding or converions.
> markup.plain HTML entities are converted to allow plain text.
Being the default if none specified.
> markup.html HTML entities are either rendered or stripped.
> markup.wiki Wiki-style commands are interpretted and rendered.
Sounds good. But if we allow html, wiki would be a tad too much overhead I
guess.
Jan.
--
http://www.horde.org - The Horde Project
http://www.ammma.de - Neue Wege des Lernens
http://www.tip4all.de - Deine private Tippgemeinschaft
More information about the dev
mailing list