mirrors/EWF
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Removed extra indentations in code.

Browse Source
This commit is contained in:
Jocelyn FIAT
2017-02-14 19:51:23 +01:00
parent f216e98430
commit ff8da87fe3
1 changed files with 127 additions and 129 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
doc/workbook/wui/readme.md
View File

@@ -24,7 +24,7 @@ A simple solution to return html content is to use the `WSF_HTML_PAGE_RESPONSE`
In a `WSF_EXECUTION` descendant, see how to implement the `execute` procedure.
```
execute
execute
local
mesg: WSF_HTML_PAGE_RESPONSE
do
@@ -39,8 +39,7 @@ In this case, the html is hardcoded, and written manually.
Now let's see how to use the WSF widgets on a more advanced usecase, a simple sign-in web form with 2 input fields `username`, `password` and `submit` button.
```
execute
execute
do
-- Basic url dispatching...
if request.is_post_request_method then
@@ -50,7 +49,7 @@ Now let's see how to use the WSF widgets on a more advanced usecase, a simple si
end
end
execute_web_form_display
execute_web_form_display
local
mesg: WSF_HTML_PAGE_RESPONSE
f: WSF_FORM
@@ -71,12 +70,12 @@ Now let's see how to use the WSF widgets on a more advanced usecase, a simple si
response.send (mesg)
end
execute_web_form_submission
execute_web_form_submission
do
... this will be explain in next section !
end
new_login_form: WSF_FORM
new_login_form: WSF_FORM
local
f: WSF_FORM
f_set: WSF_FORM_FIELD_SET
@@ -120,7 +119,7 @@ Indeed `WSF_HTML.process (request, .., ..)` analyze the request, fill the form f
See
```
process (req: WSF_REQUEST; a_before_callback, a_after_callback: detachable PROCEDURE [WSF_FORM_DATA])
process (req: WSF_REQUEST; a_before_callback, a_after_callback: detachable PROCEDURE [WSF_FORM_DATA])
-- Process Current form with request `req`,
-- and build `last_data: WSF_FORM_DATA` object containing the field values.
-- agent `a_before_callback` is called before the validation
@@ -130,7 +129,7 @@ See
In our previous sample code, `execute_web_form_submission` could be:
```
execute_web_form_submission
execute_web_form_submission
local
mesg: WSF_HTML_PAGE_RESPONSE
l_html: STRING
@@ -186,8 +185,8 @@ To set validation,
For instance, in previous sample, accepts only alpha-numeric characters:
```
f_username.set_description ("Only alpha-numeric character are accepted.")
f_username.set_validation_action (agent (fd: WSF_FORM_DATA)
f_username.set_description ("Only alpha-numeric character are accepted.")
f_username.set_validation_action (agent (fd: WSF_FORM_DATA)
do
if attached fd.string_item ("username") as u then
if across u as ic some not ic.item.is_alpha_numeric end then
@@ -237,4 +236,3 @@ For now, the `wsf_html` provides a simple solution to build web form. It is alwa
Advanced usage could be built on top of the `wsf_html` to include for instance javascript actions, but this is out of the scope of `wsf_html` .