/ - Diff - projekt kivitendo - wissen

     overwritten with C<$params{id}>).
     An additional dummy input will be generated which is used to find
     parts. For a detailed description of it's behaviour, see section
     parts. For a detailed description of its behaviour, see section
     C<PART PICKER SPECIFICATION>.
     C<$value> can be a parts id or a C<Rose::DB:Object> instance.
-...
     If C<%params> contains C<convertible_unit> only parts with a unit
     that's convertible to unit will be used for autocompletion.
     Obsolete parts will by default not displayed for selection. However they are
     Obsolete parts will by default not be displayed for selection. However they are
     accepted as default values and can persist during updates. As with other
     selectors though, they are not selectable once overridden.
-...
     =item *
     Should not be constraint to exact matches
     Should not be constrained to exact matches
     =back
-...
     =item 5
     An internal status of the part picker, indicating wether id input and dummy
     An internal status of the part picker, indicating whether id input and dummy
     input are consistent. After leaving the dummy input the part picker must
     place itself in a consistent status.

     =item C<with_columns>
     Can be set by the caller to indicate additional columns to
     list. Currently supported:
     be listed. Currently supported:
     =over 2
     =item C<record_link_destination>
     The record link destination. Requires that the records to list have
     The record link destination. Requires that the records to be listed have
     been retrieved via the L<SL::DB::Helper::LinkedRecords> helper.
     =back
-...
     =item C<edit_record_links>
     If trueish additional controls will be rendered that allow the user to
     remove and add record links. Requires that the records to list have
     remove and add record links. Requires that the records to be listed have
     been retrieved via the L<SL::DB::Helper::LinkedRecords> helper.
     =back

     =head1 SYNOPSIS
     Usage from a template:
     Usage in a template:
       [% USE P %]
-...
       [% P.select_tag('direction', [ { direction => 'left',  display => 'To the left'  },
                                      { direction => 'right', display => 'To the right' } ],
                                    value_key => 'direction', title_key => 'display', default => 'right')) %]
                                    value_key => 'direction', title_key => 'display', default => 'right') %]
       [% P.select_tag('direction', [ { direction => 'left',  display => 'To the left'  },
                                      { direction => 'right', display => 'To the right', selected => 1 } ],
                                    value_key => 'direction', title_key => 'display')) %]
                                    value_key => 'direction', title_key => 'display') %]
       # Use an RDBO object and it's n:m relatioship as the default
       # values. For example, a user can be a member in many groups. "All
       # Use an RDBO object and its n:m relationship as the default
       # values. For example, a user can be a member of many groups. "All
       # groups" is therefore the full collection and "$user->groups" is a
       # list of RDBO AuthGroup objects whose IDs must match the ones in
       # "All groups". This could look like the following:
-...
     =item C<select_tag $name, \@collection, %attributes>
     Creates a HTML 'select' tag named C<$name> with the contents of one
     Creates an HTML 'select' tag named C<$name> with the contents of one
     'E<lt>optionE<gt>' tag for each element in C<\@collection> and with arbitrary
     HTML attributes from C<%attributes>. The value
     to use and the title to display are extracted from the elements in
-...
     =back
 . also applies for single RDBO instances (due to 'wantarray'
     shenanigangs assigning RDBO's relationships to a hash key will result
 . also applies to single RDBO instances (due to 'wantarray'
     shenanigans assigning RDBO's relationships to a hash key will result
     in a single RDBO object being assigned instead of an array reference
     containing that single RDBO object).
     If the option C<with_optgroups> is set then this function expects
     C<\@collection> to be one level deeper. The upper-most level is
     translated into a HTML C<optgroup> tag. So the structure becomes:
     translated into an HTML C<optgroup> tag. So the structure becomes:
     =over 4
     =item 1. Array of array references. Each element in the
     C<\@collection> is converted into an optgroup.
     =item 2. The optgroup's C<label> attribute will be set to the the
     =item 2. The optgroup's C<label> attribute will be set to the
     first element in the array element. The second array element is then
     converted to a list of C<option> tags like it is described above.
     converted to a list of C<option> tags as described above.
     =back
-...
       # First in a controller:
       my @collection = (
         [ t8("First optgroup with two items"),
         [ t8("First optgroup with three items"),
           [ { id => 42, name => "item one" },
             { id => 54, name => "second item" },
             { id => 23, name => "and the third one" },

Projekt

Allgemein

Profil

projekt kivitendo

Revision 976b1ddf

Von Kivitendo Admin vor fast 10 Jahren hinzugefügt