MoodleDocs - Contribucions de l'usuari [ca]

Internalmail module

2013-05-15T06:59:19Z

Granludo:

The '''Internalmail module''' provides an internal email system that works within Moodle. Each user can have his or her own internal mailbox to send and receive messages from the moodle site users. Internalmail works for Moodle 1.5 and 1.6 and is no longer maintained.

==Why use internalmail==
Why would one use internalmail?
* Because Moodle providers don't have to provide internet email acounts to their users.
* Because if email is to be used as a tool for education there has to be a way to track the status of the messages.
* Because internalmail provides course contextual folders.
* Because internalmail is trully spam free.

==Versions available==
The first Internalmail Module was developed for Moodle 1.4. Then came along the version 2.0 (2.1, 2.2. and 2.3 ) for Moodle 1.5 and the version 2.4x for Moodle 1.6.

Developer by [http://essi.upc.edu/~ludo Marc Alier] and students from [http://www.upc.edu UPC] on 2005 and 2006

Internalmail module is no longer maintained, you can find the legacy code at [http://code.google.com/p/moodle-internalmail/ internalmail project site at Google Code]

[[Category:Contributed code]]

Internalmail module

2013-05-15T06:58:38Z

Granludo:

The '''Internalmail module''' provides an internal email system that works within Moodle. Each user can have his or her own internal mailbox to send and receive messages from the moodle site users.

==Why use internalmail==
Why would one use internalmail?
* Because Moodle providers don't have to provide internet email acounts to their users.
* Because if email is to be used as a tool for education there has to be a way to track the status of the messages.
* Because internalmail provides course contextual folders.
* Because internalmail is trully spam free.

==Versions available==
The first Internalmail Module was developed for Moodle 1.4. Then came along the version 2.0 (2.1, 2.2. and 2.3 ) for Moodle 1.5 and the version 2.4x for Moodle 1.6.

Developer by [http://essi.upc.edu/~ludo Marc Alier] and students from [http://www.upc.edu UPC] on 2005 and 2006

Internalmail module is no longer maintained, you can find the legacy code at [http://code.google.com/p/moodle-internalmail/ internalmail project site at Google Code]

[[Category:Contributed code]]

Wiki 2.0

2009-11-09T16:10:00Z

Granludo: /* First alpha release */

Ludo's DFwikiteam in UPC-Barcelona leaded by Jordi Piguillem are working in the new Wiki module for Moodle 2.0

= Development process and testing =

== First alpha release ==
[http://moodle.org/mod/forum/discuss.php?d=137439|Discussed at the Wiki forum] [http://dl.dropbox.com/u/765393/wiki20.zip|download release]

=== Howto install ===
Works with Moodle 2.0 devel tested Nov 9th, 2009

Copy the Mod/wiki folder into the moodle's Mod/wiki folder (replacing completelly the folder)
And you may also copy the contents of the /blocks folder into the /blocks folder of the moodle 2.0.
A clean install worked fine, so far.

=== Main Features in this version===

This version features a functional wiki featuring Creole 1.0 parser, Mediawiki like parser, and HTML WYSIWYG page edition. The teacher can let the students choose the page format of make mandatory one format.
The blocks don't work very well.
As you may see the page differences engine has been borrowed from OUWiki.
A migration engine is in place, but requires heavy testing.

=== Needs heavy testing ===

Migration from Wiki, NWiki and ouwiki form Moodle 1.9.6

===Bugs reported ===
Place your complaints here

----

= Design and tecnical stuff =

==Database design==
Changes compared to OU wiki
* used section titles instead of byte ranges
* section titles must bu unique on each page
* synonyms table
* text format in versions table (and maybe caching field for parsed text)
* Do we need one wiki per student mode?
* page lock option

[[Image:Wikidatabasedesign.png]]

==Formats, Editors & Filters==

Implemented in core.

===Filters===
We need filtering before and after conversion to HTML.

===Editors===
New mforms editor element should support all types of formats.

===Formats===
Responsible for conversions and diffs.

==Locking==

Should use section titles instead of byte ranges.

==Version & diffs==

Diffs not part of wiki code anymore, instead handled by format plugins.

==Comments==

We need general comments framework - to be used in blogs, glossary, database mod, assignments and wiki.

Questions:
* do we need attachments? yes
* threads? no
* edit timeouts like in forum? yes
* some more capabilitites

==Groups==

Group mode can be used for emulation of one wiki per student mode.

==Grading==

General grading support for assignments and wikis with group grading mode.

Grading is handled by gradebook plugins. Grading means the act of setting final grade. This is not a peer review.

Gradebook plugins may use ratings, display overview of all pages, all contributions, etc.

==Rating==

Optional peer review - ratings, could be something like proposal for final grade.

Two different types of ratings - open on wiki pages view, the other on versions history page. First for rating of page as the result of collaborative work, the other rating of individual contributions.

==File handling==

Supported in moodle core (file handling, editors, etc.).

==Backup/Restore==

Only basic restore support for 1.6-1.9. Full support only for 2.x

==Tags==

Core tags library.

==Blocks==

* Index map - ideally graph, text too?
* Add new or missing page
* List of orphaned pages
* My contributions
* Search?? better to have generic search
* standard tags (nothing special)
* navigation
* full list of pages

==Permissions==

view, edit, comment, change locking, manage (general)

==Templates==

we need to store the template in database, we need it in group mode

==Export/Import==
portfolio and repository API

==See also==

*[[Development:NWiki roadmap]]

Wiki 2.0

2009-11-09T16:09:04Z

Granludo: first alpha released

Ludo's DFwikiteam in UPC-Barcelona leaded by Jordi Piguillem are working in the new Wiki module for Moodle 2.0

= Development process and testing =

== First alpha release ==
[http://dl.dropbox.com/u/765393/wiki20.zip|download release]

=== Howto install ===
Works with Moodle 2.0 devel tested Nov 9th, 2009

Copy the Mod/wiki folder into the moodle's Mod/wiki folder (replacing completelly the folder)
And you may also copy the contents of the /blocks folder into the /blocks folder of the moodle 2.0.
A clean install worked fine, so far.

=== Main Features in this version===

This version features a functional wiki featuring Creole 1.0 parser, Mediawiki like parser, and HTML WYSIWYG page edition. The teacher can let the students choose the page format of make mandatory one format.
The blocks don't work very well.
As you may see the page differences engine has been borrowed from OUWiki.
A migration engine is in place, but requires heavy testing.

=== Needs heavy testing ===

Migration from Wiki, NWiki and ouwiki form Moodle 1.9.6

===Bugs reported ===
Place your complaints here

----
= Design and tecnical stuff =

==Database design==
Changes compared to OU wiki
* used section titles instead of byte ranges
* section titles must bu unique on each page
* synonyms table
* text format in versions table (and maybe caching field for parsed text)
* Do we need one wiki per student mode?
* page lock option

[[Image:Wikidatabasedesign.png]]

==Formats, Editors & Filters==

Implemented in core.

===Filters===
We need filtering before and after conversion to HTML.

===Editors===
New mforms editor element should support all types of formats.

===Formats===
Responsible for conversions and diffs.

==Locking==

Should use section titles instead of byte ranges.

==Version & diffs==

Diffs not part of wiki code anymore, instead handled by format plugins.

==Comments==

We need general comments framework - to be used in blogs, glossary, database mod, assignments and wiki.

Questions:
* do we need attachments? yes
* threads? no
* edit timeouts like in forum? yes
* some more capabilitites

==Groups==

Group mode can be used for emulation of one wiki per student mode.

==Grading==

General grading support for assignments and wikis with group grading mode.

Grading is handled by gradebook plugins. Grading means the act of setting final grade. This is not a peer review.

Gradebook plugins may use ratings, display overview of all pages, all contributions, etc.

==Rating==

Optional peer review - ratings, could be something like proposal for final grade.

Two different types of ratings - open on wiki pages view, the other on versions history page. First for rating of page as the result of collaborative work, the other rating of individual contributions.

==File handling==

Supported in moodle core (file handling, editors, etc.).

==Backup/Restore==

Only basic restore support for 1.6-1.9. Full support only for 2.x

==Tags==

Core tags library.

==Blocks==

* Index map - ideally graph, text too?
* Add new or missing page
* List of orphaned pages
* My contributions
* Search?? better to have generic search
* standard tags (nothing special)
* navigation
* full list of pages

==Permissions==

view, edit, comment, change locking, manage (general)

==Templates==

we need to store the template in database, we need it in group mode

==Export/Import==
portfolio and repository API

==See also==

*[[Development:NWiki roadmap]]

Moodle API Function List

2009-01-14T09:04:56Z

Granludo: /* Course */

=Proposal for expansion of the API=
''by Ludo's team UPC''
==Course==

get_course_activities($courseid=0, $groupid=null) // return the list of activity {id, name, type}

get_course_resources($courseid=0, $groupid=null) // return the list of {id,. resource, type}

===Course Format===
get_course_outline($courseid=0, $groupid=null) // to discuss, maybe xml stuff

get_course_outline would be a nice to have from the webservices consumer app. If an external app needs to render the moodle course, need's more than just activities and resources, it needs to know how to display it. this function whould be implemented by the course format.

TODO: define course outline xml dtd

Moodle API Function List

2009-01-14T08:51:22Z

Granludo: New page: =Proposal for expansion of the API= ''by Ludo's team UPC'' ==Course== get_activities($courseid=0, $groupid=null) // return the list of activity {id, name, type} get_resources($cours...

=Proposal for expansion of the API=
''by Ludo's team UPC''
==Course==

get_activities($courseid=0, $groupid=null) // return the list of activity {id, name, type}

get_resources($courseid=0, $groupid=null) // return the list of {id,. resource, type}

Broken/Web services

2008-04-14T07:09:19Z

Granludo: /* get_courses */

This page is to decide on a STANDARD list of CORE web service functions that we should support in Moodle (by XMLRPC, REST and SOAP with the option to plug in AMFPHP for Flash/Flex interfaces) as an API for those writing code to work against Moodle.

The tracker bug for all this is here: MDL-12886

==add_users==
I think we should require all data needed for a successful "first login" to Moodle without popping him out the profile page to fill in all missing required data. This may require extra inputs such as city, description ... (unsure of the full list depending of Moodle version ?).
Also password should be "required" if authentication method is "internal" .

INPUT:
one or more of these in an array
firstname
lastname
email
idnumber
login
authentication method (optional , default= manual ?)

OPERATION:
Adds one or more new users to the user database

OUTPUT:
array of ids or false

==delete_users==
INPUT:
one or more of these in an array
idnumber or
email or
id or
login

OPERATION:
User is marked as deleted
All it's role assignments are destroyed
OUTPUT:
true/false

==get_users==
INPUT:
one or more of these
idnumber or
email or
id or
login

OPERATION:
user record with optional fields set (Moodle 1.8 and later) and maybe some fields filtered out (password,
email if user said not to disclose it ...) depending of the identity of the "caller" (admin or the user himself)

OUTPUT:
false or user record

==add_courses==
INPUT:
one or more of these in an array
name
shortname
format (default topics)
idnumber

OPERATION:
Adds a new course to the course table

OUTPUT:
id or false

==delete_courses==
INPUT:
one or more of these in an array
name OR
shortname OR
idnumber OR
id

OPERATION:
Deletes courses from the course table
What about associated ressources, roles ...

OUTPUT:
true or false

==get_courses==
INPUT:
one or more of these in an array
id or idnumber or shortname

OPERATION:
fetch course record with some fields filtered out depending of the "caller" identity (admin, teacher, student ...)
OUTPUT:
false or course records in an array

Doubts: so id , idenumber or shortname stands for... user, category, the very course you want to get itself?

==add_enrolments==
INPUT:
course unique Id (Moodle's ID or idnumber or shortname) (could be one or an array)
user unique id (Moodle's ID or idnumber or login or email) (could be one or an array)
role id (id or shortname or legacy capability name) (could be one or an array)

OPERATION:
assign given user a given role to given course

OUTPUT:
true or false

==delete_enrolments==
INPUT:
course unique Id (Moodle's ID or idnumber or shortname) (could be one or an array)
user unique id (Moodle's ID or idnumber or login or email) (could be one or an array)
role id (teacher, non editing teacher, student (?) ...) (could be one or an array)

OPERATION:
remove given user's "standard" role from given course

OUTPUT:
true or false

==get_enrolments==

INPUT:
user unique id (Moodle's ID or idnumber or login or email)
context course or site

OPERATION:
return a "list" of course's id in which given user move given user has some role assigned
return all the roles for a given courseid

OUTPUT:
"array" of (course id, course shortname, course fullname, role id, role name, course url)
or false in case of error (bad user id)

==get_recent_activity==

INPUT:
user unique id (Moodle's ID or idnumber or login or email)
course unique Id (Moodle's ID ,idnumber or shortname) - optional (default = all my courses)
timestamp - optional (default = time of last connexion in every course)

OPERATION:
return a "list" of changes (resource added/modified, new activities, etc.) for courses in which given user has some role assigned - since timestamp or last connexion in given course

OUTPUT:
"array" of (course id, course shortname, course fullname, role id, role name, url of the resource/activity, time of change)
or false in case of error (bad user/course id)

==get_grades==

(see grade_get_course_grade in grade/querylib.php)

INPUT:
user unique id (Moodle's ID or idnumber or login or email)
course unique Id (Moodle's ID ,idnumber or shortname) - optional (default = all my courses)

OPERATION:
return a "list" of grades and statistics for the given student in the given course

OUTPUT:
"array" of grades records (name,maxgrade,grade,percent,weight,weighted,sortOrder)
and "array" of stats (gradeItems,allgrades, points,totalpoints, percent, weight, weighted;)
or false in case of error (bad user/course id or user not in course)

==get_groups==

OPERATION:
return a "list" of group records in a given course (or site ?)

==add_groups==

==delete_groups==

==get_group_members==

OPERATION:
return a "list" of ids for members of a group (within a course or global)

==add_group_members==

OPERATION:
add new members to a group

==delete_group_members==

OPERATION:
remove membership from a group

==add_calendar_events==

OPERATION:
add/modify an event in Moodle database (site, course, private ...)

==delete_calendar_events ==

OPERATION:
delete given events

==get_calendar_events==

OPERATION:
return in an "exportable" format (iCal, vCal ...)an event recorded in Moodle database (site, course, private ...)

Wiki features

2008-03-13T12:29:24Z

Granludo: Update on Nwiki/Wiki in Moodle 2.0 features

Features wanted for the Wiki in Moodle 2.0, and status of existence in existing wikis :

{| border="1" cellpadding="2" cellspacing="0"
|-
!Wanted feature
!eWiki (Moodle 1.8 etc)
!NWiki and Wiki in Moodle 2.0
!OUWiki
!Comment

|-
|Mediawiki syntax
|No
|Yes
|No
|There should be option to use Mediawiki syntax also in forums, resources, etc. - new text format.

|-
|Ability to quickly summarize a students total overall contributions e.g. words added/words deleted/comments added
|No
|In development
|Soon
|About Nwiki grading system (by Ludo): The 1.9 version of NWiki will come ( on april 2008) with a newly designed grading system. The pages can be graded by teacher or peers, and the contributions (single edit or group of edits in the differences page) to pages can be rated positive, negative or without significant imporvement (+ - = ).. All of this information comes to a special page that sumarices the activities and grades received by the student. A requirement added to this page by MD is to "see" in this report the contributions ( diferences in pages). This page allows the teacher to grade the student and send the grade ( of the whole wiki activity ) to the gradebook.

|-
|Preserve line breaks
|?
|yes in HTML editor
|No
|Information is often pasted into a wiki, a wiki is used by younger students, or there are a quick succession of edits during class, such as creating a list, that require preserved line breaks. Using Creole Wiki Markup as the ONLY markup unfortunately destroys pasting in information and trying to find every crlf in a pasted document and replace it with a /n is beyond most users. We have to remember that wikis will often be used by those who have never used one before. NOTE by Ludo.. If you need to copy and paste maybe you need to use the HTML editor, since you can choose the markup to be used in each page of the wiki (in nwiki) this is easy to do.

|-
|Ability to add an "add to the page" box anywhere, or multiple times, in a page
|no
|is implemented in the discussion pages, its easy to add it to the regular pages but... what is the point?
|no
|The "Add to the page" box would be added using very simple markup (e.g., it is a plus sign at the beginning of a line in Swiki). The button has a small text area with it that can be typed in and, when the button is clicked, the information goes straight to that spot in a wiki. We use this for brainstorming in class with several groups so they can work in a small group but see and build a common document. Adding comments to students' pages, either by other students, or the students place the box at the top of the page and a teacher can quickly make a comment and move on. Even during meetings several of us share recording duties, and with the add to the page box, we can each be typing then submit. Properly implemented, this eliminates editing collisions in these situations. Each submit is treated as a separate page edit in the editing recored. Additional characters or markup beyond the one to insert the box would give the option of having lines between, keeping the box above the submissions (so it stays in place), or adding a time/date/user stamp in a different font to identify who added the information. NOTE by Ludo, as I said this feature is to be placed on discussion pages, just like in Mediawiki

|-
|Table of contents
|no
|Yes in Nwiki markup
|yes
|RSS is increasingly the way I like to consume and remix my information.

|-
|RSS feeds on changes to a page and changes to the Wiki
|no
|comming up (expected May 2008)
|yes
|RSS is increasingly the way I like to consume and remix my information.

|-
|Watch a Wiki page or a bunch of them somehow related
|?
|?
|?
|Watching pages by email is sometimes needed, as it is in moodle docs (mediawiki). One click watch on a wiki book ("structure") or a category of wiki pages is very very useful (like the features implemented in Tikiwiki CMS/Groupware)... NOTE .Can it be done by RSS? Why to have tho mechanisms of subscription ?
|-
|Prevent simultaneous wiki page edits (or allow synchroedit feature :-)
|sort of
|Yes, on 1.9 NWiki implements ection edit (in Nwiki markup) with lock at section level
|?
|When two people attempt to edit the same page, the second one should get a notice reporting to be aware that somebody else opened that page before for editing. And this should be an note, not a real lock. On the contrary, if Synchroediting (http://www.synchroedit.com/) was possible, it would be even better, and would prevent many students and teachers to use Google Docs to write documents collaboratively outside Moodle.

|-
|Simple access to rendering pages outside Wiki module
|?
|dfWiki
|?
|Many many time ago I have developed tool for including wiki page in any other Moodle resources. Details here:
http://moodle.org/mod/forum/discuss.php?d=42325 But in NWiki this became impossible because rendering page outside wiki module became very difficult! I dream that in official Moodle's wiki this will once again become possible! And promise update this tool! ;-) We hold on to that ;-)

|-
|Simple compare versions tool like media wiki on the history tab.
|?
|Hard to find NOTE by Ludo How would you improve that? Like mediawiki in the history page?
|?
|current nwiki highlight differences bit is hard to find (but very effective)
|}

Reporting student contributions to OU wiki is one of the reports we are currently working on, I think.

Broken/id:5542

2007-12-22T20:14:15Z

Granludo: /* general remarks about OUTPUT of operations: */

==general remarks about OUTPUT of operations:==
Is true of false informative enough ?
Should the API have some sort of "last_error" function giving back more details such as "non existing course, non existing user, duplicate entry ...)
Shall we consider that affecting a role that already exist or removing role that do not exist as an error (output=false) or not (output=true)
:yep, agree, I'd result always one well defined $result object, with his status, error code and error msg (and perhaps, the whole original WS request encapsulated for easier debugging).
:[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 19:55, 21 December 2007 (CST)
I agree but throught the WS we need to be be carefull with the feedback we give to errors, due to security issues. --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 14:14, 22 December 2007 (CST)

==some WS to be able to... build courses ?==
Perhpas it would be a great idea to start thinking about some WS functionalities like this:

* add_course, delete_course, reset_course
* add_section, delete_section, show_section, hide_section
* add_activity, delete_activity, show_activity, hide_activity

Apart from the WS utility itself: automated creation of courses... it would help (or force, as we prefer), to better encapsulate course/section/modules internals, 100% isolating the creation and configuration from the frontend (forms, WS...). It implies some decisions, like upwards compatibility of old modules (although I think it can be maintained)... and so on, you know.

Just one idea to analyse. But with benefits in the end, IMO.
[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 20:02, 21 December 2007 (CST)

Course Report Plugins

2007-11-07T18:50:06Z

Granludo: Course Report Plugins

A course report plugin is just another folder inside course/report/

If there is a mod.html file inside there, it will be included with the others when you visit course/report.php?id={courseid} in your browser.

That HTML fragment can do anything you like. A common thing is to include a link to course/report/myreport/index.php. That's all it is, simple, and gives you almost unlimited flexibility.

Broken/Developer documentation

2007-11-07T18:49:43Z

Granludo: /* Make a new plugin */

'''Note:''' New developer documentation pages should be added to the ''Development namespace'' by typing <code>Development:</code> before the new page name i.e. <code><nowiki>[[Development:New page name]]</nowiki></code>. If you are a developer, you probably want to change your [[Special:Preferences|preferences]] to include the Development namespace in searches. A page may be added to the Developer category by typing <code><nowiki>[[Category:Developer|New page name]]</nowiki></code> at the bottom of the page.

==How Moodle development works==

This [[Development:Overview|overview of the Moodle development process]] may be handy in understanding how the development of Moodle occurs and how people become Moodle developers.

==Guidelines==

The following guidelines are crucial reading for anyone wanting to contribute to the Moodle code base:
*[[Development:Coding|Coding guidelines]] have to be followed by all Moodle developers
*[[Moodle design goals]] spells out the basic design goals behind Moodle
*[[Interface guidelines]] aim to provide a common feel to the Moodle user interface
*[[CVS (developer)|Moodle CVS for developers]] explains how to work with the Moodle code in CVS
*[[Tracker]] explains the Moodle Tracker for keeping track of bugs, issues, feature requests etc
*[[Development:Working with the Community|Working with the Community]] explains how to engage with the dev community and discuss changes
*[[Unit tests]] explains how to run the unit tests, and how to write new test cases.

==Documentation for core components==

This section is for documentation of specific components of the existing core Moodle code. Discussion of components that are under discussion or in development can be found in the [[Developer notes]] or on the [[Roadmap]].

The documents below give a general overview. For detailed function-by-function documentation, see the [http://phpdocs.moodle.org/ phpDocumentor] documentation that is automatically generated from the comments in the code. And don't forget that the most up-to-date and detailed description of how the code works is the code itself. Moodle code should be easy to read and understand. Use the source, Luke!

===Core components that affect everything===

*lib/moodlelib.php
*[[Development:lib/weblib.php|lib/weblib.php]] for outputting stuff.
*[[Development:XMLDB_Documentation|Database abstraction layer]] @ v[[1.7]]
*[[Development:Roles|Roles and Capabilities system]] @ v[[1.7]] for controlling who can do what.
*[[Development:lib/formslib.php|Forms library]] @ v[[1.8]] for creating accessible and secure HTML forms that let users edit things.

===Core libraries with a more specific uses===

*[[Authentication API]]
*[[Cookieless Sessions]]
*[[Development:Moodle Network|Moodle Network]]
*[[Email processing]]
*[[Development:Environment checking|Environment checking]] before install, check the user's server to ensure Moodle will work there.
*[[Question engine]]
*[[Stats package]]
*[[UTF-8 migration|Migration to UTF-8]] @ v[[:Category:Moodle 1.6|1.6]]
*[http://developer.yahoo.com/yui YUI JavaScript library] - YUI was selected as the official AJAX library for Moodle.

===Modules included in the standard distribution===

*[[Quiz developer docs|Quiz module]]
*[[SCORM schema|SCORM module 1.5 schema]]

==How you can contribute==

===Make a new plugin===

The M in Moodle stands for modular, and the easiest, most maintainable way to add new functionality to Moodle is by using one of the many plugin APIs. There are many types of plugin you can write:
*[[Development:Modules|Activity modules]]
*[[Development:Admin reports|Admin reports]]
*[[Development:Assignment types|Assignment types]]
*[[Development:Authentication plugins|Authentication plugins]]
*[[Development:Blocks|Blocks]]
*[[Course formats]]
*[[Development:Course reports|Course reports]]
*[[Development:Database fields|Database fields]]
*[[Development:Database presets|Database presets]]
*[[Development:Enrolment plugins|Enrolment plugins]]
*[[Development:Filters|Filters]]
*[[Development:Grade export/import|Grade export/import]]
*[[Development:Grade report|Grade report]]
*[[Development:Question engine|Question engine]]
*[[Development:Question import/export formats|Question import/export formats]]
*[[Quiz reports]]
*[[Development:Resource types|Resource types]]
*[[Development:SSO plugins|SSO plugins]]
*[[Development:Course Report Plugins|Course Report Plugins]]

When you have developed a new component please publish it in the [http://moodle.org/mod/data/view.php?id=6009 Moodle modules and plugins database].

===Change core code===

Some types of change can only be made by editing the core Moodle code. Such changes are much harder to maintain than plugins. If you want your core change to be considered for inclusion in the official Moodle release, you need to create an issue in the [[Tracker|tracker]], and attach your change as a [[Development:How_to_create_a_patch|patch]]. It is also a good idea to discuss your ideas in the forums first.

===Ways to contribute that do not involve PHP programming===

*[[Themes|Create Moodle themes]]
*[[Translation|Translate Moodle into other languages]]
*[[MoodleDocs:Guidelines for contributors|Help document Moodle]]
*[[Development:Database schemas|Database schemas]]
*[[Development:Tests|Join the testing effort]], which involves [[Tracker|participating in the bug tracker]]

==Plans for the future==

Ideas for and details of planned future features of Moodle are initially discussed on the forums in the [http://moodle.org/course/view.php?id=5 Using Moodle] course at moodle.org. That developer discussions are intermixed with user discussions in the same forums may seem strange at first but is one of the reasons for the success of Moodle. It is important that both end-users and developers discuss the future features together.

Once ideas begin to crystallize on the forums they can be summarized in this wiki, either as part of the [[Roadmap]] or in the form of [[Developer notes]]. These pages then form the basis for further discussion in the forums.

*[[Roadmap]]
*[[Development:Developer notes|Developer notes]]
*[[Student projects]]
*[[Developer conferences]]

== Resources and tools ==

*[[Developer FAQ]] - frequently asked questions, especially useful for newcomers to Moodle
*[[Development:Finding_your_way_into_the_Moodle_code|Finding your way into the Moodle code]] - also aimed at newcomers
*[http://tracker.moodle.org/ Moodle tracker] - bug reports, feature requests and other tracked issues
**[[Firefox tracker search]] - How to setup a firefox quicksearch to easily navigate to moodle bugs
*[[Unmerged files]] - changes on the stable branch in CVS that have not been merged to HEAD
*Browse the code online:
**[http://moodle.cvs.sourceforge.net/moodle/moodle/ the code with a complete change history from CVS]
**[http://xref.moodle.org/index.html the code, with links generated by PHPXref]
*[http://phpdocs.moodle.org/ Moodle PHP doc reference] - compiled from the comment attached to each class and function in the code
*[[Development:Database Schema|Database Schema]] - for recent releases
*[http://moodle.org/course/view.php?id=5#4 Development news and discussion] section of Using Moodle course
**especially the [http://moodle.org/mod/forum/view.php?id=55 General developer forum]
**[[Filters used on the Moodle.org forums|cool tricks you can use in the moodle.org forums]]
*Some tools people use when working on Moodle code:
**[[Development:Setting_up_Eclipse|Setting up Eclipse for Moodle development]] - Eclipse is a great editor to use for php development, if you can work out how to set it up.
**[[Development:vim|Setting up Vim for Moodle development]]
**[[Development:ctags|Ctags]] - Using a tags file to navigate code

==See also==

*[http://security.moodle.org/ Moodle Security Centre]
*[http://moodle.com/partners/ Moodle Partners] - providers of custom Moodle development services

[[Category:Developer]]
[[es:Documentación para Desarrolladores]]
[[fr:Documentation développeur]]
[[zh:开发者文档]]
[[ja:開発者ドキュメント]]

Broken/Developer documentation

2007-11-07T18:48:43Z

Granludo: /* Make a new plugin */

'''Note:''' New developer documentation pages should be added to the ''Development namespace'' by typing <code>Development:</code> before the new page name i.e. <code><nowiki>[[Development:New page name]]</nowiki></code>. If you are a developer, you probably want to change your [[Special:Preferences|preferences]] to include the Development namespace in searches. A page may be added to the Developer category by typing <code><nowiki>[[Category:Developer|New page name]]</nowiki></code> at the bottom of the page.

==How Moodle development works==

This [[Development:Overview|overview of the Moodle development process]] may be handy in understanding how the development of Moodle occurs and how people become Moodle developers.

==Guidelines==

The following guidelines are crucial reading for anyone wanting to contribute to the Moodle code base:
*[[Development:Coding|Coding guidelines]] have to be followed by all Moodle developers
*[[Moodle design goals]] spells out the basic design goals behind Moodle
*[[Interface guidelines]] aim to provide a common feel to the Moodle user interface
*[[CVS (developer)|Moodle CVS for developers]] explains how to work with the Moodle code in CVS
*[[Tracker]] explains the Moodle Tracker for keeping track of bugs, issues, feature requests etc
*[[Development:Working with the Community|Working with the Community]] explains how to engage with the dev community and discuss changes
*[[Unit tests]] explains how to run the unit tests, and how to write new test cases.

==Documentation for core components==

This section is for documentation of specific components of the existing core Moodle code. Discussion of components that are under discussion or in development can be found in the [[Developer notes]] or on the [[Roadmap]].

The documents below give a general overview. For detailed function-by-function documentation, see the [http://phpdocs.moodle.org/ phpDocumentor] documentation that is automatically generated from the comments in the code. And don't forget that the most up-to-date and detailed description of how the code works is the code itself. Moodle code should be easy to read and understand. Use the source, Luke!

===Core components that affect everything===

*lib/moodlelib.php
*[[Development:lib/weblib.php|lib/weblib.php]] for outputting stuff.
*[[Development:XMLDB_Documentation|Database abstraction layer]] @ v[[1.7]]
*[[Development:Roles|Roles and Capabilities system]] @ v[[1.7]] for controlling who can do what.
*[[Development:lib/formslib.php|Forms library]] @ v[[1.8]] for creating accessible and secure HTML forms that let users edit things.

===Core libraries with a more specific uses===

*[[Authentication API]]
*[[Cookieless Sessions]]
*[[Development:Moodle Network|Moodle Network]]
*[[Email processing]]
*[[Development:Environment checking|Environment checking]] before install, check the user's server to ensure Moodle will work there.
*[[Question engine]]
*[[Stats package]]
*[[UTF-8 migration|Migration to UTF-8]] @ v[[:Category:Moodle 1.6|1.6]]
*[http://developer.yahoo.com/yui YUI JavaScript library] - YUI was selected as the official AJAX library for Moodle.

===Modules included in the standard distribution===

*[[Quiz developer docs|Quiz module]]
*[[SCORM schema|SCORM module 1.5 schema]]

==How you can contribute==

===Make a new plugin===

The M in Moodle stands for modular, and the easiest, most maintainable way to add new functionality to Moodle is by using one of the many plugin APIs. There are many types of plugin you can write:
*[[Development:Modules|Activity modules]]
*[[Development:Admin reports|Admin reports]]
*[[Development:Assignment types|Assignment types]]
*[[Development:Authentication plugins|Authentication plugins]]
*[[Development:Blocks|Blocks]]
*[[Course formats]]
*[[Development:Course reports|Course reports]]
*[[Development:Database fields|Database fields]]
*[[Development:Database presets|Database presets]]
*[[Development:Enrolment plugins|Enrolment plugins]]
*[[Development:Filters|Filters]]
*[[Development:Grade export/import|Grade export/import]]
*[[Development:Grade report|Grade report]]
*[[Development:Question engine|Question engine]]
*[[Development:Question import/export formats|Question import/export formats]]
*[[Quiz reports]]
*[[Development:Resource types|Resource types]]
*[[Development:SSO plugins|SSO plugins]]
*[[Development:Course Report Plugins]]

When you have developed a new component please publish it in the [http://moodle.org/mod/data/view.php?id=6009 Moodle modules and plugins database].

===Change core code===

Some types of change can only be made by editing the core Moodle code. Such changes are much harder to maintain than plugins. If you want your core change to be considered for inclusion in the official Moodle release, you need to create an issue in the [[Tracker|tracker]], and attach your change as a [[Development:How_to_create_a_patch|patch]]. It is also a good idea to discuss your ideas in the forums first.

===Ways to contribute that do not involve PHP programming===

*[[Themes|Create Moodle themes]]
*[[Translation|Translate Moodle into other languages]]
*[[MoodleDocs:Guidelines for contributors|Help document Moodle]]
*[[Development:Database schemas|Database schemas]]
*[[Development:Tests|Join the testing effort]], which involves [[Tracker|participating in the bug tracker]]

==Plans for the future==

Ideas for and details of planned future features of Moodle are initially discussed on the forums in the [http://moodle.org/course/view.php?id=5 Using Moodle] course at moodle.org. That developer discussions are intermixed with user discussions in the same forums may seem strange at first but is one of the reasons for the success of Moodle. It is important that both end-users and developers discuss the future features together.

Once ideas begin to crystallize on the forums they can be summarized in this wiki, either as part of the [[Roadmap]] or in the form of [[Developer notes]]. These pages then form the basis for further discussion in the forums.

*[[Roadmap]]
*[[Development:Developer notes|Developer notes]]
*[[Student projects]]
*[[Developer conferences]]

== Resources and tools ==

*[[Developer FAQ]] - frequently asked questions, especially useful for newcomers to Moodle
*[[Development:Finding_your_way_into_the_Moodle_code|Finding your way into the Moodle code]] - also aimed at newcomers
*[http://tracker.moodle.org/ Moodle tracker] - bug reports, feature requests and other tracked issues
**[[Firefox tracker search]] - How to setup a firefox quicksearch to easily navigate to moodle bugs
*[[Unmerged files]] - changes on the stable branch in CVS that have not been merged to HEAD
*Browse the code online:
**[http://moodle.cvs.sourceforge.net/moodle/moodle/ the code with a complete change history from CVS]
**[http://xref.moodle.org/index.html the code, with links generated by PHPXref]
*[http://phpdocs.moodle.org/ Moodle PHP doc reference] - compiled from the comment attached to each class and function in the code
*[[Development:Database Schema|Database Schema]] - for recent releases
*[http://moodle.org/course/view.php?id=5#4 Development news and discussion] section of Using Moodle course
**especially the [http://moodle.org/mod/forum/view.php?id=55 General developer forum]
**[[Filters used on the Moodle.org forums|cool tricks you can use in the moodle.org forums]]
*Some tools people use when working on Moodle code:
**[[Development:Setting_up_Eclipse|Setting up Eclipse for Moodle development]] - Eclipse is a great editor to use for php development, if you can work out how to set it up.
**[[Development:vim|Setting up Vim for Moodle development]]
**[[Development:ctags|Ctags]] - Using a tags file to navigate code

==See also==

*[http://security.moodle.org/ Moodle Security Centre]
*[http://moodle.com/partners/ Moodle Partners] - providers of custom Moodle development services

[[Category:Developer]]
[[es:Documentación para Desarrolladores]]
[[fr:Documentation développeur]]
[[zh:开发者文档]]
[[ja:開発者ドキュメント]]

Wiki 2.0

2007-10-20T14:23:07Z

Granludo: /* New wiki */

The Moodle wiki(s) enables participants to work together on web pages to add, expand and change the content. This page can serve to provide information about different Wikis that may be used with Moodle.

= Wiki Standard =
Link to the [[Wiki]] MoodleDoc page
This is the standard Wiki which is part of 1.5 . It was developed from a version of Erfurt wiki. A flavor of it is still being used in Moodle 1.8 beta.

See the MoodleDocs [[Wiki module]] or [http://moodle.org/help.php?module=wiki&file=howtowiki.html "How to wiki" page for more information].

Initially built by Mike Churchward & Michael Schneider

= Dfwiki =
This is an addin wiki for Moodle.
[[Dfwiki]] is the MoodleDoc page.
'''DFWiki''' is an alternative [[wiki]] module to the current (1.5.3) Moodle [[Wiki module]].

Dfwiki for Moodle 1.5.3 can be found [http://appserv.lsi.upc.es/palangana/moodle/course/view.php?id=15 in dfwiki home page], and in the Moodle [[CVS]]. The [http://appserv.lsi.upc.es/palangana/moodle/course/view.php?id=15 dfwiki english home page is here].

Team leader is Marc Alier (Ludo).

= Erfurt wiki =
Named for the developer's hometown in Germany, it was the basis for the standard wiki included with Moodle.

= New wiki =
Currently is this wiki available as a plug in for 1.6.x 1.7.x and 1.8.x. "We ([[Dfwiki_module#Dfwikiteam|Dfwiki team]]) hope it will be the standard wiki in Moodle 1.8", says Team leader Marc Alier (ludo). He was mistaken for two releases.. According to the Moodle [[Roadmap]] NWiki is definitevelly into Moodle 2.0

The NewWiki16 plugin has more MediaWiki(MoodleDocs)features. For example, the characters that create, the automatic headers (<nowiki>= = or == ==</nowiki>), automatic numbers (<nowiki># or ##</nowiki>) and bullets (<nowiki>* or **</nowiki>) work. It also has a page discussion tab and provides a page outline based on headers at the top. There are two HTML edit tool bars available. The 1.6.x version does have a site map on a "navigation" tab, but not the standard pages found on the Choose Wiki links pulldown.

==Tiddlywiki integration==
New wiki can interoperate with the Ajax based portable [http://tiddlywiki.com tidlywiki].
See [[Tiddlywiki integration]]

= MediaWiki =
This is the "big" wiki. Will Taylor says "I have MediaWiki integrated now with Moodle versions 1.5.3 and 1.6, very easy to set up. Users need to log in separately to MediaWiki to edit, but they are authenticated off the Moodle database, so use the same username & password without needing to create a separate account on MediaWiki. Using the MediaWiki permissions system, I have editing privileges reserved for registered, logged-in users, and read privileges open to the world - but you could configure this in many ways if you wish. Check out the various projects created in MediaWiki (WikiPedia, Wiktionary, &c.) to see the potential of this platform."

MediaWiki should be used as a '''site-specific''' wiki. The standard Moodle wiki, or Dfwiki should be used as course-specific wiki.
= Table of Versions =
{| border="0" cellpadding="4" cellspacing ="0" rules="all"
|+ '''Wikis in Moodle'''
! -Version Name-
! Wiki version
! Moodle ver
! Status
! Download Place
! Docs
! Discussion Place
! Feature1
|-----
| Std Wiki
|
| all
|
|[http://moodle.org/mod/data/view.php?d=13&rid=273 Modules]
| [[Wiki]]
| [http://moodle.org/mod/forum/view.php?f=366 Wiki forum]
|
|-----
| Dfwiki
|
| 1.5.4
|
|[[http://moodle.org/mod/data/view.php?d=13&rid=115 CVS Page]]
| [[Dfwiki]]
|[http://moodle.org/mod/forum/view.php?f=366 Wiki forum]
|
|-----
| Erfurt Wiki
|
| 1.6
|
|[http://erfurtwiki.sourceforge.net/ Sourceforge]
| [http://erfurtwiki.sourceforge.net/README readme]
|
|
|-----
| New wiki
|
|1.7 and 1.8
|Beta
|[http://morfeo.upc.es/crom/course/view.php?id=4 DFwiki home]
|[http://morfeo.upc.es/crom/course/view.php?id=4 DFwiki home]
|[http://morfeo.upc.es/crom/course/view.php?id=4 DFwiki home]
|[http://moodle.org/mod/forum/view.php?f=366 Wiki forum]
|-----
| MediaWiki
|
|NA
|
|[http://www.mediawiki.org/wiki/MediaWiki MediaWiki Home]
|
|
|
|}

=See also=
* [[Dfwiki]]
* [[Wiki requirements|Specific wiki requirements]]
* [[dfwiki requests]]
* [[NWiki roadmap]]
* [[Wiki comments |Wiki development comments]]
*[[wikindx]] for developers

* Using Moodle [http://moodle.org/mod/forum/view.php?f=366 Wiki module forum]

[[Category:Developer|Wiki]]
[[Category:Wiki]]

Roadmap

2007-10-20T14:18:28Z

Granludo:

This roadmap collects the best information about upcoming features in Moodle. It is not 100% certain - features may change according to available funding and developers.

== Version 1.9 - very soon ==
''1.9 is currently in beta. See [[Release Notes]].
* [[Development:Grades|Gradebook development]] - Moodle.com and OU
::The gradebook system will be revamped for performance, switching from our older "pull" model to a "push" model where all modules will now publish grades as necessary into a central table. Support for (local/state) [[Development:Outcomes|outcomes/goals/competencies]] is included!
* [[Development:Events|Events API]] - Moodle.com
::The new Events API provides a way for any code to "hook" into events in a clean, loosely coupled way. It's the foundation of the new Gradebook. A lot of events in Moodle (such as adding a user or a course) now trigger events that developers can hook into.
* [[Tags]] - part of the [[Student_projects/Social_Networking_features|Google SOC Social Networking]] project by Luiz Cruz will make it's way into 1.9, allowing users to tag themselves and create interest pages around those tags, bringing information together from a variety of sources.
* [[Question_Engine_Changes_in_Moodle_1.9|Improved question bank]] - Jamie Pratt funded by [http://www.fun.ac.jp/en/ Future University Hakodate].
** Allows questions to be shared by the whole site, a course category, a singe course, or be kept private to a single module. More control over who can do what to each question.
** [[Questions linking to files|Also improved management of files linked to from questions.]]
** See also the original development plan here: [[Development:Plan to Improve Flexibility of Question Category Sharing and Permissions]]
* Other Quiz/Question improvements:
** A quiz can now [[Quiz submission email notification|send emails when an attempt is finished]] - a confirmation to the student, a notification to all teachers, or both. Implemented by Graham Miller of [http://www.webenhanced.com.au/ Web Enhanced Solutions].
** Some slight improvements to quiz layout. See [http://tracker.moodle.org/browse/MDL-10374 MDL-10374] for details. Theme designers please note!
** [[GIFT format|Gift Import/Export format]] can now handle Essay and Description question types.
** Third party question types can now implement [[Moodle XML format]] and other import and export formats. Implemented by Howard Miller.
** [[Multiple Choice question type|Multiple choice questions]] now show the feedback for all the options to students on the review page after the attempt is over.
* [[Groups]] reverted to 1.7 style and reimplemented groupings - Moodle.com, Catalyst, OU, Enrique Castro

== Version 2.0 - Expected Late 2008 ==

(This list is fluid, depending on available resources)

===Definitely===
* Moodle 2.0 will require PHP 5.2 as a minimum, allowing us to clean up the code in some areas. For more info see: [http://gophp5.org/ gophp5.org]
* [[Development:Portfolio API]] - Enovation.ie
::Interface Moodle activities and repositories to help produce portfolios for internal assessment AND external publication. The first Portfolio plugin implemented will be [http://www.mahara.org/ Mahara].
* [[Conditional activities]] - Moodle.com
::Allowing dependencies and forced paths through the content
* [[Community hub]] interfaces - Moodle.com and others
::Makes it easy for users to find and navigate other systems and external Moodle repositories, leveraging the Moodle Network in various ways.
* [[Repository API]] - Moodle.com
::Abstract all file operations to an API that allows plugins for different external repositories
* Old DB install/upgrade system removed
:: The deprecated system for installing or upgrading database entries used in Moodle < 1.7 will be completely removed, while supporting only the new XML based database scheme introduced in 1.7
* Feedback module
* [[NWiki roadmap|New Wiki]] module (nwiki) - DFWikiteam-UPC
* Messaging improvements
* Secure RSS feeds

===Hopefully===
* [[IMS Learning Design]] - Moodle.com
::Support for importing/exporting LD, converting Moodle activities and sequences of activities into a standard format for sharing, and importing standard sequences into Moodle courses
* [[Student Information API]]
::API for integrating external systems for managing student information
* [[Development:Voice|Moodle Voice]]
:: Moodle Voice is a project for embedding VoiceXML support into Moodle Core.
* [[Learning Design export]]? - Moodle.com and Open University of The Netherlands
::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.

==See also==

* [[Release Notes]]

[[Category:Developer]]
[[Category:Future]]

[[es:Planificación]]
[[fr:Planification]]

Broken/NWiki roadmap

2007-06-07T14:00:41Z

Granludo: /* rethink wiki permisions and roles */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

= NWiki roadmap=
Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=Wiki+Unit+Tests+Documentation&gid=0&uid=0 NWiki PHPUnit documentation]

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.
== rethink wiki permisions and roles ==
* a user can discuss the page while he cannot edit the page
* the teacher cat FIX a markup for a wiki in the wiki options form.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features Implemented==

=== Wiki Templates ===

* Add templates so that some content can be made available to all groups when they start using a wiki
Implemented, in release June 2007
=== mailto ===
* a mailto link for dfwiki
has already ben developed must be included in next release [http://moodle.org/mod/forum/discuss.php?d=38991 mailto dfwiki forum thread]

==And finally==
Dynamical online import from mediawiki utilty... :-D

= Old DFwiki requests =
Use this page for requests of bugfixes and new features on the [http://morfeo.upc.es/crom/course/view.php?id=4 NWiki]
The [http://morfeo.upc.es/crom/course/view.php?id=4 DFwikiteam] will keep a sharp eye on the list.

== Miscelaneous ==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

== block wikipage ==

Would be useful to have a block with the content of a wikipage.

If you select 'social' course format you have the option of inserting a social activities block... I don't get that option for the DFWiki, but I think I should so I can add other Moodle activities...

otherwise, when I go to admin/site I can choose to display a topic section where I can put activities and this may be an alternative solution.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced filter, which can include wiki-page into any filterable place. In summ with existing html block it sounds like solution for this suggestion! --[[User:Ne Nashev|Ne Nashev]] 07:52, 26 March 2006 (WST)

== Including wiki page in other Moodle resources ==
I suggest add to standard filters (like Autoformat, Markdown) tag which allow include content (not a link) of wiki page (without editing). This will allow to use wiki as general place for storage texts and use them in resources, lessons and so on.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced this filter

-----
The words "Change to one of the following editors" tells the new user to change to an editor other than the default editor. As this works now, the choice cannot be changed once selected.

In order to avoid this confusion, the teacher should be able to make the default editor the only choice.

In the meantime, the option "Change to one of the following editors" could be moved down below the buttons: save, preview, cancel.

That way new users will be more likely to use the default editor and not lock themselves into one of the other options.
[http://moodle.org/mod/forum/discuss.php?d=39191 forum tread]
-----

== Moodle wide metawiki==

We need a metawiki index to easily link between wikis.
The idea is to have admin tool to manage the wiki-names to be able to
refer easily from one wiki to another like this:

<nowiki> [wiki-name:wikipagename|label to link]</nowiki>

== Special wiki pages ==

=== Wiki reference. ===
To implement biblio references... a link like
<nowiki>[ref:refname]</nowiki> Will lead us to a editing page with a form (maybe a [[database module]] form) to enter the biblio reference ( title, author, isbn, link , pages ... and so on )...
Once we got that any page with a reference to a biblio ref will get printed at its bottom the complete reference and a link to it.

This feature proposal comes within the [[wikibook]] line of work

== weird course interaction stuff ==
If you select 'social' course format you have the option of inserting a social activities block... I don't get that option if I select DFWiki, but I think I should so I can add other Moodle activities... (using Moodle 1.6)

Otherwise, when I go to admin/site I can choose to display 1 topic section where I can put activities and this may be an alternative solution.

Also if I modify a course that had a different format, such as topics ,to be DFWiki the course crashes and you cannot get back to original course format because of the error it throws up.

*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-07T10:16:45Z

Granludo: /* Migration issues */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

= NWiki roadmap=
Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=Wiki+Unit+Tests+Documentation&gid=0&uid=0 NWiki PHPUnit documentation]

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.
== rethink wiki permisions and roles ==
a user can discuss the page while he cannot edit the page

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features Implemented==

=== Wiki Templates ===

* Add templates so that some content can be made available to all groups when they start using a wiki
Implemented, in release June 2007
=== mailto ===
* a mailto link for dfwiki
has already ben developed must be included in next release [http://moodle.org/mod/forum/discuss.php?d=38991 mailto dfwiki forum thread]

==And finally==
Dynamical online import from mediawiki utilty... :-D

= Old DFwiki requests =
Use this page for requests of bugfixes and new features on the [http://morfeo.upc.es/crom/course/view.php?id=4 NWiki]
The [http://morfeo.upc.es/crom/course/view.php?id=4 DFwikiteam] will keep a sharp eye on the list.

== Miscelaneous ==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

== block wikipage ==

Would be useful to have a block with the content of a wikipage.

If you select 'social' course format you have the option of inserting a social activities block... I don't get that option for the DFWiki, but I think I should so I can add other Moodle activities...

otherwise, when I go to admin/site I can choose to display a topic section where I can put activities and this may be an alternative solution.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced filter, which can include wiki-page into any filterable place. In summ with existing html block it sounds like solution for this suggestion! --[[User:Ne Nashev|Ne Nashev]] 07:52, 26 March 2006 (WST)

== Including wiki page in other Moodle resources ==
I suggest add to standard filters (like Autoformat, Markdown) tag which allow include content (not a link) of wiki page (without editing). This will allow to use wiki as general place for storage texts and use them in resources, lessons and so on.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced this filter

-----
The words "Change to one of the following editors" tells the new user to change to an editor other than the default editor. As this works now, the choice cannot be changed once selected.

In order to avoid this confusion, the teacher should be able to make the default editor the only choice.

In the meantime, the option "Change to one of the following editors" could be moved down below the buttons: save, preview, cancel.

That way new users will be more likely to use the default editor and not lock themselves into one of the other options.
[http://moodle.org/mod/forum/discuss.php?d=39191 forum tread]
-----

== Moodle wide metawiki==

We need a metawiki index to easily link between wikis.
The idea is to have admin tool to manage the wiki-names to be able to
refer easily from one wiki to another like this:

<nowiki> [wiki-name:wikipagename|label to link]</nowiki>

== Special wiki pages ==

=== Wiki reference. ===
To implement biblio references... a link like
<nowiki>[ref:refname]</nowiki> Will lead us to a editing page with a form (maybe a [[database module]] form) to enter the biblio reference ( title, author, isbn, link , pages ... and so on )...
Once we got that any page with a reference to a biblio ref will get printed at its bottom the complete reference and a link to it.

This feature proposal comes within the [[wikibook]] line of work

== weird course interaction stuff ==
If you select 'social' course format you have the option of inserting a social activities block... I don't get that option if I select DFWiki, but I think I should so I can add other Moodle activities... (using Moodle 1.6)

Otherwise, when I go to admin/site I can choose to display 1 topic section where I can put activities and this may be an alternative solution.

Also if I modify a course that had a different format, such as topics ,to be DFWiki the course crashes and you cannot get back to original course format because of the error it throws up.

*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-07T07:43:07Z

Granludo: /* Code Tunning : new wiki api */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

= NWiki roadmap=
Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=Wiki+Unit+Tests+Documentation&gid=0&uid=0 NWiki PHPUnit documentation]

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features Implemented==

=== Wiki Templates ===

* Add templates so that some content can be made available to all groups when they start using a wiki
Implemented, in release June 2007
=== mailto ===
* a mailto link for dfwiki
has already ben developed must be included in next release [http://moodle.org/mod/forum/discuss.php?d=38991 mailto dfwiki forum thread]

==And finally==
Dynamical online import from mediawiki utilty... :-D

= Old DFwiki requests =
Use this page for requests of bugfixes and new features on the [http://morfeo.upc.es/crom/course/view.php?id=4 NWiki]
The [http://morfeo.upc.es/crom/course/view.php?id=4 DFwikiteam] will keep a sharp eye on the list.

== Miscelaneous ==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

== block wikipage ==

Would be useful to have a block with the content of a wikipage.

If you select 'social' course format you have the option of inserting a social activities block... I don't get that option for the DFWiki, but I think I should so I can add other Moodle activities...

otherwise, when I go to admin/site I can choose to display a topic section where I can put activities and this may be an alternative solution.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced filter, which can include wiki-page into any filterable place. In summ with existing html block it sounds like solution for this suggestion! --[[User:Ne Nashev|Ne Nashev]] 07:52, 26 March 2006 (WST)

== Including wiki page in other Moodle resources ==
I suggest add to standard filters (like Autoformat, Markdown) tag which allow include content (not a link) of wiki page (without editing). This will allow to use wiki as general place for storage texts and use them in resources, lessons and so on.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced this filter

-----
The words "Change to one of the following editors" tells the new user to change to an editor other than the default editor. As this works now, the choice cannot be changed once selected.

In order to avoid this confusion, the teacher should be able to make the default editor the only choice.

In the meantime, the option "Change to one of the following editors" could be moved down below the buttons: save, preview, cancel.

That way new users will be more likely to use the default editor and not lock themselves into one of the other options.
[http://moodle.org/mod/forum/discuss.php?d=39191 forum tread]
-----

== Moodle wide metawiki==

We need a metawiki index to easily link between wikis.
The idea is to have admin tool to manage the wiki-names to be able to
refer easily from one wiki to another like this:

<nowiki> [wiki-name:wikipagename|label to link]</nowiki>

== Special wiki pages ==

=== Wiki reference. ===
To implement biblio references... a link like
<nowiki>[ref:refname]</nowiki> Will lead us to a editing page with a form (maybe a [[database module]] form) to enter the biblio reference ( title, author, isbn, link , pages ... and so on )...
Once we got that any page with a reference to a biblio ref will get printed at its bottom the complete reference and a link to it.

This feature proposal comes within the [[wikibook]] line of work

== weird course interaction stuff ==
If you select 'social' course format you have the option of inserting a social activities block... I don't get that option if I select DFWiki, but I think I should so I can add other Moodle activities... (using Moodle 1.6)

Otherwise, when I go to admin/site I can choose to display 1 topic section where I can put activities and this may be an alternative solution.

Also if I modify a course that had a different format, such as topics ,to be DFWiki the course crashes and you cannot get back to original course format because of the error it throws up.

*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-04T07:04:19Z

Granludo: /* Fixed */

Broken/NWiki roadmap

2007-06-04T07:03:54Z

Granludo: /* Add automatic transliteration of the non-latin page names */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

= NWiki roadmap=
Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features Implemented==

=== Wiki Templates ===

* Add templates so that some content can be made available to all groups when they start using a wiki
Implemented, in release June 2007
=== mailto ===
* a mailto link for dfwiki
has already ben developed must be included in next release [http://moodle.org/mod/forum/discuss.php?d=38991 mailto dfwiki forum thread]

==And finally==
Dynamical online import from mediawiki utilty... :-D

= Old DFwiki requests =
Use this page for requests of bugfixes and new features on the [http://morfeo.upc.es/crom/course/view.php?id=4 NWiki]
The [http://morfeo.upc.es/crom/course/view.php?id=4 DFwikiteam] will keep a sharp eye on the list.

== Miscelaneous ==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

== block wikipage ==

Would be useful to have a block with the content of a wikipage.

If you select 'social' course format you have the option of inserting a social activities block... I don't get that option for the DFWiki, but I think I should so I can add other Moodle activities...

otherwise, when I go to admin/site I can choose to display a topic section where I can put activities and this may be an alternative solution.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced filter, which can include wiki-page into any filterable place. In summ with existing html block it sounds like solution for this suggestion! --[[User:Ne Nashev|Ne Nashev]] 07:52, 26 March 2006 (WST)

== Including wiki page in other Moodle resources ==
I suggest add to standard filters (like Autoformat, Markdown) tag which allow include content (not a link) of wiki page (without editing). This will allow to use wiki as general place for storage texts and use them in resources, lessons and so on.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced this filter

-----
The words "Change to one of the following editors" tells the new user to change to an editor other than the default editor. As this works now, the choice cannot be changed once selected.

In order to avoid this confusion, the teacher should be able to make the default editor the only choice.

In the meantime, the option "Change to one of the following editors" could be moved down below the buttons: save, preview, cancel.

That way new users will be more likely to use the default editor and not lock themselves into one of the other options.
[http://moodle.org/mod/forum/discuss.php?d=39191 forum tread]
-----

== Moodle wide metawiki==

We need a metawiki index to easily link between wikis.
The idea is to have admin tool to manage the wiki-names to be able to
refer easily from one wiki to another like this:

<nowiki> [wiki-name:wikipagename|label to link]</nowiki>

== Special wiki pages ==

=== Wiki reference. ===
To implement biblio references... a link like
<nowiki>[ref:refname]</nowiki> Will lead us to a editing page with a form (maybe a [[database module]] form) to enter the biblio reference ( title, author, isbn, link , pages ... and so on )...
Once we got that any page with a reference to a biblio ref will get printed at its bottom the complete reference and a link to it.

This feature proposal comes within the [[wikibook]] line of work

== weird course interaction stuff ==
If you select 'social' course format you have the option of inserting a social activities block... I don't get that option if I select DFWiki, but I think I should so I can add other Moodle activities... (using Moodle 1.6)

Otherwise, when I go to admin/site I can choose to display 1 topic section where I can put activities and this may be an alternative solution.

Also if I modify a course that had a different format, such as topics ,to be DFWiki the course crashes and you cannot get back to original course format because of the error it throws up.

= Fixed =

== Inconsistencies with Standard Moodle Behaviour ==

username is used to identify the user in the database instead of userid. This is also displayed to students and teachers instead of user's full name. This is a serious bug because it poses a security risk to students by revealing their userid to all, and it is also a serious issue because anyone can change their username at any time, unlike userid. This problem exists in both Dfwiki and the new wiki.

'''FIXED'''

== Grading system ==
A way to grade users that contribute with the wiki

'''This issue has been implemented ''' in two ways in [[new wiki]]
* Grades
* Votes + ranking block
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22 dfwiki and new wiki documentation]

== Improve differences ==
* Create a more user friendly (WYSIWYG) view for the history/diff mode. Something similar to what was available in the "old" wiki would be enough, but I'm sure you guys can make it even better :-}.

Actually, I just saw the view for the diff format in this wiki (the one where MoodleDOCS are created) and it does just what I want:
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=newdiff%2FBegin+here&dfcontent=wiki_hist_content&ver=5&gid=0&uid=0 example of how it looks]

==End==

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-04T07:03:25Z

Granludo: /* Coses rares */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

= NWiki roadmap=
Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features Implemented==

=== Wiki Templates ===

* Add templates so that some content can be made available to all groups when they start using a wiki
Implemented, in release June 2007
=== mailto ===
* a mailto link for dfwiki
has already ben developed must be included in next release [http://moodle.org/mod/forum/discuss.php?d=38991 mailto dfwiki forum thread]

==And finally==
Dynamical online import from mediawiki utilty... :-D

= Old DFwiki requests =
Use this page for requests of bugfixes and new features on the [http://morfeo.upc.es/crom/course/view.php?id=4 NWiki]
The [http://morfeo.upc.es/crom/course/view.php?id=4 DFwikiteam] will keep a sharp eye on the list.

== Miscelaneous ==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

== block wikipage ==

Would be useful to have a block with the content of a wikipage.

If you select 'social' course format you have the option of inserting a social activities block... I don't get that option for the DFWiki, but I think I should so I can add other Moodle activities...

otherwise, when I go to admin/site I can choose to display a topic section where I can put activities and this may be an alternative solution.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced filter, which can include wiki-page into any filterable place. In summ with existing html block it sounds like solution for this suggestion! --[[User:Ne Nashev|Ne Nashev]] 07:52, 26 March 2006 (WST)

== Including wiki page in other Moodle resources ==
I suggest add to standard filters (like Autoformat, Markdown) tag which allow include content (not a link) of wiki page (without editing). This will allow to use wiki as general place for storage texts and use them in resources, lessons and so on.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced this filter

-----
The words "Change to one of the following editors" tells the new user to change to an editor other than the default editor. As this works now, the choice cannot be changed once selected.

In order to avoid this confusion, the teacher should be able to make the default editor the only choice.

In the meantime, the option "Change to one of the following editors" could be moved down below the buttons: save, preview, cancel.

That way new users will be more likely to use the default editor and not lock themselves into one of the other options.
[http://moodle.org/mod/forum/discuss.php?d=39191 forum tread]
-----

== Moodle wide metawiki==

We need a metawiki index to easily link between wikis.
The idea is to have admin tool to manage the wiki-names to be able to
refer easily from one wiki to another like this:

<nowiki> [wiki-name:wikipagename|label to link]</nowiki>

== Special wiki pages ==

=== Wiki reference. ===
To implement biblio references... a link like
<nowiki>[ref:refname]</nowiki> Will lead us to a editing page with a form (maybe a [[database module]] form) to enter the biblio reference ( title, author, isbn, link , pages ... and so on )...
Once we got that any page with a reference to a biblio ref will get printed at its bottom the complete reference and a link to it.

This feature proposal comes within the [[wikibook]] line of work

== weird course interaction stuff ==
If you select 'social' course format you have the option of inserting a social activities block... I don't get that option if I select DFWiki, but I think I should so I can add other Moodle activities... (using Moodle 1.6)

Otherwise, when I go to admin/site I can choose to display 1 topic section where I can put activities and this may be an alternative solution.

Also if I modify a course that had a different format, such as topics ,to be DFWiki the course crashes and you cannot get back to original course format because of the error it throws up.

== Add automatic transliteration of the non-latin page names ==
This must solve all problems with non-latin pagenames.
For each language can exist transliteration to the latin alphabet, that can be placed in language pack. Wiki module can use it to automatically translate page names for internal purposes, especially for passing as parameter in the URL string, while keeping original name for the user. This simple feature can save a lot of trouble with non-latin pagenames.

There is an example of the wiki with this feature: WackoWiki. It's Open Source Project, written on PHP.

= Fixed =

== Inconsistencies with Standard Moodle Behaviour ==

username is used to identify the user in the database instead of userid. This is also displayed to students and teachers instead of user's full name. This is a serious bug because it poses a security risk to students by revealing their userid to all, and it is also a serious issue because anyone can change their username at any time, unlike userid. This problem exists in both Dfwiki and the new wiki.

'''FIXED'''

== Grading system ==
A way to grade users that contribute with the wiki

'''This issue has been implemented ''' in two ways in [[new wiki]]
* Grades
* Votes + ranking block
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22 dfwiki and new wiki documentation]

== Improve differences ==
* Create a more user friendly (WYSIWYG) view for the history/diff mode. Something similar to what was available in the "old" wiki would be enough, but I'm sure you guys can make it even better :-}.

Actually, I just saw the view for the diff format in this wiki (the one where MoodleDOCS are created) and it does just what I want:
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=newdiff%2FBegin+here&dfcontent=wiki_hist_content&ver=5&gid=0&uid=0 example of how it looks]

==End==

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-04T07:02:37Z

Granludo: /* About Moodle groups */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

= NWiki roadmap=
Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features Implemented==

=== Wiki Templates ===

* Add templates so that some content can be made available to all groups when they start using a wiki
Implemented, in release June 2007
=== mailto ===
* a mailto link for dfwiki
has already ben developed must be included in next release [http://moodle.org/mod/forum/discuss.php?d=38991 mailto dfwiki forum thread]

==And finally==
Dynamical online import from mediawiki utilty... :-D

= Old DFwiki requests =
Use this page for requests of bugfixes and new features on the [http://morfeo.upc.es/crom/course/view.php?id=4 NWiki]
The [http://morfeo.upc.es/crom/course/view.php?id=4 DFwikiteam] will keep a sharp eye on the list.

== Miscelaneous ==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

== block wikipage ==

Would be useful to have a block with the content of a wikipage.

If you select 'social' course format you have the option of inserting a social activities block... I don't get that option for the DFWiki, but I think I should so I can add other Moodle activities...

otherwise, when I go to admin/site I can choose to display a topic section where I can put activities and this may be an alternative solution.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced filter, which can include wiki-page into any filterable place. In summ with existing html block it sounds like solution for this suggestion! --[[User:Ne Nashev|Ne Nashev]] 07:52, 26 March 2006 (WST)

== Including wiki page in other Moodle resources ==
I suggest add to standard filters (like Autoformat, Markdown) tag which allow include content (not a link) of wiki page (without editing). This will allow to use wiki as general place for storage texts and use them in resources, lessons and so on.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced this filter

-----
The words "Change to one of the following editors" tells the new user to change to an editor other than the default editor. As this works now, the choice cannot be changed once selected.

In order to avoid this confusion, the teacher should be able to make the default editor the only choice.

In the meantime, the option "Change to one of the following editors" could be moved down below the buttons: save, preview, cancel.

That way new users will be more likely to use the default editor and not lock themselves into one of the other options.
[http://moodle.org/mod/forum/discuss.php?d=39191 forum tread]
-----

== Moodle wide metawiki==

We need a metawiki index to easily link between wikis.
The idea is to have admin tool to manage the wiki-names to be able to
refer easily from one wiki to another like this:

<nowiki> [wiki-name:wikipagename|label to link]</nowiki>

== Special wiki pages ==

=== Wiki reference. ===
To implement biblio references... a link like
<nowiki>[ref:refname]</nowiki> Will lead us to a editing page with a form (maybe a [[database module]] form) to enter the biblio reference ( title, author, isbn, link , pages ... and so on )...
Once we got that any page with a reference to a biblio ref will get printed at its bottom the complete reference and a link to it.

This feature proposal comes within the [[wikibook]] line of work

== Coses rares ==
Ops ops... bug obert.
*Quan edito característiques del curs no em deixa escollir tipus editor, i quan importo continguts les pagines no passen pel parser!
Quan edito i deso llavors es veuen bé. Jo flipo!
* Les pagines wanted i pàgines orfes fan el que els rota
* el wikibook no usa els sinonims.

== weird course interaction stuff ==
If you select 'social' course format you have the option of inserting a social activities block... I don't get that option if I select DFWiki, but I think I should so I can add other Moodle activities... (using Moodle 1.6)

Otherwise, when I go to admin/site I can choose to display 1 topic section where I can put activities and this may be an alternative solution.

Also if I modify a course that had a different format, such as topics ,to be DFWiki the course crashes and you cannot get back to original course format because of the error it throws up.

== Add automatic transliteration of the non-latin page names ==
This must solve all problems with non-latin pagenames.
For each language can exist transliteration to the latin alphabet, that can be placed in language pack. Wiki module can use it to automatically translate page names for internal purposes, especially for passing as parameter in the URL string, while keeping original name for the user. This simple feature can save a lot of trouble with non-latin pagenames.

There is an example of the wiki with this feature: WackoWiki. It's Open Source Project, written on PHP.

= Fixed =

== Inconsistencies with Standard Moodle Behaviour ==

username is used to identify the user in the database instead of userid. This is also displayed to students and teachers instead of user's full name. This is a serious bug because it poses a security risk to students by revealing their userid to all, and it is also a serious issue because anyone can change their username at any time, unlike userid. This problem exists in both Dfwiki and the new wiki.

'''FIXED'''

== Grading system ==
A way to grade users that contribute with the wiki

'''This issue has been implemented ''' in two ways in [[new wiki]]
* Grades
* Votes + ranking block
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22 dfwiki and new wiki documentation]

== Improve differences ==
* Create a more user friendly (WYSIWYG) view for the history/diff mode. Something similar to what was available in the "old" wiki would be enough, but I'm sure you guys can make it even better :-}.

Actually, I just saw the view for the diff format in this wiki (the one where MoodleDOCS are created) and it does just what I want:
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=newdiff%2FBegin+here&dfcontent=wiki_hist_content&ver=5&gid=0&uid=0 example of how it looks]

==End==

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-04T07:01:42Z

Granludo: /* Wiki Templates */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

= NWiki roadmap=
Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features Implemented==

=== Wiki Templates ===

* Add templates so that some content can be made available to all groups when they start using a wiki
Implemented, in release June 2007
=== mailto ===
* a mailto link for dfwiki
has already ben developed must be included in next release [http://moodle.org/mod/forum/discuss.php?d=38991 mailto dfwiki forum thread]

==And finally==
Dynamical online import from mediawiki utilty... :-D

= Old DFwiki requests =
Use this page for requests of bugfixes and new features on the [http://morfeo.upc.es/crom/course/view.php?id=4 NWiki]
The [http://morfeo.upc.es/crom/course/view.php?id=4 DFwikiteam] will keep a sharp eye on the list.

== Miscelaneous ==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

== block wikipage ==

Would be useful to have a block with the content of a wikipage.

If you select 'social' course format you have the option of inserting a social activities block... I don't get that option for the DFWiki, but I think I should so I can add other Moodle activities...

otherwise, when I go to admin/site I can choose to display a topic section where I can put activities and this may be an alternative solution.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced filter, which can include wiki-page into any filterable place. In summ with existing html block it sounds like solution for this suggestion! --[[User:Ne Nashev|Ne Nashev]] 07:52, 26 March 2006 (WST)

== Including wiki page in other Moodle resources ==
I suggest add to standard filters (like Autoformat, Markdown) tag which allow include content (not a link) of wiki page (without editing). This will allow to use wiki as general place for storage texts and use them in resources, lessons and so on.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced this filter

-----
The words "Change to one of the following editors" tells the new user to change to an editor other than the default editor. As this works now, the choice cannot be changed once selected.

In order to avoid this confusion, the teacher should be able to make the default editor the only choice.

In the meantime, the option "Change to one of the following editors" could be moved down below the buttons: save, preview, cancel.

That way new users will be more likely to use the default editor and not lock themselves into one of the other options.
[http://moodle.org/mod/forum/discuss.php?d=39191 forum tread]
-----

==About Moodle groups==
#It appeared from our testing that setting up a wiki to have separate groups kept everyone except group members out of the wiki (including the teacher). In other moodle assignments an instructor is not limited by enabling grouping - which is why you do not put a teacher in a group!
#Visible groups enabled all others to see other groups' wikis, but also appeared to give them editing privileges in another groups' wiki.

== Moodle wide metawiki==

We need a metawiki index to easily link between wikis.
The idea is to have admin tool to manage the wiki-names to be able to
refer easily from one wiki to another like this:

<nowiki> [wiki-name:wikipagename|label to link]</nowiki>

== Special wiki pages ==

=== Wiki reference. ===
To implement biblio references... a link like
<nowiki>[ref:refname]</nowiki> Will lead us to a editing page with a form (maybe a [[database module]] form) to enter the biblio reference ( title, author, isbn, link , pages ... and so on )...
Once we got that any page with a reference to a biblio ref will get printed at its bottom the complete reference and a link to it.

This feature proposal comes within the [[wikibook]] line of work

== Coses rares ==
Ops ops... bug obert.
*Quan edito característiques del curs no em deixa escollir tipus editor, i quan importo continguts les pagines no passen pel parser!
Quan edito i deso llavors es veuen bé. Jo flipo!
* Les pagines wanted i pàgines orfes fan el que els rota
* el wikibook no usa els sinonims.

== weird course interaction stuff ==
If you select 'social' course format you have the option of inserting a social activities block... I don't get that option if I select DFWiki, but I think I should so I can add other Moodle activities... (using Moodle 1.6)

Otherwise, when I go to admin/site I can choose to display 1 topic section where I can put activities and this may be an alternative solution.

Also if I modify a course that had a different format, such as topics ,to be DFWiki the course crashes and you cannot get back to original course format because of the error it throws up.

== Add automatic transliteration of the non-latin page names ==
This must solve all problems with non-latin pagenames.
For each language can exist transliteration to the latin alphabet, that can be placed in language pack. Wiki module can use it to automatically translate page names for internal purposes, especially for passing as parameter in the URL string, while keeping original name for the user. This simple feature can save a lot of trouble with non-latin pagenames.

There is an example of the wiki with this feature: WackoWiki. It's Open Source Project, written on PHP.

= Fixed =

== Inconsistencies with Standard Moodle Behaviour ==

username is used to identify the user in the database instead of userid. This is also displayed to students and teachers instead of user's full name. This is a serious bug because it poses a security risk to students by revealing their userid to all, and it is also a serious issue because anyone can change their username at any time, unlike userid. This problem exists in both Dfwiki and the new wiki.

'''FIXED'''

== Grading system ==
A way to grade users that contribute with the wiki

'''This issue has been implemented ''' in two ways in [[new wiki]]
* Grades
* Votes + ranking block
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22 dfwiki and new wiki documentation]

== Improve differences ==
* Create a more user friendly (WYSIWYG) view for the history/diff mode. Something similar to what was available in the "old" wiki would be enough, but I'm sure you guys can make it even better :-}.

Actually, I just saw the view for the diff format in this wiki (the one where MoodleDOCS are created) and it does just what I want:
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=newdiff%2FBegin+here&dfcontent=wiki_hist_content&ver=5&gid=0&uid=0 example of how it looks]

==End==

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-04T07:01:03Z

Granludo: /* Pending */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

= NWiki roadmap=
Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features Implemented==

=== Wiki Templates ===

* Add templates so that some content can be made available to all groups when they start using a wiki
Implemented, in release June 2007

==And finally==
Dynamical online import from mediawiki utilty... :-D

= Old DFwiki requests =
Use this page for requests of bugfixes and new features on the [http://morfeo.upc.es/crom/course/view.php?id=4 NWiki]
The [http://morfeo.upc.es/crom/course/view.php?id=4 DFwikiteam] will keep a sharp eye on the list.

== Miscelaneous ==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

== block wikipage ==

Would be useful to have a block with the content of a wikipage.

If you select 'social' course format you have the option of inserting a social activities block... I don't get that option for the DFWiki, but I think I should so I can add other Moodle activities...

otherwise, when I go to admin/site I can choose to display a topic section where I can put activities and this may be an alternative solution.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced filter, which can include wiki-page into any filterable place. In summ with existing html block it sounds like solution for this suggestion! --[[User:Ne Nashev|Ne Nashev]] 07:52, 26 March 2006 (WST)

== Including wiki page in other Moodle resources ==
I suggest add to standard filters (like Autoformat, Markdown) tag which allow include content (not a link) of wiki page (without editing). This will allow to use wiki as general place for storage texts and use them in resources, lessons and so on.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced this filter

-----
The words "Change to one of the following editors" tells the new user to change to an editor other than the default editor. As this works now, the choice cannot be changed once selected.

In order to avoid this confusion, the teacher should be able to make the default editor the only choice.

In the meantime, the option "Change to one of the following editors" could be moved down below the buttons: save, preview, cancel.

That way new users will be more likely to use the default editor and not lock themselves into one of the other options.
[http://moodle.org/mod/forum/discuss.php?d=39191 forum tread]
-----

==About Moodle groups==
#It appeared from our testing that setting up a wiki to have separate groups kept everyone except group members out of the wiki (including the teacher). In other moodle assignments an instructor is not limited by enabling grouping - which is why you do not put a teacher in a group!
#Visible groups enabled all others to see other groups' wikis, but also appeared to give them editing privileges in another groups' wiki.

== Moodle wide metawiki==

We need a metawiki index to easily link between wikis.
The idea is to have admin tool to manage the wiki-names to be able to
refer easily from one wiki to another like this:

<nowiki> [wiki-name:wikipagename|label to link]</nowiki>

== Special wiki pages ==

=== Wiki reference. ===
To implement biblio references... a link like
<nowiki>[ref:refname]</nowiki> Will lead us to a editing page with a form (maybe a [[database module]] form) to enter the biblio reference ( title, author, isbn, link , pages ... and so on )...
Once we got that any page with a reference to a biblio ref will get printed at its bottom the complete reference and a link to it.

This feature proposal comes within the [[wikibook]] line of work

== Coses rares ==
Ops ops... bug obert.
*Quan edito característiques del curs no em deixa escollir tipus editor, i quan importo continguts les pagines no passen pel parser!
Quan edito i deso llavors es veuen bé. Jo flipo!
* Les pagines wanted i pàgines orfes fan el que els rota
* el wikibook no usa els sinonims.

== weird course interaction stuff ==
If you select 'social' course format you have the option of inserting a social activities block... I don't get that option if I select DFWiki, but I think I should so I can add other Moodle activities... (using Moodle 1.6)

Otherwise, when I go to admin/site I can choose to display 1 topic section where I can put activities and this may be an alternative solution.

Also if I modify a course that had a different format, such as topics ,to be DFWiki the course crashes and you cannot get back to original course format because of the error it throws up.

== Add automatic transliteration of the non-latin page names ==
This must solve all problems with non-latin pagenames.
For each language can exist transliteration to the latin alphabet, that can be placed in language pack. Wiki module can use it to automatically translate page names for internal purposes, especially for passing as parameter in the URL string, while keeping original name for the user. This simple feature can save a lot of trouble with non-latin pagenames.

There is an example of the wiki with this feature: WackoWiki. It's Open Source Project, written on PHP.

= Fixed =

== Inconsistencies with Standard Moodle Behaviour ==

username is used to identify the user in the database instead of userid. This is also displayed to students and teachers instead of user's full name. This is a serious bug because it poses a security risk to students by revealing their userid to all, and it is also a serious issue because anyone can change their username at any time, unlike userid. This problem exists in both Dfwiki and the new wiki.

'''FIXED'''

== Grading system ==
A way to grade users that contribute with the wiki

'''This issue has been implemented ''' in two ways in [[new wiki]]
* Grades
* Votes + ranking block
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22 dfwiki and new wiki documentation]

== Improve differences ==
* Create a more user friendly (WYSIWYG) view for the history/diff mode. Something similar to what was available in the "old" wiki would be enough, but I'm sure you guys can make it even better :-}.

Actually, I just saw the view for the diff format in this wiki (the one where MoodleDOCS are created) and it does just what I want:
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=newdiff%2FBegin+here&dfcontent=wiki_hist_content&ver=5&gid=0&uid=0 example of how it looks]

==End==

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-04T06:59:08Z

Granludo: /* Even More features */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

= NWiki roadmap=
Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features Implemented==

=== Wiki Templates ===

* Add templates so that some content can be made available to all groups when they start using a wiki
Implemented, in release June 2007

==And finally==
Dynamical online import from mediawiki utilty... :-D

= Old DFwiki requests =
Use this page for requests of bugfixes and new features on the [http://morfeo.upc.es/crom/course/view.php?id=4 NWiki]
The [http://morfeo.upc.es/crom/course/view.php?id=4 DFwikiteam] will keep a sharp eye on the list.

= Pending =

== block wikipage ==

Would be useful to have a block with the content of a wikipage.

If you select 'social' course format you have the option of inserting a social activities block... I don't get that option for the DFWiki, but I think I should so I can add other Moodle activities...

otherwise, when I go to admin/site I can choose to display a topic section where I can put activities and this may be an alternative solution.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced filter, which can include wiki-page into any filterable place. In summ with existing html block it sounds like solution for this suggestion! --[[User:Ne Nashev|Ne Nashev]] 07:52, 26 March 2006 (WST)

== Including wiki page in other Moodle resources ==
I suggest add to standard filters (like Autoformat, Markdown) tag which allow include content (not a link) of wiki page (without editing). This will allow to use wiki as general place for storage texts and use them in resources, lessons and so on.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced this filter

== Diff issues ==
https://docs.moodle.org/en/index.php?title=dfwiki_requests&diff=4827&oldid=4826

That's the kind of interface that would be nice to add to dfwiki.

== mailto ==
* a mailto link for dfwiki has already ben developed must be included in next release
[http://moodle.org/mod/forum/discuss.php?d=38991 mailto dfwiki forum thread]
-----
The words "Change to one of the following editors" tells the new user to change to an editor other than the default editor. As this works now, the choice cannot be changed once selected.

In order to avoid this confusion, the teacher should be able to make the default editor the only choice.

In the meantime, the option "Change to one of the following editors" could be moved down below the buttons: save, preview, cancel.

That way new users will be more likely to use the default editor and not lock themselves into one of the other options.
[http://moodle.org/mod/forum/discuss.php?d=39191 forum tread]
-----

==About Moodle groups==
#It appeared from our testing that setting up a wiki to have separate groups kept everyone except group members out of the wiki (including the teacher). In other moodle assignments an instructor is not limited by enabling grouping - which is why you do not put a teacher in a group!
#Visible groups enabled all others to see other groups' wikis, but also appeared to give them editing privileges in another groups' wiki.

== Moodle wide metawiki==

We need a metawiki index to easily link between wikis.
The idea is to have admin tool to manage the wiki-names to be able to
refer easily from one wiki to another like this:

<nowiki> [wiki-name:wikipagename|label to link]</nowiki>

== Special wiki pages ==

=== Wiki reference. ===
To implement biblio references... a link like
<nowiki>[ref:refname]</nowiki> Will lead us to a editing page with a form (maybe a [[database module]] form) to enter the biblio reference ( title, author, isbn, link , pages ... and so on )...
Once we got that any page with a reference to a biblio ref will get printed at its bottom the complete reference and a link to it.

This feature proposal comes within the [[wikibook]] line of work

== Coses rares ==
Ops ops... bug obert.
*Quan edito característiques del curs no em deixa escollir tipus editor, i quan importo continguts les pagines no passen pel parser!
Quan edito i deso llavors es veuen bé. Jo flipo!
* Les pagines wanted i pàgines orfes fan el que els rota
* el wikibook no usa els sinonims.

== weird course interaction stuff ==
If you select 'social' course format you have the option of inserting a social activities block... I don't get that option if I select DFWiki, but I think I should so I can add other Moodle activities... (using Moodle 1.6)

Otherwise, when I go to admin/site I can choose to display 1 topic section where I can put activities and this may be an alternative solution.

Also if I modify a course that had a different format, such as topics ,to be DFWiki the course crashes and you cannot get back to original course format because of the error it throws up.

== Add automatic transliteration of the non-latin page names ==
This must solve all problems with non-latin pagenames.
For each language can exist transliteration to the latin alphabet, that can be placed in language pack. Wiki module can use it to automatically translate page names for internal purposes, especially for passing as parameter in the URL string, while keeping original name for the user. This simple feature can save a lot of trouble with non-latin pagenames.

There is an example of the wiki with this feature: WackoWiki. It's Open Source Project, written on PHP.

= Fixed =

== Inconsistencies with Standard Moodle Behaviour ==

username is used to identify the user in the database instead of userid. This is also displayed to students and teachers instead of user's full name. This is a serious bug because it poses a security risk to students by revealing their userid to all, and it is also a serious issue because anyone can change their username at any time, unlike userid. This problem exists in both Dfwiki and the new wiki.

'''FIXED'''

== Grading system ==
A way to grade users that contribute with the wiki

'''This issue has been implemented ''' in two ways in [[new wiki]]
* Grades
* Votes + ranking block
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22 dfwiki and new wiki documentation]

== Improve differences ==
* Create a more user friendly (WYSIWYG) view for the history/diff mode. Something similar to what was available in the "old" wiki would be enough, but I'm sure you guys can make it even better :-}.

Actually, I just saw the view for the diff format in this wiki (the one where MoodleDOCS are created) and it does just what I want:
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=newdiff%2FBegin+here&dfcontent=wiki_hist_content&ver=5&gid=0&uid=0 example of how it looks]

==End==

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-04T06:58:00Z

Granludo: /* Templates */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

= NWiki roadmap=
Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

==And finally==
Dynamical online import from mediawiki utilty... :-D

= Old DFwiki requests =
Use this page for requests of bugfixes and new features on the [http://morfeo.upc.es/crom/course/view.php?id=4 NWiki]
The [http://morfeo.upc.es/crom/course/view.php?id=4 DFwikiteam] will keep a sharp eye on the list.

= Pending =

== block wikipage ==

Would be useful to have a block with the content of a wikipage.

If you select 'social' course format you have the option of inserting a social activities block... I don't get that option for the DFWiki, but I think I should so I can add other Moodle activities...

otherwise, when I go to admin/site I can choose to display a topic section where I can put activities and this may be an alternative solution.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced filter, which can include wiki-page into any filterable place. In summ with existing html block it sounds like solution for this suggestion! --[[User:Ne Nashev|Ne Nashev]] 07:52, 26 March 2006 (WST)

== Including wiki page in other Moodle resources ==
I suggest add to standard filters (like Autoformat, Markdown) tag which allow include content (not a link) of wiki page (without editing). This will allow to use wiki as general place for storage texts and use them in resources, lessons and so on.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced this filter

== Diff issues ==
https://docs.moodle.org/en/index.php?title=dfwiki_requests&diff=4827&oldid=4826

That's the kind of interface that would be nice to add to dfwiki.

== mailto ==
* a mailto link for dfwiki has already ben developed must be included in next release
[http://moodle.org/mod/forum/discuss.php?d=38991 mailto dfwiki forum thread]
-----
The words "Change to one of the following editors" tells the new user to change to an editor other than the default editor. As this works now, the choice cannot be changed once selected.

In order to avoid this confusion, the teacher should be able to make the default editor the only choice.

In the meantime, the option "Change to one of the following editors" could be moved down below the buttons: save, preview, cancel.

That way new users will be more likely to use the default editor and not lock themselves into one of the other options.
[http://moodle.org/mod/forum/discuss.php?d=39191 forum tread]
-----

==About Moodle groups==
#It appeared from our testing that setting up a wiki to have separate groups kept everyone except group members out of the wiki (including the teacher). In other moodle assignments an instructor is not limited by enabling grouping - which is why you do not put a teacher in a group!
#Visible groups enabled all others to see other groups' wikis, but also appeared to give them editing privileges in another groups' wiki.

== Moodle wide metawiki==

We need a metawiki index to easily link between wikis.
The idea is to have admin tool to manage the wiki-names to be able to
refer easily from one wiki to another like this:

<nowiki> [wiki-name:wikipagename|label to link]</nowiki>

== Special wiki pages ==

=== Wiki reference. ===
To implement biblio references... a link like
<nowiki>[ref:refname]</nowiki> Will lead us to a editing page with a form (maybe a [[database module]] form) to enter the biblio reference ( title, author, isbn, link , pages ... and so on )...
Once we got that any page with a reference to a biblio ref will get printed at its bottom the complete reference and a link to it.

This feature proposal comes within the [[wikibook]] line of work

== Coses rares ==
Ops ops... bug obert.
*Quan edito característiques del curs no em deixa escollir tipus editor, i quan importo continguts les pagines no passen pel parser!
Quan edito i deso llavors es veuen bé. Jo flipo!
* Les pagines wanted i pàgines orfes fan el que els rota
* el wikibook no usa els sinonims.

== weird course interaction stuff ==
If you select 'social' course format you have the option of inserting a social activities block... I don't get that option if I select DFWiki, but I think I should so I can add other Moodle activities... (using Moodle 1.6)

Otherwise, when I go to admin/site I can choose to display 1 topic section where I can put activities and this may be an alternative solution.

Also if I modify a course that had a different format, such as topics ,to be DFWiki the course crashes and you cannot get back to original course format because of the error it throws up.

== Add automatic transliteration of the non-latin page names ==
This must solve all problems with non-latin pagenames.
For each language can exist transliteration to the latin alphabet, that can be placed in language pack. Wiki module can use it to automatically translate page names for internal purposes, especially for passing as parameter in the URL string, while keeping original name for the user. This simple feature can save a lot of trouble with non-latin pagenames.

There is an example of the wiki with this feature: WackoWiki. It's Open Source Project, written on PHP.

= Fixed =

== Inconsistencies with Standard Moodle Behaviour ==

username is used to identify the user in the database instead of userid. This is also displayed to students and teachers instead of user's full name. This is a serious bug because it poses a security risk to students by revealing their userid to all, and it is also a serious issue because anyone can change their username at any time, unlike userid. This problem exists in both Dfwiki and the new wiki.

'''FIXED'''

== Grading system ==
A way to grade users that contribute with the wiki

'''This issue has been implemented ''' in two ways in [[new wiki]]
* Grades
* Votes + ranking block
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22 dfwiki and new wiki documentation]

== Improve differences ==
* Create a more user friendly (WYSIWYG) view for the history/diff mode. Something similar to what was available in the "old" wiki would be enough, but I'm sure you guys can make it even better :-}.

Actually, I just saw the view for the diff format in this wiki (the one where MoodleDOCS are created) and it does just what I want:
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=newdiff%2FBegin+here&dfcontent=wiki_hist_content&ver=5&gid=0&uid=0 example of how it looks]

==End==

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-04T06:57:03Z

Granludo:

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

= NWiki roadmap=
Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

==And finally==
Dynamical online import from mediawiki utilty... :-D

= Old DFwiki requests =
Use this page for requests of bugfixes and new features on the [http://morfeo.upc.es/crom/course/view.php?id=4 NWiki]
The [http://morfeo.upc.es/crom/course/view.php?id=4 DFwikiteam] will keep a sharp eye on the list.

= Pending =

== Templates ==

* Add templates so that some content can be made available to all groups when they start using a wiki (coming up April 2007)

== block wikipage ==

Would be useful to have a block with the content of a wikipage.

If you select 'social' course format you have the option of inserting a social activities block... I don't get that option for the DFWiki, but I think I should so I can add other Moodle activities...

otherwise, when I go to admin/site I can choose to display a topic section where I can put activities and this may be an alternative solution.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced filter, which can include wiki-page into any filterable place. In summ with existing html block it sounds like solution for this suggestion! --[[User:Ne Nashev|Ne Nashev]] 07:52, 26 March 2006 (WST)

== Including wiki page in other Moodle resources ==
I suggest add to standard filters (like Autoformat, Markdown) tag which allow include content (not a link) of wiki page (without editing). This will allow to use wiki as general place for storage texts and use them in resources, lessons and so on.

Note: In theme [http://moodle.org/mod/forum/discuss.php?d=42325 Including wiki page in other Moodle resources] was announced this filter

== Diff issues ==
https://docs.moodle.org/en/index.php?title=dfwiki_requests&diff=4827&oldid=4826

That's the kind of interface that would be nice to add to dfwiki.

== mailto ==
* a mailto link for dfwiki has already ben developed must be included in next release
[http://moodle.org/mod/forum/discuss.php?d=38991 mailto dfwiki forum thread]
-----
The words "Change to one of the following editors" tells the new user to change to an editor other than the default editor. As this works now, the choice cannot be changed once selected.

In order to avoid this confusion, the teacher should be able to make the default editor the only choice.

In the meantime, the option "Change to one of the following editors" could be moved down below the buttons: save, preview, cancel.

That way new users will be more likely to use the default editor and not lock themselves into one of the other options.
[http://moodle.org/mod/forum/discuss.php?d=39191 forum tread]
-----

==About Moodle groups==
#It appeared from our testing that setting up a wiki to have separate groups kept everyone except group members out of the wiki (including the teacher). In other moodle assignments an instructor is not limited by enabling grouping - which is why you do not put a teacher in a group!
#Visible groups enabled all others to see other groups' wikis, but also appeared to give them editing privileges in another groups' wiki.

== Moodle wide metawiki==

We need a metawiki index to easily link between wikis.
The idea is to have admin tool to manage the wiki-names to be able to
refer easily from one wiki to another like this:

<nowiki> [wiki-name:wikipagename|label to link]</nowiki>

== Special wiki pages ==

=== Wiki reference. ===
To implement biblio references... a link like
<nowiki>[ref:refname]</nowiki> Will lead us to a editing page with a form (maybe a [[database module]] form) to enter the biblio reference ( title, author, isbn, link , pages ... and so on )...
Once we got that any page with a reference to a biblio ref will get printed at its bottom the complete reference and a link to it.

This feature proposal comes within the [[wikibook]] line of work

== Coses rares ==
Ops ops... bug obert.
*Quan edito característiques del curs no em deixa escollir tipus editor, i quan importo continguts les pagines no passen pel parser!
Quan edito i deso llavors es veuen bé. Jo flipo!
* Les pagines wanted i pàgines orfes fan el que els rota
* el wikibook no usa els sinonims.

== weird course interaction stuff ==
If you select 'social' course format you have the option of inserting a social activities block... I don't get that option if I select DFWiki, but I think I should so I can add other Moodle activities... (using Moodle 1.6)

Otherwise, when I go to admin/site I can choose to display 1 topic section where I can put activities and this may be an alternative solution.

Also if I modify a course that had a different format, such as topics ,to be DFWiki the course crashes and you cannot get back to original course format because of the error it throws up.

== Add automatic transliteration of the non-latin page names ==
This must solve all problems with non-latin pagenames.
For each language can exist transliteration to the latin alphabet, that can be placed in language pack. Wiki module can use it to automatically translate page names for internal purposes, especially for passing as parameter in the URL string, while keeping original name for the user. This simple feature can save a lot of trouble with non-latin pagenames.

There is an example of the wiki with this feature: WackoWiki. It's Open Source Project, written on PHP.

= Fixed =

== Inconsistencies with Standard Moodle Behaviour ==

username is used to identify the user in the database instead of userid. This is also displayed to students and teachers instead of user's full name. This is a serious bug because it poses a security risk to students by revealing their userid to all, and it is also a serious issue because anyone can change their username at any time, unlike userid. This problem exists in both Dfwiki and the new wiki.

'''FIXED'''

== Grading system ==
A way to grade users that contribute with the wiki

'''This issue has been implemented ''' in two ways in [[new wiki]]
* Grades
* Votes + ranking block
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22 dfwiki and new wiki documentation]

== Improve differences ==
* Create a more user friendly (WYSIWYG) view for the history/diff mode. Something similar to what was available in the "old" wiki would be enough, but I'm sure you guys can make it even better :-}.

Actually, I just saw the view for the diff format in this wiki (the one where MoodleDOCS are created) and it does just what I want:
[http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=newdiff%2FBegin+here&dfcontent=wiki_hist_content&ver=5&gid=0&uid=0 example of how it looks]

==End==

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Tiddlywiki integration

2007-06-04T06:53:25Z

Granludo: /* Integration with New Wiki */

= Tiddlywiki =
Tiddlywiki is a MicroContent WikiWikiWeb created by Jeremy Ruston and a community of independent developers. It's written in HTML, CSS and JavaScript to run on any modern browser without needing any server side logic. It allows anyone to create personal self contained hypertext documents that can be posted to a web server, sent by email or kept on a USB thumb drive to make a wiki-on-a-stick.
Tiddlywiki is published under BSD license.

= Integration with New Wiki =

New wiki can act as a Server Side couterpart for tiddlywiki. DFwikiTeam is developing some tiddlywiki plugins and extensions to new wiki con wiki pages can travel both ways ( tiddlywiki -> moodle -> tiddlywiki )

Download at [http://morfeo.upc.es/crom/course/view.php?id=4 dfwikilabs] and [http://moodle.tiddlyspot.com moodle.tiddlyspot.com]

== See also ==

*Using Moodle [http://moodle.org/mod/forum/view.php?f=366 Wiki module forum]
*[http://download.moodle.org/docs/using_moodle/ch11_wikis.pdf Using Moodle Chapter 11: Wikis]
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=37671 Template for wikis] forum discussion
*[[Wiki development]]
* [[NWiki roadmap]]
* [[Dfwiki]]
* [[Development:Wiki requirements]]

[[Category:Teacher]]
[[Category:Wiki]]

Broken/NWiki roadmap

2007-06-04T06:52:41Z

Granludo: /* Most likely */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ? [[Tiddlywiki integration]]

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

==And finally==
Dynamical online import from mediawiki utilty... :-D

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Tiddlywiki integration

2007-06-04T06:52:04Z

Granludo: /* See also */

= Tiddlywiki =
Tiddlywiki is a MicroContent WikiWikiWeb created by Jeremy Ruston and a community of independent developers. It's written in HTML, CSS and JavaScript to run on any modern browser without needing any server side logic. It allows anyone to create personal self contained hypertext documents that can be posted to a web server, sent by email or kept on a USB thumb drive to make a wiki-on-a-stick.
Tiddlywiki is published under BSD license.

= Integration with New Wiki =

New wiki can act as a Server Side couterpart for tiddlywiki. DFwikiTeam is developing some tiddlywiki plugins and extensions to new wiki con wiki pages can travel both ways ( tiddlywiki -> moodle -> tiddlywiki )

Download at [http://morfeo.upc.es/crom/course/view.php?id=4 dfwikilabs]

== See also ==

*Using Moodle [http://moodle.org/mod/forum/view.php?f=366 Wiki module forum]
*[http://download.moodle.org/docs/using_moodle/ch11_wikis.pdf Using Moodle Chapter 11: Wikis]
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=37671 Template for wikis] forum discussion
*[[Wiki development]]
* [[NWiki roadmap]]
* [[Dfwiki]]
* [[Development:Wiki requirements]]

[[Category:Teacher]]
[[Category:Wiki]]

Broken/NWiki roadmap

2007-06-03T14:57:39Z

Granludo: /* Even More features */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features==
*We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].
*Section edit.
*borrow some interface ideas from OUWiki

==And finally==
Dynamical online import from mediawiki utilty... :-D

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-03T14:56:55Z

Granludo:

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==Even More features==
We need to implement some [[Special pages]] like mediawiki's [[Recent changes]].

==And finally==
Dynamical online import from mediawiki utilty... :-D

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/NWiki roadmap

2007-06-03T14:52:32Z

Granludo: /* se also */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]
*[[Development:Wiki requirements]]

Broken/Wiki requirements

2007-06-03T14:50:58Z

Granludo: /* Design Objectives */

==Moodle wiki purpose==

To provide a way for students, teachers and other Moodle participants to create an organic, on-line document collaboratively.

==Key features==

# Pages can be created and linked using simple wiki methods.
# All Moodle text formats can be supported.
# Editing and viewing can be restricted by Moodle roles (i.e. currently: Students, Groups, Teachers).
# Images can be easily inserted into the text of a wiki.
# Attachments can be made to wiki pages.
# Must be fully compliant with Moodle backup and restore.
# Must be fully compliant with Moodle logging and activity tracking.
# Must provide a method of grading (see assignment module). Grading should be optional on a per-wiki basis.
# Allow importing of external documents to create a wiki or add to an existing one.
# Allow exporting to an external document.
# Allow refactoring/moving/deleting pages with appropriate permissions.
(from Martin's list):

==Basic Operation==
'''Create the wiki:'''- Log in/ Turn editing on/ Add and activity/ Wiki
- Fill in wiki parameters (Leave defaults and experiment later. Everything except the inital page fields can be changed.)

'''Adding pages:'''

- Edit the first (& only page)/ Type the name of the new page you want within square brackets/ Click Save. The new page link is displayed beside a question mark./ Click the question mark to open the new page for data entry.

- pages can be added from any page.
(Suggestion: On your start page, type "PageIndex" and perhaps "Site Map" and/or "Newest Pages" so that the user is alerted to these options immediately on entering the wiki. They also appear on the "Choose wiki links" drop down at the top of the wiki window.

The wiki is one of the most powerful tools within moodle and suitable for many educational & administrative functions including:

# a wonderful way to encourage students to build, debate and share a summary of their course content as they work
# a great way to deliver your school administrative manuals i.e. teachers manual; student manuals. They are searchable, interlinked automatically & able to be continuously updated showing who, when & how the updates were made.

Currently '''some wiki features do not work reliably''':
* '''search''' does not find page titles (so make sure that the page title is repeated somewhere within the page itself).
* '''export''' does not export all wiki content
* '''delete pages''' and '''strip pages''' often do not work. (the most common error message is: ''Course Module is incorrect'', which sometimes can be bypassed by using another theme. formal_white is known to cause such problems.)
* '''moodle editor does not handle hyperlinks correctly'''. i.e. All links must be manually placed within square brackets rather than embedded as HTML links.

==Design Objectives==
* The Wiki should support exactly the same text formats in Moodle core as you find everywhere else (see weblib.php for standard functions, eg format_text). ie Moodle format, HTML format, Markdown, etc. Any new formats need to go in the core so they are available everywhere, and this needs to be discussed very well. We only JUST removed the old Wiki-like format to reduce confusion with the current Wiki and I don't want more of this confusion from a rushed implementation.
[[NWiki]] suports old wiki format, HTMLEditor and Mediawiki syntax --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 09:50, 3 June 2007 (CDT)
* Linking should support both CamelCase and [Bracket] styles, and also automatic linking on the fly (a la Glossary).
Since wikipedia abandoned CamelCase I don't think we should keep it --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 09:50, 3 June 2007 (CDT)
* Upgrading from the old system to any new one should be seamless and problem-free (this includes restoring old backups from 1.4, for example).
Done --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 09:50, 3 June 2007 (CDT)
* The idea with eWiki was to build on the work of the eWiki team in future. Unfortunately, so many hacks needed to be made to their monolithic script that this became almost impossible. I would like to see a lot of thought put into a very cleanly-designed architecture for the Wiki in future, something that is easy to extend and maintain (and also to use).
The NWiki architecture has been redesigned for this purpose See the [http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.html phpdoc documentation]--[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 09:50, 3 June 2007 (CDT)
* I really like MediaWiki, as this Wiki is becoming a defacto standard (for good reason) and it would be good to be compatible in some way with it. Perhaps we can use part of it as a library for us. However, the Moodle Wiki is a COMPONENT within the larger Moodle system and has a very different focus to MediaWiki (which is designed for large standalone web sites) ... much thought should be given to making our Wiki work very closely with other modules, rather than another module that tries to do everything itself. It should do exactly what it needs to do and no more.
OK see [http://morfeo.upc.es/crom/mod/wiki/view.php?id=22&page=view/NWikiMarkupReference&gid=0&uid=0 NWiki suport for mediawiki markup]
* Support for media in a very clean way is a must. This is probably my biggest criticism of the current eWiki version ... attaching images and video etc is really awkward and doesn't look good.
NWiki suports this still in a weird way, but we plan to implement it just like
mediawiki: as wiki pages. We want also to integrate media with digital repositories--[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 09:50, 3 June 2007 (CDT)

== New wiki (old)issue list ==
This list is very old, we (dfwikiteam) have commented.
Rigth now (may 07) the nwiki development plans are
being worked out in the [[NWiki roadmap]] page. --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 09:40, 3 June 2007 (CDT)
# '''There is no userid column in the wiki_pages table (author char-string instead). Must be supported in migration too.''' userid has been there since June06
# '''There is no intro and introformat in the wiki table.'''. I can't remember when Eloy Lafuente added these two columns... A long, long time ago...
# '''In the upgrade from wiki to dfwiki, as there aren't userids, my wiki-pages were assigned to "guest". Once more, userid seems to be critical.'''. Solved. We are using userids. In case of mismatching, we assign the page to the current user.
# '''Wikis having different wiki_entries (group or user ones) have no support in new wiki (only one simultaneous line of versions is available?) so we get a lot of duplicate version errors with data-lost of such pedagogical feature! Or am I losing anything? With only groupid and version in the UK of the table, old student wikis can fit in the new one. Once more, userid!''' Solved UNIQUE KEY `wiki_pages_uk` (`pagename`, `version`, `dfwiki`, `groupid`, `userid`, `ownerid`).
# '''Search doesn't work for diacritics. And/or match is performed with case matching (I think).''' Search has some bugs. We hae to improve it. Minor priority.
# '''Search seems to work against titles and contents always (no matter the checkbox was selected or no). Perhaps it's due to that usage of globals? Ah! After a second try I saw that such checkbox is to decide to show the details of the search in the body of the page. Perhaps the title should be changed to be a bit more clear? Something like "show results page" and some sort of nice help...''' I don't think so. I'll review it.
# '''The useful "What links here" block isn't available.''' Now it is.
# '''Wiki backup and restore don't support individual activities!''' Why not? Where is the problem?
# '''Wikis aren't included in the backup/restore at all!''' Backup/Restore are working correctly. We have not noticed any bug.
# '''Blocks system. Would be difficult to migrate to core block system?''' Migrated in May06.
# '''UTF-8 migration always get teacher_main_language() and it should get page author language! If we know the author responsible for the version, we must look for their original encoding instead of using the teacher one! Similar to forum_posts (if I'm not wrong). And we should know the user: userid again! ;-)''' I'm gonna take a look to this.
# '''In the wiki_pages table there is one "dfwiki" field. Should be "wikiid". Such name doesn't sound ok. (although it's possible that migation become painful, so we can change it in the future...).''' I know. Pain! It will be changed with the API integration.
# '''dfwiki is inside a lot of places in code. It should go out (although it's possible that migation become painful, so we can change it in the future...).''' Yes, variables, comments... We have to clean it out.
# '''globals, globals, globals usage should be out. Just request parameters filtered with xxxx_param() functions.''' There is only a big one. We are making it smaller every day.
# '''Attachment storage (as I've seen in the old-new migration script) seems to be a bit special with a lot of "dfwikiXXXX" dirs generated.''' I made a script to rename all these dirs.
# '''The old-new migration script seems to be twice, once under the wikimigrate dir (the used one) and under the mod directory (unused?).''' I gonna bet for duplicated code...

==See also==
*[[NWiki roadmap]]
*[http://moodle.org/mod/forum/discuss.php?d=21493 Wiki development] forum discussion
*[[Dfwiki]]
[[Category:Developer]]
[[Category:Wiki]]

Broken/Wiki requirements

2007-06-03T14:41:41Z

Granludo: /* New wiki issue list */

==Moodle wiki purpose==

To provide a way for students, teachers and other Moodle participants to create an organic, on-line document collaboratively.

==Key features==

# Pages can be created and linked using simple wiki methods.
# All Moodle text formats can be supported.
# Editing and viewing can be restricted by Moodle roles (i.e. currently: Students, Groups, Teachers).
# Images can be easily inserted into the text of a wiki.
# Attachments can be made to wiki pages.
# Must be fully compliant with Moodle backup and restore.
# Must be fully compliant with Moodle logging and activity tracking.
# Must provide a method of grading (see assignment module). Grading should be optional on a per-wiki basis.
# Allow importing of external documents to create a wiki or add to an existing one.
# Allow exporting to an external document.
# Allow refactoring/moving/deleting pages with appropriate permissions.
(from Martin's list):

==Basic Operation==
'''Create the wiki:'''- Log in/ Turn editing on/ Add and activity/ Wiki
- Fill in wiki parameters (Leave defaults and experiment later. Everything except the inital page fields can be changed.)

'''Adding pages:'''

- Edit the first (& only page)/ Type the name of the new page you want within square brackets/ Click Save. The new page link is displayed beside a question mark./ Click the question mark to open the new page for data entry.

- pages can be added from any page.
(Suggestion: On your start page, type "PageIndex" and perhaps "Site Map" and/or "Newest Pages" so that the user is alerted to these options immediately on entering the wiki. They also appear on the "Choose wiki links" drop down at the top of the wiki window.

The wiki is one of the most powerful tools within moodle and suitable for many educational & administrative functions including:

# a wonderful way to encourage students to build, debate and share a summary of their course content as they work
# a great way to deliver your school administrative manuals i.e. teachers manual; student manuals. They are searchable, interlinked automatically & able to be continuously updated showing who, when & how the updates were made.

Currently '''some wiki features do not work reliably''':
* '''search''' does not find page titles (so make sure that the page title is repeated somewhere within the page itself).
* '''export''' does not export all wiki content
* '''delete pages''' and '''strip pages''' often do not work. (the most common error message is: ''Course Module is incorrect'', which sometimes can be bypassed by using another theme. formal_white is known to cause such problems.)
* '''moodle editor does not handle hyperlinks correctly'''. i.e. All links must be manually placed within square brackets rather than embedded as HTML links.

==Design Objectives==
* The Wiki should support exactly the same text formats in Moodle core as you find everywhere else (see weblib.php for standard functions, eg format_text). ie Moodle format, HTML format, Markdown, etc. Any new formats need to go in the core so they are available everywhere, and this needs to be discussed very well. We only JUST removed the old Wiki-like format to reduce confusion with the current Wiki and I don't want more of this confusion from a rushed implementation.

* Linking should support both CamelCase and [Bracket] styles, and also automatic linking on the fly (a la Glossary).

* Upgrading from the old system to any new one should be seamless and problem-free (this includes restoring old backups from 1.4, for example).

* The idea with eWiki was to build on the work of the eWiki team in future. Unfortunately, so many hacks needed to be made to their monolithic script that this became almost impossible. I would like to see a lot of thought put into a very cleanly-designed architecture for the Wiki in future, something that is easy to extend and maintain (and also to use).

* I really like MediaWiki, as this Wiki is becoming a defacto standard (for good reason) and it would be good to be compatible in some way with it. Perhaps we can use part of it as a library for us. However, the Moodle Wiki is a COMPONENT within the larger Moodle system and has a very different focus to MediaWiki (which is designed for large standalone web sites) ... much thought should be given to making our Wiki work very closely with other modules, rather than another module that tries to do everything itself. It should do exactly what it needs to do and no more.

* Support for media in a very clean way is a must. This is probably my biggest criticism of the current eWiki version ... attaching images and video etc is really awkward and doesn't look good.

== New wiki (old)issue list ==
This list is very old, we (dfwikiteam) have commented.
Rigth now (may 07) the nwiki development plans are
being worked out in the [[NWiki roadmap]] page. --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 09:40, 3 June 2007 (CDT)
# '''There is no userid column in the wiki_pages table (author char-string instead). Must be supported in migration too.''' userid has been there since June06
# '''There is no intro and introformat in the wiki table.'''. I can't remember when Eloy Lafuente added these two columns... A long, long time ago...
# '''In the upgrade from wiki to dfwiki, as there aren't userids, my wiki-pages were assigned to "guest". Once more, userid seems to be critical.'''. Solved. We are using userids. In case of mismatching, we assign the page to the current user.
# '''Wikis having different wiki_entries (group or user ones) have no support in new wiki (only one simultaneous line of versions is available?) so we get a lot of duplicate version errors with data-lost of such pedagogical feature! Or am I losing anything? With only groupid and version in the UK of the table, old student wikis can fit in the new one. Once more, userid!''' Solved UNIQUE KEY `wiki_pages_uk` (`pagename`, `version`, `dfwiki`, `groupid`, `userid`, `ownerid`).
# '''Search doesn't work for diacritics. And/or match is performed with case matching (I think).''' Search has some bugs. We hae to improve it. Minor priority.
# '''Search seems to work against titles and contents always (no matter the checkbox was selected or no). Perhaps it's due to that usage of globals? Ah! After a second try I saw that such checkbox is to decide to show the details of the search in the body of the page. Perhaps the title should be changed to be a bit more clear? Something like "show results page" and some sort of nice help...''' I don't think so. I'll review it.
# '''The useful "What links here" block isn't available.''' Now it is.
# '''Wiki backup and restore don't support individual activities!''' Why not? Where is the problem?
# '''Wikis aren't included in the backup/restore at all!''' Backup/Restore are working correctly. We have not noticed any bug.
# '''Blocks system. Would be difficult to migrate to core block system?''' Migrated in May06.
# '''UTF-8 migration always get teacher_main_language() and it should get page author language! If we know the author responsible for the version, we must look for their original encoding instead of using the teacher one! Similar to forum_posts (if I'm not wrong). And we should know the user: userid again! ;-)''' I'm gonna take a look to this.
# '''In the wiki_pages table there is one "dfwiki" field. Should be "wikiid". Such name doesn't sound ok. (although it's possible that migation become painful, so we can change it in the future...).''' I know. Pain! It will be changed with the API integration.
# '''dfwiki is inside a lot of places in code. It should go out (although it's possible that migation become painful, so we can change it in the future...).''' Yes, variables, comments... We have to clean it out.
# '''globals, globals, globals usage should be out. Just request parameters filtered with xxxx_param() functions.''' There is only a big one. We are making it smaller every day.
# '''Attachment storage (as I've seen in the old-new migration script) seems to be a bit special with a lot of "dfwikiXXXX" dirs generated.''' I made a script to rename all these dirs.
# '''The old-new migration script seems to be twice, once under the wikimigrate dir (the used one) and under the mod directory (unused?).''' I gonna bet for duplicated code...

==See also==
*[[NWiki roadmap]]
*[http://moodle.org/mod/forum/discuss.php?d=21493 Wiki development] forum discussion
*[[Dfwiki]]
[[Category:Developer]]
[[Category:Wiki]]

Broken/id:1741

2007-06-03T14:40:26Z

Granludo: /* New wiki (old)issue list */

What about wrapping the already existing bits of Moodle together to create a new wiki (oh, no...not another wiki) My thinking is that we already have the following tools:

* a "standard" markup (Markdown)
* several ways to store attachments/images/binary files in various modules
* filters for multimedia, Latex, Math and the like.

Could these instances be refactored and refined then called from the wiki parser? This would avoid re-inventing the wheel(s) and simplify maintanence of system. I guess I'm suggesting a "plugin" mechanism where each of these tools could be added to Moodle and then assembled to form the wiki rather than create a monolithic and eventually cumbersome script. If all wiki pages are simply text, the wiki script will just dole out portions of each page to the proper tool. I'm imagining these tools could be used everywhere in Moodle, rather than being specific to the wiki...kind of following the unix philosophy of assembling several simpler tools to perform complicated tasks. Looking at Martin D's post outlining the must-have features, he alludes to this approach when discussing Mediawiki. Posts in other discussions have as well.

Regarding feature ideas, I would recommend folks look at Uniwakka. This "academically oriented" wiki engine has some great possibilities including support for MathML (better than latex filter for sophisticated maths?), Latex, chemistry (a personal favorite), and bibliographies; it exports/imports OpenOffice documents directly and exports Latex versions of the pages. Veeerryy nice!

Thoughts?

~Steve
----
These are interesting thougts Steve, in fact it was my fisrt idea twio years ago when I longed to develop tools for the current wiki. But teh coding and features of the current wiki convinced me that we needed a new wiki from scratch. I vbeliebe that the aproach you propose can be implemented once we have the [[DFWiki]] up and official.

By the way we are already working on a wiki parser compilant with mediawiki, comming soon .

Ludo - DFWikiteam
----

The features I find myself often missing in the current Moodle Wiki are:

* editable sections/sub-pages
* in history: ability to compare two arbitrary versions

These are things I have grown used to in MediaWiki.

In the markup department I'd like to see:

* at minimum: a basic wiki-like markup as the default
* optionally: ability to define your own markup
* optionally 2: ability to define what if the default markup

I find that most cases people will use the default markup. I don't use the Markdown format although I hear great things about it from people who do use it. I wouldn't want to make the users at our site transfer to Markdown, when I didn't even mention it in the basic training sessions they participated in.

~Jussi

I have used a number of different wiki systems and some of them with students. I've tried [http://www.twiki.org/ TWiki] and found that students with no knowledge of html take to it quite readily (and do understand the wiki way of makinglinks). I use different versions of [http://www.tiddlywiki.com/ Tiddlywiki] but the markup drives me bonkers (eg because links use | you cannot encluse a URL inside a table). I have also helped faculty use the Moodle wiki (Moodle v 1.5.1) for class but what I don't like about it is the html editor approach. A student actually managed to crunch the wiki at one point with mangled html code pasted in from MS Word which was then edited! My favourite and what I consider to be the most flexible markup system is [http://www.centeredwork.com/xilize2/index.html Xilize] which at version 2 is powerful strong. There's a plugin for Jedit which I use to create web pages.

Personally, I hope that the Moodle wiki behaves more like a 'traditional' wiki with CamelCase links and a default markup system that's easy to comprehend and orthogonal (I don't much like the accent on quotes in Markdown).

For me the selling point of Moodle wiki for use in a course is the flexibility of access control -- one can configure it to be individual access or group access, etc etc. If it defaulted to a wiki like markup and were more stable (especially with Postgres back end) I and many faculty would be happy campers.

~Markpea 25 Jan 2006

[[Category:Developer|Wiki requirements]]

I think you should either put the same information that you find in this link or the link itself in the wiki part of the documentation. I needed to know about the markup used in Moodle's wiki, and it would be nice if it were laid out right here.

I didn't know if it were more appropriate to link to this previous documentation, or if it would be better to re-create it.

[http://moodle.org/help.php?module=wiki&file=howtowiki.html /moodle.org help, how to wiki]

Thank you,
atw

== New wiki (old)issue list ==
This list is very old, we (dfwikiteam) have commented.
Rigth now (may 07) the nwiki development plans are
being worked out in the [[NWiki roadmap]] page. --[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 09:40, 3 June 2007 (CDT)
# '''There is no userid column in the wiki_pages table (author char-string instead). Must be supported in migration too.''' userid has been there since June06
# '''There is no intro and introformat in the wiki table.'''. I can't remember when Eloy Lafuente added these two columns... A long, long time ago...
# '''In the upgrade from wiki to dfwiki, as there aren't userids, my wiki-pages were assigned to "guest". Once more, userid seems to be critical.'''. Solved. We are using userids. In case of mismatching, we assign the page to the current user.
# '''Wikis having different wiki_entries (group or user ones) have no support in new wiki (only one simultaneous line of versions is available?) so we get a lot of duplicate version errors with data-lost of such pedagogical feature! Or am I losing anything? With only groupid and version in the UK of the table, old student wikis can fit in the new one. Once more, userid!''' Solved UNIQUE KEY `wiki_pages_uk` (`pagename`, `version`, `dfwiki`, `groupid`, `userid`, `ownerid`).
# '''Search doesn't work for diacritics. And/or match is performed with case matching (I think).''' Search has some bugs. We hae to improve it. Minor priority.
# '''Search seems to work against titles and contents always (no matter the checkbox was selected or no). Perhaps it's due to that usage of globals? Ah! After a second try I saw that such checkbox is to decide to show the details of the search in the body of the page. Perhaps the title should be changed to be a bit more clear? Something like "show results page" and some sort of nice help...''' I don't think so. I'll review it.
# '''The useful "What links here" block isn't available.''' Now it is.
# '''Wiki backup and restore don't support individual activities!''' Why not? Where is the problem?
# '''Wikis aren't included in the backup/restore at all!''' Backup/Restore are working correctly. We have not noticed any bug.
# '''Blocks system. Would be difficult to migrate to core block system?''' Migrated in May06.
# '''UTF-8 migration always get teacher_main_language() and it should get page author language! If we know the author responsible for the version, we must look for their original encoding instead of using the teacher one! Similar to forum_posts (if I'm not wrong). And we should know the user: userid again! ;-)''' I'm gonna take a look to this.
# '''In the wiki_pages table there is one "dfwiki" field. Should be "wikiid". Such name doesn't sound ok. (although it's possible that migation become painful, so we can change it in the future...).''' I know. Pain! It will be changed with the API integration.
# '''dfwiki is inside a lot of places in code. It should go out (although it's possible that migation become painful, so we can change it in the future...).''' Yes, variables, comments... We have to clean it out.
# '''globals, globals, globals usage should be out. Just request parameters filtered with xxxx_param() functions.''' There is only a big one. We are making it smaller every day.
# '''Attachment storage (as I've seen in the old-new migration script) seems to be a bit special with a lot of "dfwikiXXXX" dirs generated.''' I made a script to rename all these dirs.
# '''The old-new migration script seems to be twice, once under the wikimigrate dir (the used one) and under the mod directory (unused?).''' I gonna bet for duplicated code...

This summer three of us will apply a re-engineering process to adapt NWiki to Moodle standards, solve incoherences and improve architecture.

Broken/id:1741

2007-06-03T14:39:59Z

Granludo: /* New wiki issue list (Comments) */

What about wrapping the already existing bits of Moodle together to create a new wiki (oh, no...not another wiki) My thinking is that we already have the following tools:

* a "standard" markup (Markdown)
* several ways to store attachments/images/binary files in various modules
* filters for multimedia, Latex, Math and the like.

Could these instances be refactored and refined then called from the wiki parser? This would avoid re-inventing the wheel(s) and simplify maintanence of system. I guess I'm suggesting a "plugin" mechanism where each of these tools could be added to Moodle and then assembled to form the wiki rather than create a monolithic and eventually cumbersome script. If all wiki pages are simply text, the wiki script will just dole out portions of each page to the proper tool. I'm imagining these tools could be used everywhere in Moodle, rather than being specific to the wiki...kind of following the unix philosophy of assembling several simpler tools to perform complicated tasks. Looking at Martin D's post outlining the must-have features, he alludes to this approach when discussing Mediawiki. Posts in other discussions have as well.

Regarding feature ideas, I would recommend folks look at Uniwakka. This "academically oriented" wiki engine has some great possibilities including support for MathML (better than latex filter for sophisticated maths?), Latex, chemistry (a personal favorite), and bibliographies; it exports/imports OpenOffice documents directly and exports Latex versions of the pages. Veeerryy nice!

Thoughts?

~Steve
----
These are interesting thougts Steve, in fact it was my fisrt idea twio years ago when I longed to develop tools for the current wiki. But teh coding and features of the current wiki convinced me that we needed a new wiki from scratch. I vbeliebe that the aproach you propose can be implemented once we have the [[DFWiki]] up and official.

By the way we are already working on a wiki parser compilant with mediawiki, comming soon .

Ludo - DFWikiteam
----

The features I find myself often missing in the current Moodle Wiki are:

* editable sections/sub-pages
* in history: ability to compare two arbitrary versions

These are things I have grown used to in MediaWiki.

In the markup department I'd like to see:

* at minimum: a basic wiki-like markup as the default
* optionally: ability to define your own markup
* optionally 2: ability to define what if the default markup

I find that most cases people will use the default markup. I don't use the Markdown format although I hear great things about it from people who do use it. I wouldn't want to make the users at our site transfer to Markdown, when I didn't even mention it in the basic training sessions they participated in.

~Jussi

I have used a number of different wiki systems and some of them with students. I've tried [http://www.twiki.org/ TWiki] and found that students with no knowledge of html take to it quite readily (and do understand the wiki way of makinglinks). I use different versions of [http://www.tiddlywiki.com/ Tiddlywiki] but the markup drives me bonkers (eg because links use | you cannot encluse a URL inside a table). I have also helped faculty use the Moodle wiki (Moodle v 1.5.1) for class but what I don't like about it is the html editor approach. A student actually managed to crunch the wiki at one point with mangled html code pasted in from MS Word which was then edited! My favourite and what I consider to be the most flexible markup system is [http://www.centeredwork.com/xilize2/index.html Xilize] which at version 2 is powerful strong. There's a plugin for Jedit which I use to create web pages.

Personally, I hope that the Moodle wiki behaves more like a 'traditional' wiki with CamelCase links and a default markup system that's easy to comprehend and orthogonal (I don't much like the accent on quotes in Markdown).

For me the selling point of Moodle wiki for use in a course is the flexibility of access control -- one can configure it to be individual access or group access, etc etc. If it defaulted to a wiki like markup and were more stable (especially with Postgres back end) I and many faculty would be happy campers.

~Markpea 25 Jan 2006

[[Category:Developer|Wiki requirements]]

I think you should either put the same information that you find in this link or the link itself in the wiki part of the documentation. I needed to know about the markup used in Moodle's wiki, and it would be nice if it were laid out right here.

I didn't know if it were more appropriate to link to this previous documentation, or if it would be better to re-create it.

[http://moodle.org/help.php?module=wiki&file=howtowiki.html /moodle.org help, how to wiki]

Thank you,
atw

== New wiki (old)issue list ==
This list is very old, we (dfwikiteam) have commented. Rigth now (may 07) the nwiki development plans are being worked out in the [[NWiki roadmap]] page
# '''There is no userid column in the wiki_pages table (author char-string instead). Must be supported in migration too.''' userid has been there since June06
# '''There is no intro and introformat in the wiki table.'''. I can't remember when Eloy Lafuente added these two columns... A long, long time ago...
# '''In the upgrade from wiki to dfwiki, as there aren't userids, my wiki-pages were assigned to "guest". Once more, userid seems to be critical.'''. Solved. We are using userids. In case of mismatching, we assign the page to the current user.
# '''Wikis having different wiki_entries (group or user ones) have no support in new wiki (only one simultaneous line of versions is available?) so we get a lot of duplicate version errors with data-lost of such pedagogical feature! Or am I losing anything? With only groupid and version in the UK of the table, old student wikis can fit in the new one. Once more, userid!''' Solved UNIQUE KEY `wiki_pages_uk` (`pagename`, `version`, `dfwiki`, `groupid`, `userid`, `ownerid`).
# '''Search doesn't work for diacritics. And/or match is performed with case matching (I think).''' Search has some bugs. We hae to improve it. Minor priority.
# '''Search seems to work against titles and contents always (no matter the checkbox was selected or no). Perhaps it's due to that usage of globals? Ah! After a second try I saw that such checkbox is to decide to show the details of the search in the body of the page. Perhaps the title should be changed to be a bit more clear? Something like "show results page" and some sort of nice help...''' I don't think so. I'll review it.
# '''The useful "What links here" block isn't available.''' Now it is.
# '''Wiki backup and restore don't support individual activities!''' Why not? Where is the problem?
# '''Wikis aren't included in the backup/restore at all!''' Backup/Restore are working correctly. We have not noticed any bug.
# '''Blocks system. Would be difficult to migrate to core block system?''' Migrated in May06.
# '''UTF-8 migration always get teacher_main_language() and it should get page author language! If we know the author responsible for the version, we must look for their original encoding instead of using the teacher one! Similar to forum_posts (if I'm not wrong). And we should know the user: userid again! ;-)''' I'm gonna take a look to this.
# '''In the wiki_pages table there is one "dfwiki" field. Should be "wikiid". Such name doesn't sound ok. (although it's possible that migation become painful, so we can change it in the future...).''' I know. Pain! It will be changed with the API integration.
# '''dfwiki is inside a lot of places in code. It should go out (although it's possible that migation become painful, so we can change it in the future...).''' Yes, variables, comments... We have to clean it out.
# '''globals, globals, globals usage should be out. Just request parameters filtered with xxxx_param() functions.''' There is only a big one. We are making it smaller every day.
# '''Attachment storage (as I've seen in the old-new migration script) seems to be a bit special with a lot of "dfwikiXXXX" dirs generated.''' I made a script to rename all these dirs.
# '''The old-new migration script seems to be twice, once under the wikimigrate dir (the used one) and under the mod directory (unused?).''' I gonna bet for duplicated code...

This summer three of us will apply a re-engineering process to adapt NWiki to Moodle standards, solve incoherences and improve architecture.

Broken/Wiki requirements

2007-06-01T16:55:21Z

Granludo: /* See also */

==Moodle wiki purpose==

To provide a way for students, teachers and other Moodle participants to create an organic, on-line document collaboratively.

==Key features==

# Pages can be created and linked using simple wiki methods.
# All Moodle text formats can be supported.
# Editing and viewing can be restricted by Moodle roles (i.e. currently: Students, Groups, Teachers).
# Images can be easily inserted into the text of a wiki.
# Attachments can be made to wiki pages.
# Must be fully compliant with Moodle backup and restore.
# Must be fully compliant with Moodle logging and activity tracking.
# Must provide a method of grading (see assignment module). Grading should be optional on a per-wiki basis.
# Allow importing of external documents to create a wiki or add to an existing one.
# Allow exporting to an external document.
# Allow refactoring/moving/deleting pages with appropriate permissions.
(from Martin's list):

==Basic Operation==
'''Create the wiki:'''- Log in/ Turn editing on/ Add and activity/ Wiki
- Fill in wiki parameters (Leave defaults and experiment later. Everything except the inital page fields can be changed.)

'''Adding pages:'''

- Edit the first (& only page)/ Type the name of the new page you want within square brackets/ Click Save. The new page link is displayed beside a question mark./ Click the question mark to open the new page for data entry.

- pages can be added from any page.
(Suggestion: On your start page, type "PageIndex" and perhaps "Site Map" and/or "Newest Pages" so that the user is alerted to these options immediately on entering the wiki. They also appear on the "Choose wiki links" drop down at the top of the wiki window.

The wiki is one of the most powerful tools within moodle and suitable for many educational & administrative functions including:

# a wonderful way to encourage students to build, debate and share a summary of their course content as they work
# a great way to deliver your school administrative manuals i.e. teachers manual; student manuals. They are searchable, interlinked automatically & able to be continuously updated showing who, when & how the updates were made.

Currently '''some wiki features do not work reliably''':
* '''search''' does not find page titles (so make sure that the page title is repeated somewhere within the page itself).
* '''export''' does not export all wiki content
* '''delete pages''' and '''strip pages''' often do not work. (the most common error message is: ''Course Module is incorrect'', which sometimes can be bypassed by using another theme. formal_white is known to cause such problems.)
* '''moodle editor does not handle hyperlinks correctly'''. i.e. All links must be manually placed within square brackets rather than embedded as HTML links.

==Design Objectives==
* The Wiki should support exactly the same text formats in Moodle core as you find everywhere else (see weblib.php for standard functions, eg format_text). ie Moodle format, HTML format, Markdown, etc. Any new formats need to go in the core so they are available everywhere, and this needs to be discussed very well. We only JUST removed the old Wiki-like format to reduce confusion with the current Wiki and I don't want more of this confusion from a rushed implementation.

* Linking should support both CamelCase and [Bracket] styles, and also automatic linking on the fly (a la Glossary).

* Upgrading from the old system to any new one should be seamless and problem-free (this includes restoring old backups from 1.4, for example).

* The idea with eWiki was to build on the work of the eWiki team in future. Unfortunately, so many hacks needed to be made to their monolithic script that this became almost impossible. I would like to see a lot of thought put into a very cleanly-designed architecture for the Wiki in future, something that is easy to extend and maintain (and also to use).

* I really like MediaWiki, as this Wiki is becoming a defacto standard (for good reason) and it would be good to be compatible in some way with it. Perhaps we can use part of it as a library for us. However, the Moodle Wiki is a COMPONENT within the larger Moodle system and has a very different focus to MediaWiki (which is designed for large standalone web sites) ... much thought should be given to making our Wiki work very closely with other modules, rather than another module that tries to do everything itself. It should do exactly what it needs to do and no more.

* Support for media in a very clean way is a must. This is probably my biggest criticism of the current eWiki version ... attaching images and video etc is really awkward and doesn't look good.

== New wiki issue list ==
(This list is rather old one... most (if not all) points have been worked out)
now we are working on the [[NWiki roadmap]] page.
# There is no userid column in the wiki_pages table (author char-string instead). Must be supported in migration too.
# There is no intro and introformat in the wiki table.
# In the upgrade from wiki to dfwiki, as there aren't userids, my wiki-pages were assigned to "guest". Once more, userid seems to be critical.
# Wikis having different wiki_entries (group or user ones) have no support in new wiki (only one simultaneous line of versions is available?) so we get a lot of duplicate version errors with data-lost of such pedagogical feature! Or am I losing anything? With only groupid and version in the UK of the table, old student wikis can fit in the new one. Once more, userid!
# Search doesn't work for diacritics. And/or match is performed with case matching (I think).
# Search seems to work against titles and contents always (no matter the checkbox was selected or no). Perhaps it's due to that usage of globals? Ah! After a second try I saw that such checkbox is to decide to show the details of the search in the body of the page. Perhaps the title should be changed to be a bit more clear? Something like "show results page" and some sort of nice help...
# The useful "What links here" block isn't available.
# Wiki backup and restore don't support individual activities!
# Wikis aren't included in the backup/restore at all!
# Blocks system. Would be difficult to migrate to core block system?
# UTF-8 migration always get teacher_main_language() and it should get page author language! If we know the author responsible for the version, we must look for their original encoding instead of using the teacher one! Similar to forum_posts (if I'm not wrong). And we should know the user: userid again! ;-)
# In the wiki_pages table there is one "dfwiki" field. Should be "wikiid". Such name doesn't sound ok. (although it's possible that migation become painful, so we can change it in the future...).
# dfwiki is inside a lot of places in code. It should go out (although it's possible that migation become painful, so we can change it in the future...).
# globals, globals, globals usage should be out. Just request parameters filtered with xxxx_param() functions.
# Attachment storage (as I've seen in the old-new migration script) seems to be a bit special with a lot of "dfwikiXXXX" dirs generated.
# The old-new migration script seems to be twice, once under the wikimigrate dir (the used one) and under the mod directory (unused?).

(List taken from Using Moodle [http://moodle.org/mod/forum/discuss.php?d=43435&parent=205926 Wiki UTF is ready] forum posting.)

==See also==
*[[NWiki roadmap]]
*[http://moodle.org/mod/forum/discuss.php?d=21493 Wiki development] forum discussion
*[[Dfwiki]]
[[Category:Developer]]
[[Category:Wiki]]

Broken/Wiki requirements

2007-06-01T16:53:57Z

Granludo: /* New wiki issue list */

==Moodle wiki purpose==

To provide a way for students, teachers and other Moodle participants to create an organic, on-line document collaboratively.

==Key features==

# Pages can be created and linked using simple wiki methods.
# All Moodle text formats can be supported.
# Editing and viewing can be restricted by Moodle roles (i.e. currently: Students, Groups, Teachers).
# Images can be easily inserted into the text of a wiki.
# Attachments can be made to wiki pages.
# Must be fully compliant with Moodle backup and restore.
# Must be fully compliant with Moodle logging and activity tracking.
# Must provide a method of grading (see assignment module). Grading should be optional on a per-wiki basis.
# Allow importing of external documents to create a wiki or add to an existing one.
# Allow exporting to an external document.
# Allow refactoring/moving/deleting pages with appropriate permissions.
(from Martin's list):

==Basic Operation==
'''Create the wiki:'''- Log in/ Turn editing on/ Add and activity/ Wiki
- Fill in wiki parameters (Leave defaults and experiment later. Everything except the inital page fields can be changed.)

'''Adding pages:'''

- Edit the first (& only page)/ Type the name of the new page you want within square brackets/ Click Save. The new page link is displayed beside a question mark./ Click the question mark to open the new page for data entry.

- pages can be added from any page.
(Suggestion: On your start page, type "PageIndex" and perhaps "Site Map" and/or "Newest Pages" so that the user is alerted to these options immediately on entering the wiki. They also appear on the "Choose wiki links" drop down at the top of the wiki window.

The wiki is one of the most powerful tools within moodle and suitable for many educational & administrative functions including:

# a wonderful way to encourage students to build, debate and share a summary of their course content as they work
# a great way to deliver your school administrative manuals i.e. teachers manual; student manuals. They are searchable, interlinked automatically & able to be continuously updated showing who, when & how the updates were made.

Currently '''some wiki features do not work reliably''':
* '''search''' does not find page titles (so make sure that the page title is repeated somewhere within the page itself).
* '''export''' does not export all wiki content
* '''delete pages''' and '''strip pages''' often do not work. (the most common error message is: ''Course Module is incorrect'', which sometimes can be bypassed by using another theme. formal_white is known to cause such problems.)
* '''moodle editor does not handle hyperlinks correctly'''. i.e. All links must be manually placed within square brackets rather than embedded as HTML links.

==Design Objectives==
* The Wiki should support exactly the same text formats in Moodle core as you find everywhere else (see weblib.php for standard functions, eg format_text). ie Moodle format, HTML format, Markdown, etc. Any new formats need to go in the core so they are available everywhere, and this needs to be discussed very well. We only JUST removed the old Wiki-like format to reduce confusion with the current Wiki and I don't want more of this confusion from a rushed implementation.

* Linking should support both CamelCase and [Bracket] styles, and also automatic linking on the fly (a la Glossary).

* Upgrading from the old system to any new one should be seamless and problem-free (this includes restoring old backups from 1.4, for example).

* The idea with eWiki was to build on the work of the eWiki team in future. Unfortunately, so many hacks needed to be made to their monolithic script that this became almost impossible. I would like to see a lot of thought put into a very cleanly-designed architecture for the Wiki in future, something that is easy to extend and maintain (and also to use).

* I really like MediaWiki, as this Wiki is becoming a defacto standard (for good reason) and it would be good to be compatible in some way with it. Perhaps we can use part of it as a library for us. However, the Moodle Wiki is a COMPONENT within the larger Moodle system and has a very different focus to MediaWiki (which is designed for large standalone web sites) ... much thought should be given to making our Wiki work very closely with other modules, rather than another module that tries to do everything itself. It should do exactly what it needs to do and no more.

* Support for media in a very clean way is a must. This is probably my biggest criticism of the current eWiki version ... attaching images and video etc is really awkward and doesn't look good.

== New wiki issue list ==
(This list is rather old one... most (if not all) points have been worked out)
now we are working on the [[NWiki roadmap]] page.
# There is no userid column in the wiki_pages table (author char-string instead). Must be supported in migration too.
# There is no intro and introformat in the wiki table.
# In the upgrade from wiki to dfwiki, as there aren't userids, my wiki-pages were assigned to "guest". Once more, userid seems to be critical.
# Wikis having different wiki_entries (group or user ones) have no support in new wiki (only one simultaneous line of versions is available?) so we get a lot of duplicate version errors with data-lost of such pedagogical feature! Or am I losing anything? With only groupid and version in the UK of the table, old student wikis can fit in the new one. Once more, userid!
# Search doesn't work for diacritics. And/or match is performed with case matching (I think).
# Search seems to work against titles and contents always (no matter the checkbox was selected or no). Perhaps it's due to that usage of globals? Ah! After a second try I saw that such checkbox is to decide to show the details of the search in the body of the page. Perhaps the title should be changed to be a bit more clear? Something like "show results page" and some sort of nice help...
# The useful "What links here" block isn't available.
# Wiki backup and restore don't support individual activities!
# Wikis aren't included in the backup/restore at all!
# Blocks system. Would be difficult to migrate to core block system?
# UTF-8 migration always get teacher_main_language() and it should get page author language! If we know the author responsible for the version, we must look for their original encoding instead of using the teacher one! Similar to forum_posts (if I'm not wrong). And we should know the user: userid again! ;-)
# In the wiki_pages table there is one "dfwiki" field. Should be "wikiid". Such name doesn't sound ok. (although it's possible that migation become painful, so we can change it in the future...).
# dfwiki is inside a lot of places in code. It should go out (although it's possible that migation become painful, so we can change it in the future...).
# globals, globals, globals usage should be out. Just request parameters filtered with xxxx_param() functions.
# Attachment storage (as I've seen in the old-new migration script) seems to be a bit special with a lot of "dfwikiXXXX" dirs generated.
# The old-new migration script seems to be twice, once under the wikimigrate dir (the used one) and under the mod directory (unused?).

(List taken from Using Moodle [http://moodle.org/mod/forum/discuss.php?d=43435&parent=205926 Wiki UTF is ready] forum posting.)

==See also==

*[http://moodle.org/mod/forum/discuss.php?d=21493 Wiki development] forum discussion
*[[Dfwiki]]
[[Category:Developer]]
[[Category:Wiki]]

Wiki 2.0

2007-06-01T16:52:54Z

Granludo: /* See also */

The Moodle wiki(s) enables participants to work together on web pages to add, expand and change the content. This page can serve to provide information about different Wikis that may be used with Moodle.

= Wiki Standard =
Link to the [[Wiki]] MoodleDoc page
This is the standard Wiki which is part of 1.5 . It was developed from a version of Erfurt wiki. A flavor of it is still being used in Moodle 1.8 beta.

See the MoodleDocs [[Wiki module]] or [http://moodle.org/help.php?module=wiki&file=howtowiki.html "How to wiki" page for more information].

Initially built by Mike Churchward & Michael Schneider

= Dfwiki =
This is an addin wiki for Moodle.
[[Dfwiki]] is the MoodleDoc page.
'''DFWiki''' is an alternative [[wiki]] module to the current (1.5.3) Moodle [[Wiki module]].

Dfwiki for Moodle 1.5.3 can be found [http://appserv.lsi.upc.es/palangana/moodle/course/view.php?id=15 in dfwiki home page], and in the Moodle [[CVS]]. The [http://appserv.lsi.upc.es/palangana/moodle/course/view.php?id=15 dfwiki english home page is here].

Team leader is Marc Alier (Ludo).

= Erfurt wiki =
Named for the developer's hometown in Germany, it was the basis for the standard wiki included with Moodle.

= New wiki =
Currently is this wiki available as a plug in for 1.6.x and 1.7.x. "We ([[Dfwiki_module#Dfwikiteam|Dfwiki team]]) hope it will be the standard wiki in Moodle 1.8", says Team leader Marc Alier (ludo).

The NewWiki16 plugin has more MediaWiki(MoodleDocs)features. For example, the characters that create, the automatic headers (<nowiki>= = or == ==</nowiki>), automatic numbers (<nowiki># or ##</nowiki>) and bullets (<nowiki>* or **</nowiki>) work. It also has a page discussion tab and provides a page outline based on headers at the top. There are two HTML edit tool bars available. The 1.6.x version does have a site map on a "navigation" tab, but not the standard pages found on the Choose Wiki links pulldown.

==Tiddlywiki integration==
New wiki can interoperate with the Ajax based portable [http://tiddlywiki.com tidlywiki].
See [[Tiddlywiki integration]]

= MediaWiki =
This is the "big" wiki. Will Taylor says "I have MediaWiki integrated now with Moodle versions 1.5.3 and 1.6, very easy to set up. Users need to log in separately to MediaWiki to edit, but they are authenticated off the Moodle database, so use the same username & password without needing to create a separate account on MediaWiki. Using the MediaWiki permissions system, I have editing privileges reserved for registered, logged-in users, and read privileges open to the world - but you could configure this in many ways if you wish. Check out the various projects created in MediaWiki (WikiPedia, Wiktionary, &c.) to see the potential of this platform."

MediaWiki should be used as a '''site-specific''' wiki. The standard Moodle wiki, or Dfwiki should be used as course-specific wiki.
= Table of Versions =
{| border="0" cellpadding="4" cellspacing ="0" rules="all"
|+ '''Wikis in Moodle'''
! -Version Name-
! Wiki version
! Moodle ver
! Status
! Download Place
! Docs
! Discussion Place
! Feature1
|-----
| Std Wiki
|
| all
|
|[http://moodle.org/mod/data/view.php?d=13&rid=273 Modules]
| [[Wiki]]
| [http://moodle.org/mod/forum/view.php?f=366 Wiki forum]
|
|-----
| Dfwiki
|
| 1.5.4
|
|[[http://moodle.org/mod/data/view.php?d=13&rid=115 CVS Page]]
| [[Dfwiki]]
|[http://moodle.org/mod/forum/view.php?f=366 Wiki forum]
|
|-----
| Erfurt Wiki
|
| 1.6
|
|[http://erfurtwiki.sourceforge.net/ Sourceforge]
| [http://erfurtwiki.sourceforge.net/README readme]
|
|
|-----
| New wiki
|
|1.7 and 1.8
|Beta
|[http://morfeo.upc.es/crom/course/view.php?id=4 DFwiki home]
|[http://morfeo.upc.es/crom/course/view.php?id=4 DFwiki home]
|[http://morfeo.upc.es/crom/course/view.php?id=4 DFwiki home]
|[http://moodle.org/mod/forum/view.php?f=366 Wiki forum]
|-----
| MediaWiki
|
|NA
|
|[http://www.mediawiki.org/wiki/MediaWiki MediaWiki Home]
|
|
|
|}

=See also=
* [[Dfwiki]]
* [[Wiki requirements|Specific wiki requirements]]
* [[dfwiki requests]]
* [[NWiki roadmap]]
* [[Wiki comments |Wiki development comments]]
*[[wikindx]] for developers

* Using Moodle [http://moodle.org/mod/forum/view.php?f=366 Wiki module forum]

[[Category:Developer]]
[[Category:Wiki]]

Broken/NWiki roadmap

2007-06-01T16:32:06Z

Granludo: /* Code Tunning : new wiki api */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.
[http://morfeo.upc.es/crom/file.php/4/wikiAPIdoc/index.htmlThe PHPDoc documentation is available here].

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]

Broken/NWiki roadmap

2007-06-01T16:29:30Z

Granludo: /* Code Tunning : new wiki api */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.

'''Done!!!''' Two main layers for developers have been written and working inside of the Nwiki distributions since May 2007.

=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]

Broken/NWiki roadmap

2007-06-01T16:27:21Z

Granludo: /* New upcoming toys */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.
=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]] [http://moodle.org/mod/forum/discuss.php?d=72909 wikibook in the forum]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]

Broken/NWiki roadmap

2007-06-01T16:26:46Z

Granludo: /* More? */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.
=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
Expected mid june

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]

Broken/NWiki roadmap

2007-06-01T16:26:17Z

Granludo: /* Most likely */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional. April 2007
*NWiki complies with '''XHTML Strict''' mid May '07
** this affects main engine
** blocks not finished yet (some javascript to look up to)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.
=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

=== New upcoming toys ===
In June 2007 will come new features that need to be sorted in or out of the basic distribution
* [[Wikibook]]
* PDF Generation
* Timeline-like wiki history browser
* Import / export from openoffice writer and (eventually) msword

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]

Broken/NWiki roadmap

2007-06-01T16:24:12Z

Granludo: /* XHTML Strict */

Broken/NWiki roadmap

2007-06-01T16:22:30Z

Granludo: /* PHPUnit testing */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional.
*We are working to meet XHTML strict at mid May '07 (hopefully by may 15)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.
=== PHPUnit testing===
* a set of PHPUnit tests have been developed to ensure the quality of the thing.
* test case descriptions have been written to help developers and maintainers

== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]

Broken/NWiki roadmap

2007-06-01T16:19:55Z

Granludo: /* Logs and stats */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional.
*We are working to meet XHTML strict at mid May '07 (hopefully by may 15)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.
* Done! June 2007

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.
=== PHPUnit testing===
While this api is being developed a set of PHPUnit tests are being developed to ensure the quality of the thing.
== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]

Broken/NWiki roadmap

2007-05-12T14:31:34Z

Granludo:

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional.
*We are working to meet XHTML strict at mid May '07 (hopefully by may 15)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.
=== PHPUnit testing===
While this api is being developed a set of PHPUnit tests are being developed to ensure the quality of the thing.
== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==
Let's rememeber to complete the PDF export thing (HTML Editor wiki pages are not exported)
==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]

Broken/NWiki roadmap

2007-05-04T06:12:27Z

Granludo: /* XHTML Strict */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional.
*We are working to meet XHTML strict at mid May '07 (hopefully by may 15)

==Logs and stats==
We need to ckeck out stats and logs with nwiki.

== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.
=== PHPUnit testing===
While this api is being developed a set of PHPUnit tests are being developed to ensure the quality of the thing.
== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]

Broken/NWiki roadmap

2007-04-25T10:14:32Z

Granludo: /* shall we trim nwiki */

This page is to talk about the (likely) entrance of NWiki into 1.9 core.

Rigth Now DFwikiteam is focussed in the following issues:
== XHTML Strict ==
*NWiki complies with XHTML transitional.
*We are working to meet XHTML strict at mid May '07
== Code Tunning : new wiki api==
There's a big issue in the code, the $WS variable that acts like a big set of global variables.
*We are getting $WS smaller day by day
*We are witting a new internal API to create an internal layer of services for developers.
=== PHPUnit testing===
While this api is being developed a set of PHPUnit tests are being developed to ensure the quality of the thing.
== shall we trim nwiki ?==
NWiki is Huge ! As many have said we implement a lot of features that maybe are not necessary for everybody.
We could have a reduced set of nwiki into the oficial distribution and a 3rd party and a extended version as 3rd part plug in.
Things that could be taken outside:
===Maybe we keep them===
* wiki course format
* discussion pages ?
* grading in wikis ?
* ranking and votes?

===Most likely===
* integration with tiddlywiki ?

== Migration issues ==
So far the data migration works fine. No bugs reported without attending.

==More?==

==se also ==
*[[wiki]]
*[[Dfwiki]]
*[http://morfeo.upc.es/crom/course/view.php?id=4 DFWikilabs]