Todo List
dokeos-library
- clean up horrible structure, script is unwieldy, for example easier way to deal with different tool visibility settings: ALL_TOOLS_INVISIBLE, ALL_TOOLS_VISIBLE, CORE_TOOLS_VISIBLE...
- script has ugly ifelseifelseifelseif structure, improve
- rewrite code so it is easier to understand
- same behaviour as api_get_user_info so that api_get_course_id becomes absolete too
- move function to better place, main_api ?
- move function to better place, main_api ?
- Implementation for single database
- Add the user language to the parameters
- research: expiration date of a course
- the table constants have all to start with TABLE_ This is because of the analogy with the tool constants TOOL_
- Add option to unsubscribe class-members from the courses where the class was subscibed to
- Remove globals
- When deleting a virtual course: unsubscribe users from that virtual course from the groups in the real course if they are not subscribed in that real course.
- now only files/folders in a folder get visibility 2, we should rename them too.
- check if this function is needed as it seems that this is a copy of the Display::display_sortable_table function.
- convert queries to use Database API
- ??not only check if a file is visible, but also check if the user is allowed to see the file??
- add more array entries to abstract course info from field names
- what's the use of this function. I think this is better removed. There should be consistency in the variable names and the use throughout the scripts for the database name we should consistently use or db_name or database (db_name probably being the better one)
- add more array entries to abstract user info from field names
- what's the use of this function. I think this is better removed. There should be consistency in the variable names and the use throughout the scripts
- for more consistency: use course_info call from database API
- shouldn't this be in the course.lib.php script?
- shouldn't this be in the course.lib.php script?
- remove this function because this is of no use and should not be used.
- shouldn't this be in the user.lib.php script?
- optional course code parameter, optional sorting parameters...
- Add $course_code parameter to all functions. So this GroupManager can be used outside a session.
- Take locale into account (eg decimal point or comma ?)
- use the Database libraries
- the table constants have all to start with TABLE_ This is because of the analogy with the tool constants TOOL_
dokeos-announcements
- make AWACS out of the configuration settings
- this file is 1200+ lines without any functions -> needs to be split into multiple functions
- more security checking
- remove globals
dokeos-admin
- Add some langvars to DLTT
- Add some langvars to DLTT
- function does not belong here, move to (display?) library,
- language display used apparently no longer existing array, converted to english for now. but we should switch to display the real language names.
- function does not belong here, move to code library, also see infocours.php and index.php which contain a similar function
- the $_settings should be reloaded here. => write api function for this and use this in global.inc.php also.
- Add some langvars to DLTT
- have a 6monthly re-registration
dokeos-backup
- Use archive-folder of Dokeos?
- once the RESOURCE_* constants are replaced by the globally defined TOOL_* constants, this function will be replaced by get_type()
- Check if the archive is a correct Dokeos-export
- Use the gloabaly defined constants voor tools and remove the RESOURCE_* constants
- restore tree-structure of posts.
dokeos-auth
- check if unsubscribing from a course WITH group memberships works as it should
- constants are in uppercase, variables aren't
- complete the comments on this function: the parameter section
- when editing (moving) a course inside a user defined course category to a different user defined category the dropdown list should have the current course category selected.
- complete the comments on this function: the parameter section
- move this to a stylesheet Added id grey to CSS
- refactor, move relevant functions to code libraries
dokeos-survey
- add a checkbox weither the answer is a textarea or a wysiwyg editor
- add a limit for the number of characters that can be type
- consider adding a question_comment form element
- the form_text has to become a wysiwyg editor or adding a question_comment field
- only the available platform languages should be used => need an api get_languages and and api_get_available_languages (or a parameter)
- delete all the options of this question
- also delete the answers to this question
- open questions are not in the complete report yet.
- rename $possible_answers to $possible_options ?
- allow switching between horizontal and vertical.
- multiple response: percentage are probably not OK
- the pagebreak and comment question types should not be shown => removed from $survey_data before
- the question and option text have to be shortened and should expand when the user clicks on it.
- consider moving this to surveymanager.inc.lib.php
- use quickforms
- consider merging this function with display_complete_report
- rename $possible_answers to $possible_options ?
- check if the user already filled the survey and if this is the case then the answers have to be updated and not stored again. alterantively we could not allow people from filling the survey twice.
- performance could be improved if not the survey_id was stored with the invitation but the survey_code
- use quickforms for the forms
- consider making $defaults['additional_users'] also an array
- use survey_id parameter instead of $_GET
- one sql call should do the trick
- one sql call should do the trick
- this is the same function as in create_new_survey.php
- use survey_id parameter instead of $_GET
- consider using $form_content instead of $_POST
- use quickforms for the forms
- it would make more sense to consider yesno as a special case of multiplechoice and not the other way around
- The question has to be more clearly indicated (same style as when filling the survey)
- writing the update statement when editing a question
- editing of a shared question
- writing the update statement when editing a question
- move this file to inc/lib
- use consistent naming for the functions (save vs store for instance)
- use quickforms for the forms
- add rules: title and text cannot be empty
- check if the mailtext contains the **link** part, if not, add the link to the end
- checking if the additional emails are valid (or add a rule for this)
- The invite column is not done
- try to understand the white, blue, ... template stuff.
- use quickforms for the forms
- move this file to inc/lib
- use consistent naming for the functions (save vs store for instance)
dokeos-document
- eliminate code duplication between document/document.php, scormdocument.php
- improve script structure (FormValidator is used to display form, but not for validation at the moment)
- convert comments to be understandable to phpDocumentor
- convert comments to be understandable to phpDocumentor
- eliminate code duplication between document/document.php, scormdocument.php
dokeos-dropbox
- complete refactoring. Currently there are about at least 3 sql queries needed for every individual dropbox document. first we find all the documents that were sent (resp. received) by the user then for every individual document the user(s)information who received (resp. sent) the document is searched then for every individual document the feedback is retrieved
- the implementation of the dropbox categories could (on the database level) have been done more elegantly by storing the category in the dropbox_person table because this table stores the relationship between the files (sent OR received) and the users
- $author was originally a field but this has now been replaced by the first and lastname of the uploader (to prevent anonymous uploads) As a consequence this parameter can be removed
Dokeos
- give the user the possibility what needs to be done with the files in this category: move them to the root, download them as a zip, delete them
- use the correct api_get_path instead of $clarolineRepositoryWeb
- move this function to the user library
- check if this function is still necessary.
- add the form for adding new comment (if the other party has not deleted it yet).
- check if this function is still necessary. There might be a library function for this.
- check if this function is still necessary. There might be a library function for this.
- check if this function is still necessary.
- function does not belong here, move to code library, also see infocours.php which contains similar function
- consider moving this function to a more appropriate place.
- consider having a separate table that contains only an id and a name of the role.
- consider having a separate table that contains only an id and a name of the role.
- check if this function is still necessary. There might be a library function for this.
- eliminate global
- currently there is a setting user_permissions and group_permissions. We should merge this in one config setting.
- check if this function is still necessary.
- make config settings out of $forum_setting
- move the tool constants to the appropriate place
- use Database :: get_course_table
- remove code duplication in this function
- can't this be moved to a different file so that we can delete this file? Is this still in use? If not, then it should be removed or maybe offered as an extension
- use the correct api_get_path instead of $clarolineRepositoryWeb
- consider removing the check if the user has received or sent this file (zip download of a folder already sufficiently checks for this).
- integrate some cleanup function that removes zip files that are older than 2 days
- consider using a htaccess that denies direct access to the file but only allows the php file to access it. This would remove the scrambling requirement but it would require additional checks to see if the filename of the uploaded file is not used yet.
- when we copy the files there might be two files with the same name. We need a function that (recursively) checks this and changes the name
dokeos-exercise
- split more code up in functions, move functions to library?
- remove the debug code and use the general debug library
- small letters for table variables
- use the Database:: functions
- respect coding guidelines
dokeos-forum
- change the get parameter so that it matches the tool constants.
- check if api_item_property_update returns true or false => returnmessage depends on it.
- move to itemmanager
- an additional parameter that takes the visibility into account. For instance $countinvisible=0 would return the number of visible forums, $countinvisible=1 would return the number of visible and invisible forums
- config setting for recovery or not (see also the documents tool: real delete or not).
- write the code for the cascading deletion of the forums inside a forum category and also the threads and replies inside these forums
- write recursive function that deletes all the posts that have this message as parent
- check $sql4 because this one really looks fishy.
- consider merging both in one query.
- consider to call this function only once and let it return an array where the key is the forum id and the value is an array with number_of_topics and number of post as key of this array and the value as a value. This could reduce the number of queries needed (especially when there are more forums)
- this is the same as the Display::xxx function, so it can be removed => all calls have to be changed also
- consider removing the table_item_property calls here but this can prevent unwanted side effects when a forum does not have an entry in the item_property table but does have one in the forum table.
dokeos-include
- isn't configuration.php renamed to configuration.inc.php yet?
- make it possible to enable / disable the tracking through the Dokeos config page.
- remove the code that displays the button that links to the install page but use a redirect immediately. By doing so the $already_installed variable can be removed.
- use the $_configuration array for all the needed variables
dokeos-group
- Display error message if no group ID specified
dokeos-install
- is this the same function as in forumfunction.inc.php? If this is the case then it should not appear here.
- is this the same function as in forumfunction.inc.php? If this is the case then it should not appear here.
- function does not belong here, move to code library, also see infocours.php which contains similar function
- (busy) organise code into functions
- reduce high level of duplication in this code
- is this the same function as in forumfunction.inc.php? If this is the case then it should not appear here.
- is this the same function as in forumfunction.inc.php? If this is the case then it should not appear here.
- is this the same function as in forumfunction.inc.php? If this is the case then it should not appear here.
- is this the same function as in forumfunction.inc.php? If this is the case then it should not appear here.
- is this the same function as in forumfunction.inc.php? If this is the case then it should not appear here.
- - conditional changing of tables. Currently we execute for example ALTER TABLE `$dbNameForm`.`cours` instructions without checking wether this is necessary.
- reorganise code into functions
- use database library
- - conditional changing of tables. Currently we execute for example ALTER TABLE `$dbNameForm`.`cours` instructions without checking wether this is necessary.
- reorganise code into functions
- use database library
- - conditional changing of tables. Currently we execute for example ALTER TABLE `$dbNameForm`.`cours` instructions without checking wether this is necessary.
- reorganise code into functions
- use database library
- remove duplication: MAX_COURSE_TRANSFER is defined here and also in install.index.php
- - conditional changing of tables. Currently we execute for example ALTER TABLE `$dbNameForm`.`cours` instructions without checking wether this is necessary.
- reorganise code into functions
- use database library
dokeos-main
- use the correct get_path function
- does $_plugins need to be global?
- Couldn't this be done using the $HtmlHeadXtra array?
- add a parameter user_id so that it is possible to show the courselist of other users (=generalisation). This will prevent having to write a new function for this.
- move code for what's new icons to a separate function to clear things up
- refactor into different functions for database calls | logic | display
- replace single-character $my_course['d'] indices
- check if the news management works as expected
- check the different @todos in this page and really do them
- check for duplication of functions with index.php (user_portal.php is orginally a copy of index.php)
- display_digest, shouldn't this be removed and be made into an extension?
- move get_personal_course_list and some other functions to a more appripriate place course.lib.php or user.lib.php
- shouldn't the SCRIPTVAL_ and CONFVAL_ constant be moved to the config page? Has anybody any idea what the are used for? if these are really configuration settings then we can add those to the dokeos config settings
- use api_get_path instead of $rootAdminWeb
- rewrite code to separate display, logic, database code
dokeos-learnpath
- implement resource removal
- eliminate all global $lang declarations, use get_lang, improve structure.
- eliminate all global $lang declarations, use get_lang, improve structure.
- eliminate all global $lang declarations, use get_lang, improve structure.
- Try using the SCORM communications addition (adding a button and several javascript calls to the SCORM API) elsewhere than just in the export feature, so it doesn't look like an incoherent feature
- remove code duplication
- rename functions to coding conventions: not deleteitem but delete_item, etc
- rewrite functions to comply with phpDocumentor
- //todo insert into lp_item_view if lp_view not exists
dokeos-link
- replace strings by constants
- add the changing of the visibility of a course
- replace the globals with the appropriate $_POST or $_GET values
- rewrite the whole links tool because it is becoming completely cluttered, code does not follow the coding conventions, does not use html_quickform, ... some features were patched in
- improve organisation, tables should come from database library
dokeos-whoisonline
- the second parameter is of no use.
- the name is not very clear. I would expect that it deletes a login from the tracking info or even it deletes a user.
- remove parameter $statistics_database which is no longer necessary
dokeos-resourcelinker
- use the constants for the type definitions.
- this function is too long, rewrite
- use Database API instead of creating table names locally.
- use the constants for the tools
- use Database API instead of creating table names locally.
- use the constants for the tools
- reorganise code, use Database API instead of creating table names locally.
- reorganise code, use Database API instead of creating table names locally.
- use the constants for the type definitions.
dokeos-learnpath-scorm
dokeos-user
- users from virtual courses always show "-" for the group related output. Edit and statistics columns are disabled * for these users, for now.
- convert normal table display to display function (refactor virtual course display function)
- display table functions need support for align and valign (e.g. to center text in cells) (this is now possible)
- possibility to edit user-course rights and view statistics for users in virtual courses
- clean up script in clean sections: (1) gather information (2) tool logic (3) display
dokeos-tracking
- clean code - structure is unclear and difficult to modify
- clean code - structure is unclear and difficult to modify
dokeos-studentpublications
- Add a session check to see if subdirs_list doesn't exist yet (cached copy)
- refactor more code into functions, use quickforms, coding standards, ...
|
|
