Differences

This shows you the differences between two versions of the page.

--- pracro:devas_corner [2010/08/10 10:52] – deva
+++ pracro:devas_corner [2011/01/14 14:49] (current) – deva
@@ Line 1: / Line 1: @@
 ======Deva's corner======
+=====Session sharing======
+Client logon with (patientid, template) tupple.\\
+Server makes lookup in active sessions for tupples matching the one supplied by the client.\\
+If none matches, a new session is created and 'returned' to the client.\\
+If a match exists, the client is queried if it want to take over the session.\\
+The session state is to be stored with the session (open, closed_no_commit) so the client must actively notify the server when a session is closed without commit.\\
+If a client is about to take over an active (not closed_no_committed) a warning should be issued, about possible race conditions happening.
 =====New Clientside Scripting System=====
@@ Line 52: / Line 59: @@
 </scripts>
 </code>
 ====The Widget Events====
@@ Line 57: / Line 65: @@
 Currently the script is referred by its name, and called whenever the widget changes its value.\\
 In the new system, the script attribute is removed and replaced by event attributes. The event attributes will themselves contain lua code and not simply a name. In order to call 'external' code, simply wrap it in a function and call it here.\\
-The return values will no longer be used. Instead widget methods will be added to control the validation state of each widget, eg. setValid(true|false), setInvalid(), invalidate(), ...\\
+The return values will no longer be used. Instead widget methods will be added to control the validation state of each widget, eg. ''setValid(true|false)''.\\
 Since it is no longer required (due to redundancy) the ''regexp'' attribute will be removed.
 ====Event Handlers====
   * ''onChange'': triggered whenever the value of the widget is changed, either programmatically or by the user.
-  * ''onUserChange'': triggered whenever the value of the widget is changed by the user.
+  * more to come
-  * and many more
 ====The Widget Object====
 When in a lua function, invoked by an event handler, the calling object (the object invoking the event) will be made available through the value 'this'.
-Other object can be retrieved using the ''getWidget('name')'' function.
+Other object can be retrieved using the ''widget('name')'' function.
 <code lua>
 function foo()
-   if (this.value == 'bar')
+   if (this:value() == 'bar')
    then
-      this.setValue('dut')
+      this:setValue('dut')
    end
-   bas = getWidget('mywdg')
+   bas = widget('mywdg')
-   if (bas && bas.value == 'bar' )
+   if (bas && bas:value() == 'bar' )
    then
-      bas.setValue('dims')
+      bas:setValue('dims')
    end
 end
 </code>
 A small number of methods are common to all widget types. These include are:
-  * ''set/getValue''
+  * ''setValue(string)'', ''value()''
-  * ''set/getValid''
+  * ''setValid(boolean)'', ''valid()''
-  * ''set/getVisible''
+  * ''setVisible(boolean)'', ''visible()''
-  * ''set/getEnabled''
+  * ''setEnabled(boolean)'', ''enabled()''
-  * ''getType''
+  * ''type()''
-  * ''getName''
+  * ''name()''
 Others are specific to certain widget types, such as (and many more):
-  * ''set/getChekced'' (checkbox)
+  * ''setChekced(boolean)'', ''checked()'' (checkbox)
-  * ''set/getSelection'' (listbox)
-  * ''set/getCarriagePosition'' (lineedit)
 =====New protocol=====