"Part.pm.html#L264" data-txt="264">
|
=item * default
|
|
|
|
The id of the selected vendor.
|
|
|
|
=back
|
|
|
|
=back
|
|
|
|
=over 2
|
|
|
|
=item C<part_picker $name, $value, %params>
|
|
|
|
All-in-one picker widget for parts. The name will be both id and name
|
|
of the resulting hidden C<id> input field (but the ID can be
|
|
overwritten with C<$params{id}>).
|
|
|
|
An additional dummy input will be generated which is used to find
|
|
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<part_type> only parts of this type will be used
|
|
for autocompletion. You may comma separate multiple types as in
|
|
C<part,assembly>.
|
|
|
|
If C<%params> contains C<status> only parts of this status will be used
|
|
for autocompletion. C<status> can be one of the following strings:
|
|
C<active>, C<obsolete> or C<all>. C<active> is the default if C<status> is
|
|
not given.
|
|
|
|
If C<%params> contains C<unit> only parts with this unit will be used
|
|
for autocompletion. You may comma separate multiple units as in
|
|
C<h,min>.
|
|
|
|
If C<%params> contains C<convertible_unit> only parts with a unit
|
|
that's convertible to unit will be used for autocompletion.
|
|
|
|
If C<%params> contains C<with_makemodel> or C<with_customer_partnumber> even
|
|
parts will be used for autocompletion which partnumber is a vendor partnumber
|
|
(makemodel) or a customer partnumber.
|
|
|
|
If C<%params> contains C<multiple> an alternative popup will be opened,
|
|
allowing multiple items to be selected. Note however that this requires
|
|
an additional callback C<set_multi_items> to work.
|
|
Also note that you can set C<multiple> to 0 (or not set C<multiple>) on
|
|
creation of the picker, but can open the alternative multi select popup
|
|
with js like this:
|
|
C<$("#pp_id").data("part_picker").o.multiple=1; $("#pp_id").data("part_picker").open_dialog()'>
|
|
where C<pp_id> is the dom id of the part picker.
|
|
Or you can even do it the other way round setting C<multiple> to 1 on creation
|
|
and open a single selection popup with js.
|
|
|
|
If C<%params> contains C<multiple_pos_input> an input field with the dom id
|
|
C<multi_items_position> will be rendered in the alternative popup.
|
|
This can be used in the callback for C<set_multi_items> to controll the
|
|
input postion for the items.
|
|
|
|
If C<%params> contains C<multiple_limit> the alternative popup will not
|
|
show any results if there are more than C<multiple_limit> results. A warning
|
|
message is displayed in this case. Set C<multiple_limit> to 0 to disable
|
|
the limitation. The limit defaults to 100.
|
|
|
|
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.
|
|
|
|
C<part_picker> will register it's javascript for inclusion in the next header
|
|
rendering. If you write a standard controller that only calls C<render> once, it
|
|
will just work. In case the header is generated in a different render call
|
|
(multiple blocks, ajax, old C<bin/mozilla> style controllers) you need to
|
|
include C<kivi.Part.js> yourself.
|
|
|
|
On pressing <enter> the picker will try to commit the current selection,
|
|
resulting in one of the following events, whose corresponding callbacks can be
|
|
set in C<params.actions>:
|
|
|
|
=over 4
|
|
|
|
=item * C<commit_one>
|
|
|
|
If exactly one element matches the input, the internal id will be set to this
|
|
id, the internal state will be set to C<PICKED> and the C<change> event on the
|
|
picker will be fired. Additionally, if C<params> contains C<fat_set_item> a
|
|
special event C<set_item:PartPicker> will be fired which is guaranteed to
|
|
contain a complete JSON representation of the part.
|
|
|
|
After that the action C<commit_one> will be executed, which defaults to
|
|
clicking a button with id C<update_button> for backward compatibility reasons.
|
|
|
|
=item * C<commit_many>
|
|
|
|
If more than one element matches the input, the internal state will be set to
|
|
undefined.
|
|
|
|
After that the action C<commit_one> will be executed, which defaults to
|
|
opening a popup dialog for graphical interaction.
|
|
|
|
=item * C<commit_none>
|
|
|
|
If no element matches the input, the internal state will be set to undefined.
|
|
|
|
If an action for C<commit_none> exists, it will be called with the picker
|
|
object and current term. The caller can then implement creation of new parts.
|
|
|
|
=back
|
|
|
|
=back
|
|
|
|
=head1 PART PICKER SPECIFICATION
|
|
|
|
The following list of design goals were applied:
|
|
|
|
=over 4
|
|
|
|
=item *
|
|
|
|
Parts should not be perceived by the user as distinct inputs of partnumber and
|
|
description but as a single object
|
|
|
|
=item *
|
|
|
|
Easy to use without documentation for novice users
|
|
|
|
=item *
|
|
|
|
Fast to use with keyboard for experienced users
|
|
|
|
=item *
|
|
|
|
Possible to use without any keyboard interaction for mouse (or touchscreen)
|
|
users
|
|
|
|
=item *
|
|
|
|
Must not leave the current page in event of ambiguity (cf. current select_item
|
|
mechanism)
|
|
|
|
=item *
|
|
|
|
Should be useable with hand scanners or similar alternative keyboard devices
|
|
|
|
=item *
|
|
|
|
Should not require a feedback/check loop in the common case
|
|
|
|
=item *
|
|
|
|
Should not be constrained to exact matches
|
|
|
|
=item *
|
|
|
|
Must be atomic
|
|
|
|
=item *
|
|
|
|
Action should be overridable
|
|
|
|
=back
|
|
|
|
The implementation consists of the following parts which will be referenced later:
|
|
|
|
=over 4
|
|
|
|
=item 1
|
|
|
|
A hidden input (id input), used to hold the id of the selected part. The only
|
|
input that gets submitted
|
|
|
|
=item 2
|
|
|
|
An input (dummy input) containing a description of the currently selected part,
|
|
also used by the user to search for parts
|
|
|
|
=item 3
|
|
|
|
A jquery.autocomplete mechanism attached to the dummy field
|
|
|
|
=item 4
|
|
|
|
A popup layer for both feedback and input of additional data in case of
|
|
ambiguity.
|
|
|
|
=item 5
|
|
|
|
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 6
|
|
|
|
A clickable icon (popup trigger) attached to the dummy input, which triggers the popup layer.
|
|
|
|
=back
|
|
|
|
=head1 BUGS
|
|
|
|
None atm :)
|
|
|
|
=head1 AUTHOR
|
|
|
|
Sven Schöling E<lt>s.schoeling@linet-services.deE<gt>
|
|
|
|
Martin Helmling E<lt>martin.helmling@opendynamic.deE<gt>
|
|
|
|
=cut
|
Lade...