1 package SL::Presenter::Part;
7 use Exporter qw(import);
8 our @EXPORT = qw(part_picker part);
13 my ($self, $part, %params) = @_;
15 $params{display} ||= 'inline';
17 croak "Unknown display type '$params{display}'" unless $params{display} =~ m/^(?:inline|table-cell)$/;
20 $params{no_link} ? '' : '<a href="ic.pl?action=edit&id=' . $self->escape($part->id) . '">',
21 $self->escape($part->partnumber),
22 $params{no_link} ? '' : '</a>',
24 return $self->escaped_text($text);
28 my ($self, $name, $value, %params) = @_;
30 $value = SL::DB::Manager::Part->find_by(id => $value) if $value && !ref $value;
31 my $id = delete($params{id}) || $self->name_to_id($name);
32 my $fat_set_item = delete $params{fat_set_item};
34 my @classes = $params{class} ? ($params{class}) : ();
35 push @classes, 'part_autocomplete';
36 push @classes, 'partpicker_fat_set_item' if $fat_set_item;
39 $self->input_tag($name, (ref $value && $value->can('id') ? $value->id : ''), class => "@classes", type => 'hidden', id => $id) .
40 join('', map { $params{$_} ? $self->input_tag("", delete $params{$_}, id => "${id}_${_}", type => 'hidden') : '' } qw(column type unit convertible_unit)) .
41 $self->input_tag("", (ref $value && $value->can('description')) ? $value->description : '', id => "${id}_name", %params);
43 $::request->layout->add_javascripts('autocomplete_part.js');
44 $::request->presenter->need_reinit_widgets($id);
46 $self->html_tag('span', $ret, class => 'part_picker');
57 SL::Presenter::Part - Part related presenter stuff
61 # Create an html link for editing/opening a part/service/assembly
62 my $object = my $object = SL::DB::Manager::Part->get_first;
63 my $html = SL::Presenter->get->part($object, display => 'inline');
65 see also L<SL::Presenter>
75 =item C<part, $object, %params>
77 Returns a rendered version (actually an instance of
78 L<SL::Presenter::EscapedText>) of the part object C<$object>
80 C<%params> can include:
86 Either C<inline> (the default) or C<table-cell>. At the moment both
87 representations are identical and produce the part's name linked
88 to the corresponding 'edit' action.
96 =item C<part_picker $name, $value, %params>
98 All-in-one picker widget for parts. The name will be both id and name
99 of the resulting hidden C<id> input field (but the ID can be
100 overwritten with C<$params{id}>).
102 An additional dummy input will be generated which is used to find
103 parts. For a detailed description of it's behaviour, see section
104 C<PART PICKER SPECIFICATION>.
106 C<$value> can be a parts id or a C<Rose::DB:Object> instance.
108 If C<%params> contains C<type> only parts of this type will be used
109 for autocompletion. You may comma separate multiple types as in
112 If C<%params> contains C<unit> only parts with this unit will be used
113 for autocompletion. You may comma separate multiple units as in
116 If C<%params> contains C<convertible_unit> only parts with a unit
117 that's convertible to unit will be used for autocompletion.
119 Obsolete parts will by default not displayed for selection. However they are
120 accepted as default values and can persist during updates. As with other
121 selectors though, they are not selectable once overridden.
123 Currently you must include C<js/autocomplete_part.js> in old bin/mozilla-style
124 controllers if C<<$form->header>> is called before the template. In all other
125 cases, C<part_picker> will add the javascript for you.
129 =head1 PART PICKER SPECIFICATION
131 The following list of design goals were applied:
137 Parts should not be perceived by the user as distinct inputs of partnumber and
138 description but as a single object
142 Easy to use without documentation for novice users
146 Fast to use with keyboard for experienced users
150 Possible to use without any keyboard interaction for mouse (or touchscreen)
155 Must not leave the current page in event of ambiguity (cf. current select_item
160 Should be useable with hand scanners or similar alternative keyboard devices
164 Should not require a feedback/check loop in the common case
168 Should not be constraint to exact matches
172 The implementation consists of the following parts which will be referenced later:
178 A hidden input (id input), used to hold the id of the selected part. The only
179 input that gets submitted
183 An input (dummy input) containing a description of the currently selected part,
184 also used by the user to search for parts
188 A jquery.autocomplete mechanism attached to the dummy field
192 A popup layer for both feedback and input of additional data in case of
197 An internal status of the part picker, indicating wether id input and dummy
198 input are consistent. After leaving the dummy input the part picker must
199 place itself in a consistent status.
203 A clickable icon (popup trigger) attached to the dummy input, which triggers the popup layer.
213 Sven Schöling E<lt>s.schoeling@linet-services.deE<gt>