Reviewed: https://reviews.mahara.org/4110 Committed: http://gitorious.org/mahara/mahara/commit/dbe457bae7b45f921d5ae0058e6abb71fee2eda3 Submitter: Aaron Wells ([email protected]) Branch: master
commit dbe457bae7b45f921d5ae0058e6abb71fee2eda3 Author: Robert Lyon <[email protected]> Date: Mon Dec 22 16:33:55 2014 +1300 Separation of the functions (Bug #1393621) Allowing each of the 'classname' classes listed in external_functions to be it's own function file to make it easier for developers. Change-Id: I9c4e3dfc198abdf2c274c8a7d569fce5bf431471 Signed-off-by: Robert Lyon <[email protected]> -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/1393621 Title: split the webservices/functions.php into user / group / institution functions for better code separation Status in Mahara ePortfolio: In Progress Bug description: Currently the classes mahara_user_external, mahara_group_external, and mahara_institution_external are all within the webservices/functions.php file. I think as we add more functions to that file it will get quite large. So for easier editing will be worth breaking that up into a structure like: webservices/functions/user.php - for user functions webservices/functions/group.php - for group functions webservices/functions/institution.php - for institution functions this way if we want to add another set of functions say 'collection' it would be a matter of adding in webservices/functions/collection.php To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1393621/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
