Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
swat:rwrd [2007/10/15 06:17]
jo
swat:rwrd [2009/07/06 20:36] (current)
Line 1: Line 1:
-=====  Reports / WS / RSS / Data Exchange SWAT Objectives =====+=====  Reports / WS / RSS / Data Exchange / UI SWAT ===== 
 +__Team__ 
 + 
 +  * jo [at] opensource [dot] lk 
 +  * ishanul [at] gmail [dot] com 
 +  * hayeshais [at] gmail [dot] com 
 + 
  
  
Line 7: Line 14:
   - Check all the HTML based reports available in the module.   - Check all the HTML based reports available in the module.
   - Identify reports which need paging functionality and to apply paging to those reports.   - Identify reports which need paging functionality and to apply paging to those reports.
-  - Export the available reports in to spreadsheet.+  - Add export functionality to the reports. 
  
  
 ==== Web Services ==== ==== Web Services ====
  
-  - Identify the necessary functions to expose as web services. (Need to be consulted from the community)+    * Identify the necessary functions to expose as web services. (Need to be consulted from the community)
          Here we are focusing on to identify web services which are generic and can be used between two sahana instances. Even though we can expose a large number of web services per module we plan not to implement all of them for maintainability purposes. For example let say you implemented 10 web services and if you did a simple schema change you may need to change all of those functions which is frustrating. So as we discussed the best approach would be to implement web services when there is a solid requirement in a deployment. Further more we would enhance the web services library and the module so that it would be easy to create web services when requirement arise.          Here we are focusing on to identify web services which are generic and can be used between two sahana instances. Even though we can expose a large number of web services per module we plan not to implement all of them for maintainability purposes. For example let say you implemented 10 web services and if you did a simple schema change you may need to change all of those functions which is frustrating. So as we discussed the best approach would be to implement web services when there is a solid requirement in a deployment. Further more we would enhance the web services library and the module so that it would be easy to create web services when requirement arise.
  
-  - Write [[dev:web_services | api.inc]] file and [[dev:web_services | ws.xml]] file for the module.+    * Write [[dev:web_services | api.inc]] file and [[dev:web_services | ws.xml]] file for the module. 
  
 Implemented Web [[Services]] Implemented Web [[Services]]

Navigation
QR Code
QR Code swat:rwrd (generated for current page)