https://docs.moodle.org/24/en/api.php?action=feedcontributions&feedformat=atom&user=David.horat 2026-05-08T09:53:10Z User contributions MediaWiki 1.43.5 https://docs.moodle.org/24/en/index.php?title=Flash&diff=49950 2009-02-02T23:37:19Z

<p>David.horat: </p> <hr /> <div>Flash content can easily be included in your courses.<br /> <br /> ==General instructions for insertion==<br /> If you have the [[Filters|filter]] for the Flash [[Multimedia plugins|multimedia plugin]] enabled then simply linking to the file in an [[HTML in Moodle|HTML]] area such as a [[Label|label]], [[HTML block]] or [[Course sections#Editing_sections|section description]] will also display the Flash file inline. At the moment all flash files will play at the same size site-wide by default. <br /> <br /> You can use HTML code and the object tag to set individual movie sizes which will work with most browsers except Microsoft's Internet Explorer.<br /> <br /> &lt;object width=&quot;600&quot; height=&quot;400&quot; classid=&quot;clsid:D27CDB6E-AE6D-11cf-96B8-444553540000&quot;&lt;br&gt; codebase=&lt;br&gt; &quot;http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,0,0&quot;&gt;&lt;br&gt; &lt;param name=&quot;movie&quot; value=&quot;http://yoursite.org/file.php/2/movie.swf&quot; /&gt;&lt;br&gt; &lt;param name=&quot;quality&quot; value=&quot;high&quot; /&gt; &lt;embed width=&quot;600&quot; height=&quot;400&quot; &lt;br&gt; src=&quot;http://yoursite.org/file.php/2/movie.swf&quot; quality=&quot;high&quot; &lt;br&gt; type=&quot;application/x-shockwave-flash&quot; &lt;br&gt; pluginspage=&quot;http://www.macromedia.com/go/getflashplayer&quot; /&gt;&lt;/object&gt;<br /> <br /> :''TIP:'' If using the .swf filter you can control display size by adding the following parameters to the end of the link to specify size: ?d=widthxheight (for example ?d=600x400 where the image is 600 pixels wide 400 pixels high). You can use up to 3 characters for the width and the height, plus an optional % symbol at the end.<br /> <br /> :''TIP:'' There are also other ways to achieve sizing control. See the [http://moodle.org/mod/forum/discuss.php?d=29588 Size of embedded Flash] forum posts for some hacks.<br /> <br /> ===Update 2008===<br /> The following code works in IE7 and Firefox 3:<br /> <br /> &lt;pre&gt;<br /> &lt;embed width=&quot;600&quot; height=&quot;400&quot; type=&quot;application/x-shockwave-flash&quot; <br /> src=&quot;http://YOURSITE.com/path/to/your/swffile/swf&quot; <br /> id=&quot;myFlashId&quot; bgcolor=&quot;#ffffff&quot; quality=&quot;high&quot; wmode=&quot;opaque&quot; /&gt;<br /> &lt;/pre&gt;<br /> <br /> ==Insert flash into a lesson page==<br /> Inserting a Flash file into a [[Lesson Pages|lesson page]] (either a branch or question page) is similar to the above.<br /> #Publish the SWF and HTML upload the SWF to a central location on your server. <br /> #Then copy and paste the HTML code (between the object tags) and <br /> #place that in the HTML side of your question (switch to HTML view).<br /> # Change the value in your HTML code<br /> ##Example: Change this &lt;nowiki&gt;&lt;param name=&quot;movie&quot; value=&quot;MyFlashFile.swf&quot;&lt;/nowiki&gt; to this &lt;nowiki&gt;&lt;param name=&quot;movie&quot; value=&quot;http://www.myserver.com/flash_files/MyFlashFile.swf&quot;&lt;/nowiki&gt;<br /> # Repeat the same step, but change the src instead.<br /> ##Example:&lt;nowiki&gt;&lt;embed src=&quot;http://www.myserver.com/flash_files/MyFlashFile.swf&quot;&lt;/nowiki&gt;<br /> #Save the question<br /> <br /> ==Some external links to Flash file generating programs==<br /> This is not a comprehensive list nor an endorsement of any product.<br /> *[http://www.openoffice.org/ Open Office, an open source program] can export-create a Flash swf file in Impress, the presentation module. Very basic output.<br /> *[http://www.adobe.com/products/flash/ Adobe/Macromedia Flash site] &quot;The&quot; serious program, now owned by Adobe and part of their Creative Suite.<br /> *[http://www.debugmode.com/wink/ Wink] freeware program. Basic output functions, steps up from OO Impress but not even close to Adobe Flash.<br /> *[http://osflash.org/projects Open Source Flash Organization] list of projects probably best viewed by developers, not teachers<br /> <br /> <br /> ==See also==<br /> *[[Flash_module]] How to install a Flash plugin module.<br /> *[[Files]] for teachers<br /> *[[Filters]] part of the administration block<br /> *[http://moodle.org/mod/forum/discuss.php?d=37119 Multimedia plugin vs object embed] forum discussion<br /> *[http://moodle.org/mod/forum/discuss.php?d=29588 Size of embedded Flash] forum discussion<br /> *[[Development:SWF]] SWF Activity Module<br /> <br /> <br /> <br /> [[Category:Administrator]]<br /> [[Category:Teacher]]<br /> [[pl:Flash]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=User:David_Horat&diff=48257 2008-12-17T16:17:51Z

<p>David.horat: </p> <hr /> <div>* Personal webpage: http://davidhorat.com/<br /> * Moodle.org profile: http://moodle.org/user/view.php?id=153093</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice&diff=42585 2008-08-25T06:41:43Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> <br /> == Status ==<br /> Cancelled due to Opera´s voice control not good enough in open contexts.<br /> <br /> == Introduction ==<br /> Moodle Voice is a project for embedding VoiceXML support into Moodle Core.<br /> <br /> == Project Status ==<br /> * Project stopped.<br /> * The current voice recognition technology in Opera is not good enough to make the whole Moodle application Voice accesible.<br /> <br /> == Current Focus ==<br /> <br /> 1. Describing the functionality to be made voice enabled within this project.<br /> <br /> 2. Add an experimental option called &quot;VoiceXML&quot; so only when this variable is checked, VoiceXML code is generated.<br /> <br /> 3. Create a php lib for VoiceXML to put all functionality of VoiceXML and to be used by the rest of the code.<br /> <br /> 4. Modify weblib.php and formslib.php intensively to use the VoiceXML lib and output VoiceXML code along with the html code if the VoiceXML variable is set.<br /> <br /> 5. Create a set of tests for every function and the integration of several functions to assure that the functionality is the expected one.<br /> <br /> == Contacts ==<br /> Student : [http://mayankjain20.googlepages.com Mayank Jain]<br /> <br /> Mentor : [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> == Suggestions ==<br /> Please feel free to chip-in with your suggestions.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:DB_layer_2.0&diff=35322 2008-04-28T12:05:52Z

<p>David.horat: </p> <hr /> <div>COMING SOON<br /> <br /> == Ideas ==<br /> * [http://en.wikipedia.org/wiki/Object-relational_mapping Object Relational Mapping style]<br /> * There are already some PHP ORM tools:<br /> ** [http://www.phpdoctrine.org/ Doctrine]<br /> ** [http://www.phpobjectgenerator.com/ PHP Object Generator]<br /> ** [http://propel.phpdb.org/trac/ Propel]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Projects_for_new_developers&diff=33950 2008-03-25T09:43:00Z

<p>David.horat: /* Moodle Usability Guidelines */</p> <hr /> <div>This page lists possible student projects in Moodle, in particular suggestions for GSOC 2008 projects. <br /> __NOTOC__<br /> ===Potential GSOC students===<br /> <br /> Firstly, review the [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents GSOC advice for students].<br /> <br /> You may choose a project from the list below and/or suggest your own project ideas. Please use the [http://moodle.org/mod/forum/view.php?id=7105 Moodle.org Student projects forum] for discussing project ideas.<br /> <br /> Student applications start on Monday 24th March 2008. See the [http://code.google.com/opensource/gsoc/2008/faqs.html#0.1_timeline GSOC timeline] for more information.<br /> <br /> ===Potential mentors===<br /> <br /> Moodle developers willing to mentor a GSOC project, please suggest a new project under the heading &quot;Ideas we're considering for GSOC&quot; and/or add your name to an existing project. Contact [http://moodle.org/user/view.php?id=24152&amp;course=5 Helen Foster] if you have any questions.<br /> <br /> <br /> __TOC__<br /> ==Useful links==<br /> <br /> * [[GSOC]] - describing Moodle's involvement with Google in their Summer of Code program, including a list of GSOC projects from 2006 and 2007<br /> * [http://tracker.moodle.org/secure/IssueNavigator.jspa?mode=hide&amp;requestId=10512 Popular Requests] - Most voted-for enhancements and new feature requests in the tracker<br /> <br /> ==GSOC suggested projects==<br /> <br /> Following a review, approved suggested projects which have mentors will be moved under this heading. ''More approved suggested projects coming soon!''<br /> <br /> === Consuming RSS feeds ===<br /> <br /> RSS/Atom feeds are becoming an important technology on the web and so it's crucial that Moodle has good support for consuming these feeds for a variety of different uses. At present we generate [[RSS|RSS feeds]] for use by other applications, though only consume feeds in the [[RSS feeds block]]. It would be useful to have a core library which can take care of aggregating feeds (and the issues around it) and to provide them in a simple format for plugins and other core parts of Moodle to use.<br /> <br /> This project will involve creating a feed aggregation library which:<br /> * Will consume most current aggregation technologies (RSS 0.90/1.0/2.0 /Atom etc)<br /> * Will work behind a variety of web proxies <br /> * Periodically aggregates and uses a caching mechanism (doesn't query remote server with every request)<br /> * (Is probably based on an existing PHP framework)<br /> <br /> In order test this library, it will be necessary to refactor the RSS block to use it.<br /> <br /> '''Mentor:''' [http://moodle.org/user/view.php?id=104159&amp;course=5 Dan Poltawski]<br /> <br /> === Secure RSS feeds ===<br /> <br /> Currently RSS is less than useful because:<br /> * Either we can't publish private information to the outside world because it's too sensitive.<br /> * We open up sensitive information to the outside world<br /> <br /> We should add codes to make the RSS URLs practically impossible to guess, much the same way as Google Calendar does it.<br /> <br /> * Overhaul all the RSS feeds in Moodle to make use of a long hash-like string in the URL for identification (Forums, Data etc). We already have a mechanism for managing these, developed for the grade export reports, called user_key_login.<br /> * Add RSS to other areas of Moodle such as the participants &quot;last logins&quot; and the activity logs.<br /> * Explore/research other methods of opening up RSS in a safe way to the outside world.<br /> <br /> '''Mentor:''' [http://moodle.org/user/view.php?id=240338&amp;course=5 Nicolas Connault]<br /> <br /> ===New customisable theme===<br /> <br /> Creation of a new [[Themes|theme]] (theme/custom) that includes a configuration page so that the theme can be easily edited directly via Moodle. The page would include:<br /> <br /> * Select a logo from the site files and/or interface to upload a file<br /> * Several input fields to customise various CSS elements such as block headings, text colour, background colour, headings, header, footer, extra custom CSS etc.<br /> * Select a parent theme<br /> <br /> Also include the option of an administrator setting the theme for the site with their particular configuration or allowing users to customise various elements of the theme.<br /> <br /> '''Mentor:''' [http://moodle.org/user/view.php?id=11995 Shane Elliott]<br /> <br /> === Blog Assignment Type ===<br /> <br /> '''What is it for?'''<br /> <br /> Blogs are inherently user owned and driven by definition, however teachers would like to have a way to use blogs as assignments in their courses, comment, grade, etc.<br /> <br /> A solution to this conundrum would be a new Assignment type that makes it possible for a student to easily submit the link one of their blogs to an assignment in a course, and have that blog entry privately graded and commented on by the instructor of that course. The blog entry itself remains public along with all of the student's other blogs. The tool would provide a time filter in the Assignment, so that the instructor could limit the blog entry posting dates that will be accepted (both to ensure 'fresh' entries and to keep the list of entries the student chooses short for frequent student bloggers).<br /> <br /> I suggest a blog assignment type that functions as follows:<br /> <br /> '''Teacher:'''<br /> Teacher creates a blog assignment, this puts a grade in the gradebook and provides an assignment link for students to see.<br /> <br /> The teacher can configure options to allow a blog entry posted in the last X days to be used for the assignment.<br /> <br /> '''Students:'''<br /> When students enter the assignment they see a drop down menu of all their current (blog entries posted in the last X days as chosen by the teacher) blog entries, and they choose one to satisfy the assignment.<br /> <br /> '''Assessment:'''<br /> The teacher goes in to the Assignment, views the blogs that are linked from the assignment, leaves comments (the comments only show up to the student when they view the blog assignment), and gives a grade.<br /> <br /> The blog entries themselves stay on the student's blog, only the grades, links, and comments go in the assignment (optionally the assignment scrapes the student's blog and loads the full text in to store for backup and restore).<br /> <br /> '''Mentor:''' Mathieu Petit-Clair<br /> <br /> '''Interested Student''': [http://moodle.org/user/view.php?id=27192&amp;course=1 Joey Morwick]<br /> <br /> === Competency tracking ===<br /> <br /> Currently in Moodle 1.9 we have a way of saying &quot;these courses and these activities are intended to achieve these outcomes&quot; and teachers can grade students against those outcomes. eg You could grade &quot;Understands basic evacuation procedures&quot; on a scale like &quot;No understanding, Partial understanding, Total understanding&quot;. <br /> <br /> What we need now is a way to <br /> * Relate a list of desired outcomes to each USER, for the site, like a &quot;learning plan&quot; for that user.<br /> * For each outcome, specify a desired competency (eg Total understanding) for that competency to be &quot;achieved&quot;.<br /> * Find a good way to connect Grades in gradebooks to these competencies<br /> ** We'll have to cope with results that might not contribute to final grading, such as initial evaluations. <br /> ** We'll have to cope with final grading from more than one course, and aggregate them<br /> * In the end we'll have to generate nice reports to admins and users so that they can see what a particular user can do and what they still have to learn or prove.<br /> * Finally, for extra credit, it would be nice to have a &quot;suggest courses&quot; features which would suggest upcoming courses that can help a user gain missing competencies.<br /> <br /> '''Mentor:''' [http://moodle.org/user/view.php?id=1 Martin Dougiamas]<br /> <br /> <br /> ==Ideas we're considering for GSOC==<br /> <br /> ''Please add your ideas for GSOC projects under this heading.''<br /> <br /> Following a review, approved suggested projects which have mentors will be moved under the heading &quot;GSOC suggested projects&quot; above. Please note that suggested projects require a mentor in order for them to be approved.<br /> <br /> === Roles interface improvements ===<br /> <br /> Improve the roles editing interface by making it more dynamic and flexible. You can use the YUI library for ajax if you like, but there must be a good fall-back interface too. Some ideas include:<br /> <br /> * Improve the order of the capabilities and implement better grouping.<br /> * Make the groups of capabilities collapsible to make it easier to &quot;zoom in&quot; to a particular section.<br /> * Add floating tooltip help when you hover over any given capability.<br /> * Experiment with an (alternate) interface seeing the roles all side-by-side for easier comparison/editing.<br /> * Implement a roles backup and restore system to allow site administrators to distribute useful roles in the Moodle community (rather than having to describe the permissions setup)<br /> * More clearly designate the scope of capabilities. Does the capability apply at the site, category, course, activity, or user to user levels.<br /> * Analyse the problem carefully with feedback from the community for more ideas.<br /> <br /> ===Integration with bibliographic systems such as Wikindx===<br /> <br /> Managing references and citing them is an important behaviour in university education and research. Bibliographic facilities are quite complicated and go beyond the capabilities of Moodle built-in technology (e.g. the database activity). Integrating Moodle with open-source bibliographic software such as [http://wikindx.sourceforge.net/ Wikindx] could much facilitate this practice within Moodle.<br /> <br /> Design and construct an integration with Wikindx (or other open-source bibliographic tools, if appropriate).<br /> <br /> Teachers should be able to easily refer to wikindx bibliography items throughout a Moodle course, and be able to:<br /> <br /> * Generate correctly-formatted in-place references (using standard styles e.g. Harvard, APA) for the commonly-cited reference types (e.g. journal article, book chapter, book). It may be possible to delegate the formatting directly to wikindx (since it already performs functions like these) rather than implementing a whole new set of logic in the Moodle integration.<br /> ** Possibly, allow some kind of direct searching of a wikindx database from within Moodle, so as to make it easier to refer to items<br /> * Generate reading lists / bibliographies<br /> * Allow export of the above into common machine-readable formats such as Bibtex or RIS. (Wikindx can perform this so again it's a question of hooking into, or expanding, wikindx functionality.)<br /> <br /> See also [[Development:Wikindx]] and [http://moodle.org/mod/forum/discuss.php?d=23022 this forum discussion] too<br /> <br /> ===Implement CATs in Moodle===<br /> <br /> [http://www.amazon.com/Classroom-Assessment-Techniques-Handbook-Education/dp/1555425003/ This book] describes a number of assessment techniques that involve collaboration and group work, and therefore fit very well into Moodle's Social Constructivist philosophy. The book about using these techniques in the classroom, but at an conference I attended there was a talk by Jean Runyon and Thomas Gorecki from the College of Southern Maryland saying how well these techniques work online. <br /> <br /> Some of them just need a forum of something basic, but others would need to be done as a database module templates. Doing this would<br /> <br /> # Make Moodle an even better teaching tool.<br /> # Provide some good exemplars of how to do interesting things with database templates.<br /> # Possibly highlight limitations in the database template system, that would require improvements to the database module code to overcome.<br /> # One of the outcomes of this project could be some really good 'How to write a database template' tutorial, which would be very valuable to the community.<br /> <br /> This is my (Tim Hunt's) idea, but I would not be interested in mentoring it. It would need to be someone who knows all about the database module.<br /> <br /> <br /> <br /> === Moodle IDE ===<br /> The objective of this project is to create a Moodle IDE based on Eclipse so that new developers can get to develop Moodle in less time.<br /> <br /> '''Ideas'''<br /> * First release: Eclipse + Plugins + Moodle splashscreen + CVS Configuration + Apache + MySQL + Moodle CVS code. All preconfigured and ready out of the box.<br /> * Every X time, it checks for new versions of Moodle and packs it.<br /> * Checkstyle plugin alike to follow Moodle Design Guidelines.<br /> * Development help (can be wiki pages to navigate offline)<br /> <br /> '''More mentors needed'''<br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Download (Old Version)''': [http://mirrors.davidhorat.com/moodle/MoodleIDE-latest.zip MoodleIDE-latest]<br /> <br /> '''Join the [http://moodle.org/mod/forum/discuss.php?d=92859 discussion thread]'''<br /> <br /> === Moodle Multisite ===<br /> <br /> The objective of this project is to make Moodle able to manage several Moodle sites with just one source code. This will help administrators of several sites to centralize code upgrades and ''technical problems''.<br /> <br /> '''Ideas'''<br /> * config.php will be a proxy that executes the concrete config file depending on the current url.<br /> * The concrete config file will be under the directory /config and will have an arbitrary name created by the user.<br /> * Create an XML file with all the pairs URL(n)-ConfigFile(1).<br /> * Every time this file changes, it should be created the config.php file cache (to speed up things).<br /> * Develop a Web frontend to change this file, that can be just accessed by the super admin in every site.<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Join the [http://moodle.org/mod/forum/discuss.php?d=92860 discussion thread]'''<br /> <br /> === Automatic Accessibility Checking ===<br /> <br /> The objective of this project is to make a tool that can check Moodle´s accessibility automatically before realising a version.<br /> <br /> '''Ideas'''<br /> * Automatic Tool (see down)<br /> * Create an example course which introduces every XHTML code of the Moodle application, in order to have a way to test it.<br /> * Create a button called &quot;Check XHTML&quot; which will send the current page code to a validator.<br /> ** This button just helps to check if the current page is valid. Good for development purposes.<br /> ** This button will be (de)activated in the administration panel<br /> ** Keep in mind that this button will not pass the URL as a referer, but it will take all the code from the page and send it to the validation service<br /> ** This button can be used in other web applications<br /> <br /> '''Automatic Tool'''<br /> * Create (or use an existing one) an automatic and easy to use tool that retrieves all the pages in a site until a concrete level (recursive calling it for each link)<br /> ** Use concrete user agent names<br /> ** Be able to store cookies in order to check it with a concrete user and password<br /> * Plug each output to an automatic XHTML validator<br /> ** In the future we can plug in different validators: CSS, WCAG (what it can be checkable automatically), etc.<br /> * Generate stats<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Interested Student''': David Knight email - david[at]allsopmedia[dot]com irc - Lucias O`Neil<br /> <br /> '''Join the [http://moodle.org/mod/forum/discuss.php?d=92861 discussion thread]'''<br /> <br /> === Moodle Usability ===<br /> The main objective of this project is to detect and solve specific usability issues.<br /> <br /> '''Main tasks'''<br /> * Research in the tracker, forums, etc. to create a hitlist of the top 10 (or 20) specific usability issues.<br /> * For each issue, identify the problem clearly (screenshots) and clearly describe one or more solutions (incl mock screenshots) for the community to evaluate.<br /> * Create code to solve the problem with the best decided solution (optional, depending on Moodle community thoughs).<br /> * Take a look at [http://fluidproject.org/ Fluid Project] (who we are involved with already) to see where some of their components can be used in Moodle (optional).<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Join the [http://moodle.org/mod/forum/discuss.php?d=92862 discussion thread]'''<br /> <br /> ===Moodle Target tracking + rewards/gifts===<br /> <br /> This one would suit a facebook enthusiast! The Facebook gifts system is very popular and an ideal motivator for students at school level. Moodle needs an equivalent.<br /> <br /> The aim is to develop a system for setting targets e.g. 'get at least 60% in this assignment/quiz/whatever' and for reward credits to be awarded automatically when it is completed. These reward credits translate to a system of Gifts similar to Facebook ones (small images, akin to stickers, which can be bought for a small fee and sent to friends who then display them on their profile). Admins can control what the reward images are for their site, maybe having them in some sort of rank order of value, or having different ones with different meanings. There are several ways they could be implemented beyond that:<br /> * Teachers could choose which rewards can be earned for a specific task. For example, there may be different rewards for forums and assignments<br /> * Teachers may want to specify different rewards for different levels of performance on the same task<br /> * Teachers decide how many points a certain target is worth and the students cash in those points for rewards of various values<br /> * Teachers decide how many rewards a target is worth and students choose that many rewards. None are worth more than 1 point each, the only difference is the graphic.<br /> Once students have rewards, they need a way of allocating them (presumably permanently) to their friends. A system for logically displaying them on the friend's profile page would be needed too and will need to take into account<br /> * Students with only a few stickers given to them by friends will want them to maximise their display<br /> * Students who are very popular with hundreds of stickers may need to groups of 10 similar ones substituted for a super-sticker to use less space<br /> * Hovering over the sticker should give details of who awarded it and when and possibly a short message.<br /> Additionally, the social rating/ranking that this achieves will have most effect when it is publicly visible in various places e.g. under forum avatars and maybe in the online users block as well as the user profile. <br /> <br /> Maybe this would sit well with the 'Friends' part of last years GSOC social networking project if it were finished.<br /> <br /> I can't offer to mentor in coding terms, but will help with ideas all I can. [[User:Matt Gibson|Matt Gibson]] 05:26, 4 March 2008 (CST)<br /> <br /> Interested Student : Rajan Vaish ( GTALK/GMAIL:vaish.rajan@gmail.com, IRC: vaish)<br /> <br /> ===Use of Video Material Effectively within Moodle===<br /> <br /> The main purpose of this module will be to get use of video content, most probably a lecture, in a more formal/controlled/effective way within Moodle.<br /> <br /> The main features of this module will be;<br /> * Stream the video file (most probably in flv format)<br /> ** Should be able to stream by using multiple ways (e.x. FMS, Red5, lighttpd, etc..)<br /> ** Develop a front-end to configure the streaming server settings<br /> ** automatic media conversion (controlled by other Moodle settings like max file size, etc..)<br /> * The teacher can give related notes, websites or other resources with the video<br /> * The students can keep a note related to each video<br /> * Share/view other student's notes (probably controlled by the teachers and/or students)<br /> * Optionally assess the student notes and include them in the grade book <br /> <br /> The above list may expanded based on your views.<br /> <br /> '''Difficulty Level:''' Easy/Medium<br /> <br /> '''Skills Required:'''<br /> * Familiarity with streaming servers like Red5 and video streaming in general.<br /> * Should be able to install and configure required products (Moodle, Red5, lighttpd, etc..) in any OS (Windows, Linux, Mac, etc..)<br /> * Understanding of UI design concepts.<br /> * Familiarity with Moodle APIs and [[Developer_documentation |Developing Moodle in general]]<br /> <br /> '''Join the [http://moodle.org/mod/forum/discuss.php?d=92310 discussion thread]'''<br /> <br /> '''References'''<br /> * [http://moodle.org/mod/data/view.php?rid=931&amp;page=102 FlashVideo]<br /> * [http://osflash.org/red5 RED5 Open Source Streaming Server]<br /> <br /> <br /> '''Potential Mentor:''' [http://moodle.org/user/edit.php?id=68520 Rashan Anushka]<br /> <br /> ===Web-based upgrade and plugins interface===<br /> <br /> A system for Moodle to be upgraded along with its plugins from within the admin interface.<br /> <br /> Currently, adding third party modules/patches can be messy and can especially slow down the upgrade process if CVS is not used. The aim would be to develop a way to package plugins in a standardised way so that a single zip file could be retrieved and installed automatically, similar to the way courses are restored. An added feature would be for the modules and plugins database on moodle.org to have an XML index so that you could browse available plugins from within your own moodle instance and have a one-click install option. Version compatibility info could be included so that only those which will work with your install will be shown. At upgrade time, the new third-party components screen could then show which ones could be upgraded along with the rest of the code and which would need to dropped because there is no compatible replacement.<br /> <br /> <br /> ===Add SQLite Support to XMLDB===<br /> Having local sqlite database has been discussed in the past by developers for uses such as prototyping and testing. In this project you would add sqllite to the moodle database abstraction layer. Once this had been archieved you would look at adding a mechanism to copy a live moodle database into a sqllite database to implement a mechnism to switch into 'testing mode' using a sqlite copy of the live database. See also [http://moodle.org/mod/forum/discuss.php?d=88827 this thread on sqllite in moodle]<br /> <br /> ==See also==<br /> <br /> * Using Moodle [http://moodle.org/mod/forum/discuss.php?d=92797 Simple Quiz building user interface] forum discussion about work that might be done this summer, although as part of something other than GSOC<br /> <br /> [[Category:Developer]]<br /> [[Category:Project]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Projects_for_new_developers&diff=33739 2008-03-18T10:07:44Z

<p>David.horat: </p> <hr /> <div>This page lists possible student projects in Moodle, in particular suggestions for GSOC 2008 projects.<br /> __NOTOC__<br /> ==To do this week (17th - 24th March 2008)==<br /> <br /> *Would-be GSOC student participants please discuss your application ideas in the [http://moodle.org/mod/forum/view.php?id=7105 Moodle.org Student projects forum]. ''You're welcome to suggest ideas for projects too!''<br /> *Moodlers willing to mentor a GSOC project, please add your name to a project on this page.<br /> <br /> <br /> __TOC__<br /> == Secure RSS feeds ==<br /> <br /> Currently RSS is less than useful because:<br /> * Either we can't publish private information to the outside world because it's too sensitive.<br /> * We open up sensitive information to the outside world<br /> <br /> We should add codes to make the RSS URLs practically impossible to guess, much the same way as Google Calendar does it.<br /> <br /> * Overhaul all the RSS feeds in Moodle to make use of a long hash-like string in the URL for identification (Forums, Data etc).<br /> * Store these codes in a new field per-user and per-course. <br /> * Add GUIs to let the user recreate their code to something else should they suspect a breach.<br /> * Add RSS to other areas of Moodle such as the participants &quot;last logins&quot; and the activity logs.<br /> * Explore/research other methods of opening up RSS in a safe way to the outside world.<br /> <br /> '''Old Specification:''' [[Student projects/Secure RSS feeds|Secure RSS feeds]]<br /> <br /> == Roles interface improvements ==<br /> <br /> Improve the roles editing interface by making it more dynamic and flexible. You can use the YUI library for ajax if you like, but there must be a good fall-back interface too. Some ideas include:<br /> <br /> * Improve the order of the capabilities and implement better grouping.<br /> * Make the groups of capabilities collapsible to make it easier to &quot;zoom in&quot; to a particular section.<br /> * Add floating tooltip help when you hover over any given capability.<br /> * Experiment with an (alternate) interface seeing the roles all side-by-side for easier comparison/editing.<br /> * Implement a roles backup and restore system to allow site administrators to distribute useful roles in the moodle comunity (rather than having to describe the permissions setup)<br /> * Analyse the problem carefully with feedback from the community for more ideas.<br /> <br /> ==Integration with bibliographic systems such as Wikindx==<br /> <br /> Managing references and citing them is an important behaviour in university education and research. Bibliographic facilities are quite complicated and go beyond the capabilities of Moodle built-in technology (e.g. the database activity). Integrating Moodle with open-source bibliographic software such as [http://wikindx.sourceforge.net/ Wikindx] could much facilitate this practice within Moodle.<br /> <br /> Design and construct an integration with Wikindx (or other open-source bibliographic tools, if appropriate).<br /> <br /> Teachers should be able to easily refer to wikindx bibliography items throughout a Moodle course, and be able to:<br /> <br /> * Generate correctly-formatted in-place references (using standard styles e.g. Harvard, APA) for the commonly-cited reference types (e.g. journal article, book chapter, book). It may be possible to delegate the formatting directly to wikindx (since it already performs functions like these) rather than implementing a whole new set of logic in the Moodle integration.<br /> ** Possibly, allow some kind of direct searching of a wikindx database from within Moodle, so as to make it easier to refer to items<br /> * Generate reading lists / bibliographies<br /> * Allow export of the above into common machine-readable formats such as Bibtex or RIS. (Wikindx can perform this so again it's a question of hooking into, or expanding, wikindx functionality.)<br /> <br /> See also [[Development:Wikindx]] and [http://moodle.org/mod/forum/discuss.php?d=23022 this forum discussion] too<br /> <br /> ==Implement CATs in Moodle==<br /> <br /> [http://www.amazon.com/Classroom-Assessment-Techniques-Handbook-Education/dp/1555425003/ This book] describes a number of assessment techniques that involve collaboration and group work, and therefore fit very well into Moodle's Social Constructivist philosophy. The book about using these techniques in the classroom, but at an conference I attended there was a talk by Jean Runyon and Thomas Gorecki from the College of Southern Maryland saying how well these techniques work online. <br /> <br /> Some of them just need a forum of something basic, but others would need to be done as a database module templates. Doing this would<br /> <br /> # Make Moodle an even better teaching tool.<br /> # Provide some good exemplars of how to do interesting things with database templates.<br /> # Possibly highlight limitations in the database template system, that would require improvements to the database module code to overcome.<br /> # One of the outcomes of this project could be some really good 'How to write a database template' tutorial, which would be very valuable to the community.<br /> <br /> This is my (Tim Hunt's) idea, but I would not be interested in mentoring it. It would need to be someone who knows all about the database module.<br /> <br /> == Blog Assignment Type ==<br /> <br /> '''What is it for?'''<br /> <br /> Blogs are inherently user owned and driven by definition, however teachers would like to have a way to use blogs as assignments in their courses, comment, grade, etc.<br /> <br /> A solution to this conundrum would be a new Assignment type that makes it possible for a student to easily submit the link one of their blogs to an assignment in a course, and have that blog entry privately graded and commented on by the instructor of that course. The blog entry itself remains public along with all of the student's other blogs. The tool would provide a time filter in the Assignment, so that the instructor could limit the blog entry posting dates that will be accepted (both to ensure 'fresh' entries and to keep the list of entries the student chooses short for frequent student bloggers).<br /> <br /> I suggest a blog assignment type that functions as follows:<br /> <br /> '''Teacher:'''<br /> Teacher creates a blog assignment, this puts a grade in the gradebook and provides an assignment link for students to see.<br /> <br /> The teacher can configure options to allow a blog entry posted in the last X days to be used for the assignment.<br /> <br /> '''Students:'''<br /> When students enter the assignment they see a drop down menu of all their current (blog entries posted in the last X days as chosen by the teacher) blog entries, and they choose one to satisfy the assignment.<br /> <br /> '''Assessment:'''<br /> The teacher goes in to the Assignment, views the blogs that are linked from the assignment, leaves comments (the comments only show up to the student when they view the blog assignment), and gives a grade.<br /> <br /> The blog entries themselves stay on the student's blog, only the grades, links, and comments go in the assignment (optionally the assignment scrapes the student's blog and loads the full text in to store for backup and restore).<br /> <br /> == Moodle IDE ==<br /> The objective of this project is to create a Moodle IDE based on Eclipse so that new developers can get to develop Moodle in less time.<br /> <br /> '''Ideas'''<br /> * First release: Eclipse + Plugins + Moodle splashscreen + CVS Configuration + Apache + MySQL + Moodle CVS code. All preconfigured and ready out of the box.<br /> * Every X time, it checks for new versions of Moodle and packs it.<br /> * Checkstyle plugin alike fo follow Moodle Design Guidelines.<br /> * Development help (can be wiki pages to navigate offline)<br /> <br /> '''More mentors needed'''<br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Download (Old Version)''': [http://mirrors.davidhorat.com/moodle/MoodleIDE-latest.zip MoodleIDE-latest]<br /> <br /> '''Join the [http://moodle.org/mod/forum/discuss.php?d=92859 discussion thread]'''<br /> <br /> == Moodle Multisite ==<br /> The objective of this project is to make Moodle able to manage several Moodle sites with just one source code. This will help administrators of several sites to centralize code upgrades and ''technical problems''.<br /> <br /> '''Ideas'''<br /> * config.php will be a proxy that executes the concrete config file depending on the current url.<br /> * The concrete config file will be under the directory /config and will have an arbitrary name created by the user.<br /> * Create an XML file with all the pairs URL(n)-ConfigFile(1).<br /> * Every time this file changes, it should be created the config.php file cache (to speed up things).<br /> * Develop a Web frontend to change this file, that can be just accessed by the super admin in every site.<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Join the [http://moodle.org/mod/forum/discuss.php?d=92860 discussion thread]'''<br /> <br /> == Automatic Accesibility Checking ==<br /> The objective of this project is to make a tool that can check Moodle´s accesibility automatically before realising a version.<br /> <br /> '''Ideas'''<br /> * Automatic Tool (see down)<br /> * Create an example course which introduces every XHTML code of the Moodle application, in order to have a way to test it.<br /> * Create a button called &quot;Check XHTML&quot; which will send the current page code to a validator.<br /> ** This button just helps to check if the current page is valid. Good for development purposes.<br /> ** This button will be (de)activated in the administration panel<br /> ** Keep in mind that this button will not pass the URL as a referer, but it will take all the code from the page and send it to the validation service<br /> ** This button can be used in other web applications<br /> <br /> '''Automatic Tool'''<br /> * Create (or use an existing one) an automatic and easy to use tool that retrieves all the pages in a site until a concrete level (recursive calling it for each link)<br /> ** Use concrete user agent names<br /> ** Be able to store cookies in order to check it with a concrete user and password<br /> * Plug each output to an automatic XHTML validator<br /> ** In the future we can plug in different validators: CSS, WCAG (what it can be checkable automaticly), etc.<br /> * Generate stats<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Join the [http://moodle.org/mod/forum/discuss.php?d=92861 discussion thread]'''<br /> <br /> == Moodle Usability Guidelines ==<br /> The main objective of this project is to develop a usability guidelines and testing methods in order to have a real view of Moodle usage.<br /> <br /> '''Main tasks'''<br /> * Research in the usability world to see which methods are most used and which are most reliable.<br /> * Select the ones that are more appropiate for Moodle<br /> * Create a usability guideline with the way to apply these methods for Moodle<br /> * Try them with real world people (optional, although it would be very interesting)<br /> * Analyse the results in order to extract conclusions of the current Moodle Usage<br /> * Report the ways we could improve current Moodle Usability<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Join the [http://moodle.org/mod/forum/discuss.php?d=92862 discussion thread]'''<br /> <br /> ==Moodle Target tracking + rewards/gifts==<br /> This one would suit a facebook enthusiast! The Facebook gifts system is very popular and an ideal motivator for students at school level. Moodle needs an equivalent.<br /> <br /> The aim is to develop a system for setting targets e.g. 'get at least 60% in this assignment/quiz/whatever' and for reward credits to be awarded automatically when it is completed. These reward credits translate to a system of Gifts similar to facebook ones (small images, akin to stickers, which can be bought for a small fee and sent to friends who then display them on their profile). Admins can control what the reward images are for their site, maybe having them in some sort of rank order of value, or having different ones with different meanings. There are several ways they could be implemented beyond that:<br /> * Teachers could choose which rewards can be earned for a specific task. For example, there may be different rewards for forums and assignments<br /> * Teachers may want to specify different rewards for different levels of performance on the same task<br /> * Teachers decide how many points a certain target is worth and the students cash in those points for rewards of various values<br /> * Teachers decide how many rewards a target is worth and students choose that many rewards. None are worth more than 1 point each, the only difference is the graphic.<br /> Once students have rewards, they need a way of allocating them (presumably permanently) to their friends. A system for logically displaying them on the friend's profile page would be needed too and will need to take into account<br /> * Students with only a few stickers given to them by friends will want them to maximise their display<br /> * Students who are very popular with hundreds of stickers may need to groups of 10 similar ones substituted for a super-sticker to use less space<br /> * Hovering over the sticker should give details of who awarded it and when and possibly a short message.<br /> Additionally, the social rating/ranking that this achieves will have most effect when it is publicly visible in various places e.g. under forum avatars and maybe in the online users block as well as the user profile. <br /> <br /> Maybe this would sit well with the 'Friends' part of last years GSOC social networking project if it were finished.<br /> <br /> I can't offer to mentor in coding terms, but will help with ideas all I can. [[User:Matt Gibson|Matt Gibson]] 05:26, 4 March 2008 (CST)<br /> <br /> ==Use of Video Material Effectively within Moodle==<br /> The main purpose of this module will be to get use of video content, most probably a lecture, in a more fomal/controled/affective way within moodle.<br /> <br /> The main features of this module will be;<br /> * Stream the video file (most probably in flv format)<br /> ** Should be able to stream by using multiple ways (e.x. FMS, Red5, lighttpd, etc..)<br /> ** Develop a fronted to configure the streaming server settings<br /> ** automatic media conversion (controlled by other moodle settings like max file size, etc..)<br /> * The teacher can give related notes, websites or other resources with the video<br /> * The students can keep a note related to each video<br /> * Share/view other student's notes (probably controlled by the teachers and/or students)<br /> * Optionally asses the student notes and include them in the grade book <br /> <br /> The above list may expanded based on your views.<br /> <br /> '''Difficulty Level:''' Easy/Medium<br /> <br /> '''Skills Required:'''<br /> * Familiarity with Streaming Servers like Red5 and video streaming in general.<br /> * Should be able to install and configure required products (Moodle, Red5, lighttpd, etc..) in any OS (Windows, Linux, Mac, etc..)<br /> * Understanding of UI design concepts.<br /> * Familiarity with Moodle APIs and [[Developer_documentation |Developing Moodle in general]]<br /> <br /> '''References'''<br /> * [http://moodle.org/mod/data/view.php?rid=931&amp;page=102 FlashVideo]<br /> * [http://osflash.org/red5 RED5 Open Source Streaming Server]<br /> <br /> <br /> '''Potential Mentor:''' [http://moodle.org/user/edit.php?id=68520 Rashan Anushka]<br /> <br /> ----<br /> <br /> ==Web-based upgrade and plugins interface==<br /> A system for Moodle to be upgraded along with its plugins from within the admin interface.<br /> <br /> Currently, adding third party modules/patches can be messy and can especially slow down the upgrade process if CVS is not used. The aim would be to develop a way to package plugins in a standardised way so that a single zip file could be retrieved and installed automatically, similar to the way courses are restored. An added feature would be for the modules and plugins database on moodle.org to have an XML index so that you could browse available plugins from within your own moodle instance and have a one-click install option. Version compatibility info could be included so that only those which will work with your install will be shown. At upgrade time, the new third-party components screen could then show which ones could be upgraded along with the rest of the code and which would need to dropped because there is no compatible replacement.<br /> <br /> ==See also==<br /> <br /> * [[GSOC]], including a list of GSOC projects from 2006 and 2007<br /> * [http://moodle.org/mod/forum/discuss.php?d=92797 this forum thread] about work that might be done this summer, although as part of something other than GSOC.<br /> <br /> [[Category:Developer]]<br /> [[Category:Project]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Projects_for_new_developers&diff=33738 2008-03-18T10:02:05Z

<p>David.horat: </p> <hr /> <div>This page lists possible student projects in Moodle, in particular suggestions for GSOC 2008 projects.<br /> __NOTOC__<br /> ==To do this week (17th - 24th March 2008)==<br /> <br /> *Would-be GSOC student participants please discuss your application ideas in the [http://moodle.org/mod/forum/view.php?id=7105 Moodle.org Student projects forum]. ''You're welcome to suggest ideas for projects too!''<br /> *Moodlers willing to mentor a GSOC project, please add your name to a project on this page.<br /> <br /> <br /> __TOC__<br /> == Secure RSS feeds ==<br /> <br /> Currently RSS is less than useful because:<br /> * Either we can't publish private information to the outside world because it's too sensitive.<br /> * We open up sensitive information to the outside world<br /> <br /> We should add codes to make the RSS URLs practically impossible to guess, much the same way as Google Calendar does it.<br /> <br /> * Overhaul all the RSS feeds in Moodle to make use of a long hash-like string in the URL for identification (Forums, Data etc).<br /> * Store these codes in a new field per-user and per-course. <br /> * Add GUIs to let the user recreate their code to something else should they suspect a breach.<br /> * Add RSS to other areas of Moodle such as the participants &quot;last logins&quot; and the activity logs.<br /> * Explore/research other methods of opening up RSS in a safe way to the outside world.<br /> <br /> '''Old Specification:''' [[Student projects/Secure RSS feeds|Secure RSS feeds]]<br /> <br /> == Roles interface improvements ==<br /> <br /> Improve the roles editing interface by making it more dynamic and flexible. You can use the YUI library for ajax if you like, but there must be a good fall-back interface too. Some ideas include:<br /> <br /> * Improve the order of the capabilities and implement better grouping.<br /> * Make the groups of capabilities collapsible to make it easier to &quot;zoom in&quot; to a particular section.<br /> * Add floating tooltip help when you hover over any given capability.<br /> * Experiment with an (alternate) interface seeing the roles all side-by-side for easier comparison/editing.<br /> * Implement a roles backup and restore system to allow site administrators to distribute useful roles in the moodle comunity (rather than having to describe the permissions setup)<br /> * Analyse the problem carefully with feedback from the community for more ideas.<br /> <br /> ==Integration with bibliographic systems such as Wikindx==<br /> <br /> Managing references and citing them is an important behaviour in university education and research. Bibliographic facilities are quite complicated and go beyond the capabilities of Moodle built-in technology (e.g. the database activity). Integrating Moodle with open-source bibliographic software such as [http://wikindx.sourceforge.net/ Wikindx] could much facilitate this practice within Moodle.<br /> <br /> Design and construct an integration with Wikindx (or other open-source bibliographic tools, if appropriate).<br /> <br /> Teachers should be able to easily refer to wikindx bibliography items throughout a Moodle course, and be able to:<br /> <br /> * Generate correctly-formatted in-place references (using standard styles e.g. Harvard, APA) for the commonly-cited reference types (e.g. journal article, book chapter, book). It may be possible to delegate the formatting directly to wikindx (since it already performs functions like these) rather than implementing a whole new set of logic in the Moodle integration.<br /> ** Possibly, allow some kind of direct searching of a wikindx database from within Moodle, so as to make it easier to refer to items<br /> * Generate reading lists / bibliographies<br /> * Allow export of the above into common machine-readable formats such as Bibtex or RIS. (Wikindx can perform this so again it's a question of hooking into, or expanding, wikindx functionality.)<br /> <br /> See also [[Development:Wikindx]] and [http://moodle.org/mod/forum/discuss.php?d=23022 this forum discussion] too<br /> <br /> ==Implement CATs in Moodle==<br /> <br /> [http://www.amazon.com/Classroom-Assessment-Techniques-Handbook-Education/dp/1555425003/ This book] describes a number of assessment techniques that involve collaboration and group work, and therefore fit very well into Moodle's Social Constructivist philosophy. The book about using these techniques in the classroom, but at an conference I attended there was a talk by Jean Runyon and Thomas Gorecki from the College of Southern Maryland saying how well these techniques work online. <br /> <br /> Some of them just need a forum of something basic, but others would need to be done as a database module templates. Doing this would<br /> <br /> # Make Moodle an even better teaching tool.<br /> # Provide some good exemplars of how to do interesting things with database templates.<br /> # Possibly highlight limitations in the database template system, that would require improvements to the database module code to overcome.<br /> # One of the outcomes of this project could be some really good 'How to write a database template' tutorial, which would be very valuable to the community.<br /> <br /> This is my (Tim Hunt's) idea, but I would not be interested in mentoring it. It would need to be someone who knows all about the database module.<br /> <br /> == Blog Assignment Type ==<br /> <br /> '''What is it for?'''<br /> <br /> Blogs are inherently user owned and driven by definition, however teachers would like to have a way to use blogs as assignments in their courses, comment, grade, etc.<br /> <br /> A solution to this conundrum would be a new Assignment type that makes it possible for a student to easily submit the link one of their blogs to an assignment in a course, and have that blog entry privately graded and commented on by the instructor of that course. The blog entry itself remains public along with all of the student's other blogs. The tool would provide a time filter in the Assignment, so that the instructor could limit the blog entry posting dates that will be accepted (both to ensure 'fresh' entries and to keep the list of entries the student chooses short for frequent student bloggers).<br /> <br /> I suggest a blog assignment type that functions as follows:<br /> <br /> '''Teacher:'''<br /> Teacher creates a blog assignment, this puts a grade in the gradebook and provides an assignment link for students to see.<br /> <br /> The teacher can configure options to allow a blog entry posted in the last X days to be used for the assignment.<br /> <br /> '''Students:'''<br /> When students enter the assignment they see a drop down menu of all their current (blog entries posted in the last X days as chosen by the teacher) blog entries, and they choose one to satisfy the assignment.<br /> <br /> '''Assessment:'''<br /> The teacher goes in to the Assignment, views the blogs that are linked from the assignment, leaves comments (the comments only show up to the student when they view the blog assignment), and gives a grade.<br /> <br /> The blog entries themselves stay on the student's blog, only the grades, links, and comments go in the assignment (optionally the assignment scrapes the student's blog and loads the full text in to store for backup and restore).<br /> <br /> == Moodle IDE ==<br /> The objective of this project is to create a Moodle IDE based on Eclipse so that new developers can get to develop Moodle in less time.<br /> <br /> '''Ideas'''<br /> * First release: Eclipse + Plugins + Moodle splashscreen + CVS Configuration + Apache + MySQL + Moodle CVS code. All preconfigured and ready out of the box.<br /> * Every X time, it checks for new versions of Moodle and packs it.<br /> * Checkstyle plugin alike fo follow Moodle Design Guidelines.<br /> * Development help (can be wiki pages to navigate offline)<br /> <br /> '''More mentors needed'''<br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Download (Old Version)''': [http://mirrors.davidhorat.com/moodle/MoodleIDE-latest.zip MoodleIDE-latest]<br /> <br /> == Moodle Multisite ==<br /> The objective of this project is to make Moodle able to manage several Moodle sites with just one source code. This will help administrators of several sites to centralize code upgrades and ''technical problems''.<br /> <br /> '''Ideas'''<br /> * config.php will be a proxy that executes the concrete config file depending on the current url.<br /> * The concrete config file will be under the directory /config and will have an arbitrary name created by the user.<br /> * Create an XML file with all the pairs URL(n)-ConfigFile(1).<br /> * Every time this file changes, it should be created the config.php file cache (to speed up things).<br /> * Develop a Web frontend to change this file, that can be just accessed by the super admin in every site.<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> == Automatic Accesibility Checking ==<br /> The objective of this project is to make a tool that can check Moodle´s accesibility automatically before realising a version.<br /> <br /> '''Ideas'''<br /> * Automatic Tool (see down)<br /> * Create an example course which introduces every XHTML code of the Moodle application, in order to have a way to test it.<br /> * Create a button called &quot;Check XHTML&quot; which will send the current page code to a validator.<br /> ** This button just helps to check if the current page is valid. Good for development purposes.<br /> ** This button will be (de)activated in the administration panel<br /> ** Keep in mind that this button will not pass the URL as a referer, but it will take all the code from the page and send it to the validation service<br /> ** This button can be used in other web applications<br /> <br /> '''Automatic Tool'''<br /> * Create (or use an existing one) an automatic and easy to use tool that retrieves all the pages in a site until a concrete level (recursive calling it for each link)<br /> ** Use concrete user agent names<br /> ** Be able to store cookies in order to check it with a concrete user and password<br /> * Plug each output to an automatic XHTML validator<br /> ** In the future we can plug in different validators: CSS, WCAG (what it can be checkable automaticly), etc.<br /> * Generate stats<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> == Moodle Usability Guidelines ==<br /> The main objective of this project is to develop a usability guidelines and testing methods in order to have a real view of Moodle usage.<br /> <br /> '''Main tasks'''<br /> * Research in the usability world to see which methods are most used and which are most reliable.<br /> * Select the ones that are more appropiate for Moodle<br /> * Create a usability guideline with the way to apply these methods for Moodle<br /> * Try them with real world people (optional, although it would be very interesting)<br /> * Analyse the results in order to extract conclusions of the current Moodle Usage<br /> * Report the ways we could improve current Moodle Usability<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> ==Moodle Target tracking + rewards/gifts==<br /> This one would suit a facebook enthusiast! The Facebook gifts system is very popular and an ideal motivator for students at school level. Moodle needs an equivalent.<br /> <br /> The aim is to develop a system for setting targets e.g. 'get at least 60% in this assignment/quiz/whatever' and for reward credits to be awarded automatically when it is completed. These reward credits translate to a system of Gifts similar to facebook ones (small images, akin to stickers, which can be bought for a small fee and sent to friends who then display them on their profile). Admins can control what the reward images are for their site, maybe having them in some sort of rank order of value, or having different ones with different meanings. There are several ways they could be implemented beyond that:<br /> * Teachers could choose which rewards can be earned for a specific task. For example, there may be different rewards for forums and assignments<br /> * Teachers may want to specify different rewards for different levels of performance on the same task<br /> * Teachers decide how many points a certain target is worth and the students cash in those points for rewards of various values<br /> * Teachers decide how many rewards a target is worth and students choose that many rewards. None are worth more than 1 point each, the only difference is the graphic.<br /> Once students have rewards, they need a way of allocating them (presumably permanently) to their friends. A system for logically displaying them on the friend's profile page would be needed too and will need to take into account<br /> * Students with only a few stickers given to them by friends will want them to maximise their display<br /> * Students who are very popular with hundreds of stickers may need to groups of 10 similar ones substituted for a super-sticker to use less space<br /> * Hovering over the sticker should give details of who awarded it and when and possibly a short message.<br /> Additionally, the social rating/ranking that this achieves will have most effect when it is publicly visible in various places e.g. under forum avatars and maybe in the online users block as well as the user profile. <br /> <br /> Maybe this would sit well with the 'Friends' part of last years GSOC social networking project if it were finished.<br /> <br /> I can't offer to mentor in coding terms, but will help with ideas all I can. [[User:Matt Gibson|Matt Gibson]] 05:26, 4 March 2008 (CST)<br /> <br /> ==Use of Video Material Effectively within Moodle==<br /> The main purpose of this module will be to get use of video content, most probably a lecture, in a more fomal/controled/affective way within moodle.<br /> <br /> The main features of this module will be;<br /> * Stream the video file (most probably in flv format)<br /> ** Should be able to stream by using multiple ways (e.x. FMS, Red5, lighttpd, etc..)<br /> ** Develop a fronted to configure the streaming server settings<br /> ** automatic media conversion (controlled by other moodle settings like max file size, etc..)<br /> * The teacher can give related notes, websites or other resources with the video<br /> * The students can keep a note related to each video<br /> * Share/view other student's notes (probably controlled by the teachers and/or students)<br /> * Optionally asses the student notes and include them in the grade book <br /> <br /> The above list may expanded based on your views.<br /> <br /> '''Difficulty Level:''' Easy/Medium<br /> <br /> '''Skills Required:'''<br /> * Familiarity with Streaming Servers like Red5 and video streaming in general.<br /> * Should be able to install and configure required products (Moodle, Red5, lighttpd, etc..) in any OS (Windows, Linux, Mac, etc..)<br /> * Understanding of UI design concepts.<br /> * Familiarity with Moodle APIs and [[Developer_documentation |Developing Moodle in general]]<br /> <br /> '''References'''<br /> * [http://moodle.org/mod/data/view.php?rid=931&amp;page=102 FlashVideo]<br /> * [http://osflash.org/red5 RED5 Open Source Streaming Server]<br /> <br /> <br /> '''Potential Mentor:''' [http://moodle.org/user/edit.php?id=68520 Rashan Anushka]<br /> <br /> ----<br /> <br /> ==Web-based upgrade and plugins interface==<br /> A system for Moodle to be upgraded along with its plugins from within the admin interface.<br /> <br /> Currently, adding third party modules/patches can be messy and can especially slow down the upgrade process if CVS is not used. The aim would be to develop a way to package plugins in a standardised way so that a single zip file could be retrieved and installed automatically, similar to the way courses are restored. An added feature would be for the modules and plugins database on moodle.org to have an XML index so that you could browse available plugins from within your own moodle instance and have a one-click install option. Version compatibility info could be included so that only those which will work with your install will be shown. At upgrade time, the new third-party components screen could then show which ones could be upgraded along with the rest of the code and which would need to dropped because there is no compatible replacement.<br /> <br /> ==See also==<br /> <br /> * [[GSOC]], including a list of GSOC projects from 2006 and 2007<br /> * [http://moodle.org/mod/forum/discuss.php?d=92797 this forum thread] about work that might be done this summer, although as part of something other than GSOC.<br /> <br /> [[Category:Developer]]<br /> [[Category:Project]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice&diff=33056 2008-02-28T21:39:38Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> <br /> == Introduction ==<br /> Moodle Voice is a project for embedding VoiceXML support into Moodle Core.<br /> <br /> == Project Status ==<br /> * Project stopped.<br /> * The current voice recognition technology in Opera is not good enough to make the whole Moodle application Voice accesible.<br /> <br /> == Current Focus ==<br /> <br /> 1. Describing the functionality to be made voice enabled within this project.<br /> <br /> 2. Add an experimental option called &quot;VoiceXML&quot; so only when this variable is checked, VoiceXML code is generated.<br /> <br /> 3. Create a php lib for VoiceXML to put all functionality of VoiceXML and to be used by the rest of the code.<br /> <br /> 4. Modify weblib.php and formslib.php intensively to use the VoiceXML lib and output VoiceXML code along with the html code if the VoiceXML variable is set.<br /> <br /> 5. Create a set of tests for every function and the integration of several functions to assure that the functionality is the expected one.<br /> <br /> == Contacts ==<br /> Student : [http://mayankjain20.googlepages.com Mayank Jain]<br /> <br /> Mentor : [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> == Suggestions ==<br /> Please feel free to chip-in with your suggestions.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice&diff=33055 2008-02-28T21:39:20Z

<p>David.horat: /* Project Status */</p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> == Introduction ==<br /> Moodle Voice is a project for embedding VoiceXML support into Moodle Core.<br /> <br /> == Project Status ==<br /> * Project stopped.<br /> * The current voice recognition technology in Opera is not good enough to make the whole Moodle application Voice accesible.<br /> <br /> == Current Focus ==<br /> <br /> 1. Describing the functionality to be made voice enabled within this project.<br /> <br /> 2. Add an experimental option called &quot;VoiceXML&quot; so only when this variable is checked, VoiceXML code is generated.<br /> <br /> 3. Create a php lib for VoiceXML to put all functionality of VoiceXML and to be used by the rest of the code.<br /> <br /> 4. Modify weblib.php and formslib.php intensively to use the VoiceXML lib and output VoiceXML code along with the html code if the VoiceXML variable is set.<br /> <br /> 5. Create a set of tests for every function and the integration of several functions to assure that the functionality is the expected one.<br /> <br /> == Contacts ==<br /> Student : [http://mayankjain20.googlepages.com Mayank Jain]<br /> <br /> Mentor : [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> == Suggestions ==<br /> Please feel free to chip-in with your suggestions.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_ToDo&diff=23694 2007-05-26T07:57:45Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> Here we will put the tasks we need to complete. If no tasks assigned, then keep on with the timeplan.<br /> <br /> == ToDo ==<br /> * Take the HTML output of a page in Moodle and change all its link tags to make it Voice enabled.<br /> * Take the HTML out of a page with a form in Moodle and change the form to make it Voice enabled.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_Changelog&diff=23693 2007-05-26T07:57:06Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> = Moodle Code =<br /> <br /> ==Lib==<br /> <br /> ===Voice XML===<br /> voicexmlenabled(): Returns whether voicexml feature is enabled/allowed or not.<br /> voicexmllib:anotherfunction(): bla bla bla<br /> <br /> ===Weblib===<br /> weblib:yetanotherfunction(): Changed so now it will output</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_Timelog&diff=23692 2007-05-26T07:56:53Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> == May 07 ==<br /> <br /> === 25/05/07 ===<br /> <br /> - I analysed the weblib functions to see how can I change them to fit the Voice XML function calls.<br /> <br /> - I changed the function X of fle Y to make it interact with Z.<br /> <br /> === 24/05/07 ===<br /> <br /> - ...<br /> <br /> - ...</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_Timelog&diff=23691 2007-05-26T07:56:02Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> 25/05/07<br /> - I analysed the weblib functions to see how can I change them to fit the Voice XML function calls.<br /> - I changed the function X of fle Y to make it interact with Z.<br /> <br /> 24/05/07<br /> ...<br /> ...</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_Timelog&diff=23690 2007-05-26T07:55:28Z

<p>David.horat: </p> <hr /> <div>25/05/07<br /> - I analysed the weblib functions to see how can I change them to fit the Voice XML function calls.<br /> - I changed the function X of fle Y to make it interact with Z.<br /> <br /> 24/05/07<br /> ...<br /> ...</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_Changelog&diff=23689 2007-05-26T07:53:56Z

<p>David.horat: </p> <hr /> <div>= Moodle Code =<br /> <br /> ==Lib==<br /> <br /> ===Voice XML===<br /> voicexmlenabled(): Returns whether voicexml feature is enabled/allowed or not.<br /> voicexmllib:anotherfunction(): bla bla bla<br /> <br /> ===Weblib===<br /> weblib:yetanotherfunction(): Changed so now it will output</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice&diff=23688 2007-05-26T07:49:55Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> == Introduction ==<br /> Moodle Voice is a project for embedding VoiceXML support into Moodle Core.<br /> <br /> == Project Status ==<br /> Analysis and Requirement Extraction Phase<br /> <br /> == Current Focus ==<br /> <br /> 1. Describing the functionality to be made voice enabled within this project.<br /> <br /> 2. Add and experimental option called &quot;VoiceXML&quot; so only when this variable is checked, VoiceXML code is generated.<br /> <br /> 3. Create a php lib for VoiceXML to put all functionality of VoiceXML and to be used by the rest of the code.<br /> <br /> 4. Modify weblib.php and formslib.php intensively to use the VoiceXML lib and output VoiceXML code along with the html code if the VoiceXML variable is set.<br /> <br /> 5. Create a set of tests for every function and the integration of several functions to assure that the functionlity is the expected one.<br /> <br /> == Contacts ==<br /> Student : [http://mayankjain20.googlepages.com Mayank Jain]<br /> <br /> Mentor : [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> == Suggestions ==<br /> Please feel free to chip-in with your suggestions.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Tasks_completed&diff=23687 2007-05-26T07:49:19Z

<p>David.horat: </p> <hr /> <div>= Tasks Completed =<br /> <br /> == Initial Setup ==<br /> 1. Read All Coding guidelines.<br /> <br /> 2. Read through the Moodle Developer Information<br /> <br /> 3. Setup of the php-eclipse environment done.<br /> <br /> 4. Downloaded and installed moodle code from CVS<br /> Repository used : eu.cvs.moodle.org<br /> 5. Setup of Opera done<br /> Tested and Learnt opera browser voice support commands(opera 9.01)<br /> <br /> 6. Read Understood and Tested all Voice Examples on [http://dev.opera.com/articles/voice/ Opera Website] <br /> <br /> 7. Read on voicexml intricacies - needed to analyse moodle output to identify what could be converted and what not.<br /> <br /> 8. Added an experimental option called &quot;VoiceXML&quot; so only when this variable is checked, VoiceXML code is generated. <br /> <br /> 9. Created a php lib for VoiceXML to put all functionality of VoiceXML and to be used by the rest of the code (lib/voicexml/voicexmllib.php).<br /> <br /> 10. Created a unit test for voicexmllib to test all functionality in voicexmllib.php in (lib/simpletest/testvoicexmllib.php).</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_VoiceXML_Examples&diff=23686 2007-05-26T07:47:53Z

<p>David.horat: </p> <hr /> <div>== Preparation ==<br /> [http://www.opera.com/products/desktop/voice/ Download and install Opera in English with Voice Support]<br /> <br /> {{Voice}}<br /> {{Moodle 1.9}}<br /> == Examples ==<br /> # [http://devfiles.myopera.com/articles/74/helloworld.xml Hello World!]: In this example, the browser will just say &quot;Hello world&quot;.<br /> # [http://devfiles.myopera.com/articles/39/colorpicker.xml Color picker]: In this example, the browser will say: &quot;Hello. Voice is installed.&quot; Then you can clik on the button &quot;Change colour now&quot; and says in loud voice one of the colours of the box: Red | Pink | Purple | Blue | Green | Maroon | Orange ...<br /> # [http://devfiles.myopera.com/articles/39/opera2go.xml Best browser]: In this example, the browser will ask: &quot;What is the name of the best browser?&quot;. If you say Opera, it will redirect you to the Opera webpage &lt;code&gt;&lt;nowiki&gt;http://www.opera.com/features/&lt;/nowiki&gt;&lt;/code&gt;. In other cases, it will say &quot;Try again.&quot;<br /> # [http://dev.opera.com/articles/view/temporary-x-v-by-example/ More examples]: In this article, you can see several examples of how Voice works. I suggest looking at the one named &quot;I don't understand what you are saying, but I can pretend to&quot; in which you see the potential of the grammars used.<br /> # [http://dev.opera.com/articles/view/add-voice-interactivity-to-your-site/ Tutorial: How to add voice interactivity to your site]: In this tutorial you will find all the basic information about how to add VoiceXML to your site without having to change too much of the code. The idea is having just one output that can be recognized by both VoiceXML browsers, such as Opera, and other standard browsers, such as Internet Explorer and Mozilla Firefox. Firefox and Konqueror are already planning to implement VoiceXML.<br /> # [http://www.robodesign.ro/coding/how-to-add-voice/site/ Site example]: Here you can see a normal site with embedded VoiceXML that works in Internet Explorer, Firefox and Opera (and more). Of course, the only one which support Voice is Opera, so you will only hear in this last one.<br /> # [http://www.uwplatt.edu/auralCSS/pizza.xml Pizza Order Form]<br /> <br /> == See also ==<br /> * [http://dev.opera.com/articles/voice/ Opera Developer Community: Voice Articles]<br /> * [http://jamiep.org/voicexml/ Basic Examples from Jamie Pratt]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_Project&diff=23164 2007-05-09T21:27:17Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> == Objective ==<br /> Adapt Moodle interface to output the needed VoiceXML so you can navigate with your voice with a VoiceXML enabled browser, such as Opera.<br /> <br /> == Benefits ==<br /> Moodle is a free software e-learning platform which is designed to help educators create online courses with rich multimedia content. Making Moodle voice enabled will help disabled people, specially blind and motor disabled, to interact with this great e-Learning tool. Not only that, but also this gives another input interface which can be used to interact faster with the application.<br /> <br /> == Timeplan ==<br /> * Analysis (2 weeks : May 28th - June 10th)<br /> ** Study W3C VoiceXML 2.0<br /> ** Extract requirements: study Moodle output and code to choose what to make voice enabled<br /> ** Begin project webpage, documentation and logs<br /> * Design (1 weeks : June 11 th - June 17th)<br /> ** Make an Architectural Design<br /> ** Make an Implementation Proposal<br /> * Implementation (8 weeks : June 18th - August 5th)<br /> ** Milestone X (each 2 weeks) <br /> * Documentation (2 weeks : August 20th - August 31th)<br /> ** Developer documentation<br /> ** Moodle administrator documentation<br /> ** Future roadmap and design plans<br /> <br /> == Scope ==<br /> Due to the large Moodle code, the scope of what to make voice enabled will be decided in the Analysis phase, although it will be at least all navigational stuff, such as course selection, profile configuration and resource selection.<br /> <br /> == State of the Art of VoiceXML ==<br /> VoiceXML is a well known technology that has been used and supported by IVR several years. Now it has finally come to our desktop. Currently, this technology is only supported by [http://dev.opera.com/articles/voice/ Opera] in the standard browsers field, but since it is a [http://www.w3.org/TR/voicexml20/ W3C Standard], I hope it will become the defacto technology for this kind of service in all browsers. There are already plans to implement it in [http://wiki.mozilla.org/Firefox:2.0_Accessibility Firefox] and [http://www.qsos.org/sheets/webbrowser/konqueror/konqueror-3.5.5.html Konqueror]. Some examples of this technology can be found at: <br /> * http://dev.opera.com/articles/view/add-voice-interactivity-to-your-site/<br /> * http://dev.opera.com/articles/view/temporary-x-v-by-example/<br /> * http://dev.opera.com/articles/view/xhtml-voice-in-action/<br /> <br /> == Architecture Description ==<br /> # We have the option of using [http://moodle.org/mod/forum/discuss.php?d=31895 Customized Scripts] so we will [https://docs.moodle.org/en/Developer_Overview_of_MFM_Code not interfere with normal Moodle development]. On the other hand, we can directly merge it in the current CVS.<br /> # Our code will detect whether the user browser is VoiceXML enabled or not and send the corresponding code<br /> # In the &quot;future roadmap&quot; it will be included how to embed the code in Moodle core (in case it isnt) and make a Moodle configuration option to activate voice features. (It can be done in the project if we have enough time)<br /> <br /> == Related Work ==<br /> * [https://docs.moodle.org/en/Moodle_for_Mobiles Moodle for Mobiles] [http://moodle.cvs.sourceforge.net/moodle/contrib/patches/mobile/ CVS]<br /> ** Outputs [http://www.w3.org/TR/1998/NOTE-compactHTML-19980209/ Compact HTML], uses [http://moodle.org/mod/forum/discuss.php?d=31895 Customized Scripts]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Projects_for_new_developers&diff=22961 2007-04-30T16:08:07Z

<p>David.horat: /* Moodle IDE */</p> <hr /> <div>This page currently lists the projects available Moodle's participation in the [http://code.google.com/soc Google Summer of Code 2007]. Each project here is a nice self-contained project suitable for student programmers to complete in three months or less, and must have an associate mentor who is a regular Moodle developer.<br /> <br /> Current status: Thank you to all the applicants! Google have now confirmed the final selections and we have ten projects with a mentor and a student. Here is a [http://moodle.org/mod/forum/discuss.php?d=69206 general discussion about the project]. Complete details are below.<br /> <br /> ==Google Summer of Code 2007 Timeline==<br /> * '''Starting now''': construct detailed specifications for each project (see below), with feedback from the mentor and the Moodle community. Some questions will be easy for your mentor to answer directly, but some you may have to post in the appropriate [http://moodle.org/course/view.php?id=5 Using Moodle] forums to gather and evaluate community feedback.<br /> * '''May 31''': Coding officially starts. At this time you should have a bug in the [http://tracker.moodle.org Moodle Tracker] that breaks your project down into subtasks. Please keep this tracker up to date with all your subsequent work - it's the best place for all asynchronous discussion with your mentor.<br /> * '''July 9-16''': Interim evaluation of code so far<br /> * '''August 20''': Coding should be completed <br /> <br /> <br /> ==Google Summer of Code 2007 Projects==<br /> <br /> The following projects are in no particular order!<br /> <br /> ===Developing new question types for the quiz===<br /> <br /> The quiz has a plug-in architecture for question types. We currently have implementations of most of the basic question types, it would be nice to have implementations of some more interesting types, perhaps using the YUI JavaScript library to do some interesting interactions (but with an accessible fall-back). Which question types could be left up to the student, but some suggestions are:<br /> <br /> * Drag and drop versions of ordering and matching question types.<br /> * Place a marker or draw a line on an image question types.<br /> * Drag the missing words into the sentence/onto an image question type.<br /> <br /> Another way to find question types to implement would be to review other systems and make sure Moodle supports all the question types that other systems support.<br /> <br /> I envisage that some of these question types would be incorporated into the standard Moodle install, but others would just be put in the contrib area. Part of the project could also be improving the plugin API. There are some minor know issues with it that make it harder that it needs to be to install new question types from contrib.<br /> <br /> '''Mentor:''' Tim Hunt<br /> <br /> '''Student:''' Adriane Boyd<br /> <br /> '''Full Specification:''' [[Student projects/New question types|New question types]]<br /> <br /> <br /> ===Enterprise-level improvements===<br /> <br /> Here are a few things you could do to help Moodle run in a heavy environment (either big Moodles or many multiple Moodles).<br /> <br /> * Adapt all the DB installation and upgrade scripts to run from the command line, so fully scripted installations are possible without using the web interface.<br /> <br /> * Develop a profiling system for developers to use when testing their code. Aim to spot and fix performance bottlenecks in Moodle with good reports and suggestions about what developers could do.<br /> <br /> '''Mentor:''' Penny Leach<br /> <br /> '''Student:''' Dilan Anuruddha Karanachcharighe<br /> <br /> '''Full Specification:''' [[Student projects/Enterprise-level improvements|Enterprise-level improvements]]<br /> <br /> <br /> ===Chat revamp===<br /> <br /> mod/chat needs a bit of an overhaul. Possible interesting approaches:<br /> <br /> * Simplify chatd and rewrite as a proper forking daemon. Great process control and networking project, and properly a good case for a bit of AJAX.<br /> * Integrate Moodle with a Jabber backend, plus frontend glue. <br /> ** On the backend, we need to consider authentication, chatroom creation, and logging. <br /> ** On the frontend, ensuring that we can get Jabber clients started reliably on the end-user's machine, and integrate a preexisting web-based Jabber client for Jabber-impaired users.<br /> ** Installation matter: a clear install HowTo for the Jabber + Moodle.<br /> <br /> '''Mentor:''' [[User:Geoff Cant|Geoff Cant]], Martin Langhoff<br /> <br /> '''Student:''' Thotage Piyasena<br /> <br /> '''Full Specification:''' [[Student projects/Chat revamp|Chat revamp]]<br /> <br /> <br /> ===Messaging improvements===<br /> <br /> The Moodle messaging system in Moodle is a bit clunky and could use improvements to make it slicker and more efficient as a tool for messaging people within the Moodle environment.<br /> <br /> Functionality improvements:<br /> * Add a messaging API class to the core of Moodle which all modules will start using for sending messages (currently they all format their own emails).<br /> * Add output plugins to messaging so that users can choose exactly how to route their messages, especially when they aren't online at the time. Initially the two plugins would be &quot;browser&quot; and &quot;email&quot;, but later there could be a jabber plugin, an IRC plugin etc)<br /> <br /> Gui improvements:<br /> * Improve the main message GUI using AJAX (Moodle includes the YUI library so you'd need to use that)<br /> * Improve the messaging window to allow chats among three or more other people at once.<br /> * GUI for the output plugins to allow users to set rules about each plugin independently, and also to select from incoming messages by type, by user or by moodle module.<br /> * Improve the methods to search messages and find discussions from the past.<br /> * Improve administrator auditing of message logs, including filtering etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luis Filipe Romão Rodrigues<br /> <br /> '''Full Specification:''' [[Student projects/Messaging improvements|Messaging improvements]]<br /> <br /> <br /> <br /> ===Automated grading for Computer Programming Assignments===<br /> <br /> The project here is to develop two things<br /> <br /> #A Moodle assignment plugin to handle the GUI and higher-level processes involved in submitting and grading a programming assignment<br /> #An interface to an external 3rd party program (preferably an established, active open source project) to handle the actual analysis and grading of the source code. It should have plugins to handle arbitrary languages.<br /> <br /> '''Mentor:''' [[User:Nicolas Connault]]<br /> <br /> '''Student:''' Arkaitz Garro<br /> <br /> '''Full Specification:''' [[Student projects/Automated grading of programs|Automated grading of programs]]<br /> <br /> === User Management Improvements ===<br /> <br /> * Improve the User features in moodle to allow bulk-operations. <br /> ** Create an interface to do bulk operations on users (e.g. delete users, reset passwords etc) This could potentially use an AJAX implementation for multiple filtering/selection of required students for bulk operations.<br /> ** Overhall the CSV upload features to allow more flexibility (more options, features to auto-generate more fields such as usernames)<br /> * Enrolment<br /> ** Specify time of manual enrollments ([http://tracker.moodle.org/browse/MDL-8877 MDL-8877])<br /> * Notes<br /> ** Allow teachers to put notes for each student in every course, much requested feature ([http://tracker.moodle.org/browse/MDL-7077 MDL-7077])<br /> <br /> '''Mentor:''' Yu Zhang<br /> <br /> '''Student:''' Andrei Bautu<br /> <br /> '''Full Specification:''' [[Student projects/User Management Improvements|User Management Improvements]]<br /> <br /> <br /> <br /> === Email interface to Moodle ===<br /> <br /> The idea is to let people reply naturally to email they receive from Moodle to change settings or add further comments into forums etc. Moodle activities can then be accessed like a mailing list.<br /> <br /> * Add a setting so admins can specify if they want an email interface enabled. Without it, none of the following is active and Moodle functions just as it does today.<br /> * Improve the outgoing emails in Moodle to contain a unique and robust code in the headers and potentially also in the subject line (switchable by user setting) that encrypts information about the receiver, the activity instance and the specific data. For example, all the information to securely identify a forum post.<br /> * Write a PHP script designed to run from the commandline as part of an email filter, that accepts emails on standard input, parses them and then calls a function in the relevant module. For example forum_incoming_email() in mod/forum/lib.php.<br /> * Write function for forum module (at least) to parse the content of the email and add it as a post from the user. Other modules can be worked on if there's time ... resources could be sent back as attachments, quizzes could send questions and accept multiple choice answers, the course could send back a listing of activities with further codes for each one, etc.<br /> * Security is essential!<br /> <br /> '''Mentor:''' Martin Langhoff<br /> <br /> '''Student:''' Peter Boswood<br /> <br /> '''Full Specification:''' [[Student projects/Email interface|Email interface]]<br /> <br /> <br /> === Secure RSS feeds ===<br /> <br /> Currently RSS is less than useful because:<br /> * Either we can't publish private information to the outside world because it's too sensitive.<br /> * We open up sensitive information to the outside world<br /> <br /> We should add codes to make the RSS URLs practically impossible to guess, much the same way as Google Calendar does it.<br /> <br /> * Overhaul all the RSS feeds in Moodle to make use of a long hash-like string in the URL for identification (Forums, Data etc).<br /> * Store these codes in a new field per-user and per-course. <br /> * Add GUIs to let the user recreate their code to something else should they suspect a breach.<br /> * Add RSS to other areas of Moodle such as the participants &quot;last logins&quot; and the activity logs.<br /> * Explore/research other methods of opening up RSS in a safe way to the outside world.<br /> <br /> '''Mentor:''' Petr Škoda<br /> <br /> '''Student:''' Udit Sajjanhar<br /> <br /> '''Full Specification:''' [[Student projects/Secure RSS feeds|Secure RSS feeds]]<br /> <br /> <br /> <br /> === Social Networking features ===<br /> <br /> Explore the possibilities of social networking features by expanding the user profile page:<br /> <br /> * add user tags that describe interests etc, as links to &quot;interest pages&quot; eg constructivism<br /> * interest pages that contain information about all the people who share that interest, as well as blog entries that use that tag, google searches, other info using standard Moodle blocks etc<br /> * allow users to add other users as &quot;friends&quot;, which are displayed on their user profile pages<br /> * think about controls to prevent abuse of these features in a school environment.<br /> * allow users to specify an external RSS feed to their own external blog, parsing the feed insert entries (optionally selecting by tag) as internal blog entries for that user, adding new tags/permissions as specified, with links back to external entry etc.<br /> * if time, explore deeper integrations with Youtube, Flickr, MySpace, Facebook etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luiz Eduardo Laydner Cruz<br /> <br /> '''Full Specification:''' [[Student projects/Social Networking features|Social Networking features]]<br /> <br /> <br /> <br /> ===Moodle Voice===<br /> <br /> *Objective: Adapt Moodle interface to output the needed VoiceXML so you can navigate with your voice with a VoiceXML enabled browser, such as [http://www.opera.com/ Opera].<br /> *[[Development:Voice_Project|Project Proposal]]<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Student''': Mayank Jain<br /> <br /> '''Full Specification''': [[Development:Voice|Development:Voice]]<br /> <br /> <br /> ----<br /> <br /> ==Other open projects still looking for students==<br /> <br /> <br /> === Roles interface improvements ===<br /> <br /> Improve the roles editing interface by making it more dynamic and flexible. You can use the YUI library for ajax if you like, but there must be a good fall-back interface too. Some ideas include:<br /> <br /> * Improve the order of the capabilities and implement better grouping.<br /> * Make the groups of capabilities collapsible to make it easier to &quot;zoom in&quot; to a particular section.<br /> * Add floating tooltip help when you hover over any given capability.<br /> * Experiment with an (alternate) interface seeing the roles all side-by-side for easier comparison/editing.<br /> * Implement a roles backup and restore system to allow site administrators to distribute useful roles in the moodle comunity (rather than having to describe the permissions setup)<br /> * Analyse the problem carefully with feedback from the community for more ideas.<br /> <br /> <br /> <br /> ===Integration with bibliographic systems such as Wikindx===<br /> <br /> Managing references and citing them is an important behaviour in university education and research. Bibliographic facilities are quite complicated and go beyond the capabilities of Moodle built-in technology (e.g. the database activity). Integrating Moodle with open-source bibliographic software such as [http://wikindx.sourceforge.net/ Wikindx] could much facilitate this practice within Moodle.<br /> <br /> Design and construct an integration with Wikindx (or other open-source bibliographic tools, if appropriate).<br /> <br /> Teachers should be able to easily refer to wikindx bibliography items throughout a Moodle course, and be able to:<br /> <br /> * Generate correctly-formatted in-place references (using standard styles e.g. Harvard, APA) for the commonly-cited reference types (e.g. journal article, book chapter, book). It may be possible to delegate the formatting directly to wikindx (since it already performs functions like these) rather than implementing a whole new set of logic in the Moodle integration.<br /> ** Possibly, allow some kind of direct searching of a wikindx database from within Moodle, so as to make it easier to refer to items<br /> * Generate reading lists / bibliographies<br /> * Allow export of the above into common machine-readable formats such as Bibtex or RIS. (Wikindx can perform this so again it's a question of hooking into, or expanding, wikindx functionality.)<br /> <br /> See also [[Development:Wikindx]] and [http://moodle.org/mod/forum/discuss.php?d=23022 this forum discussion] too<br /> <br /> <br /> <br /> ===Implement CATs in Moodle===<br /> <br /> [http://www.amazon.com/Classroom-Assessment-Techniques-Handbook-Education/dp/1555425003/ This book] describes a number of assessment techniques that involve collaboration and group work, and therefore fit very well into Moodle's Social Constructivist philosophy. The book about using these techniques in the classroom, but at an conference I attended there was a talk by Jean Runyon and Thomas Gorecki from the College of Southern Maryland saying how well these techniques work online. <br /> <br /> Some of them just need a forum of something basic, but others would need to be done as a database module templates. Doing this would<br /> <br /> # Make Moodle an even better teaching tool.<br /> # Provide some good exemplars of how to do interesting things with database templates.<br /> # Possibly highlight limitations in the database template system, that would require improvements to the database module code to overcome.<br /> # One of the outcomes of this project could be some really good 'How to write a database template' tutorial, which would be very valuable to the community.<br /> <br /> This is my (Tim Hunt's) idea, but I would not be interested in mentoring it. It would need to be someone who knows all about the database module.<br /> <br /> <br /> <br /> === Blog Assignment Type ===<br /> <br /> '''What is it for?'''<br /> <br /> Blogs are inherently user owned and driven by definition, however teachers would like to have a way to use blogs as assignments in their courses, comment, grade, etc.<br /> <br /> A solution to this conundrum would be a new Assignment type that makes it possible for a student to easily submit the link one of their blogs to an assignment in a course, and have that blog entry privately graded and commented on by the instructor of that course. The blog entry itself remains public along with all of the student's other blogs. The tool would provide a time filter in the Assignment, so that the instructor could limit the blog entry posting dates that will be accepted (both to ensure 'fresh' entries and to keep the list of entries the student chooses short for frequent student bloggers).<br /> <br /> I suggest a blog assignment type that functions as follows:<br /> <br /> '''Teacher:'''<br /> Teacher creates a blog assignment, this puts a grade in the gradebook and provides an assignment link for students to see.<br /> <br /> The teacher can configure options to allow a blog entry posted in the last X days to be used for the assignment.<br /> <br /> '''Students:'''<br /> When students enter the assignment they see a drop down menu of all their current (blog entries posted in the last X days as chosen by the teacher) blog entries, and they choose one to satisfy the assignment.<br /> <br /> '''Assessment:'''<br /> The teacher goes in to the Assignment, views the blogs that are linked from the assignment, leaves comments (the comments only show up to the student when they view the blog assignment), and gives a grade.<br /> <br /> The blog entries themselves stay on the student's blog, only the grades, links, and comments go in the assignment (optionally the assignment scrapes the student's blog and loads the full text in to store for backup and restore).<br /> <br /> <br /> === Moodle IDE ===<br /> The objective of this project is to create a Moodle IDE based on Eclipse so that new developers can get to develop Moodle in less time.<br /> <br /> '''Ideas'''<br /> * First release: Eclipse + Plugins + Moodle splashscreen + CVS Configuration + Apache + MySQL + Moodle CVS code. All preconfigured and ready out of the box.<br /> * Future<br /> ** Every X time, it checks for new versions of Moodle and packs it.<br /> ** Checkstyle plugin alike fo follow Moodle Design Guidelines.<br /> ** Development help (can be wiki pages to navigate offline)<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Download''': [http://mirrors.davidhorat.com/moodle/MoodleIDE-latest.zip MoodleIDE-latest]<br /> <br /> === Moodle Multisite ===<br /> The objective of this project is to make Moodle able to manage several Moodle sites with just one source code. This will help administrators of several sites to centralize code upgrades and ''technical problems''.<br /> <br /> '''Ideas'''<br /> * First release<br /> ** config.php will be a proxy that executes the concrete config file depending on the current url.<br /> ** The concrete config file will be under the directory /config and will have an arbitrary name created by the user.<br /> * Future<br /> ** Create an XML file with all the pairs URL(n)-ConfigFile(1).<br /> ** Every time this file changes, it should be created the config.php file proxy.<br /> ** Develop a Web frontend to change this file, that can be just accessed by the super admin in every site.<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> ==Google Summer of Code 2006 Projects==<br /> #[[Student projects/Presets for Database module|Presets for Database module project notes]]<br /> #[[Student projects/Integrated bug tracker|Integrated bug tracker project notes]]<br /> #[[Student projects/AJAX course format|AJAX course format project notes]]<br /> #[[Student projects/Admin page cleanup|Admin page cleanup project notes]]<br /> #[[Student projects/Global search|Global search project notes]]<br /> <br /> <br /> ==Other Projects==<br /> <br /> #[[Student projects/ical|Calendar export to iCal]]<br /> <br /> [[Category:Developer]]<br /> [[Category:Project]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Projects_for_new_developers&diff=22960 2007-04-30T16:07:55Z

<p>David.horat: /* Moodle IDE */</p> <hr /> <div>This page currently lists the projects available Moodle's participation in the [http://code.google.com/soc Google Summer of Code 2007]. Each project here is a nice self-contained project suitable for student programmers to complete in three months or less, and must have an associate mentor who is a regular Moodle developer.<br /> <br /> Current status: Thank you to all the applicants! Google have now confirmed the final selections and we have ten projects with a mentor and a student. Here is a [http://moodle.org/mod/forum/discuss.php?d=69206 general discussion about the project]. Complete details are below.<br /> <br /> ==Google Summer of Code 2007 Timeline==<br /> * '''Starting now''': construct detailed specifications for each project (see below), with feedback from the mentor and the Moodle community. Some questions will be easy for your mentor to answer directly, but some you may have to post in the appropriate [http://moodle.org/course/view.php?id=5 Using Moodle] forums to gather and evaluate community feedback.<br /> * '''May 31''': Coding officially starts. At this time you should have a bug in the [http://tracker.moodle.org Moodle Tracker] that breaks your project down into subtasks. Please keep this tracker up to date with all your subsequent work - it's the best place for all asynchronous discussion with your mentor.<br /> * '''July 9-16''': Interim evaluation of code so far<br /> * '''August 20''': Coding should be completed <br /> <br /> <br /> ==Google Summer of Code 2007 Projects==<br /> <br /> The following projects are in no particular order!<br /> <br /> ===Developing new question types for the quiz===<br /> <br /> The quiz has a plug-in architecture for question types. We currently have implementations of most of the basic question types, it would be nice to have implementations of some more interesting types, perhaps using the YUI JavaScript library to do some interesting interactions (but with an accessible fall-back). Which question types could be left up to the student, but some suggestions are:<br /> <br /> * Drag and drop versions of ordering and matching question types.<br /> * Place a marker or draw a line on an image question types.<br /> * Drag the missing words into the sentence/onto an image question type.<br /> <br /> Another way to find question types to implement would be to review other systems and make sure Moodle supports all the question types that other systems support.<br /> <br /> I envisage that some of these question types would be incorporated into the standard Moodle install, but others would just be put in the contrib area. Part of the project could also be improving the plugin API. There are some minor know issues with it that make it harder that it needs to be to install new question types from contrib.<br /> <br /> '''Mentor:''' Tim Hunt<br /> <br /> '''Student:''' Adriane Boyd<br /> <br /> '''Full Specification:''' [[Student projects/New question types|New question types]]<br /> <br /> <br /> ===Enterprise-level improvements===<br /> <br /> Here are a few things you could do to help Moodle run in a heavy environment (either big Moodles or many multiple Moodles).<br /> <br /> * Adapt all the DB installation and upgrade scripts to run from the command line, so fully scripted installations are possible without using the web interface.<br /> <br /> * Develop a profiling system for developers to use when testing their code. Aim to spot and fix performance bottlenecks in Moodle with good reports and suggestions about what developers could do.<br /> <br /> '''Mentor:''' Penny Leach<br /> <br /> '''Student:''' Dilan Anuruddha Karanachcharighe<br /> <br /> '''Full Specification:''' [[Student projects/Enterprise-level improvements|Enterprise-level improvements]]<br /> <br /> <br /> ===Chat revamp===<br /> <br /> mod/chat needs a bit of an overhaul. Possible interesting approaches:<br /> <br /> * Simplify chatd and rewrite as a proper forking daemon. Great process control and networking project, and properly a good case for a bit of AJAX.<br /> * Integrate Moodle with a Jabber backend, plus frontend glue. <br /> ** On the backend, we need to consider authentication, chatroom creation, and logging. <br /> ** On the frontend, ensuring that we can get Jabber clients started reliably on the end-user's machine, and integrate a preexisting web-based Jabber client for Jabber-impaired users.<br /> ** Installation matter: a clear install HowTo for the Jabber + Moodle.<br /> <br /> '''Mentor:''' [[User:Geoff Cant|Geoff Cant]], Martin Langhoff<br /> <br /> '''Student:''' Thotage Piyasena<br /> <br /> '''Full Specification:''' [[Student projects/Chat revamp|Chat revamp]]<br /> <br /> <br /> ===Messaging improvements===<br /> <br /> The Moodle messaging system in Moodle is a bit clunky and could use improvements to make it slicker and more efficient as a tool for messaging people within the Moodle environment.<br /> <br /> Functionality improvements:<br /> * Add a messaging API class to the core of Moodle which all modules will start using for sending messages (currently they all format their own emails).<br /> * Add output plugins to messaging so that users can choose exactly how to route their messages, especially when they aren't online at the time. Initially the two plugins would be &quot;browser&quot; and &quot;email&quot;, but later there could be a jabber plugin, an IRC plugin etc)<br /> <br /> Gui improvements:<br /> * Improve the main message GUI using AJAX (Moodle includes the YUI library so you'd need to use that)<br /> * Improve the messaging window to allow chats among three or more other people at once.<br /> * GUI for the output plugins to allow users to set rules about each plugin independently, and also to select from incoming messages by type, by user or by moodle module.<br /> * Improve the methods to search messages and find discussions from the past.<br /> * Improve administrator auditing of message logs, including filtering etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luis Filipe Romão Rodrigues<br /> <br /> '''Full Specification:''' [[Student projects/Messaging improvements|Messaging improvements]]<br /> <br /> <br /> <br /> ===Automated grading for Computer Programming Assignments===<br /> <br /> The project here is to develop two things<br /> <br /> #A Moodle assignment plugin to handle the GUI and higher-level processes involved in submitting and grading a programming assignment<br /> #An interface to an external 3rd party program (preferably an established, active open source project) to handle the actual analysis and grading of the source code. It should have plugins to handle arbitrary languages.<br /> <br /> '''Mentor:''' [[User:Nicolas Connault]]<br /> <br /> '''Student:''' Arkaitz Garro<br /> <br /> '''Full Specification:''' [[Student projects/Automated grading of programs|Automated grading of programs]]<br /> <br /> === User Management Improvements ===<br /> <br /> * Improve the User features in moodle to allow bulk-operations. <br /> ** Create an interface to do bulk operations on users (e.g. delete users, reset passwords etc) This could potentially use an AJAX implementation for multiple filtering/selection of required students for bulk operations.<br /> ** Overhall the CSV upload features to allow more flexibility (more options, features to auto-generate more fields such as usernames)<br /> * Enrolment<br /> ** Specify time of manual enrollments ([http://tracker.moodle.org/browse/MDL-8877 MDL-8877])<br /> * Notes<br /> ** Allow teachers to put notes for each student in every course, much requested feature ([http://tracker.moodle.org/browse/MDL-7077 MDL-7077])<br /> <br /> '''Mentor:''' Yu Zhang<br /> <br /> '''Student:''' Andrei Bautu<br /> <br /> '''Full Specification:''' [[Student projects/User Management Improvements|User Management Improvements]]<br /> <br /> <br /> <br /> === Email interface to Moodle ===<br /> <br /> The idea is to let people reply naturally to email they receive from Moodle to change settings or add further comments into forums etc. Moodle activities can then be accessed like a mailing list.<br /> <br /> * Add a setting so admins can specify if they want an email interface enabled. Without it, none of the following is active and Moodle functions just as it does today.<br /> * Improve the outgoing emails in Moodle to contain a unique and robust code in the headers and potentially also in the subject line (switchable by user setting) that encrypts information about the receiver, the activity instance and the specific data. For example, all the information to securely identify a forum post.<br /> * Write a PHP script designed to run from the commandline as part of an email filter, that accepts emails on standard input, parses them and then calls a function in the relevant module. For example forum_incoming_email() in mod/forum/lib.php.<br /> * Write function for forum module (at least) to parse the content of the email and add it as a post from the user. Other modules can be worked on if there's time ... resources could be sent back as attachments, quizzes could send questions and accept multiple choice answers, the course could send back a listing of activities with further codes for each one, etc.<br /> * Security is essential!<br /> <br /> '''Mentor:''' Martin Langhoff<br /> <br /> '''Student:''' Peter Boswood<br /> <br /> '''Full Specification:''' [[Student projects/Email interface|Email interface]]<br /> <br /> <br /> === Secure RSS feeds ===<br /> <br /> Currently RSS is less than useful because:<br /> * Either we can't publish private information to the outside world because it's too sensitive.<br /> * We open up sensitive information to the outside world<br /> <br /> We should add codes to make the RSS URLs practically impossible to guess, much the same way as Google Calendar does it.<br /> <br /> * Overhaul all the RSS feeds in Moodle to make use of a long hash-like string in the URL for identification (Forums, Data etc).<br /> * Store these codes in a new field per-user and per-course. <br /> * Add GUIs to let the user recreate their code to something else should they suspect a breach.<br /> * Add RSS to other areas of Moodle such as the participants &quot;last logins&quot; and the activity logs.<br /> * Explore/research other methods of opening up RSS in a safe way to the outside world.<br /> <br /> '''Mentor:''' Petr Škoda<br /> <br /> '''Student:''' Udit Sajjanhar<br /> <br /> '''Full Specification:''' [[Student projects/Secure RSS feeds|Secure RSS feeds]]<br /> <br /> <br /> <br /> === Social Networking features ===<br /> <br /> Explore the possibilities of social networking features by expanding the user profile page:<br /> <br /> * add user tags that describe interests etc, as links to &quot;interest pages&quot; eg constructivism<br /> * interest pages that contain information about all the people who share that interest, as well as blog entries that use that tag, google searches, other info using standard Moodle blocks etc<br /> * allow users to add other users as &quot;friends&quot;, which are displayed on their user profile pages<br /> * think about controls to prevent abuse of these features in a school environment.<br /> * allow users to specify an external RSS feed to their own external blog, parsing the feed insert entries (optionally selecting by tag) as internal blog entries for that user, adding new tags/permissions as specified, with links back to external entry etc.<br /> * if time, explore deeper integrations with Youtube, Flickr, MySpace, Facebook etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luiz Eduardo Laydner Cruz<br /> <br /> '''Full Specification:''' [[Student projects/Social Networking features|Social Networking features]]<br /> <br /> <br /> <br /> ===Moodle Voice===<br /> <br /> *Objective: Adapt Moodle interface to output the needed VoiceXML so you can navigate with your voice with a VoiceXML enabled browser, such as [http://www.opera.com/ Opera].<br /> *[[Development:Voice_Project|Project Proposal]]<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Student''': Mayank Jain<br /> <br /> '''Full Specification''': [[Development:Voice|Development:Voice]]<br /> <br /> <br /> ----<br /> <br /> ==Other open projects still looking for students==<br /> <br /> <br /> === Roles interface improvements ===<br /> <br /> Improve the roles editing interface by making it more dynamic and flexible. You can use the YUI library for ajax if you like, but there must be a good fall-back interface too. Some ideas include:<br /> <br /> * Improve the order of the capabilities and implement better grouping.<br /> * Make the groups of capabilities collapsible to make it easier to &quot;zoom in&quot; to a particular section.<br /> * Add floating tooltip help when you hover over any given capability.<br /> * Experiment with an (alternate) interface seeing the roles all side-by-side for easier comparison/editing.<br /> * Implement a roles backup and restore system to allow site administrators to distribute useful roles in the moodle comunity (rather than having to describe the permissions setup)<br /> * Analyse the problem carefully with feedback from the community for more ideas.<br /> <br /> <br /> <br /> ===Integration with bibliographic systems such as Wikindx===<br /> <br /> Managing references and citing them is an important behaviour in university education and research. Bibliographic facilities are quite complicated and go beyond the capabilities of Moodle built-in technology (e.g. the database activity). Integrating Moodle with open-source bibliographic software such as [http://wikindx.sourceforge.net/ Wikindx] could much facilitate this practice within Moodle.<br /> <br /> Design and construct an integration with Wikindx (or other open-source bibliographic tools, if appropriate).<br /> <br /> Teachers should be able to easily refer to wikindx bibliography items throughout a Moodle course, and be able to:<br /> <br /> * Generate correctly-formatted in-place references (using standard styles e.g. Harvard, APA) for the commonly-cited reference types (e.g. journal article, book chapter, book). It may be possible to delegate the formatting directly to wikindx (since it already performs functions like these) rather than implementing a whole new set of logic in the Moodle integration.<br /> ** Possibly, allow some kind of direct searching of a wikindx database from within Moodle, so as to make it easier to refer to items<br /> * Generate reading lists / bibliographies<br /> * Allow export of the above into common machine-readable formats such as Bibtex or RIS. (Wikindx can perform this so again it's a question of hooking into, or expanding, wikindx functionality.)<br /> <br /> See also [[Development:Wikindx]] and [http://moodle.org/mod/forum/discuss.php?d=23022 this forum discussion] too<br /> <br /> <br /> <br /> ===Implement CATs in Moodle===<br /> <br /> [http://www.amazon.com/Classroom-Assessment-Techniques-Handbook-Education/dp/1555425003/ This book] describes a number of assessment techniques that involve collaboration and group work, and therefore fit very well into Moodle's Social Constructivist philosophy. The book about using these techniques in the classroom, but at an conference I attended there was a talk by Jean Runyon and Thomas Gorecki from the College of Southern Maryland saying how well these techniques work online. <br /> <br /> Some of them just need a forum of something basic, but others would need to be done as a database module templates. Doing this would<br /> <br /> # Make Moodle an even better teaching tool.<br /> # Provide some good exemplars of how to do interesting things with database templates.<br /> # Possibly highlight limitations in the database template system, that would require improvements to the database module code to overcome.<br /> # One of the outcomes of this project could be some really good 'How to write a database template' tutorial, which would be very valuable to the community.<br /> <br /> This is my (Tim Hunt's) idea, but I would not be interested in mentoring it. It would need to be someone who knows all about the database module.<br /> <br /> <br /> <br /> === Blog Assignment Type ===<br /> <br /> '''What is it for?'''<br /> <br /> Blogs are inherently user owned and driven by definition, however teachers would like to have a way to use blogs as assignments in their courses, comment, grade, etc.<br /> <br /> A solution to this conundrum would be a new Assignment type that makes it possible for a student to easily submit the link one of their blogs to an assignment in a course, and have that blog entry privately graded and commented on by the instructor of that course. The blog entry itself remains public along with all of the student's other blogs. The tool would provide a time filter in the Assignment, so that the instructor could limit the blog entry posting dates that will be accepted (both to ensure 'fresh' entries and to keep the list of entries the student chooses short for frequent student bloggers).<br /> <br /> I suggest a blog assignment type that functions as follows:<br /> <br /> '''Teacher:'''<br /> Teacher creates a blog assignment, this puts a grade in the gradebook and provides an assignment link for students to see.<br /> <br /> The teacher can configure options to allow a blog entry posted in the last X days to be used for the assignment.<br /> <br /> '''Students:'''<br /> When students enter the assignment they see a drop down menu of all their current (blog entries posted in the last X days as chosen by the teacher) blog entries, and they choose one to satisfy the assignment.<br /> <br /> '''Assessment:'''<br /> The teacher goes in to the Assignment, views the blogs that are linked from the assignment, leaves comments (the comments only show up to the student when they view the blog assignment), and gives a grade.<br /> <br /> The blog entries themselves stay on the student's blog, only the grades, links, and comments go in the assignment (optionally the assignment scrapes the student's blog and loads the full text in to store for backup and restore).<br /> <br /> <br /> === Moodle IDE ===<br /> The objective of this project is to create a Moodle IDE based on Eclipse so that new developers can get to develop Moodle in less time.<br /> <br /> '''Ideas'''<br /> * First release: Eclipse + Plugins + Moodle splashscreen + CVS Configuration + Apache + MySQL + Moodle CVS code. All preconfigured and ready out of the box.<br /> * Future<br /> ** Every X time, it checks for new versions of Moodle and packs it.<br /> ** Checkstyle plugin alike fo follow Moodle Design Guidelines.<br /> ** Development help (can be wiki pages to navigate offline)<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> '''Download''': [http://mirrors.davidhorat.com/moodle/MoodleIDE-latest.zip MoodleIDE-latest]<br /> <br /> === Moodle Multisite ===<br /> The objective of this project is to make Moodle able to manage several Moodle sites with just one source code. This will help administrators of several sites to centralize code upgrades and ''technical problems''.<br /> <br /> '''Ideas'''<br /> * First release<br /> ** config.php will be a proxy that executes the concrete config file depending on the current url.<br /> ** The concrete config file will be under the directory /config and will have an arbitrary name created by the user.<br /> * Future<br /> ** Create an XML file with all the pairs URL(n)-ConfigFile(1).<br /> ** Every time this file changes, it should be created the config.php file proxy.<br /> ** Develop a Web frontend to change this file, that can be just accessed by the super admin in every site.<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> ==Google Summer of Code 2006 Projects==<br /> #[[Student projects/Presets for Database module|Presets for Database module project notes]]<br /> #[[Student projects/Integrated bug tracker|Integrated bug tracker project notes]]<br /> #[[Student projects/AJAX course format|AJAX course format project notes]]<br /> #[[Student projects/Admin page cleanup|Admin page cleanup project notes]]<br /> #[[Student projects/Global search|Global search project notes]]<br /> <br /> <br /> ==Other Projects==<br /> <br /> #[[Student projects/ical|Calendar export to iCal]]<br /> <br /> [[Category:Developer]]<br /> [[Category:Project]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Projects_for_new_developers&diff=22701 2007-04-24T18:51:01Z

<p>David.horat: /* Moodle Integrated Development Environment (Moodle IDE) */</p> <hr /> <div>This page currently lists the projects available Moodle's participation in the [http://code.google.com/soc Google Summer of Code 2007]. Each project here is a nice self-contained project suitable for student programmers to complete in three months or less, and must have an associate mentor who is a regular Moodle developer.<br /> <br /> Current status: Thank you to all the applicants! Google have now confirmed the final selections and we have ten projects with a mentor and a student. Here is a [http://moodle.org/mod/forum/discuss.php?d=69206 general discussion about the project]. Complete details are below.<br /> <br /> ==Google Summer of Code 2007 Timeline==<br /> * '''Starting now''': construct detailed specifications for each project (see below), with feedback from the mentor and the Moodle community. Some questions will be easy for your mentor to answer directly, but some you may have to post in the appropriate [http://moodle.org/course/view.php?id=5 Using Moodle] forums to gather and evaluate community feedback.<br /> * '''May 31''': Coding officially starts. At this time you should have a bug in the [http://tracker.moodle.org Moodle Tracker] that breaks your project down into subtasks. Please keep this tracker up to date with all your subsequent work - it's the best place for all asynchronous discussion with your mentor.<br /> * '''July 9-16''': Interim evaluation of code so far<br /> * '''August 20''': Coding should be completed <br /> <br /> <br /> ==Google Summer of Code 2007 Projects==<br /> <br /> The following projects are in no particular order!<br /> <br /> ===Developing new question types for the quiz===<br /> <br /> The quiz has a plug-in architecture for question types. We currently have implementations of most of the basic question types, it would be nice to have implementations of some more interesting types, perhaps using the YUI JavaScript library to do some interesting interactions (but with an accessible fall-back). Which question types could be left up to the student, but some suggestions are:<br /> <br /> * Drag and drop versions of ordering and matching question types.<br /> * Place a marker or draw a line on an image question types.<br /> * Drag the missing words into the sentence/onto an image question type.<br /> <br /> Another way to find question types to implement would be to review other systems and make sure Moodle supports all the question types that other systems support.<br /> <br /> I envisage that some of these question types would be incorporated into the standard Moodle install, but others would just be put in the contrib area. Part of the project could also be improving the plugin API. There are some minor know issues with it that make it harder that it needs to be to install new question types from contrib.<br /> <br /> '''Mentor:''' Tim Hunt<br /> <br /> '''Student:''' Adriane Boyd<br /> <br /> '''Full Specification:''' [[Student projects/New question types|New question types]]<br /> <br /> <br /> ===Enterprise-level improvements===<br /> <br /> Here are a few things you could do to help Moodle run in a heavy environment (either big Moodles or many multiple Moodles).<br /> <br /> * Adapt all the DB installation and upgrade scripts to run from the command line, so fully scripted installations are possible without using the web interface.<br /> <br /> * Develop a profiling system for developers to use when testing their code. Aim to spot and fix performance bottlenecks in Moodle with good reports and suggestions about what developers could do.<br /> <br /> '''Mentor:''' Penny Leach<br /> <br /> '''Student:''' Dilan Anuruddha Karanachcharighe<br /> <br /> '''Full Specification:''' [[Student projects/Enterprise-level improvements|Enterprise-level improvements]]<br /> <br /> <br /> ===Chat revamp===<br /> <br /> mod/chat needs a bit of an overhaul. Possible interesting approaches:<br /> <br /> * Simplify chatd and rewrite as a proper forking daemon. Great process control and networking project, and properly a good case for a bit of AJAX.<br /> * Integrate Moodle with a Jabber backend, plus frontend glue. <br /> ** On the backend, we need to consider authentication, chatroom creation, and logging. <br /> ** On the frontend, ensuring that we can get Jabber clients started reliably on the end-user's machine, and integrate a preexisting web-based Jabber client for Jabber-impaired users.<br /> ** Installation matter: a clear install HowTo for the Jabber + Moodle.<br /> <br /> '''Mentor:''' [[User:Geoff Cant|Geoff Cant]], Martin Langhoff<br /> <br /> '''Student:''' Thotage Piyasena<br /> <br /> '''Full Specification:''' [[Student projects/Chat revamp|Chat revamp]]<br /> <br /> <br /> ===Messaging improvements===<br /> <br /> The Moodle messaging system in Moodle is a bit clunky and could use improvements to make it slicker and more efficient as a tool for messaging people within the Moodle environment.<br /> <br /> Functionality improvements:<br /> * Add a messaging API class to the core of Moodle which all modules will start using for sending messages (currently they all format their own emails).<br /> * Add output plugins to messaging so that users can choose exactly how to route their messages, especially when they aren't online at the time. Initially the two plugins would be &quot;browser&quot; and &quot;email&quot;, but later there could be a jabber plugin, an IRC plugin etc)<br /> <br /> Gui improvements:<br /> * Improve the main message GUI using AJAX (Moodle includes the YUI library so you'd need to use that)<br /> * Improve the messaging window to allow chats among three or more other people at once.<br /> * GUI for the output plugins to allow users to set rules about each plugin independently, and also to select from incoming messages by type, by user or by moodle module.<br /> * Improve the methods to search messages and find discussions from the past.<br /> * Improve administrator auditing of message logs, including filtering etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luis Filipe Romão Rodrigues<br /> <br /> '''Full Specification:''' [[Student projects/Messaging improvements|Messaging improvements]]<br /> <br /> <br /> <br /> ===Automated grading for Computer Programming Assignments===<br /> <br /> The project here is to develop two things<br /> <br /> #A Moodle assignment plugin to handle the GUI and higher-level processes involved in submitting and grading a programming assignment<br /> #An interface to an external 3rd party program (preferably an established, active open source project) to handle the actual analysis and grading of the source code. It should have plugins to handle arbitrary languages.<br /> <br /> '''Mentor:''' [[User:Nicolas Connault]]<br /> <br /> '''Student:''' Arkaitz Garro<br /> <br /> '''Full Specification:''' [[Student projects/Automated grading of programs|Automated grading of programs]]<br /> <br /> === User Management Improvements ===<br /> <br /> * Improve the User features in moodle to allow bulk-operations. <br /> ** Create an interface to do bulk operations on users (e.g. delete users, reset passwords etc) This could potentially use an AJAX implementation for multiple filtering/selection of required students for bulk operations.<br /> ** Overhall the CSV upload features to allow more flexibility (more options, features to auto-generate more fields such as usernames)<br /> * Enrolment<br /> ** Specify time of manual enrollments ([http://tracker.moodle.org/browse/MDL-8877 MDL-8877])<br /> * Notes<br /> ** Allow teachers to put notes for each student in every course, much requested feature ([http://tracker.moodle.org/browse/MDL-7077 MDL-7077])<br /> <br /> '''Mentor:''' Yu Zhang<br /> <br /> '''Student:''' Andrei Bautu<br /> <br /> '''Full Specification:''' [[Student projects/User Management Improvements|User Management Improvements]]<br /> <br /> <br /> <br /> === Email interface to Moodle ===<br /> <br /> The idea is to let people reply naturally to email they receive from Moodle to change settings or add further comments into forums etc. Moodle activities can then be accessed like a mailing list.<br /> <br /> * Add a setting so admins can specify if they want an email interface enabled. Without it, none of the following is active and Moodle functions just as it does today.<br /> * Improve the outgoing emails in Moodle to contain a unique and robust code in the headers and potentially also in the subject line (switchable by user setting) that encrypts information about the receiver, the activity instance and the specific data. For example, all the information to securely identify a forum post.<br /> * Write a PHP script designed to run from the commandline as part of an email filter, that accepts emails on standard input, parses them and then calls a function in the relevant module. For example forum_incoming_email() in mod/forum/lib.php.<br /> * Write function for forum module (at least) to parse the content of the email and add it as a post from the user. Other modules can be worked on if there's time ... resources could be sent back as attachments, quizzes could send questions and accept multiple choice answers, the course could send back a listing of activities with further codes for each one, etc.<br /> * Security is essential!<br /> <br /> '''Mentor:''' Martin Langhoff<br /> <br /> '''Student:''' Peter Boswood<br /> <br /> '''Full Specification:''' [[Student projects/Email interface|Email interface]]<br /> <br /> <br /> === Secure RSS feeds ===<br /> <br /> Currently RSS is less than useful because:<br /> * Either we can't publish private information to the outside world because it's too sensitive.<br /> * We open up sensitive information to the outside world<br /> <br /> We should add codes to make the RSS URLs practically impossible to guess, much the same way as Google Calendar does it.<br /> <br /> * Overhaul all the RSS feeds in Moodle to make use of a long hash-like string in the URL for identification (Forums, Data etc).<br /> * Store these codes in a new field per-user and per-course. <br /> * Add GUIs to let the user recreate their code to something else should they suspect a breach.<br /> * Add RSS to other areas of Moodle such as the participants &quot;last logins&quot; and the activity logs.<br /> * Explore/research other methods of opening up RSS in a safe way to the outside world.<br /> <br /> '''Mentor:''' Petr Škoda<br /> <br /> '''Student:''' Udit Sajjanhar<br /> <br /> '''Full Specification:''' [[Student projects/Secure RSS feeds|Secure RSS feeds]]<br /> <br /> <br /> <br /> === Social Networking features ===<br /> <br /> Explore the possibilities of social networking features by expanding the user profile page:<br /> <br /> * add user tags that describe interests etc, as links to &quot;interest pages&quot; eg constructivism<br /> * interest pages that contain information about all the people who share that interest, as well as blog entries that use that tag, google searches, other info using standard Moodle blocks etc<br /> * allow users to add other users as &quot;friends&quot;, which are displayed on their user profile pages<br /> * think about controls to prevent abuse of these features in a school environment.<br /> * allow users to specify an external RSS feed to their own external blog, parsing the feed insert entries (optionally selecting by tag) as internal blog entries for that user, adding new tags/permissions as specified, with links back to external entry etc.<br /> * if time, explore deeper integrations with Youtube, Flickr, MySpace, Facebook etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luiz Eduardo Laydner Cruz<br /> <br /> '''Full Specification:''' [[Student projects/Social Networking features|Social Networking features]]<br /> <br /> <br /> <br /> ===Moodle Voice===<br /> <br /> *Objective: Adapt Moodle interface to output the needed VoiceXML so you can navigate with your voice with a VoiceXML enabled browser, such as [http://www.opera.com/ Opera].<br /> *[[Development:Voice_Project|Project Proposal]]<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Student''': Mayank Jain<br /> <br /> '''Full Specification''': [[Development:Voice|Development:Voice]]<br /> <br /> <br /> ----<br /> <br /> ==Other open projects still looking for students==<br /> <br /> <br /> === Roles interface improvements ===<br /> <br /> Improve the roles editing interface by making it more dynamic and flexible. You can use the YUI library for ajax if you like, but there must be a good fall-back interface too. Some ideas include:<br /> <br /> * Improve the order of the capabilities and implement better grouping.<br /> * Make the groups of capabilities collapsible to make it easier to &quot;zoom in&quot; to a particular section.<br /> * Add floating tooltip help when you hover over any given capability.<br /> * Experiment with an (alternate) interface seeing the roles all side-by-side for easier comparison/editing.<br /> * Implement a roles backup and restore system to allow site administrators to distribute useful roles in the moodle comunity (rather than having to describe the permissions setup)<br /> * Analyse the problem carefully with feedback from the community for more ideas.<br /> <br /> <br /> <br /> ===Integration with bibliographic systems such as Wikindx===<br /> <br /> Managing references and citing them is an important behaviour in university education and research. Bibliographic facilities are quite complicated and go beyond the capabilities of Moodle built-in technology (e.g. the database activity). Integrating Moodle with open-source bibliographic software such as [http://wikindx.sourceforge.net/ Wikindx] could much facilitate this practice within Moodle.<br /> <br /> Design and construct an integration with Wikindx (or other open-source bibliographic tools, if appropriate).<br /> <br /> Teachers should be able to easily refer to wikindx bibliography items throughout a Moodle course, and be able to:<br /> <br /> * Generate correctly-formatted in-place references (using standard styles e.g. Harvard, APA) for the commonly-cited reference types (e.g. journal article, book chapter, book). It may be possible to delegate the formatting directly to wikindx (since it already performs functions like these) rather than implementing a whole new set of logic in the Moodle integration.<br /> ** Possibly, allow some kind of direct searching of a wikindx database from within Moodle, so as to make it easier to refer to items<br /> * Generate reading lists / bibliographies<br /> * Allow export of the above into common machine-readable formats such as Bibtex or RIS. (Wikindx can perform this so again it's a question of hooking into, or expanding, wikindx functionality.)<br /> <br /> See also [[Development:Wikindx]] and [http://moodle.org/mod/forum/discuss.php?d=23022 this forum discussion] too<br /> <br /> <br /> <br /> ===Implement CATs in Moodle===<br /> <br /> [http://www.amazon.com/Classroom-Assessment-Techniques-Handbook-Education/dp/1555425003/ This book] describes a number of assessment techniques that involve collaboration and group work, and therefore fit very well into Moodle's Social Constructivist philosophy. The book about using these techniques in the classroom, but at an conference I attended there was a talk by Jean Runyon and Thomas Gorecki from the College of Southern Maryland saying how well these techniques work online. <br /> <br /> Some of them just need a forum of something basic, but others would need to be done as a database module templates. Doing this would<br /> <br /> # Make Moodle an even better teaching tool.<br /> # Provide some good exemplars of how to do interesting things with database templates.<br /> # Possibly highlight limitations in the database template system, that would require improvements to the database module code to overcome.<br /> # One of the outcomes of this project could be some really good 'How to write a database template' tutorial, which would be very valuable to the community.<br /> <br /> This is my (Tim Hunt's) idea, but I would not be interested in mentoring it. It would need to be someone who knows all about the database module.<br /> <br /> <br /> <br /> === Blog Assignment Type ===<br /> <br /> '''What is it for?'''<br /> <br /> Blogs are inherently user owned and driven by definition, however teachers would like to have a way to use blogs as assignments in their courses, comment, grade, etc.<br /> <br /> A solution to this conundrum would be a new Assignment type that makes it possible for a student to easily submit the link one of their blogs to an assignment in a course, and have that blog entry privately graded and commented on by the instructor of that course. The blog entry itself remains public along with all of the student's other blogs. The tool would provide a time filter in the Assignment, so that the instructor could limit the blog entry posting dates that will be accepted (both to ensure 'fresh' entries and to keep the list of entries the student chooses short for frequent student bloggers).<br /> <br /> I suggest a blog assignment type that functions as follows:<br /> <br /> '''Teacher:'''<br /> Teacher creates a blog assignment, this puts a grade in the gradebook and provides an assignment link for students to see.<br /> <br /> The teacher can configure options to allow a blog entry posted in the last X days to be used for the assignment.<br /> <br /> '''Students:'''<br /> When students enter the assignment they see a drop down menu of all their current (blog entries posted in the last X days as chosen by the teacher) blog entries, and they choose one to satisfy the assignment.<br /> <br /> '''Assessment:'''<br /> The teacher goes in to the Assignment, views the blogs that are linked from the assignment, leaves comments (the comments only show up to the student when they view the blog assignment), and gives a grade.<br /> <br /> The blog entries themselves stay on the student's blog, only the grades, links, and comments go in the assignment (optionally the assignment scrapes the student's blog and loads the full text in to store for backup and restore).<br /> <br /> <br /> === Moodle IDE ===<br /> The objective of this project is to create a Moodle IDE based on Eclipse so that new developers can get to develop Moodle in less time.<br /> <br /> '''Ideas'''<br /> * First release: Eclipse + Plugins + Moodle splashscreen + CVS Configuration + Apache + MySQL + Moodle CVS code. All preconfigured and ready out of the box.<br /> * Future<br /> ** Every X time, it checks for new versions of Moodle and packs it.<br /> ** Checkstyle plugin alike fo follow Moodle Design Guidelines.<br /> ** Development help (can be wiki pages to navigate offline)<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> === Moodle Multisite ===<br /> The objective of this project is to make Moodle able to manage several Moodle sites with just one source code. This will help administrators of several sites to centralize code upgrades and ''technical problems''.<br /> <br /> '''Ideas'''<br /> * First release<br /> ** config.php will be a proxy that executes the concrete config file depending on the current url.<br /> ** The concrete config file will be under the directory /config and will have an arbitrary name created by the user.<br /> * Future<br /> ** Create an XML file with all the pairs URL(n)-ConfigFile(1).<br /> ** Every time this file changes, it should be created the config.php file proxy.<br /> ** Develop a Web frontend to change this file, that can be just accessed by the super admin in every site.<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> ==Google Summer of Code 2006 Projects==<br /> #[[Student projects/Presets for Database module|Presets for Database module project notes]]<br /> #[[Student projects/Integrated bug tracker|Integrated bug tracker project notes]]<br /> #[[Student projects/AJAX course format|AJAX course format project notes]]<br /> #[[Student projects/Admin page cleanup|Admin page cleanup project notes]]<br /> #[[Student projects/Global search|Global search project notes]]<br /> <br /> <br /> ==Other Projects==<br /> <br /> #[[Student projects/ical|Calendar export to iCal]]<br /> <br /> [[Category:Developer]]<br /> [[Category:Project]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Projects_for_new_developers&diff=22700 2007-04-24T18:50:45Z

<p>David.horat: /* Moodle Integrated Development Environment (Moodle IDE) */</p> <hr /> <div>This page currently lists the projects available Moodle's participation in the [http://code.google.com/soc Google Summer of Code 2007]. Each project here is a nice self-contained project suitable for student programmers to complete in three months or less, and must have an associate mentor who is a regular Moodle developer.<br /> <br /> Current status: Thank you to all the applicants! Google have now confirmed the final selections and we have ten projects with a mentor and a student. Here is a [http://moodle.org/mod/forum/discuss.php?d=69206 general discussion about the project]. Complete details are below.<br /> <br /> ==Google Summer of Code 2007 Timeline==<br /> * '''Starting now''': construct detailed specifications for each project (see below), with feedback from the mentor and the Moodle community. Some questions will be easy for your mentor to answer directly, but some you may have to post in the appropriate [http://moodle.org/course/view.php?id=5 Using Moodle] forums to gather and evaluate community feedback.<br /> * '''May 31''': Coding officially starts. At this time you should have a bug in the [http://tracker.moodle.org Moodle Tracker] that breaks your project down into subtasks. Please keep this tracker up to date with all your subsequent work - it's the best place for all asynchronous discussion with your mentor.<br /> * '''July 9-16''': Interim evaluation of code so far<br /> * '''August 20''': Coding should be completed <br /> <br /> <br /> ==Google Summer of Code 2007 Projects==<br /> <br /> The following projects are in no particular order!<br /> <br /> ===Developing new question types for the quiz===<br /> <br /> The quiz has a plug-in architecture for question types. We currently have implementations of most of the basic question types, it would be nice to have implementations of some more interesting types, perhaps using the YUI JavaScript library to do some interesting interactions (but with an accessible fall-back). Which question types could be left up to the student, but some suggestions are:<br /> <br /> * Drag and drop versions of ordering and matching question types.<br /> * Place a marker or draw a line on an image question types.<br /> * Drag the missing words into the sentence/onto an image question type.<br /> <br /> Another way to find question types to implement would be to review other systems and make sure Moodle supports all the question types that other systems support.<br /> <br /> I envisage that some of these question types would be incorporated into the standard Moodle install, but others would just be put in the contrib area. Part of the project could also be improving the plugin API. There are some minor know issues with it that make it harder that it needs to be to install new question types from contrib.<br /> <br /> '''Mentor:''' Tim Hunt<br /> <br /> '''Student:''' Adriane Boyd<br /> <br /> '''Full Specification:''' [[Student projects/New question types|New question types]]<br /> <br /> <br /> ===Enterprise-level improvements===<br /> <br /> Here are a few things you could do to help Moodle run in a heavy environment (either big Moodles or many multiple Moodles).<br /> <br /> * Adapt all the DB installation and upgrade scripts to run from the command line, so fully scripted installations are possible without using the web interface.<br /> <br /> * Develop a profiling system for developers to use when testing their code. Aim to spot and fix performance bottlenecks in Moodle with good reports and suggestions about what developers could do.<br /> <br /> '''Mentor:''' Penny Leach<br /> <br /> '''Student:''' Dilan Anuruddha Karanachcharighe<br /> <br /> '''Full Specification:''' [[Student projects/Enterprise-level improvements|Enterprise-level improvements]]<br /> <br /> <br /> ===Chat revamp===<br /> <br /> mod/chat needs a bit of an overhaul. Possible interesting approaches:<br /> <br /> * Simplify chatd and rewrite as a proper forking daemon. Great process control and networking project, and properly a good case for a bit of AJAX.<br /> * Integrate Moodle with a Jabber backend, plus frontend glue. <br /> ** On the backend, we need to consider authentication, chatroom creation, and logging. <br /> ** On the frontend, ensuring that we can get Jabber clients started reliably on the end-user's machine, and integrate a preexisting web-based Jabber client for Jabber-impaired users.<br /> ** Installation matter: a clear install HowTo for the Jabber + Moodle.<br /> <br /> '''Mentor:''' [[User:Geoff Cant|Geoff Cant]], Martin Langhoff<br /> <br /> '''Student:''' Thotage Piyasena<br /> <br /> '''Full Specification:''' [[Student projects/Chat revamp|Chat revamp]]<br /> <br /> <br /> ===Messaging improvements===<br /> <br /> The Moodle messaging system in Moodle is a bit clunky and could use improvements to make it slicker and more efficient as a tool for messaging people within the Moodle environment.<br /> <br /> Functionality improvements:<br /> * Add a messaging API class to the core of Moodle which all modules will start using for sending messages (currently they all format their own emails).<br /> * Add output plugins to messaging so that users can choose exactly how to route their messages, especially when they aren't online at the time. Initially the two plugins would be &quot;browser&quot; and &quot;email&quot;, but later there could be a jabber plugin, an IRC plugin etc)<br /> <br /> Gui improvements:<br /> * Improve the main message GUI using AJAX (Moodle includes the YUI library so you'd need to use that)<br /> * Improve the messaging window to allow chats among three or more other people at once.<br /> * GUI for the output plugins to allow users to set rules about each plugin independently, and also to select from incoming messages by type, by user or by moodle module.<br /> * Improve the methods to search messages and find discussions from the past.<br /> * Improve administrator auditing of message logs, including filtering etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luis Filipe Romão Rodrigues<br /> <br /> '''Full Specification:''' [[Student projects/Messaging improvements|Messaging improvements]]<br /> <br /> <br /> <br /> ===Automated grading for Computer Programming Assignments===<br /> <br /> The project here is to develop two things<br /> <br /> #A Moodle assignment plugin to handle the GUI and higher-level processes involved in submitting and grading a programming assignment<br /> #An interface to an external 3rd party program (preferably an established, active open source project) to handle the actual analysis and grading of the source code. It should have plugins to handle arbitrary languages.<br /> <br /> '''Mentor:''' [[User:Nicolas Connault]]<br /> <br /> '''Student:''' Arkaitz Garro<br /> <br /> '''Full Specification:''' [[Student projects/Automated grading of programs|Automated grading of programs]]<br /> <br /> === User Management Improvements ===<br /> <br /> * Improve the User features in moodle to allow bulk-operations. <br /> ** Create an interface to do bulk operations on users (e.g. delete users, reset passwords etc) This could potentially use an AJAX implementation for multiple filtering/selection of required students for bulk operations.<br /> ** Overhall the CSV upload features to allow more flexibility (more options, features to auto-generate more fields such as usernames)<br /> * Enrolment<br /> ** Specify time of manual enrollments ([http://tracker.moodle.org/browse/MDL-8877 MDL-8877])<br /> * Notes<br /> ** Allow teachers to put notes for each student in every course, much requested feature ([http://tracker.moodle.org/browse/MDL-7077 MDL-7077])<br /> <br /> '''Mentor:''' Yu Zhang<br /> <br /> '''Student:''' Andrei Bautu<br /> <br /> '''Full Specification:''' [[Student projects/User Management Improvements|User Management Improvements]]<br /> <br /> <br /> <br /> === Email interface to Moodle ===<br /> <br /> The idea is to let people reply naturally to email they receive from Moodle to change settings or add further comments into forums etc. Moodle activities can then be accessed like a mailing list.<br /> <br /> * Add a setting so admins can specify if they want an email interface enabled. Without it, none of the following is active and Moodle functions just as it does today.<br /> * Improve the outgoing emails in Moodle to contain a unique and robust code in the headers and potentially also in the subject line (switchable by user setting) that encrypts information about the receiver, the activity instance and the specific data. For example, all the information to securely identify a forum post.<br /> * Write a PHP script designed to run from the commandline as part of an email filter, that accepts emails on standard input, parses them and then calls a function in the relevant module. For example forum_incoming_email() in mod/forum/lib.php.<br /> * Write function for forum module (at least) to parse the content of the email and add it as a post from the user. Other modules can be worked on if there's time ... resources could be sent back as attachments, quizzes could send questions and accept multiple choice answers, the course could send back a listing of activities with further codes for each one, etc.<br /> * Security is essential!<br /> <br /> '''Mentor:''' Martin Langhoff<br /> <br /> '''Student:''' Peter Boswood<br /> <br /> '''Full Specification:''' [[Student projects/Email interface|Email interface]]<br /> <br /> <br /> === Secure RSS feeds ===<br /> <br /> Currently RSS is less than useful because:<br /> * Either we can't publish private information to the outside world because it's too sensitive.<br /> * We open up sensitive information to the outside world<br /> <br /> We should add codes to make the RSS URLs practically impossible to guess, much the same way as Google Calendar does it.<br /> <br /> * Overhaul all the RSS feeds in Moodle to make use of a long hash-like string in the URL for identification (Forums, Data etc).<br /> * Store these codes in a new field per-user and per-course. <br /> * Add GUIs to let the user recreate their code to something else should they suspect a breach.<br /> * Add RSS to other areas of Moodle such as the participants &quot;last logins&quot; and the activity logs.<br /> * Explore/research other methods of opening up RSS in a safe way to the outside world.<br /> <br /> '''Mentor:''' Petr Škoda<br /> <br /> '''Student:''' Udit Sajjanhar<br /> <br /> '''Full Specification:''' [[Student projects/Secure RSS feeds|Secure RSS feeds]]<br /> <br /> <br /> <br /> === Social Networking features ===<br /> <br /> Explore the possibilities of social networking features by expanding the user profile page:<br /> <br /> * add user tags that describe interests etc, as links to &quot;interest pages&quot; eg constructivism<br /> * interest pages that contain information about all the people who share that interest, as well as blog entries that use that tag, google searches, other info using standard Moodle blocks etc<br /> * allow users to add other users as &quot;friends&quot;, which are displayed on their user profile pages<br /> * think about controls to prevent abuse of these features in a school environment.<br /> * allow users to specify an external RSS feed to their own external blog, parsing the feed insert entries (optionally selecting by tag) as internal blog entries for that user, adding new tags/permissions as specified, with links back to external entry etc.<br /> * if time, explore deeper integrations with Youtube, Flickr, MySpace, Facebook etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luiz Eduardo Laydner Cruz<br /> <br /> '''Full Specification:''' [[Student projects/Social Networking features|Social Networking features]]<br /> <br /> <br /> <br /> ===Moodle Voice===<br /> <br /> *Objective: Adapt Moodle interface to output the needed VoiceXML so you can navigate with your voice with a VoiceXML enabled browser, such as [http://www.opera.com/ Opera].<br /> *[[Development:Voice_Project|Project Proposal]]<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Student''': Mayank Jain<br /> <br /> '''Full Specification''': [[Development:Voice|Development:Voice]]<br /> <br /> <br /> ----<br /> <br /> ==Other open projects still looking for students==<br /> <br /> <br /> === Roles interface improvements ===<br /> <br /> Improve the roles editing interface by making it more dynamic and flexible. You can use the YUI library for ajax if you like, but there must be a good fall-back interface too. Some ideas include:<br /> <br /> * Improve the order of the capabilities and implement better grouping.<br /> * Make the groups of capabilities collapsible to make it easier to &quot;zoom in&quot; to a particular section.<br /> * Add floating tooltip help when you hover over any given capability.<br /> * Experiment with an (alternate) interface seeing the roles all side-by-side for easier comparison/editing.<br /> * Implement a roles backup and restore system to allow site administrators to distribute useful roles in the moodle comunity (rather than having to describe the permissions setup)<br /> * Analyse the problem carefully with feedback from the community for more ideas.<br /> <br /> <br /> <br /> ===Integration with bibliographic systems such as Wikindx===<br /> <br /> Managing references and citing them is an important behaviour in university education and research. Bibliographic facilities are quite complicated and go beyond the capabilities of Moodle built-in technology (e.g. the database activity). Integrating Moodle with open-source bibliographic software such as [http://wikindx.sourceforge.net/ Wikindx] could much facilitate this practice within Moodle.<br /> <br /> Design and construct an integration with Wikindx (or other open-source bibliographic tools, if appropriate).<br /> <br /> Teachers should be able to easily refer to wikindx bibliography items throughout a Moodle course, and be able to:<br /> <br /> * Generate correctly-formatted in-place references (using standard styles e.g. Harvard, APA) for the commonly-cited reference types (e.g. journal article, book chapter, book). It may be possible to delegate the formatting directly to wikindx (since it already performs functions like these) rather than implementing a whole new set of logic in the Moodle integration.<br /> ** Possibly, allow some kind of direct searching of a wikindx database from within Moodle, so as to make it easier to refer to items<br /> * Generate reading lists / bibliographies<br /> * Allow export of the above into common machine-readable formats such as Bibtex or RIS. (Wikindx can perform this so again it's a question of hooking into, or expanding, wikindx functionality.)<br /> <br /> See also [[Development:Wikindx]] and [http://moodle.org/mod/forum/discuss.php?d=23022 this forum discussion] too<br /> <br /> <br /> <br /> ===Implement CATs in Moodle===<br /> <br /> [http://www.amazon.com/Classroom-Assessment-Techniques-Handbook-Education/dp/1555425003/ This book] describes a number of assessment techniques that involve collaboration and group work, and therefore fit very well into Moodle's Social Constructivist philosophy. The book about using these techniques in the classroom, but at an conference I attended there was a talk by Jean Runyon and Thomas Gorecki from the College of Southern Maryland saying how well these techniques work online. <br /> <br /> Some of them just need a forum of something basic, but others would need to be done as a database module templates. Doing this would<br /> <br /> # Make Moodle an even better teaching tool.<br /> # Provide some good exemplars of how to do interesting things with database templates.<br /> # Possibly highlight limitations in the database template system, that would require improvements to the database module code to overcome.<br /> # One of the outcomes of this project could be some really good 'How to write a database template' tutorial, which would be very valuable to the community.<br /> <br /> This is my (Tim Hunt's) idea, but I would not be interested in mentoring it. It would need to be someone who knows all about the database module.<br /> <br /> <br /> <br /> === Blog Assignment Type ===<br /> <br /> '''What is it for?'''<br /> <br /> Blogs are inherently user owned and driven by definition, however teachers would like to have a way to use blogs as assignments in their courses, comment, grade, etc.<br /> <br /> A solution to this conundrum would be a new Assignment type that makes it possible for a student to easily submit the link one of their blogs to an assignment in a course, and have that blog entry privately graded and commented on by the instructor of that course. The blog entry itself remains public along with all of the student's other blogs. The tool would provide a time filter in the Assignment, so that the instructor could limit the blog entry posting dates that will be accepted (both to ensure 'fresh' entries and to keep the list of entries the student chooses short for frequent student bloggers).<br /> <br /> I suggest a blog assignment type that functions as follows:<br /> <br /> '''Teacher:'''<br /> Teacher creates a blog assignment, this puts a grade in the gradebook and provides an assignment link for students to see.<br /> <br /> The teacher can configure options to allow a blog entry posted in the last X days to be used for the assignment.<br /> <br /> '''Students:'''<br /> When students enter the assignment they see a drop down menu of all their current (blog entries posted in the last X days as chosen by the teacher) blog entries, and they choose one to satisfy the assignment.<br /> <br /> '''Assessment:'''<br /> The teacher goes in to the Assignment, views the blogs that are linked from the assignment, leaves comments (the comments only show up to the student when they view the blog assignment), and gives a grade.<br /> <br /> The blog entries themselves stay on the student's blog, only the grades, links, and comments go in the assignment (optionally the assignment scrapes the student's blog and loads the full text in to store for backup and restore).<br /> <br /> <br /> === Moodle Integrated Development Environment (Moodle IDE) ===<br /> The objective of this project is to create a Moodle IDE based on Eclipse so that new developers can get to develop Moodle in less time.<br /> <br /> '''Ideas'''<br /> * First release: Eclipse + Plugins + Moodle splashscreen + CVS Configuration + Apache + MySQL + Moodle CVS code. All preconfigured and ready out of the box.<br /> * Future<br /> ** Every X time, it checks for new versions of Moodle and packs it.<br /> ** Checkstyle plugin alike fo follow Moodle Design Guidelines.<br /> ** Development help (can be wiki pages to navigate offline)<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> === Moodle Multisite ===<br /> The objective of this project is to make Moodle able to manage several Moodle sites with just one source code. This will help administrators of several sites to centralize code upgrades and ''technical problems''.<br /> <br /> '''Ideas'''<br /> * First release<br /> ** config.php will be a proxy that executes the concrete config file depending on the current url.<br /> ** The concrete config file will be under the directory /config and will have an arbitrary name created by the user.<br /> * Future<br /> ** Create an XML file with all the pairs URL(n)-ConfigFile(1).<br /> ** Every time this file changes, it should be created the config.php file proxy.<br /> ** Develop a Web frontend to change this file, that can be just accessed by the super admin in every site.<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> ==Google Summer of Code 2006 Projects==<br /> #[[Student projects/Presets for Database module|Presets for Database module project notes]]<br /> #[[Student projects/Integrated bug tracker|Integrated bug tracker project notes]]<br /> #[[Student projects/AJAX course format|AJAX course format project notes]]<br /> #[[Student projects/Admin page cleanup|Admin page cleanup project notes]]<br /> #[[Student projects/Global search|Global search project notes]]<br /> <br /> <br /> ==Other Projects==<br /> <br /> #[[Student projects/ical|Calendar export to iCal]]<br /> <br /> [[Category:Developer]]<br /> [[Category:Project]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Projects_for_new_developers&diff=22699 2007-04-24T18:49:23Z

<p>David.horat: /* Other open projects still looking for students */</p> <hr /> <div>This page currently lists the projects available Moodle's participation in the [http://code.google.com/soc Google Summer of Code 2007]. Each project here is a nice self-contained project suitable for student programmers to complete in three months or less, and must have an associate mentor who is a regular Moodle developer.<br /> <br /> Current status: Thank you to all the applicants! Google have now confirmed the final selections and we have ten projects with a mentor and a student. Here is a [http://moodle.org/mod/forum/discuss.php?d=69206 general discussion about the project]. Complete details are below.<br /> <br /> ==Google Summer of Code 2007 Timeline==<br /> * '''Starting now''': construct detailed specifications for each project (see below), with feedback from the mentor and the Moodle community. Some questions will be easy for your mentor to answer directly, but some you may have to post in the appropriate [http://moodle.org/course/view.php?id=5 Using Moodle] forums to gather and evaluate community feedback.<br /> * '''May 31''': Coding officially starts. At this time you should have a bug in the [http://tracker.moodle.org Moodle Tracker] that breaks your project down into subtasks. Please keep this tracker up to date with all your subsequent work - it's the best place for all asynchronous discussion with your mentor.<br /> * '''July 9-16''': Interim evaluation of code so far<br /> * '''August 20''': Coding should be completed <br /> <br /> <br /> ==Google Summer of Code 2007 Projects==<br /> <br /> The following projects are in no particular order!<br /> <br /> ===Developing new question types for the quiz===<br /> <br /> The quiz has a plug-in architecture for question types. We currently have implementations of most of the basic question types, it would be nice to have implementations of some more interesting types, perhaps using the YUI JavaScript library to do some interesting interactions (but with an accessible fall-back). Which question types could be left up to the student, but some suggestions are:<br /> <br /> * Drag and drop versions of ordering and matching question types.<br /> * Place a marker or draw a line on an image question types.<br /> * Drag the missing words into the sentence/onto an image question type.<br /> <br /> Another way to find question types to implement would be to review other systems and make sure Moodle supports all the question types that other systems support.<br /> <br /> I envisage that some of these question types would be incorporated into the standard Moodle install, but others would just be put in the contrib area. Part of the project could also be improving the plugin API. There are some minor know issues with it that make it harder that it needs to be to install new question types from contrib.<br /> <br /> '''Mentor:''' Tim Hunt<br /> <br /> '''Student:''' Adriane Boyd<br /> <br /> '''Full Specification:''' [[Student projects/New question types|New question types]]<br /> <br /> <br /> ===Enterprise-level improvements===<br /> <br /> Here are a few things you could do to help Moodle run in a heavy environment (either big Moodles or many multiple Moodles).<br /> <br /> * Adapt all the DB installation and upgrade scripts to run from the command line, so fully scripted installations are possible without using the web interface.<br /> <br /> * Develop a profiling system for developers to use when testing their code. Aim to spot and fix performance bottlenecks in Moodle with good reports and suggestions about what developers could do.<br /> <br /> '''Mentor:''' Penny Leach<br /> <br /> '''Student:''' Dilan Anuruddha Karanachcharighe<br /> <br /> '''Full Specification:''' [[Student projects/Enterprise-level improvements|Enterprise-level improvements]]<br /> <br /> <br /> ===Chat revamp===<br /> <br /> mod/chat needs a bit of an overhaul. Possible interesting approaches:<br /> <br /> * Simplify chatd and rewrite as a proper forking daemon. Great process control and networking project, and properly a good case for a bit of AJAX.<br /> * Integrate Moodle with a Jabber backend, plus frontend glue. <br /> ** On the backend, we need to consider authentication, chatroom creation, and logging. <br /> ** On the frontend, ensuring that we can get Jabber clients started reliably on the end-user's machine, and integrate a preexisting web-based Jabber client for Jabber-impaired users.<br /> ** Installation matter: a clear install HowTo for the Jabber + Moodle.<br /> <br /> '''Mentor:''' [[User:Geoff Cant|Geoff Cant]], Martin Langhoff<br /> <br /> '''Student:''' Thotage Piyasena<br /> <br /> '''Full Specification:''' [[Student projects/Chat revamp|Chat revamp]]<br /> <br /> <br /> ===Messaging improvements===<br /> <br /> The Moodle messaging system in Moodle is a bit clunky and could use improvements to make it slicker and more efficient as a tool for messaging people within the Moodle environment.<br /> <br /> Functionality improvements:<br /> * Add a messaging API class to the core of Moodle which all modules will start using for sending messages (currently they all format their own emails).<br /> * Add output plugins to messaging so that users can choose exactly how to route their messages, especially when they aren't online at the time. Initially the two plugins would be &quot;browser&quot; and &quot;email&quot;, but later there could be a jabber plugin, an IRC plugin etc)<br /> <br /> Gui improvements:<br /> * Improve the main message GUI using AJAX (Moodle includes the YUI library so you'd need to use that)<br /> * Improve the messaging window to allow chats among three or more other people at once.<br /> * GUI for the output plugins to allow users to set rules about each plugin independently, and also to select from incoming messages by type, by user or by moodle module.<br /> * Improve the methods to search messages and find discussions from the past.<br /> * Improve administrator auditing of message logs, including filtering etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luis Filipe Romão Rodrigues<br /> <br /> '''Full Specification:''' [[Student projects/Messaging improvements|Messaging improvements]]<br /> <br /> <br /> <br /> ===Automated grading for Computer Programming Assignments===<br /> <br /> The project here is to develop two things<br /> <br /> #A Moodle assignment plugin to handle the GUI and higher-level processes involved in submitting and grading a programming assignment<br /> #An interface to an external 3rd party program (preferably an established, active open source project) to handle the actual analysis and grading of the source code. It should have plugins to handle arbitrary languages.<br /> <br /> '''Mentor:''' [[User:Nicolas Connault]]<br /> <br /> '''Student:''' Arkaitz Garro<br /> <br /> '''Full Specification:''' [[Student projects/Automated grading of programs|Automated grading of programs]]<br /> <br /> === User Management Improvements ===<br /> <br /> * Improve the User features in moodle to allow bulk-operations. <br /> ** Create an interface to do bulk operations on users (e.g. delete users, reset passwords etc) This could potentially use an AJAX implementation for multiple filtering/selection of required students for bulk operations.<br /> ** Overhall the CSV upload features to allow more flexibility (more options, features to auto-generate more fields such as usernames)<br /> * Enrolment<br /> ** Specify time of manual enrollments ([http://tracker.moodle.org/browse/MDL-8877 MDL-8877])<br /> * Notes<br /> ** Allow teachers to put notes for each student in every course, much requested feature ([http://tracker.moodle.org/browse/MDL-7077 MDL-7077])<br /> <br /> '''Mentor:''' Yu Zhang<br /> <br /> '''Student:''' Andrei Bautu<br /> <br /> '''Full Specification:''' [[Student projects/User Management Improvements|User Management Improvements]]<br /> <br /> <br /> <br /> === Email interface to Moodle ===<br /> <br /> The idea is to let people reply naturally to email they receive from Moodle to change settings or add further comments into forums etc. Moodle activities can then be accessed like a mailing list.<br /> <br /> * Add a setting so admins can specify if they want an email interface enabled. Without it, none of the following is active and Moodle functions just as it does today.<br /> * Improve the outgoing emails in Moodle to contain a unique and robust code in the headers and potentially also in the subject line (switchable by user setting) that encrypts information about the receiver, the activity instance and the specific data. For example, all the information to securely identify a forum post.<br /> * Write a PHP script designed to run from the commandline as part of an email filter, that accepts emails on standard input, parses them and then calls a function in the relevant module. For example forum_incoming_email() in mod/forum/lib.php.<br /> * Write function for forum module (at least) to parse the content of the email and add it as a post from the user. Other modules can be worked on if there's time ... resources could be sent back as attachments, quizzes could send questions and accept multiple choice answers, the course could send back a listing of activities with further codes for each one, etc.<br /> * Security is essential!<br /> <br /> '''Mentor:''' Martin Langhoff<br /> <br /> '''Student:''' Peter Boswood<br /> <br /> '''Full Specification:''' [[Student projects/Email interface|Email interface]]<br /> <br /> <br /> === Secure RSS feeds ===<br /> <br /> Currently RSS is less than useful because:<br /> * Either we can't publish private information to the outside world because it's too sensitive.<br /> * We open up sensitive information to the outside world<br /> <br /> We should add codes to make the RSS URLs practically impossible to guess, much the same way as Google Calendar does it.<br /> <br /> * Overhaul all the RSS feeds in Moodle to make use of a long hash-like string in the URL for identification (Forums, Data etc).<br /> * Store these codes in a new field per-user and per-course. <br /> * Add GUIs to let the user recreate their code to something else should they suspect a breach.<br /> * Add RSS to other areas of Moodle such as the participants &quot;last logins&quot; and the activity logs.<br /> * Explore/research other methods of opening up RSS in a safe way to the outside world.<br /> <br /> '''Mentor:''' Petr Škoda<br /> <br /> '''Student:''' Udit Sajjanhar<br /> <br /> '''Full Specification:''' [[Student projects/Secure RSS feeds|Secure RSS feeds]]<br /> <br /> <br /> <br /> === Social Networking features ===<br /> <br /> Explore the possibilities of social networking features by expanding the user profile page:<br /> <br /> * add user tags that describe interests etc, as links to &quot;interest pages&quot; eg constructivism<br /> * interest pages that contain information about all the people who share that interest, as well as blog entries that use that tag, google searches, other info using standard Moodle blocks etc<br /> * allow users to add other users as &quot;friends&quot;, which are displayed on their user profile pages<br /> * think about controls to prevent abuse of these features in a school environment.<br /> * allow users to specify an external RSS feed to their own external blog, parsing the feed insert entries (optionally selecting by tag) as internal blog entries for that user, adding new tags/permissions as specified, with links back to external entry etc.<br /> * if time, explore deeper integrations with Youtube, Flickr, MySpace, Facebook etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luiz Eduardo Laydner Cruz<br /> <br /> '''Full Specification:''' [[Student projects/Social Networking features|Social Networking features]]<br /> <br /> <br /> <br /> ===Moodle Voice===<br /> <br /> *Objective: Adapt Moodle interface to output the needed VoiceXML so you can navigate with your voice with a VoiceXML enabled browser, such as [http://www.opera.com/ Opera].<br /> *[[Development:Voice_Project|Project Proposal]]<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Student''': Mayank Jain<br /> <br /> '''Full Specification''': [[Development:Voice|Development:Voice]]<br /> <br /> <br /> ----<br /> <br /> ==Other open projects still looking for students==<br /> <br /> <br /> === Roles interface improvements ===<br /> <br /> Improve the roles editing interface by making it more dynamic and flexible. You can use the YUI library for ajax if you like, but there must be a good fall-back interface too. Some ideas include:<br /> <br /> * Improve the order of the capabilities and implement better grouping.<br /> * Make the groups of capabilities collapsible to make it easier to &quot;zoom in&quot; to a particular section.<br /> * Add floating tooltip help when you hover over any given capability.<br /> * Experiment with an (alternate) interface seeing the roles all side-by-side for easier comparison/editing.<br /> * Implement a roles backup and restore system to allow site administrators to distribute useful roles in the moodle comunity (rather than having to describe the permissions setup)<br /> * Analyse the problem carefully with feedback from the community for more ideas.<br /> <br /> <br /> <br /> ===Integration with bibliographic systems such as Wikindx===<br /> <br /> Managing references and citing them is an important behaviour in university education and research. Bibliographic facilities are quite complicated and go beyond the capabilities of Moodle built-in technology (e.g. the database activity). Integrating Moodle with open-source bibliographic software such as [http://wikindx.sourceforge.net/ Wikindx] could much facilitate this practice within Moodle.<br /> <br /> Design and construct an integration with Wikindx (or other open-source bibliographic tools, if appropriate).<br /> <br /> Teachers should be able to easily refer to wikindx bibliography items throughout a Moodle course, and be able to:<br /> <br /> * Generate correctly-formatted in-place references (using standard styles e.g. Harvard, APA) for the commonly-cited reference types (e.g. journal article, book chapter, book). It may be possible to delegate the formatting directly to wikindx (since it already performs functions like these) rather than implementing a whole new set of logic in the Moodle integration.<br /> ** Possibly, allow some kind of direct searching of a wikindx database from within Moodle, so as to make it easier to refer to items<br /> * Generate reading lists / bibliographies<br /> * Allow export of the above into common machine-readable formats such as Bibtex or RIS. (Wikindx can perform this so again it's a question of hooking into, or expanding, wikindx functionality.)<br /> <br /> See also [[Development:Wikindx]] and [http://moodle.org/mod/forum/discuss.php?d=23022 this forum discussion] too<br /> <br /> <br /> <br /> ===Implement CATs in Moodle===<br /> <br /> [http://www.amazon.com/Classroom-Assessment-Techniques-Handbook-Education/dp/1555425003/ This book] describes a number of assessment techniques that involve collaboration and group work, and therefore fit very well into Moodle's Social Constructivist philosophy. The book about using these techniques in the classroom, but at an conference I attended there was a talk by Jean Runyon and Thomas Gorecki from the College of Southern Maryland saying how well these techniques work online. <br /> <br /> Some of them just need a forum of something basic, but others would need to be done as a database module templates. Doing this would<br /> <br /> # Make Moodle an even better teaching tool.<br /> # Provide some good exemplars of how to do interesting things with database templates.<br /> # Possibly highlight limitations in the database template system, that would require improvements to the database module code to overcome.<br /> # One of the outcomes of this project could be some really good 'How to write a database template' tutorial, which would be very valuable to the community.<br /> <br /> This is my (Tim Hunt's) idea, but I would not be interested in mentoring it. It would need to be someone who knows all about the database module.<br /> <br /> <br /> <br /> === Blog Assignment Type ===<br /> <br /> '''What is it for?'''<br /> <br /> Blogs are inherently user owned and driven by definition, however teachers would like to have a way to use blogs as assignments in their courses, comment, grade, etc.<br /> <br /> A solution to this conundrum would be a new Assignment type that makes it possible for a student to easily submit the link one of their blogs to an assignment in a course, and have that blog entry privately graded and commented on by the instructor of that course. The blog entry itself remains public along with all of the student's other blogs. The tool would provide a time filter in the Assignment, so that the instructor could limit the blog entry posting dates that will be accepted (both to ensure 'fresh' entries and to keep the list of entries the student chooses short for frequent student bloggers).<br /> <br /> I suggest a blog assignment type that functions as follows:<br /> <br /> '''Teacher:'''<br /> Teacher creates a blog assignment, this puts a grade in the gradebook and provides an assignment link for students to see.<br /> <br /> The teacher can configure options to allow a blog entry posted in the last X days to be used for the assignment.<br /> <br /> '''Students:'''<br /> When students enter the assignment they see a drop down menu of all their current (blog entries posted in the last X days as chosen by the teacher) blog entries, and they choose one to satisfy the assignment.<br /> <br /> '''Assessment:'''<br /> The teacher goes in to the Assignment, views the blogs that are linked from the assignment, leaves comments (the comments only show up to the student when they view the blog assignment), and gives a grade.<br /> <br /> The blog entries themselves stay on the student's blog, only the grades, links, and comments go in the assignment (optionally the assignment scrapes the student's blog and loads the full text in to store for backup and restore).<br /> <br /> <br /> === Moodle Integrated Development Environment (Moodle IDE) ===<br /> The objective of this project is to create a Moodle IDE based on Eclipse so that new developers can get to develop Moodle in less time.<br /> <br /> '''Ideas'''<br /> * First release: Eclipse + Plugins + Moodle splashscreen + CVS Configuration + Apache + MySQL + Moodle CVS code. All preconfigured and ready out of the box.<br /> * Future<br /> ** Every X time, it checks for new versions of Moodle and packs it.<br /> ** Checkstyle plugin alike fo follow Moodle Design Guidelines.<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> <br /> === Moodle Multisite ===<br /> The objective of this project is to make Moodle able to manage several Moodle sites with just one source code. This will help administrators of several sites to centralize code upgrades and ''technical problems''.<br /> <br /> '''Ideas'''<br /> * First release<br /> ** config.php will be a proxy that executes the concrete config file depending on the current url.<br /> ** The concrete config file will be under the directory /config and will have an arbitrary name created by the user.<br /> * Future<br /> ** Create an XML file with all the pairs URL(n)-ConfigFile(1).<br /> ** Every time this file changes, it should be created the config.php file proxy.<br /> ** Develop a Web frontend to change this file, that can be just accessed by the super admin in every site.<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> ==Google Summer of Code 2006 Projects==<br /> #[[Student projects/Presets for Database module|Presets for Database module project notes]]<br /> #[[Student projects/Integrated bug tracker|Integrated bug tracker project notes]]<br /> #[[Student projects/AJAX course format|AJAX course format project notes]]<br /> #[[Student projects/Admin page cleanup|Admin page cleanup project notes]]<br /> #[[Student projects/Global search|Global search project notes]]<br /> <br /> <br /> ==Other Projects==<br /> <br /> #[[Student projects/ical|Calendar export to iCal]]<br /> <br /> [[Category:Developer]]<br /> [[Category:Project]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Projects_for_new_developers&diff=22408 2007-04-16T08:40:35Z

<p>David.horat: /* Moodle Voice */</p> <hr /> <div>This page currently lists the projects available Moodle's participation in the [http://code.google.com/soc Google Summer of Code 2007]. Each project here is a nice self-contained project suitable for student programmers to complete in three months or less, and must have an associate mentor who is a regular Moodle developer.<br /> <br /> Current status: Thank you to all the applicants! Google have now confirmed the final selections and we have ten projects with a mentor and a student. Here is a [http://moodle.org/mod/forum/discuss.php?d=69206 general discussion about the project]. Complete details are below.<br /> <br /> ==Google Summer of Code 2007 Timeline==<br /> * '''Starting now''': construct detailed specifications for each project (see below), with feedback from the mentor and the Moodle community. Some questions will be easy for your mentor to answer directly, but some you may have to post in the appropriate [http://moodle.org/course/view.php?id=5 Using Moodle] forums to gather and evaluate community feedback.<br /> * '''May 31''': Coding officially starts. At this time you should have a bug in the [http://tracker.moodle.org Moodle Tracker] that breaks your project down into subtasks. Please keep this tracker up to date with all your subsequent work - it's the best place for all asynchronous discussion with your mentor.<br /> * '''July 9-16''': Interim evaluation of code so far<br /> * '''August 20''': Coding should be completed <br /> <br /> <br /> ==Google Summer of Code 2007 Projects==<br /> <br /> The following projects are in no particular order!<br /> <br /> ===Developing new question types for the quiz===<br /> <br /> The quiz has a plug-in architecture for question types. We currently have implementations of most of the basic question types, it would be nice to have implementations of some more interesting types, perhaps using the YUI JavaScript library to do some interesting interactions (but with an accessible fall-back). Which question types could be left up to the student, but some suggestions are:<br /> <br /> * Drag and drop versions of ordering and matching question types.<br /> * Place a marker or draw a line on an image question types.<br /> * Drag the missing words into the sentence/onto an image question type.<br /> <br /> Another way to find question types to implement would be to review other systems and make sure Moodle supports all the question types that other systems support.<br /> <br /> I envisage that some of these question types would be incorporated into the standard Moodle install, but others would just be put in the contrib area. Part of the project could also be improving the plugin API. There are some minor know issues with it that make it harder that it needs to be to install new question types from contrib.<br /> <br /> '''Mentor:''' Tim Hunt<br /> <br /> '''Student:''' Adriane Boyd<br /> <br /> '''Full Specification:''' [[Student projects/New question types|New question types]]<br /> <br /> <br /> ===Enterprise-level improvements===<br /> <br /> Here are a few things you could do to help Moodle run in a heavy environment (either big Moodles or many multiple Moodles).<br /> <br /> * Adapt all the DB installation and upgrade scripts to run from the command line, so fully scripted installations are possible without using the web interface.<br /> <br /> * Develop a profiling system for developers to use when testing their code. Aim to spot and fix performance bottlenecks in Moodle with good reports and suggestions about what developers could do.<br /> <br /> '''Mentor:''' Penny Leach<br /> <br /> '''Student:''' Dilan Anuruddha Karanachcharighe<br /> <br /> '''Full Specification:''' [[Student projects/Enterprise-level improvements|Enterprise-level improvements]]<br /> <br /> <br /> ===Chat revamp===<br /> <br /> mod/chat needs a bit of an overhaul. Possible interesting approaches:<br /> <br /> * Simplify chatd and rewrite as a proper forking daemon. Great process control and networking project, and properly a good case for a bit of AJAX.<br /> * Integrate Moodle with a Jabber backend, plus frontend glue. <br /> ** On the backend, we need to consider authentication, chatroom creation, and logging. <br /> ** On the frontend, ensuring that we can get Jabber clients started reliably on the end-user's machine, and integrate a preexisting web-based Jabber client for Jabber-impaired users.<br /> ** Installation matter: a clear install HowTo for the Jabber + Moodle.<br /> <br /> '''Mentor:''' [[User:Geoff Cant|Geoff Cant]], Martin Langhoff<br /> <br /> '''Student:''' Thotage Piyasena<br /> <br /> '''Full Specification:''' [[Student projects/Chat revamp|Chat revamp]]<br /> <br /> <br /> ===Messaging improvements===<br /> <br /> The Moodle messaging system in Moodle is a bit clunky and could use improvements to make it slicker and more efficient as a tool for messaging people within the Moodle environment.<br /> <br /> Functionality improvements:<br /> * Add a messaging API class to the core of Moodle which all modules will start using for sending messages (currently they all format their own emails).<br /> * Add output plugins to messaging so that users can choose exactly how to route their messages, especially when they aren't online at the time. Initially the two plugins would be &quot;browser&quot; and &quot;email&quot;, but later there could be a jabber plugin, an IRC plugin etc)<br /> <br /> Gui improvements:<br /> * Improve the main message GUI using AJAX (Moodle includes the YUI library so you'd need to use that)<br /> * Improve the messaging window to allow chats among three or more other people at once.<br /> * GUI for the output plugins to allow users to set rules about each plugin independently, and also to select from incoming messages by type, by user or by moodle module.<br /> * Improve the methods to search messages and find discussions from the past.<br /> * Improve administrator auditing of message logs, including filtering etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luis Filipe Romão Rodrigues<br /> <br /> '''Full Specification:''' [[Student projects/Messaging improvements|Messaging improvements]]<br /> <br /> <br /> <br /> ===Automated grading for Computer Programming Assignments===<br /> <br /> The project here is to develop two things<br /> <br /> #A Moodle assignment plugin to handle the GUI and higher-level processes involved in submitting and grading a programming assignment<br /> #An interface to an external 3rd party program (preferably an established, active open source project) to handle the actual analysis and grading of the source code. It should have plugins to handle arbitrary languages.<br /> <br /> '''Mentor:''' [[User:Nicolas Connault]]<br /> <br /> '''Student:''' Arkaitz Garro<br /> <br /> '''Full Specification:''' [[Student projects/Automated grading of programs|Automated grading of programs]]<br /> <br /> === User Management Improvements ===<br /> <br /> * Improve the User features in moodle to allow bulk-operations. <br /> ** Create an interface to do bulk operations on users (e.g. delete users, reset passwords etc) This could potentially use an AJAX implementation for multiple filtering/selection of required students for bulk operations.<br /> ** Overhall the CSV upload features to allow more flexibility (more options, features to auto-generate more fields such as usernames)<br /> * Enrolment<br /> ** Specify time of manual enrollments ([http://tracker.moodle.org/browse/MDL-8877 MDL-8877])<br /> * Notes<br /> ** Allow teachers to put notes for each student in every course, much requested feature ([http://tracker.moodle.org/browse/MDL-7077 MDL-7077])<br /> <br /> '''Mentor:''' Yu Zhang<br /> <br /> '''Student:''' Andrei Bautu<br /> <br /> '''Full Specification:''' [[Student projects/User Management Improvements|User Management Improvements]]<br /> <br /> <br /> <br /> === Email interface to Moodle ===<br /> <br /> The idea is to let people reply naturally to email they receive from Moodle to change settings or add further comments into forums etc. Moodle activities can then be accessed like a mailing list.<br /> <br /> * Add a setting so admins can specify if they want an email interface enabled. Without it, none of the following is active and Moodle functions just as it does today.<br /> * Improve the outgoing emails in Moodle to contain a unique and robust code in the headers and potentially also in the subject line (switchable by user setting) that encrypts information about the receiver, the activity instance and the specific data. For example, all the information to securely identify a forum post.<br /> * Write a PHP script designed to run from the commandline as part of an email filter, that accepts emails on standard input, parses them and then calls a function in the relevant module. For example forum_incoming_email() in mod/forum/lib.php.<br /> * Write function for forum module (at least) to parse the content of the email and add it as a post from the user. Other modules can be worked on if there's time ... resources could be sent back as attachments, quizzes could send questions and accept multiple choice answers, the course could send back a listing of activities with further codes for each one, etc.<br /> * Security is essential!<br /> <br /> '''Mentor:''' Martin Langhoff<br /> <br /> '''Student:''' Peter Boswood<br /> <br /> '''Full Specification:''' [[Student projects/Email interface|Email interface]]<br /> <br /> <br /> === Secure RSS feeds ===<br /> <br /> Currently RSS is less than useful because:<br /> * Either we can't publish private information to the outside world because it's too sensitive.<br /> * We open up sensitive information to the outside world<br /> <br /> We should add codes to make the RSS URLs practically impossible to guess, much the same way as Google Calendar does it.<br /> <br /> * Overhaul all the RSS feeds in Moodle to make use of a long hash-like string in the URL for identification (Forums, Data etc).<br /> * Store these codes in a new field per-user and per-course. <br /> * Add GUIs to let the user recreate their code to something else should they suspect a breach.<br /> * Add RSS to other areas of Moodle such as the participants &quot;last logins&quot; and the activity logs.<br /> * Explore/research other methods of opening up RSS in a safe way to the outside world.<br /> <br /> '''Mentor:''' Petr Škoda<br /> <br /> '''Student:''' Udit Sajjanhar<br /> <br /> '''Full Specification:''' [[Student projects/Secure RSS feeds|Secure RSS feeds]]<br /> <br /> <br /> <br /> === Social Networking features ===<br /> <br /> Explore the possibilities of social networking features by expanding the user profile page:<br /> <br /> * add user tags that describe interests etc, as links to &quot;interest pages&quot; eg constructivism<br /> * interest pages that contain information about all the people who share that interest, as well as blog entries that use that tag, google searches, other info using standard Moodle blocks etc<br /> * allow users to add other users as &quot;friends&quot;, which are displayed on their user profile pages<br /> * think about controls to prevent abuse of these features in a school environment.<br /> * allow users to specify an external RSS feed to their own external blog, parsing the feed insert entries (optionally selecting by tag) as internal blog entries for that user, adding new tags/permissions as specified, with links back to external entry etc.<br /> * if time, explore deeper integrations with Youtube, Flickr, MySpace, Facebook etc.<br /> <br /> '''Mentor:''' Martin Dougiamas<br /> <br /> '''Student:''' Luiz Eduardo Laydner Cruz<br /> <br /> '''Full Specification:''' [[Student projects/Social Networking features|Social Networking features]]<br /> <br /> <br /> <br /> ===Moodle Voice===<br /> <br /> *Objective: Adapt Moodle interface to output the needed VoiceXML so you can navigate with your voice with a VoiceXML enabled browser, such as [http://www.opera.com/ Opera].<br /> *[[Development:Voice_Project|Project Proposal]]<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> '''Student''': Mayank Jain<br /> <br /> '''Full Specification''': [[Development:Voice|Development:Voice]]<br /> <br /> <br /> ----<br /> <br /> ==Other open projects still looking for students==<br /> <br /> <br /> === Roles interface improvements ===<br /> <br /> Improve the roles editing interface by making it more dynamic and flexible. You can use the YUI library for ajax if you like, but there must be a good fall-back interface too. Some ideas include:<br /> <br /> * Improve the order of the capabilities and implement better grouping.<br /> * Make the groups of capabilities collapsible to make it easier to &quot;zoom in&quot; to a particular section.<br /> * Add floating tooltip help when you hover over any given capability.<br /> * Experiment with an (alternate) interface seeing the roles all side-by-side for easier comparison/editing.<br /> * Implement a roles backup and restore system to allow site administrators to distribute useful roles in the moodle comunity (rather than having to describe the permissions setup)<br /> * Analyse the problem carefully with feedback from the community for more ideas.<br /> <br /> <br /> <br /> ===Integration with bibliographic systems such as Wikindx===<br /> <br /> Managing references and citing them is an important behaviour in university education and research. Bibliographic facilities are quite complicated and go beyond the capabilities of Moodle built-in technology (e.g. the database activity). Integrating Moodle with open-source bibliographic software such as [http://wikindx.sourceforge.net/ Wikindx] could much facilitate this practice within Moodle.<br /> <br /> Design and construct an integration with Wikindx (or other open-source bibliographic tools, if appropriate).<br /> <br /> Teachers should be able to easily refer to wikindx bibliography items throughout a Moodle course, and be able to:<br /> <br /> * Generate correctly-formatted in-place references (using standard styles e.g. Harvard, APA) for the commonly-cited reference types (e.g. journal article, book chapter, book). It may be possible to delegate the formatting directly to wikindx (since it already performs functions like these) rather than implementing a whole new set of logic in the Moodle integration.<br /> ** Possibly, allow some kind of direct searching of a wikindx database from within Moodle, so as to make it easier to refer to items<br /> * Generate reading lists / bibliographies<br /> * Allow export of the above into common machine-readable formats such as Bibtex or RIS. (Wikindx can perform this so again it's a question of hooking into, or expanding, wikindx functionality.)<br /> <br /> See also [[Development:Wikindx]] and [http://moodle.org/mod/forum/discuss.php?d=23022 this forum discussion] too<br /> <br /> <br /> <br /> ===Implement CATs in Moodle===<br /> <br /> [http://www.amazon.com/Classroom-Assessment-Techniques-Handbook-Education/dp/1555425003/ This book] describes a number of assessment techniques that involve collaboration and group work, and therefore fit very well into Moodle's Social Constructivist philosophy. The book about using these techniques in the classroom, but at an conference I attended there was a talk by Jean Runyon and Thomas Gorecki from the College of Southern Maryland saying how well these techniques work online. <br /> <br /> Some of them just need a forum of something basic, but others would need to be done as a database module templates. Doing this would<br /> <br /> # Make Moodle an even better teaching tool.<br /> # Provide some good exemplars of how to do interesting things with database templates.<br /> # Possibly highlight limitations in the database template system, that would require improvements to the database module code to overcome.<br /> # One of the outcomes of this project could be some really good 'How to write a database template' tutorial, which would be very valuable to the community.<br /> <br /> This is my (Tim Hunt's) idea, but I would not be interested in mentoring it. It would need to be someone who knows all about the database module.<br /> <br /> <br /> <br /> === Blog Assignment Type ===<br /> <br /> '''What is it for?'''<br /> <br /> Blogs are inherently user owned and driven by definition, however teachers would like to have a way to use blogs as assignments in their courses, comment, grade, etc.<br /> <br /> A solution to this conundrum would be a new Assignment type that makes it possible for a student to easily submit the link one of their blogs to an assignment in a course, and have that blog entry privately graded and commented on by the instructor of that course. The blog entry itself remains public along with all of the student's other blogs. The tool would provide a time filter in the Assignment, so that the instructor could limit the blog entry posting dates that will be accepted (both to ensure 'fresh' entries and to keep the list of entries the student chooses short for frequent student bloggers).<br /> <br /> I suggest a blog assignment type that functions as follows:<br /> <br /> '''Teacher:'''<br /> Teacher creates a blog assignment, this puts a grade in the gradebook and provides an assignment link for students to see.<br /> <br /> The teacher can configure options to allow a blog entry posted in the last X days to be used for the assignment.<br /> <br /> '''Students:'''<br /> When students enter the assignment they see a drop down menu of all their current (blog entries posted in the last X days as chosen by the teacher) blog entries, and they choose one to satisfy the assignment.<br /> <br /> '''Assessment:'''<br /> The teacher goes in to the Assignment, views the blogs that are linked from the assignment, leaves comments (the comments only show up to the student when they view the blog assignment), and gives a grade.<br /> <br /> The blog entries themselves stay on the student's blog, only the grades, links, and comments go in the assignment (optionally the assignment scrapes the student's blog and loads the full text in to store for backup and restore).<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> ==Google Summer of Code 2006 Projects==<br /> #[[Student projects/Presets for Database module|Presets for Database module project notes]]<br /> #[[Student projects/Integrated bug tracker|Integrated bug tracker project notes]]<br /> #[[Student projects/AJAX course format|AJAX course format project notes]]<br /> #[[Student projects/Admin page cleanup|Admin page cleanup project notes]]<br /> #[[Student projects/Global search|Global search project notes]]<br /> <br /> <br /> ==Other Projects==<br /> <br /> #[[Student projects/ical|Calendar export to iCal]]<br /> <br /> [[Category:Developer]]<br /> [[Category:Project]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_ToDo&diff=22301 2007-04-12T09:39:20Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> Here we will put the tasks we need to complete. If no tasks assigned, then keep on with the timeplan.<br /> <br /> == ToDo ==<br /> * Create a user and password for moodle.org, docs.moodle.org and tracker.moodle.org. Better use the same user and password for all.<br /> * Select tools to be used.<br /> ** David Horat: I recommend using Eclipse + PHPEclipse plugin. See: [[Setting_up_Eclipse_for_Moodle_development]]<br /> * Begin to study Moodle development documentation: [[Development:Voice_Moodle]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_Timeplan&diff=22287 2007-04-12T09:03:33Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> == Project ==<br /> * 14th May - 20th May: Analysis (1 week)<br /> ** Extract requirements: study Moodle output and code to choose what to make voice enabled<br /> *** Identify navigation(links) to be voice enabled.<br /> *** Identify forms to be voice enabled.<br /> *** Identify Text to be converted to speech to convey information through speech.<br /> ** Begin project webpage, documentation and logs<br /> * 21th May - 3rd June: Design (2 weeks)<br /> ** Make an Architectural Design<br /> ** Make an Implementation Proposal<br /> * 4th June - 5th August: Implementation (9 weeks)<br /> ** Implement Navigational Links (5 weeks)<br /> *** Learn implementation intricacies VoiceXML(1 week)<br /> *** Subtasks (to be decided in analysis phase)(4 week)<br /> ** Implement forms to be voice enabled(4 weeks)<br /> * 6th August - 17th August: Documentation (2 weeks)<br /> ** Beta testing<br /> ** Developer documentation<br /> ** Moodle administrator documentation<br /> ** Future roadmap and design plans<br /> * 18th August - 31th August: Revision and Documentation<br /> <br /> == Mentor ==<br /> * 16th April - 27th April: teach the student about the community (about 30 mins per day)<br /> * 28th April - 13th May: create basic documentation about the project and tools to be used (about 1 hour per day)<br /> * 14th May - 17th August (about 1-2 hours per day)<br /> ** Solve student questions<br /> ** Improve project design<br /> ** Code quality assurance<br /> ** Commit to Moodle CVS<br /> ** Beta testing<br /> * 20th August - 31th August: Marketing (1-2 hours per day)<br /> <br /> == Student ==<br /> * 16th April - 27th April: learn about the community (about 30 mins per day)<br /> * 14th May - 17th August: the project itself (about 7-8 hours per day)<br /> * 20th August - 31th August: revision and marketing (2 hours per day)<br /> <br /> == Others ==<br /> * [http://code.google.com/support/bin/answer.py?answer=60325&amp;topic=10729 Google Summer of Code 2007 Timeplan]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_ToDo&diff=22285 2007-04-12T08:58:15Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> Here we will put the tasks we need to complete. If no tasks assigned, then keep on with the timeplan.<br /> <br /> == ToDo ==</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_Timeplan&diff=22284 2007-04-12T08:52:23Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> == Project ==<br /> * 14th May - 20th May: Analysis (1 week)<br /> ** Extract requirements: study Moodle output and code to choose what to make voice enabled<br /> *** Identify navigation(links) to be voice enabled.<br /> *** Identify forms to be voice enabled.<br /> *** Identify Text to be converted to speech to convey information through speech.<br /> ** Begin project webpage, documentation and logs<br /> * 21th May - 3rd June: Design (2 weeks)<br /> ** Make an Architectural Design<br /> ** Make an Implementation Proposal<br /> * 4th June - 5th August: Implementation (9 weeks)<br /> ** Implement Navigational Links (5 weeks)<br /> *** Learn implementation intricacies VoiceXML(1 week)<br /> *** Subtasks (to be decided in analysis phase)(4 week)<br /> ** Implement forms to be voice enabled(4 weeks)<br /> * 6th August - 17th August: Documentation (2 weeks)<br /> ** Beta testing<br /> ** Developer documentation<br /> ** Moodle administrator documentation<br /> ** Future roadmap and design plans<br /> * 18th August - 31th August: Revision and Documentation<br /> <br /> == Mentor ==<br /> * 16th April - 27th April: teach the student about the community (about 30 mins per day)<br /> * 28th April - 13th May: create basic documentation about the project and tools to be used (about 1 hour per day)<br /> * 14th May - 17th August (about 1-2 hours per day)<br /> ** Solve student questions<br /> ** Improve project design<br /> ** Code quality assurance<br /> ** Commit to Moodle CVS<br /> ** Beta testing<br /> * 20th August - 31th August: Marketing (1-2 hours per day)<br /> <br /> == Student ==<br /> * 16th April - 27th April: learn about the community (about 30 mins per day)<br /> * 14th May - 17th August: the project itself (about 7-8 hours per day)<br /> * 20th August - 31th August: revision and marketing (2 hours per day)</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_Timeplan&diff=22283 2007-04-12T08:51:41Z

<p>David.horat: </p> <hr /> <div>== Project ==<br /> * 14th May - 20th May: Analysis (1 week)<br /> ** Extract requirements: study Moodle output and code to choose what to make voice enabled<br /> *** Identify navigation(links) to be voice enabled.<br /> *** Identify forms to be voice enabled.<br /> *** Identify Text to be converted to speech to convey information through speech.<br /> ** Begin project webpage, documentation and logs<br /> * 21th May - 3rd June: Design (2 weeks)<br /> ** Make an Architectural Design<br /> ** Make an Implementation Proposal<br /> * 4th June - 5th August: Implementation (9 weeks)<br /> ** Implement Navigational Links (5 weeks)<br /> *** Learn implementation intricacies VoiceXML(1 week)<br /> *** Subtasks (to be decided in analysis phase)(4 week)<br /> ** Implement forms to be voice enabled(4 weeks)<br /> * 6th August - 17th August: Documentation (2 weeks)<br /> ** Beta testing<br /> ** Developer documentation<br /> ** Moodle administrator documentation<br /> ** Future roadmap and design plans<br /> * 18th August - 31th August: Revision and Documentation<br /> <br /> == Mentor ==<br /> * 16th April - 27th April: teach the student about the community (about 30 mins per day)<br /> * 28th April - 13th May: create basic documentation about the project and tools to be used (about 1 hour per day)<br /> * 14th May - 17th August (about 1-2 hours per day)<br /> ** Solve student questions<br /> ** Improve project design<br /> ** Code quality assurance<br /> ** Commit to Moodle CVS<br /> ** Beta testing<br /> * 20th August - 31th August: Marketing (1-2 hours per day)<br /> <br /> == Student ==<br /> * 16th April - 27th April: learn about the community (about 30 mins per day)<br /> * 14th May - 17th August: the project itself (about 7-8 hours per day)<br /> * 20th August - 31th August: revision and marketing (2 hours per day)</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_GsocFormslibExercise&diff=22093 2007-04-04T10:08:40Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Deadline''': 8th of April, 2007<br /> ### Estimated time to finish: 4 hours<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Does it need to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ### What aspects will be taken into account?<br /> #### Well documented<br /> #### Easy to understand<br /> #### It should work<br /> #### It should not have security breaches or if it has, they should to be documented<br /> ### What Coding Guidelines should I use?<br /> #### Output HTML code should be [http://www.w3.org/TR/xhtml1/ XHTML 1.0 Strict].<br /> #### Use 4 spaces for indentation (tabs are forbidden). Use correctly nested indentations.<br /> #### Document every function: parameters, return value and functionality.<br /> #### Specify the system you used for development and testing: Operating System, browser and IDE.<br /> #### We suggest using [http://www.phpdoc.org/ PHP Doc] documentation format, the standard Moodle documentation format, although it is not required at this stage. It is very similar to Javadoc.<br /> #### We suggest using [https://docs.moodle.org/en/Coding Moodle Coding Guidelines], although it is not required at this stage.<br /> ## '''Finally''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them. Please, '''do not''' include temporal files!</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_GsocFormslibExercise&diff=22092 2007-04-04T09:53:45Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Deadline''': 8th of April, 2007<br /> ### Estimated time to finish: 4 hours<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Does it need to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ### What aspects will be taken into account?<br /> #### Well documented<br /> #### Easy to understand<br /> #### It should work<br /> #### It should not have security breaches or if it has, they should to be documented<br /> ### What Coding Guidelines should I use?<br /> #### Output HTML code should be [http://www.w3.org/TR/xhtml1/ XHTML 1.0 Strict]<br /> #### Use 4 spaces for indentation (tabs are forbidden)<br /> #### Document every function: parameters, return value and functionality<br /> #### We suggest using [http://www.phpdoc.org/ PHP Doc] documentation format, the standard Moodle documentation format, although it is not required at this stage. It is very similar to Javadoc.<br /> #### We suggest using [https://docs.moodle.org/en/Coding Moodle Coding Guidelines], although it is not required at this stage<br /> ## '''Finally''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them. Please, '''do not''' include temporal files!</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_GsocFormslibExercise&diff=22091 2007-04-04T09:45:42Z

<p>David.horat: FAQ 7: Coding Guidelines added</p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Deadline''': 8th of April, 2007<br /> ### Estimated time to finish: 4 hours<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Does it need to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ### What aspects will be taken into account?<br /> #### Well documented<br /> #### Easy to understand<br /> #### It should work<br /> #### It should not have security breaches or if it has, they should to be documented<br /> ### What Coding Guidelines should I use?<br /> #### Output HTML code should be [http://www.w3.org/TR/xhtml1/ XHTML 1.0 Strict] or [http://www.w3.org/TR/1999/REC-html401-19991224/ HTML 4.01 Strict]<br /> #### Use 4 spaces for indentation (tabs are forbidden)<br /> #### We suggest using [http://www.phpdoc.org/ PHP Doc] documentation format, the standard Moodle document format, although it is not required at this stage<br /> #### We suggest using [https://docs.moodle.org/en/Coding Moodle Coding Guidelines], although it is not required at this stage<br /> ## '''Finally''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them. Please, '''do not''' include temporal files!</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Projects_for_new_developers&diff=22090 2007-04-04T08:40:20Z

<p>David.horat: </p> <hr /> <div>This page currently lists the projects available Moodle's participation in the [http://code.google.com/soc Google Summer of Code 2007]. Each project here is a nice self-contained project suitable for student programmers to complete in three months or less, and must have an associate mentor who is a regular Moodle developer.<br /> <br /> Current status: Applications to Google SOC are now over: we received 83 applications! The mentors are currently considering and voting on these and Google will announce the final students on April 12th.<br /> <br /> <br /> <br /> ==Google Summer of Code 2007 Projects==<br /> <br /> ===Projects with Mentors===<br /> <br /> The following projects are in no particular order!<br /> <br /> ====Developing new question types for the quiz====<br /> <br /> The quiz has a plug-in architecture for question types. We currently have implementations of most of the basic question types, it would be nice to have implementations of some more interesting types, perhaps using the YUI JavaScript library to do some interesting interactions (but with an accessible fall-back). Which question types could be left up to the student, but some suggestions are:<br /> <br /> * Drag and drop versions of ordering and matching question types.<br /> * Place a marker or draw a line on an image question types.<br /> * Drag the missing words into the sentence/onto an image question type.<br /> <br /> Another way to find question types to implement would be to review other systems and make sure Moodle supports all the question types that other systems support.<br /> <br /> I envisage that some of these question types would be incorporated into the standard Moodle install, but others would just be put in the contrib area. Part of the project could also be improving the plugin API. There are some minor know issues with it that make it harder that it needs to be to install new question types from contrib.<br /> <br /> '''Mentor:''' Tim Hunt<br /> <br /> <br /> <br /> ====Enterprise-level improvements====<br /> <br /> Here are a few things you could do to help Moodle run in a heavy environment (either big Moodles or many multiple Moodles).<br /> <br /> * Adapt all the DB installation and upgrade scripts to run from the command line, so fully scripted installations are possible without using the web interface.<br /> <br /> * Develop a profiling system for developers to use when testing their code. Aim to spot and fix performance bottlenecks in Moodle with good reports and suggestions about what developers could do.<br /> <br /> Mentor: Martin Langhoff or Penny Leach<br /> <br /> ====Chat revamp====<br /> <br /> mod/chat needs a bit of an overhaul. Possible interesting approaches:<br /> <br /> * Simplify chatd and rewrite as a proper forking daemon. Great process control and networking project, and properly a good case for a bit of AJAX.<br /> * Integrate Moodle with a Jabber backend, plus frontend glue. <br /> ** On the backend, we need to consider authentication, chatroom creation, and logging. <br /> ** On the frontend, ensuring that we can get Jabber clients started reliably on the end-user's machine, and integrate a preexisting web-based Jabber client for Jabber-impaired users.<br /> ** Installation matter: a clear install HowTo for the Jabber + Moodle.<br /> <br /> Mentors: Martin Langhoff, [[User:Geoff Cant|Geoff Cant]] (ejabberd)<br /> <br /> Notes from Geoff (who's a keen Erlang hacker):<br /> <br /> :ejabberd (http://ejabberd.jabber.ru/) is the worlds most scalable jabber server (tested to 600k concurrent connections :) and written in Erlang so I'm keen on it and able to hack on it.<br /> <br /> :ejabberd supports http bind (http://www.xmpp.org/extensions/xep-0124.html) which will allow the integration of a jabber client directly into moodle web pages. ejabberd also supports traditional GUI jabber clients.<br /> <br /> :We could hack ejabberd to authenticate against a moodle and probably create MUC/groupchats automatically based on moodle course information.<br /> <br /> :jwchat (http://jwchat.sourceforge.net) seems like it could provide the basis for a generic http jabber client for moodle. The chat revamp could be two projects - one PHP/HTML to integrate jwchat into moodle and an Erlang one to alter ejabberd to do SSO, auth, automatic roster creation and so on.<br /> <br /> ====Messaging improvements====<br /> <br /> The Moodle messaging system in Moodle is a bit clunky and could use improvements to make it slicker and more efficient as a tool for messaging people within the Moodle environment.<br /> <br /> Functionality improvements:<br /> * Add a messaging API class to the core of Moodle which all modules will start using for sending messages (currently they all format their own emails).<br /> * Add output plugins to messaging so that users can choose exactly how to route their messages, especially when they aren't online at the time. Initially the two plugins would be &quot;browser&quot; and &quot;email&quot;, but later there could be a jabber plugin, an IRC plugin etc)<br /> <br /> Gui improvements:<br /> * Improve the main message GUI using AJAX (Moodle includes the YUI library so you'd need to use that)<br /> * Improve the messaging window to allow chats among three or more other people at once.<br /> * GUI for the output plugins to allow users to set rules about each plugin independently, and also to select from incoming messages by type, by user or by moodle module.<br /> * Improve the methods to search messages and find discussions from the past.<br /> * Improve administrator auditing of message logs, including filtering etc.<br /> <br /> Mentors: Martin Dougiamas, Dan Poltawski (and others?)<br /> <br /> ====Automated grading for Computer Programming Assignments====<br /> <br /> From Arkaitz Garro &lt;arkaitz.garro@gmail.com&gt;:<br /> <br /> My name is Arkaitz Garro, and I'm actually studing computer science<br /> engineering at Basque Country University (Spain).<br /> <br /> As a part of my master thesis (graduating final work), I'm developing a plugin<br /> for Moodle that consists in automated grading system designed to process<br /> computer programming assignments, bassed on actual Assignment plugin.<br /> <br /> Computer Programming students will submit their programming assignments<br /> (developed in Java, C++, C# or other OOP language) to Moodle, and our plugin<br /> will test that the output of these programs is correct (or not). Besides that,<br /> our plugin will test security and performance issues before and during the<br /> grading automation. <br /> <br /> From Xing Shi &lt;paradiseHIT@gmail.com&gt;<br /> <br /> I also want to join this project, and I have developed a similar plugin (I call it &quot;PA-Plugin&quot;) one years ago. But it can only work for language C and C++, and only for one source file(such as main.c), not for a project. Till now it works very well on our department web. And I want to develop more functions for the plugin, such as add the java language, and make a more better architecture.<br /> <br /> Mainly, PA-Plugin realizes two functions: delivery of programming assignments by teachers and submission of programming assignments by students.<br /> <br /> To the teachers, PA-Plugin can set lots of parameters to the programming assignments, such as compiler type, grader type, max time and the max memory limitation, the resubmit times, the test data for the grader, and the grade standard data. Also the teacher can regrade all the programming assignments when one (or many) parameter is changed.<br /> <br /> To the students, the PA-Plugin will firstly detective the submitted file's type, size. If OK, then the server will compile the file to produce the bin-file, and the grader will execute the bin-file and grade the output, such as acm(Association for Computing Machinery).<br /> <br /> comment from [[User:Canizales|Jorge Cañizales]]:<br /> <br /> Well, I don't know if this is the place to put it, but we at Universidad de Las Palmas de Gran Canaria, and two other universities in Spain, have been using a system to do this for 7 years now. The software is called GAP, its author is Juan Carlos Rodríguez and it can be found [http://www.gedlc.ulpgc.es/~juanca/gap/index.html here]. The software right now isn't open source (possibly non free, either), and I don't know if Juan Carlos is willing to release the source to the OS community, but I think it's worth trying asking him.<br /> <br /> Its 7 years of actual use with hundreds of students each year have made it a very mature software, very student- and teacher-oriented. I remember it was already very comfortable when I used it as a student 5 and 6 years ago. When you submit your project (can be multiple files), the tool compiles it and reports to the student the errors and warnings found (because the compiler &amp; libraries &amp; O.S. used by the teacher have not necesarilly to match the ones used by the student, and may be stricter). Your submited files are accesible (the software presents them sintax-coloured) and you can resubmit them until the assignemet deadline. If I don't remember wrong, the system is also able to run your project through teacher-written unit tests, to help the task of the teacher. On grading, the teacher can add per-file comments the student can access when the grading is done.<br /> <br /> GAP's web page also says it is now able to handle group tasks. I've not used this feature though.<br /> <br /> So I believe that if Juan Carlos is OK with donating his software to the OS community, this project could be very strong from the beginning. The student's project could consist on integrating GAP into Moodle's technology, or porting its features and &quot;savoir-faire&quot; if both technologies are incompatible enough.<br /> <br /> I'm completely new to the developer community here, so don't know your feelings about this sort of things. What do you think of this?<br /> <br /> Mentor: Penny Leach<br /> <br /> ==== User Management Improvements ====<br /> <br /> * Improve the User features in moodle to allow bulk-operations. <br /> ** Create an interface to do bulk operations on users (e.g. delete users, reset passwords etc) This could potentially use an AJAX implementation for multiple filtering/selection of required students for bulk operations.<br /> ** Overhall the CSV upload features to allow more flexibility (more options, features to auto-generate more fields such as usernames)<br /> * Enrolment<br /> ** Specify time of manual enrollments ([http://tracker.moodle.org/browse/MDL-8877 MDL-8877])<br /> * Notes<br /> ** Allow teachers to put notes for each student in every course, much requested feature ([http://tracker.moodle.org/browse/MDL-7077 MDL-7077])<br /> Mentor: Yu Zhang<br /> <br /> ==== Email interface to Moodle ====<br /> <br /> The idea is to let people reply naturally to email they receive from Moodle to change settings or add further comments into forums etc. Moodle activities can then be accessed like a mailing list.<br /> <br /> * Add a setting so admins can specify if they want an email interface enabled. Without it, none of the following is active and Moodle functions just as it does today.<br /> * Improve the outgoing emails in Moodle to contain a unique and robust code in the headers and potentially also in the subject line (switchable by user setting) that encrypts information about the receiver, the activity instance and the specific data. For example, all the information to securely identify a forum post.<br /> * Write a PHP script designed to run from the commandline as part of an email filter, that accepts emails on standard input, parses them and then calls a function in the relevant module. For example forum_incoming_email() in mod/forum/lib.php.<br /> * Write function for forum module (at least) to parse the content of the email and add it as a post from the user. Other modules can be worked on if there's time ... resources could be sent back as attachments, quizzes could send questions and accept multiple choice answers, the course could send back a listing of activities with further codes for each one, etc.<br /> * Security is essential!<br /> <br /> Mentor: Martin Dougiamas<br /> <br /> <br /> <br /> <br /> ==== Secure RSS feeds ====<br /> <br /> Currently RSS is less than useful because:<br /> * Either we can't publish private information to the outside world because it's too sensitive.<br /> * We open up sensitive information to the outside world<br /> <br /> We should add codes to make the RSS URLs practically impossible to guess, much the same way as Google Calendar does it.<br /> <br /> * Overhaul all the RSS feeds in Moodle to make use of a long hash-like string in the URL for identification (Forums, Data etc).<br /> * Store these codes in a new field per-user and per-course. <br /> * Add GUIs to let the user recreate their code to something else should they suspect a breach.<br /> * Add RSS to other areas of Moodle such as the participants &quot;last logins&quot; and the activity logs.<br /> * Explore/research other methods of opening up RSS in a safe way to the outside world.<br /> <br /> Mentor: Petr Škoda<br /> <br /> <br /> <br /> ==== External RSS feeds into Blogs ====<br /> <br /> A lot of people already have their own blogs and don't want to use Moodle's blogs. Fair enough!<br /> <br /> This project would add user settings allowing users to specify an external RSS feed to their own external blog. Moodle will parse the feed and insert entries as internal blog entries for that user. other features include:<br /> <br /> * Specifying tags that identify required posts in that feed (eg &quot;school&quot;).<br /> * Specifying default access permissions and Moodle tags for those entries.<br /> * Keeping links to the external entry, so that when you want to &quot;comment&quot; on the blog entry you are taken to that external blog system.<br /> * Tools for admins to monitor information flow.<br /> * Other things the community may ask for.<br /> <br /> Mentor: Martin Dougiamas<br /> <br /> <br /> ==== Social Networking features ====<br /> <br /> Explore the possibilities of social networking features by expanding the user profile page:<br /> <br /> * add user tags that describe interests etc, as links to &quot;interest pages&quot; eg constructivism<br /> * interest pages that contain information about all the people who share that interest, as well as blog entries that use that tag, google searches, other info using standard Moodle blocks etc<br /> * allow users to add other users as &quot;friends&quot;, which are displayed on their user profile pages<br /> * think about controls to prevent abuse of these features in a school environment.<br /> <br /> <br /> Mentor: Martin Dougiamas<br /> <br /> <br /> <br /> ==== Roles interface improvements ====<br /> <br /> Improve the roles editing interface by making it more dynamic and flexible. You can use the YUI library for ajax if you like, but there must be a good fall-back interface too. Some ideas include:<br /> <br /> * Improve the order of the capabilities and implement better grouping.<br /> * Make the groups of capabilities collapsible to make it easier to &quot;zoom in&quot; to a particular section.<br /> * Add floating tooltip help when you hover over any given capability.<br /> * Experiment with an (alternate) interface seeing the roles all side-by-side for easier comparison/editing.<br /> * Implement a roles backup and restore system to allow site administrators to distribute useful roles in the moodle comunity (rather than having to describe the permissions setup)<br /> * Analyse the problem carefully with feedback from the community for more ideas.<br /> <br /> '''Mentor''': Nicolas Connault<br /> <br /> ====Moodle Voice====<br /> <br /> *Moodle Wiki page [[Development:Voice|Development:Voice]]<br /> *[[Development:Voice_Project|Project Proposal]]<br /> *Objective: Adapt Moodle interface to output the needed VoiceXML so you can navigate with your voice with a VoiceXML enabled browser, such as [http://www.opera.com/ Opera].<br /> <br /> '''Mentor''': [http://moodle.org/user/view.php?id=153093&amp;course=1 David Horat]<br /> <br /> ----<br /> <br /> ===Projects without Mentors===<br /> <br /> ====Integration with bibliographic systems such as Wikindx====<br /> <br /> Managing references and citing them is an important behaviour in university education and research. Bibliographic facilities are quite complicated and go beyond the capabilities of Moodle built-in technology (e.g. the database activity). Integrating Moodle with open-source bibliographic software such as [http://wikindx.sourceforge.net/ Wikindx] could much facilitate this practice within Moodle.<br /> <br /> Design and construct an integration with Wikindx (or other open-source bibliographic tools, if appropriate).<br /> <br /> Teachers should be able to easily refer to wikindx bibliography items throughout a Moodle course, and be able to:<br /> <br /> * Generate correctly-formatted in-place references (using standard styles e.g. Harvard, APA) for the commonly-cited reference types (e.g. journal article, book chapter, book). It may be possible to delegate the formatting directly to wikindx (since it already performs functions like these) rather than implementing a whole new set of logic in the Moodle integration.<br /> ** Possibly, allow some kind of direct searching of a wikindx database from within Moodle, so as to make it easier to refer to items<br /> * Generate reading lists / bibliographies<br /> * Allow export of the above into common machine-readable formats such as Bibtex or RIS. (Wikindx can perform this so again it's a question of hooking into, or expanding, wikindx functionality.)<br /> <br /> See also [[Development:Wikindx]] and [http://moodle.org/mod/forum/discuss.php?d=23022 this forum discussion] too<br /> <br /> <br /> <br /> ====Implement CATs in Moodle====<br /> <br /> [http://www.amazon.com/Classroom-Assessment-Techniques-Handbook-Education/dp/1555425003/ This book] describes a number of assessment techniques that involve collaboration and group work, and therefore fit very well into Moodle's Social Constructivist philosophy. The book about using these techniques in the classroom, but at an conference I attended there was a talk by Jean Runyon and Thomas Gorecki from the College of Southern Maryland saying how well these techniques work online. <br /> <br /> Some of them just need a forum of something basic, but others would need to be done as a database module templates. Doing this would<br /> <br /> # Make Moodle an even better teaching tool.<br /> # Provide some good exemplars of how to do interesting things with database templates.<br /> # Possibly highlight limitations in the database template system, that would require improvements to the database module code to overcome.<br /> # One of the outcomes of this project could be some really good 'How to write a database template' tutorial, which would be very valuable to the community.<br /> <br /> This is my (Tim Hunt's) idea, but I would not be interested in mentoring it. It would need to be someone who knows all about the database module.<br /> <br /> <br /> <br /> ==== Blog Assignment Type ====<br /> <br /> '''What is it for?'''<br /> <br /> Blogs are inherently user owned and driven by definition, however teachers would like to have a way to use blogs as assignments in their courses, comment, grade, etc.<br /> <br /> A solution to this conundrum would be a new Assignment type that makes it possible for a student to easily submit the link one of their blogs to an assignment in a course, and have that blog entry privately graded and commented on by the instructor of that course. The blog entry itself remains public along with all of the student's other blogs. The tool would provide a time filter in the Assignment, so that the instructor could limit the blog entry posting dates that will be accepted (both to ensure 'fresh' entries and to keep the list of entries the student chooses short for frequent student bloggers).<br /> <br /> I suggest a blog assignment type that functions as follows:<br /> <br /> '''Teacher:'''<br /> Teacher creates a blog assignment, this puts a grade in the gradebook and provides an assignment link for students to see.<br /> <br /> The teacher can configure options to allow a blog entry posted in the last X days to be used for the assignment.<br /> <br /> '''Students:'''<br /> When students enter the assignment they see a drop down menu of all their current (blog entries posted in the last X days as chosen by the teacher) blog entries, and they choose one to satisfy the assignment.<br /> <br /> '''Assessment:'''<br /> The teacher goes in to the Assignment, views the blogs that are linked from the assignment, leaves comments (the comments only show up to the student when they view the blog assignment), and gives a grade.<br /> <br /> The blog entries themselves stay on the student's blog, only the grades, links, and comments go in the assignment (optionally the assignment scrapes the student's blog and loads the full text in to store for backup and restore).<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> ==Google Summer of Code 2006 Projects==<br /> #[[Student projects/Presets for Database module|Presets for Database module project notes]]<br /> #[[Student projects/Integrated bug tracker|Integrated bug tracker project notes]]<br /> #[[Student projects/AJAX course format|AJAX course format project notes]]<br /> #[[Student projects/Admin page cleanup|Admin page cleanup project notes]]<br /> #[[Student projects/Global search|Global search project notes]]<br /> <br /> <br /> ==Other Projects==<br /> <br /> #[[Student projects/ical|Calendar export to iCal]]<br /> <br /> [[Category:Developer]]<br /> [[Category:Project]]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_GsocFormslibExercise&diff=22089 2007-04-04T08:36:44Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Deadline''': 8th of April, 2007<br /> ### Estimated time to finish: 4 hours<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Does it need to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ### What aspects will be taken into account?<br /> #### Well documented<br /> #### Easy to understand<br /> #### It should work<br /> #### It should not have security breaches or if it has, they should to be documented<br /> ## '''Finally''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_GsocFormslibExercise&diff=22060 2007-04-03T11:14:58Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Deadline''': 8th of April, 2007<br /> ### Estimated time to finish: 4 hours<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Does it need to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ### What aspects will be taken into account?<br /> #### It should be well documented<br /> #### It should work<br /> #### It should not have security breaches or if it has, they should to be documented<br /> ## '''Finally''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_GsocFormslibExercise&diff=22047 2007-04-02T10:45:28Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Deadline''': 8th of April, 2007<br /> ### Estimated time to finish: 4 hours<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Does it need to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ## '''Finally''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_GsocFormslibExercise&diff=22046 2007-04-02T10:38:49Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Deadline''': 8th of April, 2007<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Does it need to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ## '''Finally''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_GsocFormslibExercise&diff=22045 2007-04-02T10:38:23Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Deadline''': 8th of April, 2007<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Does it need to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ## '''At the end''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_GsocFormslibExercise&diff=22044 2007-04-02T10:35:18Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Deadline''': 8th of April, 2007<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Do it needs to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ## '''At the end''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_GsocFormslibExercise&diff=22043 2007-04-02T10:35:05Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Deadline''': 8th April 2007<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Do it needs to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ## '''At the end''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_GsocFormslibExercise&diff=22042 2007-04-02T10:11:48Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Date limit''': 8th April 2007<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Do it needs to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ## '''At the end''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice/GsocFormslibExercise&diff=22036 2007-04-02T08:23:02Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Date limit''': 8th April 2007<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### email: max 20 chars, obligatory, preferably with validation<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Do it needs to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ## '''At the end''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice/GsocFormslibExercise&diff=22035 2007-04-02T08:21:46Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> <br /> # '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Date limit''': 8th April 2007<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Do it needs to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ## '''At the end''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice/GsocFormslibExercise&diff=22034 2007-04-02T08:20:23Z

<p>David.horat: </p> <hr /> <div># '''Write a form using the [http://moodle.cvs.sourceforge.net/moodle/moodle/lib/formslib.php?view=markup Formslib class] and its [[Development:lib/formslib.php|documentation]].'''<br /> ## '''Date limit''': 8th April 2007<br /> ## There should be two files: example.php and example_form.php<br /> ### '''example.php''': It should invoke the form the first time called. If the form is the caller, then just present the parameters and their values on screen (to test if it has worked).<br /> ### '''example_form.php''': The form itself. It should be a class that extends &quot;moodleform&quot; from &quot;formslib.php&quot;. Note that this file should not be invoked from the browser.<br /> ## The form should have the next fields<br /> ### name: max 20 chars, obligatory<br /> ### password: max 20 chars, it should be presented with asterisks, obligatory<br /> ### comment: textfield, max 250 chars, optional<br /> ## You can use the next '''examples''' (and all you can find) from the Moodle CVS:<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/signup_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/change_password_form.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password.php?view=markup<br /> ### http://moodle.cvs.sourceforge.net/moodle/moodle/login/forgot_password_form.php?view=markup<br /> ## '''FAQ'''<br /> ### Do I have to install the whole Moodle? No, just use the formslib.php file and any other if needed.<br /> ### Do I need any tools? You can use any tools as you need. In the project we will work probably with Eclipse and phpEclipse, although it can be discussed.<br /> ### Can I strip down the formslib.php file so it doesn´t have any references to other Moodle files? Yes you can, although you should state somewhere the changes so I can see them.<br /> ### Do it needs to work? Well, let´s just say that if it works, it gets more points. :)<br /> ### Where do I find the Moodle CVS? [http://moodle.cvs.sourceforge.net/moodle/moodle/ Here is the Moodle CVS]<br /> ## '''At the end''', you can either send me the files with two screenshots of them running (the first time called and second time called) or you can set it up in your webserver so I can see them running, plus a zip or tar.gz file with the files so I can download them.</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice/VoiceXML&diff=22031 2007-04-02T07:58:42Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> == VoiceXML Technology ==<br /> * [http://www.voicexml.org/ VoiceXML.org]<br /> * [http://www.w3.org/Voice/ W3C Voice Standards]<br /> * [http://www.w3.org/TR/voicexml20/ W3C VoiceXML Version 2.0]<br /> <br /> === Examples ===<br /> * [[Development:Voice VoiceXML Examples|VoiceXML Examples]]<br /> * [http://www.youtube.com/watch?v=FSp4RJ8U3Ts Voice Web Form example video]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice/Moodle&diff=22030 2007-04-02T07:58:30Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> == Moodle General ==<br /> * [http://moodle.org/ Moodle]<br /> * [http://moodle.com/ Moodle Services]<br /> * [https://docs.moodle.org/ Moodle Documentation]<br /> <br /> == Moodle Google Summer of Code ==<br /> * [http://code.google.com/soc/ Google Summer of Code]<br /> * [https://docs.moodle.org/en/Student_projects Student projects]<br /> * [http://moodle.org/mod/forum/discuss.php?d=65046#p298033 Google Summer of Code 2007 discussion]<br /> <br /> == Developing Moodle ==<br /> * [https://docs.moodle.org/en/Developer_documentation Developer Documentation]<br /> * [https://docs.moodle.org/en/Coding Moodle Coding Guidelines]<br /> * [https://docs.moodle.org/en/CVS_%28developer%29 CVS for Moodle Developers]<br /> * [https://docs.moodle.org/en/Setting_up_Eclipse_for_Moodle_development Setting up Eclipse for Moodle Development]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice/Project&diff=22029 2007-04-02T07:58:00Z

<p>David.horat: </p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> == Objective ==<br /> Adapt Moodle interface to output the needed VoiceXML so you can navigate with your voice with a VoiceXML enabled browser, such as Opera.<br /> <br /> == Benefits ==<br /> Moodle is a free software e-learning platform which is designed to help educators create online courses with rich multimedia content. Making Moodle voice enabled will help disabled people, specially blind and motor disabled, to interact with this great e-Learning tool. Not only that, but also this gives another input interface which can be used to interact faster with the application.<br /> <br /> == Timeplan ==<br /> * Analysis (2 weeks : May 28th - June 10th)<br /> ** Study W3C VoiceXML 2.0<br /> ** Extract requirements: study Moodle output and code to choose what to make voice enabled<br /> ** Begin project webpage, documentation and logs<br /> * Design (1 weeks : June 11 th - June 17th)<br /> ** Make an Architectural Design<br /> ** Make an Implementation Proposal<br /> * Implementation (8 weeks : June 18th - August 5th)<br /> ** Milestone X (each 2 weeks) <br /> * Documentation (2 weeks : August 20th - August 31th)<br /> ** Developer documentation<br /> ** Moodle administrator documentation<br /> ** Future roadmap and design plans<br /> <br /> == Scope ==<br /> Due to the large Moodle code, the scope of what to make voice enabled will be decided in the Analysis phase, although it will be at least all navigational stuff, such as course selection, profile configuration and resource selection.<br /> <br /> == State of the Art of VoiceXML ==<br /> VoiceXML is a well known technology that has been used and supported by IVR several years. Now it has finally come to our desktop. Currently, this technology is only supported by [http://dev.opera.com/articles/voice/ Opera] in the standard browsers field, but since it is a [http://www.w3.org/TR/voicexml20/ W3C Standard], I hope it will become the defacto technology for this kind of service in all browsers. There are already plans to implement it in [http://wiki.mozilla.org/Firefox:2.0_Accessibility Firefox] and [http://www.qsos.org/sheets/webbrowser/konqueror/konqueror-3.5.5.html Konqueror]. Some examples of this technology can be found at: <br /> * http://dev.opera.com/articles/view/add-voice-interactivity-to-your-site/<br /> * http://dev.opera.com/articles/view/temporary-x-v-by-example/<br /> * http://dev.opera.com/articles/view/xhtml-voice-in-action/<br /> <br /> == Architecture Description ==<br /> # We have the option of using [http://moodle.org/mod/forum/discuss.php?d=31895 Customized Scripts] so we will [https://docs.moodle.org/en/Developer_Overview_of_MFM_Code not interfere with normal Moodle development]. On the other hand, we can directly merge it in the current CVS.<br /> # Our code will detect whether the user browser is VoiceXML enabled or not and send the corresponding code<br /> # In the &quot;future roadmap&quot; it will be included how to embed the code in Moodle core (in case it isnt) and make a Moodle configuration option to activate voice features. (It can be done in the project if we have enough time)<br /> <br /> == Related Work ==<br /> * [https://docs.moodle.org/en/Moodle_for_Mobiles Moodle for Mobiles] [http://moodle.cvs.sourceforge.net/moodle/contrib/patches/mobile/ CVS]<br /> ** Outputs [http://www.w3.org/TR/1998/NOTE-compactHTML-19980209/ Compact HTML], uses [http://moodle.org/mod/forum/discuss.php?d=31895 Customized Scripts]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_VoiceXML&diff=21986 2007-03-30T20:01:36Z

<p>David.horat: /* Examples */</p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> == VoiceXML Technology ==<br /> * [http://www.voicexml.org/ VoiceXML.org]<br /> * [http://www.w3.org/Voice/ W3C Voice Standards]<br /> * [http://www.w3.org/TR/voicexml20/ W3C VoiceXML Version 2.0]<br /> <br /> === Examples ===<br /> * [[Development:Voice VoiceXML Examples|VoiceXML Examples]]<br /> * [http://www.youtube.com/watch?v=FSp4RJ8U3Ts Voice Web Form example video]</div>

David.horat https://docs.moodle.org/24/en/index.php?title=Development:Voice_VoiceXML&diff=21983 2007-03-30T19:34:27Z

<p>David.horat: /* VoiceXML Technology */</p> <hr /> <div>{{Voice}}<br /> {{Moodle 2.0}}<br /> == VoiceXML Technology ==<br /> * [http://www.voicexml.org/ VoiceXML.org]<br /> * [http://www.w3.org/Voice/ W3C Voice Standards]<br /> * [http://www.w3.org/TR/voicexml20/ W3C VoiceXML Version 2.0]<br /> <br /> === Examples ===<br /> * [[Development:Voice VoiceXML Examples|VoiceXML Examples]]<br /> * [http://www.youtube.com/watch?v=FSp4RJ8U3Ts Voice Web Form example]</div>

David.horat