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);
34 $self->input_tag($name, (ref $value && $value->can('id') ? $value->id : ''), class => 'part_autocomplete', type => 'hidden', id => $id) .
35 join('', map { $params{$_} ? $self->input_tag("", delete $params{$_}, id => "${id}_${_}", type => 'hidden') : '' } qw(column type unit convertible_unit)) .
36 $self->input_tag("", (ref $value && $value->can('description')) ? $value->description : '', id => "${id}_name", %params);
38 $::request->presenter->need_reinit_widgets($id);
40 $self->html_tag('span', $ret, class => 'part_picker');
51 SL::Presenter::Part - Part related presenter stuff
55 # Create an html link for editing/opening a part/service/assembly
56 my $object = my $object = SL::DB::Manager::Part->get_first;
57 my $html = SL::Presenter->get->part($object, display => 'inline');
59 see also L<SL::Presenter>
69 =item C<part, $object, %params>
71 Returns a rendered version (actually an instance of
72 L<SL::Presenter::EscapedText>) of the part object C<$object>
74 C<%params> can include:
80 Either C<inline> (the default) or C<table-cell>. At the moment both
81 representations are identical and produce the part's name linked
82 to the corresponding 'edit' action.
90 =item C<part_picker $name, $value, %params>
92 All-in-one picker widget for parts. The name will be both id and name
93 of the resulting hidden C<id> input field (but the ID can be
94 overwritten with C<$params{id}>).
96 An additional dummy input will be generated which is used to find
97 parts. For a detailed description of it's behaviour, see section
98 C<PART PICKER SPECIFICATION>.
100 C<$value> can be a parts id or a C<Rose::DB:Object> instance.
102 If C<%params> contains C<type> only parts of this type will be used
103 for autocompletion. You may comma separate multiple types as in
106 If C<%params> contains C<unit> only parts with this unit will be used
107 for autocompletion. You may comma separate multiple units as in
110 If C<%params> contains C<convertible_unit> only parts with a unit
111 that's convertible to unit will be used for autocompletion.
113 Obsolete parts will by default not displayed for selection. However they are
114 accepted as default values and can persist during updates. As with other
115 selectors though, they are not selectable once overridden.
117 Currently you must include C<js/autocomplete_part.js> in your controller, the
118 presenter can not do this from the template.
122 =head1 PART PICKER SPECIFICATION
124 The following list of design goals were applied:
130 Parts should not be perceived by the user as distinct inputs of partnumber and
131 description but as a single object
135 Easy to use without documentation for novice users
139 Fast to use with keyboard for experienced users
143 Possible to use without any keyboard interaction for mouse (or touchscreen)
148 Must not leave the current page in event of ambiguity (cf. current select_item
153 Should be useable with hand scanners or similar alternative keyboard devices
157 Should not require a feedback/check loop in the common case
161 Should not be constraint to exact matches
165 The implementation consists of the following parts which will be referenced later:
171 A hidden input (id input), used to hold the id of the selected part. The only
172 input that gets submitted
176 An input (dummy input) containing a description of the currently selected part,
177 also used by the user to search for parts
181 A jquery.autocomplete mechanism attached to the dummy field
185 A popup layer for both feedback and input of additional data in case of
190 An internal status of the part picker, indicating wether id input and dummy
191 input are consistent. After leaving the dummy input the part picker must
192 place itself in a consistent status.
196 A clickable icon (popup trigger) attached to the dummy input, which triggers the popup layer.
206 Sven Schöling E<lt>s.schoeling@linet-services.deE<gt>