Project:
| View Revisions: Issue #18467 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0018467: API change for performance improvements (int-api/2364) | ||
| Revision | 2011-09-11 15:51 by shuehner | ||
| Description | In reference to: http://builds.openbravo.com/job/int-api/2364/console [^] Currently the generation of field definitions, used in the form/grid in the UI, is spread over several classes with duplicate code. The result is that also too much javascript is generated. There are clear and easy performance benefits to improve this. For improving this the idea is to centralize the generation of field definitions and only send one set of fields per tab, from the server to the client. The above proposal means that code needs to be moved/combined which is now present in several classes and will mean an api change. The change that anyone has ever extended or directly used this api is practically zero. The components in questions are used from Openbravo templates, it does not at all make sense for a third party to directly call these components. So the risk of this change is (imv) very very small. The api change is in the classes in the org.openbravo.client.application.window package. |
||
| Revision | 2011-09-11 14:41 by shuehner | ||
| Description | Currently the generation of field definitions, used in the form/grid in the UI, is spread over several classes with duplicate code. The result is that also too much javascript is generated. There are clear and easy performance benefits to improve this. For improving this the idea is to centralize the generation of field definitions and only send one set of fields per tab, from the server to the client. The above proposal means that code needs to be moved/combined which is now present in several classes and will mean an api change. The change that anyone has ever extended or directly used this api is practically zero. The components in questions are used from Openbravo templates, it does not at all make sense for a third party to directly call these components. So the risk of this change is (imv) very very small. The api change is in the classes in the org.openbravo.client.application.window package. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |