MoodleDocs - User contributions [en]

Talk:Core Function List

2009-04-15T07:47:35Z

Pigui: New page: Ohhhh great!! Finally we have get_course_by_id ($id) function :)

Ohhhh great!! Finally we have get_course_by_id ($id) function :)

Talk:Moodle API Function List

2009-02-05T14:26:13Z

Pigui:

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

== Admin ==
== Blocks ==
== Blog ==
== Calendar ==
== Category ==
get_category()
create_category()
delete_category()
update_category()
update_parent_category()

== 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}
create_section()
get_sections()
delete_section()
get_metacourse()

=== 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

== Grade ==
== Group ==
create_grouping()
delete_grouping()
update_grouping()
get_grouping()
add_group_to_grouping()
get_groups_from_grouping()
delete_group_from_grouping()

== Mod ==
=== Assignment ===
=== Chat ===
=== Choice ===
=== Data ===
=== Feedback ===
=== Forum ===
=== Glossary ===
=== Lesson ===
=== Quiz ===
=== Resource ===
=== Scorm ===
=== Survey ===
=== Wiki ===
== Portfolio ==
== Repository ==
== Role ==
create_role()
get_roles()
update_role()
delete_role()
assign_role()
inherit_capability()
allow_capability()
prevent_capability()
prohibit_capability()
get_users_by_role()
has_capability()

== Search ==
== Tag ==
== User ==

Talk:Moodle API Function List

2009-02-05T14:25:36Z

Pigui: /* Course */

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

== Admin ==
== Blocks ==
== Blog ==
== Calendar ==
== Category ==
get_category()
create_category()
delete_category()
update_category()
update_parent_category()

== 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}

create_section()

get_sections()

delete_section()

get_metacourse()

=== 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

== Grade ==
== Group ==
create_grouping()
delete_grouping()
update_grouping()
get_grouping()
add_group_to_grouping()
get_groups_from_grouping()
delete_group_from_grouping()

== Mod ==
=== Assignment ===
=== Chat ===
=== Choice ===
=== Data ===
=== Feedback ===
=== Forum ===
=== Glossary ===
=== Lesson ===
=== Quiz ===
=== Resource ===
=== Scorm ===
=== Survey ===
=== Wiki ===
== Portfolio ==
== Repository ==
== Role ==
create_role()
get_roles()
update_role()
delete_role()
assign_role()
inherit_capability()
allow_capability()
prevent_capability()
prohibit_capability()
get_users_by_role()
has_capability()

== Search ==
== Tag ==
== User ==

Talk:Moodle API Function List

2009-01-29T09:30:19Z

Pigui: /* Role */

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

== Admin ==
== Blocks ==
== Blog ==
== Calendar ==
== Category ==
get_category()
create_category()
delete_category()
update_category()
update_parent_category()

== 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

== Grade ==
== Group ==
create_grouping()
delete_grouping()
update_grouping()
get_grouping()
add_group_to_grouping()
get_groups_from_grouping()
delete_group_from_grouping()

== Mod ==
=== Assignment ===
=== Chat ===
=== Choice ===
=== Data ===
=== Feedback ===
=== Forum ===
=== Glossary ===
=== Lesson ===
=== Quiz ===
=== Resource ===
=== Scorm ===
=== Survey ===
=== Wiki ===
== Portfolio ==
== Repository ==
== Role ==
create_role()
get_roles()
update_role()
delete_role()
assign_role()
inherit_capability()
allow_capability()
prevent_capability()
prohibit_capability()
get_users_by_role()
has_capability()

== Search ==
== Tag ==
== User ==

Talk:Moodle API Function List

2009-01-29T09:29:06Z

Pigui: /* Group */

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

== Admin ==
== Blocks ==
== Blog ==
== Calendar ==
== Category ==
get_category()
create_category()
delete_category()
update_category()
update_parent_category()

== 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

== Grade ==
== Group ==
create_grouping()
delete_grouping()
update_grouping()
get_grouping()
add_group_to_grouping()
get_groups_from_grouping()
delete_group_from_grouping()

== Mod ==
=== Assignment ===
=== Chat ===
=== Choice ===
=== Data ===
=== Feedback ===
=== Forum ===
=== Glossary ===
=== Lesson ===
=== Quiz ===
=== Resource ===
=== Scorm ===
=== Survey ===
=== Wiki ===
== Portfolio ==
== Repository ==
== Role ==
create_role()
get_roles()
update_role()
delete_role()
assign_role()
inherit_capability()
allow_capability()
prevent_capability()
prohibit_capability()
get_users_by_role()

== Search ==
== Tag ==
== User ==

Talk:Moodle API Function List

2009-01-29T09:28:52Z

Pigui: /* Group */

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

== Admin ==
== Blocks ==
== Blog ==
== Calendar ==
== Category ==
get_category()
create_category()
delete_category()
update_category()
update_parent_category()

== 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

== Grade ==
== Group ==
create_grouping()
delete_grouping()
update_grouping()
get_grouping()
add_group_to_grouping()
get_groups_from_grouping()
delete_group_from_grouping()

== Mod ==
=== Assignment ===
=== Chat ===
=== Choice ===
=== Data ===
=== Feedback ===
=== Forum ===
=== Glossary ===
=== Lesson ===
=== Quiz ===
=== Resource ===
=== Scorm ===
=== Survey ===
=== Wiki ===
== Portfolio ==
== Repository ==
== Role ==
create_role()
get_roles()
update_role()
delete_role()
assign_role()
inherit_capability()
allow_capability()
prevent_capability()
prohibit_capability()
get_users_by_role()

== Search ==
== Tag ==
== User ==

Talk:Moodle API Function List

2009-01-29T09:25:48Z

Pigui:

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

== Admin ==
== Blocks ==
== Blog ==
== Calendar ==
== Category ==
get_category()
create_category()
delete_category()
update_category()
update_parent_category()

== 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

== Grade ==
== Group ==
== Mod ==
=== Assignment ===
=== Chat ===
=== Choice ===
=== Data ===
=== Feedback ===
=== Forum ===
=== Glossary ===
=== Lesson ===
=== Quiz ===
=== Resource ===
=== Scorm ===
=== Survey ===
=== Wiki ===
== Portfolio ==
== Repository ==
== Role ==
create_role()
get_roles()
update_role()
delete_role()
assign_role()
inherit_capability()
allow_capability()
prevent_capability()
prohibit_capability()
get_users_by_role()

== Search ==
== Tag ==
== User ==

Talk:Moodle API Function List

2009-01-29T09:20:08Z

Pigui:

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

== Admin ==
== Blocks ==
== Blog ==
== Calendar ==
== Category ==
get_category()
create_category()
delete_category()
update_category()
update_parent_category()

== 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

== Grade ==
== Group ==
== Mod ==
=== Assignment ===
=== Chat ===
=== Choice ===
=== Data ===
=== Feedback ===
=== Forum ===
=== Glossary ===
=== Lesson ===
=== Quiz ===
=== Resource ===
=== Scorm ===
=== Survey ===
=== Wiki ===
== Portfolio ==
== Repository ==
== Search ==
== Tag ==
== User ==

Talk:Moodle API Function List

2009-01-29T09:16:50Z

Pigui:

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

== Admin ==
== Blocks ==
== Blog ==
== Calendar ==

== 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

== Grade ==
== Group ==
== Mod ==
=== Assignment ===
=== Chat ===
=== Choice ===
=== Data ===
=== Feedback ===
=== Forum ===
=== Glossary ===
=== Lesson ===
=== Quiz ===
=== Resource ===
=== Scorm ===
=== Survey ===
=== Wiki ===
== Portfolio ==
== Repository ==
== Search ==
== Tag ==
== User ==

Talk:Moodle API Function List

2009-01-29T09:16:29Z

Pigui:

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

== Admin ==
== Blocks ==
== Blog ==
== Calendar ==

== 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

== Grade ==
== Group ==
== Mod ==
=== Assignment ==
=== Chat ===
=== Choice ===
=== Data ===
=== Feedback ===
=== Forum ===
=== Glossary ===
=== Lesson ===
=== Quiz ===
=== Resource ===
=== Scorm ===
=== Survey ===
=== Wiki ===

== Portfolio ==
== Repository ==
== Search ==
== Tag ==
== User ==

Wiki 2.0

2008-11-14T08:00:52Z

Pigui: /* Database design */

Let's restart the wiki movement, yay!

Here is the plan for 2.0 - we are not looking back, you can access information that was here previously in page history, sorry :-)

=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

Talk:Wiki 2.0

2008-11-12T16:52:59Z

Pigui:

=Database design=
=Formats, Editors & Filters=
=Locking=
=Version & diffs=
=Comments=
=Groups=
=Grading=
=Rating=
=File handling=
=Backup/Restore=
=Tags=
=Blocks=
=Permisions=
=Templates=

Talk:Wiki 2.0

2008-11-12T16:30:13Z

Pigui:

=Database design=
=Formats, Editors & Filters=
=Version & diffs=
=Comments=
=Groups=
=Grading=
=Rating=
=File handling=
=Backup/Restore=
=Tags=
=Blocks=
=Permisions=
=Templates=

NWiki roadmap

2007-09-12T10:31:07Z

Pigui:

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.

== 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.

==Tracked issues==
There are several bugs and improvements listed in Moodle's [http://tracker.moodle.org/secure/IssueNavigator.jspa?assigneeSelect=specificuser&assignee=dfwikiteam tracker].
==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.

== Miscellaneous ==
*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]
*[[Wiki requirements]]

NWiki roadmap

2007-09-12T10:23:33Z

Pigui: /* Logs and stats */

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.

== 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.

== Miscellaneous ==
*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]
*[[Wiki requirements]]

Talk:Wiki requirements

2007-06-03T11:16:28Z

Pigui: /* 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: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 issue list (Comments) ==

# '''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.

Talk:Wiki requirements

2007-06-03T11:09:37Z

Pigui: New wiki issue list (Comments)