EPrints Technical Mailing List Archive

Message: #04983

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Re: Help text in workflows

Indeed there is:



   <component type="XHTML">
	HTML in here
   </component>



--
Adam Field
Business Relationship Manager and Community Lead
EPrints Services
+44 (0)23 8059 8814





On 22 Oct 2015, at 13:21, Andrew Beeken wrote:

> Is there not simply a way of dropping a block of plain text into the
> workflow near the field in question?
> 
> On 22/10/2015 11:42, "eprints-tech-bounces@ecs.soton.ac.uk on behalf of
> Field A.N." <eprints-tech-bounces@ecs.soton.ac.uk on behalf of
> af05v@ecs.soton.ac.uk> wrote:
> 
>> You could adjust the field input renderer to render the field with some
>> text above it...  You can do this in eprint_field.pl by setting  a
>> render_input property like this:
>> 
>> .
>> .
>> .
>> {
>> 	name => 'foo',
>> 	type => 'text',
>> 	render_input => 'render_text_input_with_help',
>> }
>> .
>> .
>> .
>> 
>> 
>> $c->{render_text_input_with_help} = sub
>> {
>> 	my ($field, $repo, $value, $dataset, $staff, $hidden_fields, $obj,
>> $basename) = @_;
>> 
>> 	my $frag = $rep->xml->create_doc_fragment;
>> 
>> 	my $input = $field->render_input_field_actual($repo, $value, $dataset,
>> $staff, $hidden_fields, $obj, $basename);
>> 	my $help = $field->render_help;
>> 
>> 	$frag->appendChild($help);
>> 	$frag->appendChild($input);
>> 
>> 	return $frag;
>> }
>> 
>> 
>> 
>> ...note that this is a half-baked idea.  It will come out with a
>> collapsed help to, which will mean if someone opens it, they'll have the
>> same help twice.  You might want to use a different phrase so that you
>> can have different hidden and revealed help.
>> 
>> --
>> Adam Field
>> Business Relationship Manager and Community Lead
>> EPrints Services
>> +44 (0)23 8059 8814
>> 
>> 
>> 
>> 
>> 
>> On 22 Oct 2015, at 11:31, Andrew Beeken wrote:
>> 
>>> Hi Adam,
>>> 
>>> Sorry for the delay in looking at this. So, you have to apply the rule
>>> at
>>> a component level meaning that it would effect every field within that
>>> component? That¹s a bit heavy for what I want to do - can I not have
>>> this
>>> decided on a per field basis, or at least put some other form of alert
>>> text in?
>>> 
>>> Andrew
>>> 
>>> On 19/10/2015 10:28, "eprints-tech-bounces@ecs.soton.ac.uk on behalf of
>>> Field A.N." <eprints-tech-bounces@ecs.soton.ac.uk on behalf of
>>> af05v@ecs.soton.ac.uk> wrote:
>>> 
>>>> Try:
>>>> 
>>>> <component show_help="always">
>>>> 	<field....>
>>>> </component>
>>>> 
>>>> 
>>>> --
>>>> Adam Field
>>>> Business Relationship Manager and Community Lead
>>>> EPrints Services
>>>> +44 (0)23 8059 8814
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On 19 Oct 2015, at 10:16, Andrew Beeken wrote:
>>>> 
>>>>> Morning all,
>>>>> 
>>>>> Is there any way of making help text boxes on the workflow open
>>>>> automatically so that important help messages are always on display?
>>>>> 
>>>>> Thanks!
>>>>> Andrew
>>>>> 
>>>>> The University of Lincoln, located in the heart of the city of
>>>>> Lincoln,
>>>>> has established an international reputation based on high student
>>>>> satisfaction, excellent graduate employment and world-class research.
>>>>> 
>>>>> The information in this e-mail and any attachments may be
>>>>> confidential.
>>>>> If you have received this email in error please notify the sender
>>>>> immediately and remove it from your system. Do not disclose the
>>>>> contents
>>>>> to another person or take copies.
>>>>> 
>>>>> Email is not secure and may contain viruses. The University of Lincoln
>>>>> makes every effort to ensure email is sent without viruses, but cannot
>>>>> guarantee this and recommends recipients take appropriate precautions.
>>>>> 
>>>>> The University may monitor email traffic data and content in
>>>>> accordance
>>>>> with its policies and English law. Further information can be found
>>>>> at:
>>>>> http://lincoln.ac.uk/legal.
>>>>> 
>>>>> *** Options: 
>>>>> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>>>>> *** Archive: http://www.eprints.org/tech.php/
>>>>> *** EPrints community wiki: http://wiki.eprints.org/
>>>>> *** EPrints developers Forum: http://forum.eprints.org/
>>>> 
>>>> 
>>>> *** Options: 
>>>> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>>>> *** Archive: http://www.eprints.org/tech.php/
>>>> *** EPrints community wiki: http://wiki.eprints.org/
>>>> *** EPrints developers Forum: http://forum.eprints.org/
>>> 
>>> 
>>> *** Options: 
>>> http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>>> *** Archive: http://www.eprints.org/tech.php/
>>> *** EPrints community wiki: http://wiki.eprints.org/
>>> *** EPrints developers Forum: http://forum.eprints.org/
>> 
>> 
>> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
>> *** Archive: http://www.eprints.org/tech.php/
>> *** EPrints community wiki: http://wiki.eprints.org/
>> *** EPrints developers Forum: http://forum.eprints.org/
> 
> 
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
> *** EPrints developers Forum: http://forum.eprints.org/