Table Row (tr) |
---|
Table Cell (td) |
---|
Use application.getApplicationType() |
| {td}
{td}{td}
{tr}
{tr}
{td}Use style sheets and style classes as opposed to specifying styling on elements directly by setting their properties.{td}
{td}Besides a more consistent styling throughout your solution, it means less styling info is send to the client, thus the Web Client performance will improve.{td}
{tr}
{tr}
{td}Transparent PNG images are not supported by Internet Explorer <= 6. If you need transparent images and support for Internet Explorer <= 6, use transparent GIF's.{td}
{td}{td}
{tr}
{tr}
{td}Use short running locks and transactions, preferably acquire and release them within the execution of the same method.{td}
{td}If user interaction is required to release an acquired lock of transaction and the user closes the browser/navigates away from the Web Client page without releasing the lock or transaction, the lock/transaction will remain until the Web Client session times out and is destroyed. Use autosave=false to accumulate edits without having a lock/transaction active.{td}
{tr}
{tr}
{td}Keep in mind that the user can, at any time, navigate away from your solution, by opening a bookmark, typing a new URL etc. (see previous remark){td}
{td}{td}
{tr}
{tr}
{td}Try to minimize the use of comboboxes/editable fields with (long) valuelists attached, especially in combination with forms in Tableview.{td}
{td}Use type-ahead fields for long valuelists or consider a edit popup dialog with search capabilities. For each field/combobox, the entire valuelist has to be included in the HTML source of the Web Client.{td}
{tr}
{tr}
{td}Minimize the use of dialogs, both modal and non-modal, and create a flat interface instead.{td}
{td}Multiple windows/dialogs, in general, is not a concept users like when using a browser. Popup blockers might block your (non-modal) dialog from showing.{td}
{tr}
{tr}
{td}Minimize the switching between forms as much as possible. For example: Add search functionality directly on the form, instead of on a separate form.{td}
{td}Minimal switching between forms provides a faster user experience.{td}
{tr}
{tr}
{td}When using images that do not come from the Servoy Media Library, do re-use images. For example: On a TreeView, when using the same image on multiple nodes, do not store the image for the node on each node record, but link to one shared image stored somewhere else.{td}
{td}This means that only one image needs to be downloaded to the Web Client, instead of multiple copies of the same image.{td}
{tr}
{tr}
{td}Always design for a minimal resolution and allow the UI to grow{td}
{td}This advice is also applicable for Smart Client development, but the Smart Client is more forgiving when not properly sizing elements and forms{td}
{tr}
{tr}
{td}Always place elements within the bounds of the form(part){td}
{td}Not doing so will result in (unwanted) scrollbars in the Web Client. The Smart Client is more forgiving in this area{td}
{tr}
{table}
\\
h6. Differences:
{table:class=servoy sSummery}
{colgroup}
{column}{column}
{column}{column}
{column}{column}
{column}{column}
{colgroup}
{tr:style=height: 30px;}
{th}What{th}
{th}Smart Client{th}
{th}Web Client{th}
{th}Comment{th}
{tr}
{tr}
{td}Automatic closing of a client that has been idle for a certain period of time{td}
{td}Possible with plugin/additional coding{td}
{td}Servoy Web Client is automatically closed when the HTTP session expires on the application server(configurable).{td}
{td}{td}
{tr}
{tr}
{td}Commands{td}
{td}Fully supported{td}
{td}Commands are not supported, as there is no menubar in the Web Client for the user to trigger the command. Using the window plugin, it is possible to simulate the behavior of Servoy Smart Client.{td}
{td}{td}
{tr}
{tr}
{td}Method execution after the method shows a modal dialog using the dialogs plugin or Table Row (tr) |
---|
Table Cell (td) |
---|
Use style sheets and style classes as opposed to specifying styling on elements directly by setting their properties. |
Table Cell (td) |
---|
Besides a more consistent styling throughout your solution, it means less styling info is send to the client, thus the Web Client performance will improve. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Transparent PNG images are not supported by Internet Explorer <= 6. If you need transparent images and support for Internet Explorer <= 6, use transparent GIF's. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Use short running locks and transactions, preferably acquire and release them within the execution of the same method. |
Table Cell (td) |
---|
If user interaction is required to release an acquired lock of transaction and the user closes the browser/navigates away from the Web Client page without releasing the lock or transaction, the lock/transaction will remain until the Web Client session times out and is destroyed. Use autosave=false to accumulate edits without having a lock/transaction active. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Keep in mind that the user can, at any time, navigate away from your solution, by opening a bookmark, typing a new URL etc. (see previous remark) |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Try to minimize the use of comboboxes/editable fields with (long) valuelists attached, especially in combination with forms in Tableview. |
Table Cell (td) |
---|
Use type-ahead fields for long valuelists or consider a edit popup dialog with search capabilities. For each field/combobox, the entire valuelist has to be included in the HTML source of the Web Client. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Minimize the use of dialogs, both modal and non-modal, and create a flat interface instead. |
Table Cell (td) |
---|
Multiple windows/dialogs, in general, is not a concept users like when using a browser. Popup blockers might block your (non-modal) dialog from showing. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Minimize the switching between forms as much as possible. For example: Add search functionality directly on the form, instead of on a separate form. |
Table Cell (td) |
---|
Minimal switching between forms provides a faster user experience. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
When using images that do not come from the Servoy Media Library, do re-use images. For example: On a TreeView, when using the same image on multiple nodes, do not store the image for the node on each node record, but link to one shared image stored somewhere else. |
Table Cell (td) |
---|
This means that only one image needs to be downloaded to the Web Client, instead of multiple copies of the same image. |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Always design for a minimal resolution and allow the UI to grow |
Table Cell (td) |
---|
This advice is also applicable for Smart Client development, but the Smart Client is more forgiving when not properly sizing elements and forms |
|
Table Row (tr) |
---|
Table Cell (td) |
---|
Always place elements within the bounds of the form(part) |
Table Cell (td) |
---|
Not doing so will result in (unwanted) scrollbars in the Web Client. The Smart Client is more forgiving in this area |
|
|