Hi Rok,
It should be the field name as defined in ad_field. This because maybe later we
will have non-db fields also.
HQL should use entity names, so I am not sure what example/tablename you are
refering to.
With Regards, Martin Taal
Openbravo
M: +31 6 288 48 943
@: martin.t...@openbravo.com
Skype: martintaal
Openbravo Headquarters:
P: +34 93 27 25 947
F: +34 93 27 25 905
Address: Edificio Slan, Planta 2a, Landaben, Calle J, 31012 Pamplona, Navarra,
Spain
Mailing address: PO Box 5117, 31010 Pamplona, Navarra, Spain
On 09/23/2011 12:00 PM, Rok Lenardic wrote:
Hey Martin,
love it, especially the ActionHandler which seems real easy to write.
One question:
An OnChange function is registered through the OB.OnChangeRegistry.register
method. It expects 4 parameters:
o tab id
o *field: the name of the field for which the onchange is registered*
o callback function: the onchange function itself
o id: can be used to overwrite an existing OnChange function
registered using the same id
An example of a registration:
OB.OnChangeRegistry.register('FF8081813290114F0132901EB0A2001A','*value*',
OBEXAPP.OnChangeFunctions.Note_Value,'OBEXAPP_Value');
What does the field name correspond to? DB Column name or DAL name?
On another subject, how come the HQL uses table name and not entity name to
reference entities?
Great job! I will include this in the AD as soon as it is fully released...
Cheers
ROk
On Fri, Sep 23, 2011 at 6:39 AM, Martin Taal <martin.t...@openbravo.com
<mailto:martin.t...@openbravo.com>> wrote:
Hi,
I pushed a change to pi which makes it possible to define client side
callouts (or OnChange) functions. They
correspond to the classic callout concept with as main difference that the
function is implemented in javascript.
The main benefit is simplicity and performance, as callouts/onchange
functions can be executed completely in the
client. The new callouts/onchange function still allows you to do server
side calls if needed.
The new concept is described in this howto:
http://wiki.openbravo.com/wiki/How_to_create_client_side_callout_onchange_function
The goal is to deliver this with MP4.
As the new callouts make it possible to access the client side code
directly I also expanded the documentation on
the client side object/class structure:
http://wiki.openbravo.com/wiki/Client_Side_Development_and_API#Openbravo_Window_Components
The changes for this functionality are tracked through this issue:
https://issues.openbravo.com/view.php?id=18588
Let me know if you have any comments/feedback.
--
With Regards, Martin Taal
Openbravo
M: +31 6 288 48 943 <tel:%2B31%206%20288%2048%20943>
@: martin.t...@openbravo.com <mailto:martin.t...@openbravo.com>
Skype: martintaal
Openbravo Headquarters:
P: +34 93 27 25 947 <tel:%2B34%2093%2027%2025%20947>
F: +34 93 27 25 905 <tel:%2B34%2093%2027%2025%20905>
Address: Edificio Slan, Planta 2a, Landaben, Calle J, 31012 Pamplona,
Navarra, Spain
Mailing address: PO Box 5117, 31010 Pamplona, Navarra, Spain
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Openbravo-development mailing list
Openbravo-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbravo-development
