I am having troubles with the current changes in the subselect class. while trying to fix this I see two ways I could do it and would like to know what is the "chamilo way". (I think I already know the answer but I am just making educated guesses here)
in some applications (like the portfolio application) the data_manager/database.class.php extends the application's general datamanager (e.g. PortfolioDataManager) and has a private datamember "database". I see many other applications written the same way but I also see other applications having a database.class.php file where the class extends the database class and implements the application's general datamanager which has changed from a class to an interface. Some of the recent changes in the core assume this new structure so i also *assume* this is the *new* structure *every* application *must* have. please correct me if I am wrong, otherwise please put the explanation on the general "idea" of this refactoring on the bugtracker Kind regards, Nathalie p.s. yes I could just pick up the phone and have an answer to my question immediately but i would much rather see information like this on the devlist or on the bugtracker or publicly available anywhere else so maybe it can save others from wasting their time with useless debugging and getting frustrated in the process. (feeling better already ;-) ) -- Nathalie Blocry Onderwijstechnoloog Vrije Universiteit Brussel Dienst Onderwijszaken - Onderwijstechnologische Cel Tel: +32-2-6291249 _______________________________________________ Dev mailing list [email protected] http://lists.chamilo.org/listinfo/dev
