From 3d619726e5d6e0a769ad705c4a4298f6b28aa743 Mon Sep 17 00:00:00 2001 From: Tom Feist Date: Mon, 23 Aug 2010 01:22:09 +0100 Subject: lots of doc updates --- docs/Irssi/UI/Theme.pod | 66 ++++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 63 insertions(+), 3 deletions(-) (limited to 'docs/Irssi/UI') diff --git a/docs/Irssi/UI/Theme.pod b/docs/Irssi/UI/Theme.pod index 323e6b3..344b5ae 100644 --- a/docs/Irssi/UI/Theme.pod +++ b/docs/Irssi/UI/Theme.pod @@ -10,11 +10,59 @@ Irssi::UI::Theme =head2 C -I +C<$flags> is an optional bitmask of any of the following flags: + +=over + +=item C + +Any replacements specified in the theme are not applied to this expansion. + +=item C + +B + +=item C + +If the format contains variables and no values are specified, an empty string is +returned instead of a partially filled template. + +=back + +B + +Example: + + my $formatted_str = Irssi::current_theme()->format_expand('{hilight Hello}'); + +B. Weird> =head2 C -I +Returns the unexpanded format template for the format name supplied in C<$tag>. + +Valid values for C<$module> are: + +=over + +=item C + +=item C + +=item C + +=item C + +=item C + +=item C + +=back + +Example: + + my $pubmsg_format = Irssi::current_theme()->get_format('fe-common/core', 'pubmsg'); =head1 THEME DETAILS @@ -49,7 +97,19 @@ The actual mechanism used by Irssi to print text into the client involves a certain amount of indirection, which allows themes to reformat messages in various ways before they are displayed. -The overall structure of these +The overall structure of these templates is based around 3 basic ideas: + +=over + +=item Nested Templates + +=item Colour Codes + +=item Variable Expansion + +=item Special Variables + +=back The real text formats that irssi uses are the ones you can find with /FORMAT command. Back in the old days all the colors and texts were mixed -- cgit v1.2.3