From version 1.1 >
edited by Thomas Mortagne
on 2018/03/20 10:42
To version < 2.1 >
edited by Thomas Mortagne
on 2018/03/20 10:44
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,12 +1,14 @@
1 1  When the job is in interactive mode it can ask questions and wait for the answer. The UI is then supposed to make sure the user is going to see the question and answer it.
2 2  
3 += User interface =
4 +
3 3  To make easier to provide UI for your job the Job module provide generic tools to show and answer a question and allow customizing and extending it in various ways.
4 4  
5 -= Enable standard question support =
7 +== Enable standard question support ==
6 6  
7 7  Standard question UI is triggered by a ##<div class="ui-question">## located in a ##<div class="job-status">## containing a ##<div class="ui-progress">##. If these conditions are fulfilled you will automatically get a form displayed when the running job is waiting for an answer.
8 8  
9 -= Customize question display =
11 +== Customize question display ==
10 10  
11 11  The default question UI is a form containing inputs generated from the question bean descriptor (each get/set couple producing an input based on its type).
12 12  
... ... @@ -49,7 +49,7 @@
49 49  
50 50  * by using [[JQuery#data>>https://api.jquery.com/data/]] and the key ##job-answer-createRequest## to provide a function which will return a custom URL and the data to use in an ajax call. The custom service must answer with the expected job status JSON.
51 51  
52 -= Customize answer =
54 +== Customize answer ==
53 53  
54 54  The default answer service populate all request parameters starting with ##qproperty_## in the question object and return the JSON expected by the UI.
55 55  

Get Connected