abijah abd45244e1 Changed account to split the table requests into two parts. ...

git-svn-id: file:///svn-source/pmgr/branches/ledger_transactions_20090605/site@132 97e9348a-65ac-dc4b-aefc-98561f571b83

2009-06-15 06:31:21 +00:00

..

accounts_controller.php

Changed account to split the table requests into two parts.

2009-06-15 06:31:21 +00:00

contacts_controller.php

Fixed a bug in which jqGrid would fetch data from the current controller, not the controller responsible for populating the data. Added the ability to fetch data based strictly off of an ID list, which is useful for lists that are embedded in other pages, where the list conditions are entirely foreign to the controller responsible for providing the data. To assist with this one jqGrid virtual function needed the model added as a parameter, so I added it to them all and modified the jqGrid functions in the existing derived controllers. Right now the elements (such as contacts.ctp, the only working one) receive a full list of data to populate themselves. I could have simply taken this and passed it directly to jqGrid, with no need for further server interaction. However, this could result in some very large lists, and although pagination will ensure the user is not overwhelmed, the connection or the browser could be. Unless we have a strong performance need, I'll keep it this way. In the meantime, I'll leave the underlying data available to each element, in case I have to switch over. When all is proven out, I can simplify all the queries such that the extra data is never requested in the first place.

2009-06-14 22:05:44 +00:00

customers_controller.php

Added mechanism to easily create links in the listing grids. I'm not very keen on how it works, but it's good enough for the moment, unless/until I figure out how to push this to the view. If it should stay in the controller, I'm sure a more sophisticated mechanism will be required.

2009-06-15 02:50:21 +00:00

leases_controller.php

Added mechanism to easily create links in the listing grids. I'm not very keen on how it works, but it's good enough for the moment, unless/until I figure out how to push this to the view. If it should stay in the controller, I'm sure a more sophisticated mechanism will be required.

2009-06-15 02:50:21 +00:00

ledger_entries_controller.php

Added the Containable behavior back into the AppModel, since it's obviously getting used in every controller.

2009-06-10 21:09:23 +00:00

ledgers_controller.php

Moved ledgers over the jqGrid. Working reasonably well at the moment.

2009-06-15 06:22:38 +00:00

maps_controller.php

Due to an apparent bug in the core View class, raw images were not being generated with the inclusion of the DebugToolkit. This checkin does NOT fix the problem, but it does include some debug mechanisms that I have continued to need from time to time.

2009-06-11 02:38:54 +00:00

monetary_sources_controller.php

Added a monetary_sources controller/view. Don't know if we'll really want this, since it might just make the most sense to embed its actions within ledger entry. We'll keep it for now.

2009-06-10 21:24:05 +00:00

pages_controller.php

Load pmgr into branches/initial_20090526/site.

2009-05-27 04:18:23 +00:00

transactions_controller.php

Added the Containable behavior back into the AppModel, since it's obviously getting used in every controller.

2009-06-10 21:09:23 +00:00

units_controller.php

Fixed a bug in which jqGrid would fetch data from the current controller, not the controller responsible for populating the data. Added the ability to fetch data based strictly off of an ID list, which is useful for lists that are embedded in other pages, where the list conditions are entirely foreign to the controller responsible for providing the data. To assist with this one jqGrid virtual function needed the model added as a parameter, so I added it to them all and modified the jqGrid functions in the existing derived controllers. Right now the elements (such as contacts.ctp, the only working one) receive a full list of data to populate themselves. I could have simply taken this and passed it directly to jqGrid, with no need for further server interaction. However, this could result in some very large lists, and although pagination will ensure the user is not overwhelmed, the connection or the browser could be. Unless we have a strong performance need, I'll keep it this way. In the meantime, I'll leave the underlying data available to each element, in case I have to switch over. When all is proven out, I can simplify all the queries such that the extra data is never requested in the first place.

2009-06-14 22:05:44 +00:00