Great, clear.

Thank you!

Ismael

On Fri, Sep 23, 2011 at 9:36 AM, Martin Taal <martin.t...@openbravo.com>wrote:

> **
> The risk on existing code is very little, I mean if you don't explicitly
> specify an onchange function on a field then it is not used and the old
> callout is used. This is handled by one if statement, which works afaics.
>
> Ofcourse as with any new feature, there is a change that it will not work
> correctly. But I think that's acceptable *as long as existing code is not
> broken*.
>
> For the howto I wrote I implemented several callout/onchange functions in
> an example module. But my goal is to add a UI test after next week.
>
>  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 09:29 AM, Ismael Ciordia wrote:
>
> Amazing! Really curious to see the results but ... isn't it too risky to
> push this change in MP4? Wouldn't it safer to "mature" it for a while in a
> temporary branch? Anyway, I'm just guessing (fully trust you :-).
>
> Thanks!
>
> Ismael
>
> On Fri, Sep 23, 2011 at 6:39 AM, Martin Taal <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
>> @: 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
>>
>> _______________________________________________
>> team.platform mailing list
>> team.platf...@openbravo.com
>> http://list.openbravo.com/mailman/listinfo/openbravo.com.team.platform
>>
>
>
------------------------------------------------------------------------------
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

Reply via email to