MoodleDocs - Contribucions de l'usuari [ca]

bootstrap-Theme

2012-10-01T09:04:24Z

Bawjaws: /* Resources */

== Twitter Bootstrap Theme==
This page aims to bring together discussions from the themes forum related to the development of a moodle 'base' theme that conforms to the [http://twitter.github.com/bootstrap/ Twitter Bootstrap] coding conventions. There has already been a great deal of work done by individuals within the Moodle community and it's hoped that by formulating this work we may be able to collaborate and build on this.

== Technical Approah ==
There are 5 major categories of development for this theme family:

* Layouts
* Renderers
* Stylesheets
* Javascripts
* Settings (child themes)

=== Layout ===
The General layout will be a 2 column layout based on the [http://twitter.github.com/bootstrap/examples/fluid.html "Fluid" example] providing an "out of the box" responsive grid.

=== Renderers ===
Multiple renderers will be developed to make Moodle output more bootstrap friendly by 1) outputting classes defined in bootstrap.css and 2) outputting semantic HTML exemplified in the bootstrap documentation

=== Stylesheets ===
Bootstrap.css will be the core CSS sheet with adjustments made to reduce re-duplication (like 'reset') and to define Moodle core classes that can't be matched to bootstrap via a renderer

=== Javascripts ===
[http://jshirley.github.com/bootstrap/javascript.html YUI Bootstrap plugins] will be dropped in to the theme in place of the jQuery version(s).

=== Settings ===
On the roadmap: create a child theme (or themes) to provide end users with custom settings, possibly including:

* static or fixed navbar
* light or dark color
* 2 or 3 column layout
* custom logo
* [http://bootswatch.com/ bootswatches]

== Success criteria ==
To have developed a theme that can be used as a base theme, that looks and feels like the default bootsrap interface. (see: [http://twitter.github.com/bootstrap/getting-started.html#examples examples].

==Future developments ==

* To make a responsive version
* Create a library of custom renderers that can be used in themes to make UI changes
* Add theme settings that allow administrators to change the layout of templates through the theme interface.

== Potential projects ==

Some projects that don't require knowledge of PHP to help with:

=== Bootstrap for Educational Content ===

Take some of your existing content, or freely available courses and use Bootstrap styles to format it. Maybe write a document, that uses Bootstrap styles to explain how to apply Bootstrap styles to educational content. Look at the Bootstrap documentation for inspiration, it not only tells you what is possible, it demonstrates many of them in its own presentation:

* http://twitter.github.com/bootstrap/base-css.html#typography
* http://twitter.github.com/bootstrap/base-css.html#code
* http://twitter.github.com/bootstrap/base-css.html#tables
* http://twitter.github.com/bootstrap/base-css.html#images
* http://twitter.github.com/bootstrap/base-css.html#icons
* http://twitter.github.com/bootstrap/components.html#labels-badges
* http://twitter.github.com/bootstrap/components.html#typography
* http://twitter.github.com/bootstrap/components.html#thumbnails
* http://twitter.github.com/bootstrap/components.html#alerts
* http://twitter.github.com/bootstrap/components.html#misc

=== Bootstrap in Moodle content ===

There's plenty of places in Moodle that accept HTML and so can be spruced up with Bootstrap. For example, if you have a public access course, you could add a big green "start learning now" button with a white tick icon to the course description (or many other places on your site) just by using the following html:

<a href="#" class="btn btn-success btn-large"><i class="icon-white icon-ok"></i> Start Learning Now</a>

and the href is simply pointing to the course like any normal link, yet the presentation is transformed. There's probably a million other examples, try coming up with some and sharing them. For experimenting with what's possible with buttons, try: http://www.plugolabs.com/twitter-bootstrap-button-generator/

=== Bootstrap editor ===

Of course, to do the above currently takes HTML coding. But it would be nice if you could just press buttons on a gui. Moodle allows plugin editors, maybe we could use this: http://jhollingworth.github.com/bootstrap-wysihtml5/

=== Bootstrap for TinyMCE ===

The current editor is actually incredibly flexible. It is themeable (http://www.tinymce.com/wiki.php/Creating_a_theme) and Bootstrap comes with a range of editor icons. It should also be able to pick up and use classes from an editor.css file you feed it (http://www.tinymce.com/wiki.php/Configuration:content_css). It should be possible to create a better Bootstrap editor using this flexibility

=== Checkout the competition ===

There's all sorts of Bootstrap projects for various blog engines and content management systems. If you already use say Wordpress you could install some of them an report back anything useful, or just nice looking, that they do and you think would transfer across to Moodle. The new version of Joomla ([http://www.joomla.org/3/]) also uses Bootstrap throughout the user and admin interface and can probably provide some inspiration.

=== Create alternate icon sprites ===

All the Bootstrap icons are merged into one single image to make things download faster. If you want to use a different set of icons you'll need to do the same. Instructions here: http://favbulous.com/post/1006/create-custom-icons-for-twitter-bootstrap-easily

== Links to Discussions in Forums ==

* [http://moodle.org/mod/forum/discuss.php?d=212222 (re-)bootstrap: work in progress]
* [http://moodle.org/mod/forum/discuss.php?d=212341 Amelia and Cyborg Bootswatches for Moodle]
* [http://moodle.org/mod/forum/discuss.php?d=208162 Bootstrap for Moodle project]

== Resources ==

* [http://twitter.github.com/bootstrap/ Twitter Bootstrap Home]
* [http://jshirley.github.com/bootstrap/javascript.html Bootstrap YUI Plugins]
* [http://bootswatch.com/ Bootswatch]
* [http://bootsnipp.com/ Bootsnipp]
* [http://fortawesome.github.com/Font-Awesome/ Font Awesome] (icon font for Bootstrap)
* [http://www.alistapart.com/articles/building-twitter-bootstrap/ A List Apart: Building Twitter Bootstrap] (the story behind and philosophy of Bootstrap)

bootstrap-Theme

2012-10-01T09:02:37Z

Bawjaws: /* Checkout the competition */ Joomla 3

Usuari:David Scotson

2012-10-01T09:01:05Z

Bawjaws:

An E-learning Technologist / software developer working for the [http://www.gla.ac.uk University of Glasgow] as part of the newly formed Learning and Teaching Centre.

[http://moodle.org/user/view.php?id=3152&course=5 My profile at Moodle.org]

== Current work ==

Mostly working on getting Bootstrap embedded into Moodle.

== Me and MoodleDocs ==

I gave a talk about Moodle recently to some of our IT support teams, one of the main points of which was was a great project MoodleDocs was (or at that time 'was going to be'), and how it could be a 'killer app' for Moodle i.e. so good that people use Moodle rather than alternatives simply because the documentation is so good. It's certainly the case that when we evaluated Moodle, the strong community support was a key deciding factor (it's a fruitless chicken and egg question whether the quality of Moodle attracted the strong community or the strong community contributed to the quality of Moodle, obviously they re-inforce each other). Having a commited, passionate community building documentation in a wiki just seemed like such a great idea, especially as I was aware of how much great info was 'hidden' within the postings of the Using Moodle forums, and the shared urge to teach/share that drives much of that. As I'm one of those people who loves to say 'I told you so!' when things turn out as I predict them to and, more importantly, because I think lack of good documentation is one of the areas holding back widespread adoption of e-learning/Moodle, I thought I'd get involved.

I'm particularly interested in:

* the social/community aspects of the project (including it's role as a community of practice)
* how the documentation caters to different audiences (dev/admin/teacher/student) while at the same time supporting/encouraging people to move between (or at least understand) different roles
* effective use of hypertext/web/wiki medium (meaning both collaborative text writing and using hyperlinks to break up and interwingle content)
* the interaction between the project websites, forums, databases, and this wiki

== Things I've learned, realised or had brought home to me through contributing to this Wiki ==

=== prose versus lists ===

Short version: lists win every time. They:
* allow others to easily interject, add to or edit your contributions, without having to untangle your text. Even editing your own text as you add things can turn into a scene reminiscent of Monty Python: "NOBODY expects the Spanish Inquisition! Our chief weapon is surprise...surprise and fear...fear and surprise.... Our two weapons are fear and surprise...and ruthless efficiency.... Our *three* weapons are fear, surprise, and ruthless efficiency...and an almost fanatical devotion to the Pope.... Our *four*...no... *Amongst* our weapons.... Amongst our weaponry...are such elements as fear, surprise.... I'll come in again."
* make following step-by-step lists easy, aiding readability and scan-ability
* act as an open invite for other others to contribute (I think at least part of this is to do with depersonalisation, which sounds bad, but in a collaborative wiki text is necessary for effective copy-editing for clarity, length etc.)
* can be easily scannable indexes, into various documentation sub-topics.

=== singular versus plural ===

* MediaWiki seems to have a slight technical preference for singular names of articles. You can use <nowiki>[[Module]]s and
[[Quiz]]zes when you need to use a plural in a sentence instead of [[Modules|Module]] and [[Quizzes|Quiz]] if the page is pluralised</nowiki>
* Categories, when used as lists, make more sense (to me at least) as plurals, but means possibly having two similar very terms e.g. if themes is a list of Moodle Themes, then what do you use for Theme related content? ''Themeing''?

bootstrap-Theme

2012-09-29T20:43:10Z

Bawjaws: /* Bootstrap for Educational Content */

== Twitter Bootstrap Theme==
This page aims to bring together discussions from the themes forum related to the development of a moodle 'base' theme that conforms to the [http://twitter.github.com/bootstrap/ Twitter Bootstrap] coding conventions. There has already been a great deal of work done by individuals within the Moodle community and it's hoped that by formulating this work we may be able to collaborate and build on this.

== Technical Approah ==
There are 5 major categories of development for this theme family:

* Layouts
* Renderers
* Stylesheets
* Javascripts
* Settings (child themes)

=== Layout ===
The General layout will be a 2 column layout based on the [http://twitter.github.com/bootstrap/examples/fluid.html "Fluid" example] providing an "out of the box" responsive grid.

=== Renderers ===
Multiple renderers will be developed to make Moodle output more bootstrap friendly by 1) outputting classes defined in bootstrap.css and 2) outputting semantic HTML exemplified in the bootstrap documentation

=== Stylesheets ===
Bootstrap.css will be the core CSS sheet with adjustments made to reduce re-duplication (like 'reset') and to define Moodle core classes that can't be matched to bootstrap via a renderer

=== Javascripts ===
[http://jshirley.github.com/bootstrap/javascript.html YUI Bootstrap plugins] will be dropped in to the theme in place of the jQuery version(s).

=== Settings ===
On the roadmap: create a child theme (or themes) to provide end users with custom settings, possibly including:

* static or fixed navbar
* light or dark color
* 2 or 3 column layout
* custom logo
* [http://bootswatch.com/ bootswatches]

== Success criteria ==
To have developed a theme that can be used as a base theme, that looks and feels like the default bootsrap interface. (see: [http://twitter.github.com/bootstrap/getting-started.html#examples examples].

==Future developments ==

* To make a responsive version
* Create a library of custom renderers that can be used in themes to make UI changes
* Add theme settings that allow administrators to change the layout of templates through the theme interface.

== Potential projects ==

Some projects that don't require knowledge of PHP to help with:

=== Bootstrap for Educational Content ===

Take some of your existing content, or freely available courses and use Bootstrap styles to format it. Maybe write a document, that uses Bootstrap styles to explain how to apply Bootstrap styles to educational content. Look at the Bootstrap documentation for inspiration, it not only tells you what is possible, it demonstrates many of them in its own presentation:

* http://twitter.github.com/bootstrap/base-css.html#typography
* http://twitter.github.com/bootstrap/base-css.html#code
* http://twitter.github.com/bootstrap/base-css.html#tables
* http://twitter.github.com/bootstrap/base-css.html#images
* http://twitter.github.com/bootstrap/base-css.html#icons
* http://twitter.github.com/bootstrap/components.html#labels-badges
* http://twitter.github.com/bootstrap/components.html#typography
* http://twitter.github.com/bootstrap/components.html#thumbnails
* http://twitter.github.com/bootstrap/components.html#alerts
* http://twitter.github.com/bootstrap/components.html#misc

=== Bootstrap in Moodle content ===

There's plenty of places in Moodle that accept HTML and so can be spruced up with Bootstrap. For example, if you have a public access course, you could add a big green "start learning now" button with a white tick icon to the course description (or many other places on your site) just by using the following html:

<a href="#" class="btn btn-success btn-large"><i class="icon-white icon-ok"></i> Start Learning Now</a>

and the href is simply pointing to the course like any normal link, yet the presentation is transformed. There's probably a million other examples, try coming up with some and sharing them. For experimenting with what's possible with buttons, try: http://www.plugolabs.com/twitter-bootstrap-button-generator/

=== Bootstrap editor ===

Of course, to do the above currently takes HTML coding. But it would be nice if you could just press buttons on a gui. Moodle allows plugin editors, maybe we could use this: http://jhollingworth.github.com/bootstrap-wysihtml5/

=== Bootstrap for TinyMCE ===

The current editor is actually incredibly flexible. It is themeable (http://www.tinymce.com/wiki.php/Creating_a_theme) and Bootstrap comes with a range of editor icons. It should also be able to pick up and use classes from an editor.css file you feed it (http://www.tinymce.com/wiki.php/Configuration:content_css). It should be possible to create a better Bootstrap editor using this flexibility

=== Checkout the competition ===

There's all sorts of Bootstrap projects for various blog engines and content management systems. If you already use say Wordpress you could install some of them an report back anything useful, or just nice looking, that they do and you think would transfer across to Moodle.

=== Create alternate icon sprites ===

All the Bootstrap icons are merged into one single image to make things download faster. If you want to use a different set of icons you'll need to do the same. Instructions here: http://favbulous.com/post/1006/create-custom-icons-for-twitter-bootstrap-easily

== Links to Discussions in Forums ==

* [http://moodle.org/mod/forum/discuss.php?d=212222 (re-)bootstrap: work in progress]
* [http://moodle.org/mod/forum/discuss.php?d=212341 Amelia and Cyborg Bootswatches for Moodle]
* [http://moodle.org/mod/forum/discuss.php?d=208162 Bootstrap for Moodle project]

== Resources ==

* [http://twitter.github.com/bootstrap/ Twitter Bootstrap Home]
* [http://jshirley.github.com/bootstrap/javascript.html Bootstrap YUI Plugins]
* [http://bootswatch.com/ Bootswatch]
* [http://bootsnipp.com/ Bootsnipp]
* [http://fortawesome.github.com/Font-Awesome/ Font Awesome (icon font for Bootstrap)]

bootstrap-Theme

2012-09-29T11:36:55Z

Bawjaws: /* Resources */

== Twitter Bootstrap Theme==
This page aims to bring together discussions from the themes forum related to the development of a moodle 'base' theme that conforms to the [http://twitter.github.com/bootstrap/ Twitter Bootstrap] coding conventions. There has already been a great deal of work done by individuals within the Moodle community and it's hoped that by formulating this work we may be able to collaborate and build on this.

== Technical Approah ==
There are 5 major categories of development for this theme family:

* Layouts
* Renderers
* Stylesheets
* Javascripts
* Settings (child themes)

=== Layout ===
The General layout will be a 2 column layout based on the [http://twitter.github.com/bootstrap/examples/fluid.html "Fluid" example] providing an "out of the box" responsive grid.

=== Renderers ===
Multiple renderers will be developed to make Moodle output more bootstrap friendly by 1) outputting classes defined in bootstrap.css and 2) outputting semantic HTML exemplified in the bootstrap documentation

=== Stylesheets ===
Bootstrap.css will be the core CSS sheet with adjustments made to reduce re-duplication (like 'reset') and to define Moodle core classes that can't be matched to bootstrap via a renderer

=== Javascripts ===
[http://jshirley.github.com/bootstrap/javascript.html YUI Bootstrap plugins] will be dropped in to the theme in place of the jQuery version(s).

=== Settings ===
On the roadmap: create a child theme (or themes) to provide end users with custom settings, possibly including:

* static or fixed navbar
* light or dark color
* 2 or 3 column layout
* custom logo
* [http://bootswatch.com/ bootswatches]

== Success criteria ==
To have developed a theme that can be used as a base theme, that looks and feels like the default bootsrap interface. (see: [http://twitter.github.com/bootstrap/getting-started.html#examples examples].

==Future developments ==

* To make a responsive version
* Create a library of custom renderers that can be used in themes to make UI changes
* Add theme settings that allow administrators to change the layout of templates through the theme interface.

== Potential projects ==

Some projects that don't require knowledge of PHP to help with:

=== Bootstrap for Educational Content ===

Take some of your existing content, or freely available courses and use Bootstrap styles to format it. Maybe write a document, that uses Bootstrap styles to explain how to apply Bootstrap styles to educational content. Look at the Bootstrap documentation for inspiration, it not only tells you what is possible, it demonstrates many of them in its own presentation:
** http://twitter.github.com/bootstrap/base-css.html#typography
** http://twitter.github.com/bootstrap/base-css.html#code
** http://twitter.github.com/bootstrap/base-css.html#tables
** http://twitter.github.com/bootstrap/base-css.html#images
** http://twitter.github.com/bootstrap/base-css.html#icons
** http://twitter.github.com/bootstrap/components.html#labels-badges
** http://twitter.github.com/bootstrap/components.html#typography
** http://twitter.github.com/bootstrap/components.html#thumbnails
** http://twitter.github.com/bootstrap/components.html#alerts
** http://twitter.github.com/bootstrap/components.html#misc

=== Bootstrap in Moodle content ===

There's plenty of places in Moodle that accept HTML and so can be spruced up with Bootstrap. For example, if you have a public access course, you could add a big green "start learning now" button with a white tick icon to the course description (or many other places on your site) just by using the following html:

<a href="#" class="btn btn-success btn-large"><i class="icon-white icon-ok"></i> Start Learning Now</a>

and the href is simply pointing to the course like any normal link, yet the presentation is transformed. There's probably a million other examples, try coming up with some and sharing them. For experimenting with what's possible with buttons, try: http://www.plugolabs.com/twitter-bootstrap-button-generator/

=== Bootstrap editor ===

Of course, to do the above currently takes HTML coding. But it would be nice if you could just press buttons on a gui. Moodle allows plugin editors, maybe we could use this: http://jhollingworth.github.com/bootstrap-wysihtml5/

=== Bootstrap for TinyMCE ===

The current editor is actually incredibly flexible. It is themeable (http://www.tinymce.com/wiki.php/Creating_a_theme) and Bootstrap comes with a range of editor icons. It should also be able to pick up and use classes from an editor.css file you feed it (http://www.tinymce.com/wiki.php/Configuration:content_css). It should be possible to create a better Bootstrap editor using this flexibility

=== Checkout the competition ===

There's all sorts of Bootstrap projects for various blog engines and content management systems. If you already use say Wordpress you could install some of them an report back anything useful, or just nice looking, that they do and you think would transfer across to Moodle.

=== Create alternate icon sprites ===

All the Bootstrap icons are merged into one single image to make things download faster. If you want to use a different set of icons you'll need to do the same. Instructions here: http://favbulous.com/post/1006/create-custom-icons-for-twitter-bootstrap-easily

== Links to Discussions in Forums ==

* [http://moodle.org/mod/forum/discuss.php?d=212222 (re-)bootstrap: work in progress]
* [http://moodle.org/mod/forum/discuss.php?d=212341 Amelia and Cyborg Bootswatches for Moodle]
* [http://moodle.org/mod/forum/discuss.php?d=208162 Bootstrap for Moodle project]

== Resources ==

* [http://twitter.github.com/bootstrap/ Twitter Bootstrap Home]
* [http://jshirley.github.com/bootstrap/javascript.html Bootstrap YUI Plugins]
* [http://bootswatch.com/ Bootswatch]
* [http://bootsnipp.com/ Bootsnipp]
* [http://fortawesome.github.com/Font-Awesome/ Font Awesome (icon font for Bootstrap)]

bootstrap-Theme

2012-09-29T11:35:40Z

Bawjaws: /* Potential projects */

== Twitter Bootstrap Theme==
This page aims to bring together discussions from the themes forum related to the development of a moodle 'base' theme that conforms to the [http://twitter.github.com/bootstrap/ Twitter Bootstrap] coding conventions. There has already been a great deal of work done by individuals within the Moodle community and it's hoped that by formulating this work we may be able to collaborate and build on this.

== Technical Approah ==
There are 5 major categories of development for this theme family:

* Layouts
* Renderers
* Stylesheets
* Javascripts
* Settings (child themes)

=== Layout ===
The General layout will be a 2 column layout based on the [http://twitter.github.com/bootstrap/examples/fluid.html "Fluid" example] providing an "out of the box" responsive grid.

=== Renderers ===
Multiple renderers will be developed to make Moodle output more bootstrap friendly by 1) outputting classes defined in bootstrap.css and 2) outputting semantic HTML exemplified in the bootstrap documentation

=== Stylesheets ===
Bootstrap.css will be the core CSS sheet with adjustments made to reduce re-duplication (like 'reset') and to define Moodle core classes that can't be matched to bootstrap via a renderer

=== Javascripts ===
[http://jshirley.github.com/bootstrap/javascript.html YUI Bootstrap plugins] will be dropped in to the theme in place of the jQuery version(s).

=== Settings ===
On the roadmap: create a child theme (or themes) to provide end users with custom settings, possibly including:

* static or fixed navbar
* light or dark color
* 2 or 3 column layout
* custom logo
* [http://bootswatch.com/ bootswatches]

== Success criteria ==
To have developed a theme that can be used as a base theme, that looks and feels like the default bootsrap interface. (see: [http://twitter.github.com/bootstrap/getting-started.html#examples examples].

==Future developments ==

* To make a responsive version
* Create a library of custom renderers that can be used in themes to make UI changes
* Add theme settings that allow administrators to change the layout of templates through the theme interface.

== Potential projects ==

Some projects that don't require knowledge of PHP to help with:

=== Bootstrap for Educational Content ===

Take some of your existing content, or freely available courses and use Bootstrap styles to format it. Maybe write a document, that uses Bootstrap styles to explain how to apply Bootstrap styles to educational content. Look at the Bootstrap documentation for inspiration, it not only tells you what is possible, it demonstrates many of them in its own presentation:
** http://twitter.github.com/bootstrap/base-css.html#typography
** http://twitter.github.com/bootstrap/base-css.html#code
** http://twitter.github.com/bootstrap/base-css.html#tables
** http://twitter.github.com/bootstrap/base-css.html#images
** http://twitter.github.com/bootstrap/base-css.html#icons
** http://twitter.github.com/bootstrap/components.html#labels-badges
** http://twitter.github.com/bootstrap/components.html#typography
** http://twitter.github.com/bootstrap/components.html#thumbnails
** http://twitter.github.com/bootstrap/components.html#alerts
** http://twitter.github.com/bootstrap/components.html#misc

=== Bootstrap in Moodle content ===

There's plenty of places in Moodle that accept HTML and so can be spruced up with Bootstrap. For example, if you have a public access course, you could add a big green "start learning now" button with a white tick icon to the course description (or many other places on your site) just by using the following html:

<a href="#" class="btn btn-success btn-large"><i class="icon-white icon-ok"></i> Start Learning Now</a>

and the href is simply pointing to the course like any normal link, yet the presentation is transformed. There's probably a million other examples, try coming up with some and sharing them. For experimenting with what's possible with buttons, try: http://www.plugolabs.com/twitter-bootstrap-button-generator/

=== Bootstrap editor ===

Of course, to do the above currently takes HTML coding. But it would be nice if you could just press buttons on a gui. Moodle allows plugin editors, maybe we could use this: http://jhollingworth.github.com/bootstrap-wysihtml5/

=== Bootstrap for TinyMCE ===

The current editor is actually incredibly flexible. It is themeable (http://www.tinymce.com/wiki.php/Creating_a_theme) and Bootstrap comes with a range of editor icons. It should also be able to pick up and use classes from an editor.css file you feed it (http://www.tinymce.com/wiki.php/Configuration:content_css). It should be possible to create a better Bootstrap editor using this flexibility

=== Checkout the competition ===

There's all sorts of Bootstrap projects for various blog engines and content management systems. If you already use say Wordpress you could install some of them an report back anything useful, or just nice looking, that they do and you think would transfer across to Moodle.

=== Create alternate icon sprites ===

All the Bootstrap icons are merged into one single image to make things download faster. If you want to use a different set of icons you'll need to do the same. Instructions here: http://favbulous.com/post/1006/create-custom-icons-for-twitter-bootstrap-easily

== Links to Discussions in Forums ==

* [http://moodle.org/mod/forum/discuss.php?d=212222 (re-)bootstrap: work in progress]
* [http://moodle.org/mod/forum/discuss.php?d=212341 Amelia and Cyborg Bootswatches for Moodle]
* [http://moodle.org/mod/forum/discuss.php?d=208162 Bootstrap for Moodle project]

== Resources ==

* [http://twitter.github.com/bootstrap/ Twitter Bootstrap Home]
* [http://jshirley.github.com/bootstrap/javascript.html Bootstrap YUI Plugins]
* [http://bootswatch.com/ Bootswatch]
* [http://bootsnipp.com/ Bootsnipp]

bootstrap-Theme

2012-09-29T11:28:40Z

Bawjaws: adding some non-php projects

== Twitter Bootstrap Theme==
This page aims to bring together discussions from the themes forum related to the development of a moodle 'base' theme that conforms to the [http://twitter.github.com/bootstrap/ Twitter Bootstrap] coding conventions. There has already been a great deal of work done by individuals within the Moodle community and it's hoped that by formulating this work we may be able to collaborate and build on this.

== Technical Approah ==
There are 5 major categories of development for this theme family:

* Layouts
* Renderers
* Stylesheets
* Javascripts
* Settings (child themes)

=== Layout ===
The General layout will be a 2 column layout based on the [http://twitter.github.com/bootstrap/examples/fluid.html "Fluid" example] providing an "out of the box" responsive grid.

=== Renderers ===
Multiple renderers will be developed to make Moodle output more bootstrap friendly by 1) outputting classes defined in bootstrap.css and 2) outputting semantic HTML exemplified in the bootstrap documentation

=== Stylesheets ===
Bootstrap.css will be the core CSS sheet with adjustments made to reduce re-duplication (like 'reset') and to define Moodle core classes that can't be matched to bootstrap via a renderer

=== Javascripts ===
[http://jshirley.github.com/bootstrap/javascript.html YUI Bootstrap plugins] will be dropped in to the theme in place of the jQuery version(s).

=== Settings ===
On the roadmap: create a child theme (or themes) to provide end users with custom settings, possibly including:

* static or fixed navbar
* light or dark color
* 2 or 3 column layout
* custom logo
* [http://bootswatch.com/ bootswatches]

== Success criteria ==
To have developed a theme that can be used as a base theme, that looks and feels like the default bootsrap interface. (see: [http://twitter.github.com/bootstrap/getting-started.html#examples examples].

==Future developments ==

* To make a responsive version
* Create a library of custom renderers that can be used in themes to make UI changes
* Add theme settings that allow administrators to change the layout of templates through the theme interface.

==Potential projects ==

Some projects that don't require knowledge of PHP to help with:

* '''Bootstrap for Educational Content''' - take some of your existing content, or freely available courses and use Bootstrap styles to format it. Maybe write a document, that uses Bootstrap styles to explain how to apply Bootstrap styles to educational content. Look at the Bootstrap documentation for inspiration, it not only tells you what is possible, it demonstrates many of them in its own presentation:
** http://twitter.github.com/bootstrap/base-css.html#typography
** http://twitter.github.com/bootstrap/base-css.html#code
** http://twitter.github.com/bootstrap/base-css.html#tables
** http://twitter.github.com/bootstrap/base-css.html#images
** http://twitter.github.com/bootstrap/base-css.html#icons
** http://twitter.github.com/bootstrap/components.html#labels-badges
** http://twitter.github.com/bootstrap/components.html#typography
** http://twitter.github.com/bootstrap/components.html#thumbnails
** http://twitter.github.com/bootstrap/components.html#alerts
** http://twitter.github.com/bootstrap/components.html#misc

* '''Bootstrap in Moodle content''' - there's plenty of places in Moodle that accept HTML and so can be spruced up with Bootstrap. For example, if you have a public access course, you could add a big green "start learning now" button with a white tick icon to the course description (or many other places on your site) just by using the following html:

<a href="#" class="btn btn-success btn-large"><i class="icon-white icon-ok"></i> Start Learning Now</a>

and the href is simply pointing to the course like any normal link, yet the presentation is transformed. There's probably a million other examples, try coming up with some and sharing them. For experimenting with what's possible with buttons, try: http://www.plugolabs.com/twitter-bootstrap-button-generator/

* '''Bootstrap editor''' - of course, to do the above currently takes HTML coding. But it would be nice if you could just press buttons on a gui. Moodle allows plugin editors, maybe we could use this: http://jhollingworth.github.com/bootstrap-wysihtml5/

* '''Bootstrap for TinyMCE''' - the current editor is actually incredibly flexible. It is themeable (http://www.tinymce.com/wiki.php/Creating_a_theme) and Bootstrap comes with a range of editor icons. It should also be able to pick up and use classes from an editor.css file you feed it (http://www.tinymce.com/wiki.php/Configuration:content_css). It should be possible to create a better Bootstrap editor using this flexibility

* '''Checkout the competition''' - there's all sorts of Bootsrap projects for various blog engines and content management systems. If you already use say Wordpress you could install some of them an report back anything useful, or just nice looking, that they do and you think would transfer across to Moodle.

* '''Create alternate icon sprites''' - all the Bootstrap icons are merged into one single image to make things download faster. If you want to use a different set of icons you'll need to do the same. Instructions here: http://favbulous.com/post/1006/create-custom-icons-for-twitter-bootstrap-easily

== Links to Discussions in Forums ==

* [http://moodle.org/mod/forum/discuss.php?d=212222 (re-)bootstrap: work in progress]
* [http://moodle.org/mod/forum/discuss.php?d=212341 Amelia and Cyborg Bootswatches for Moodle]
* [http://moodle.org/mod/forum/discuss.php?d=208162 Bootstrap for Moodle project]

== Resources ==

* [http://twitter.github.com/bootstrap/ Twitter Bootstrap Home]
* [http://jshirley.github.com/bootstrap/javascript.html Bootstrap YUI Plugins]
* [http://bootswatch.com/ Bootswatch]
* [http://bootsnipp.com/ Bootsnipp]

Autenticació

2008-06-26T13:05:29Z

Bawjaws:

Location: ''Administration > Users > Authentication > Manage authentication''

==Authentication methods==

One of the first things you need to consider when setting up your Moodle site is user authentication i.e. enabling people to login to your Moodle site.

Authentication methods (also known as authentication plugins) include:

*[[Manual accounts]]
*[[No login]]
*[[Email-based self-registration]]
*[[CAS server (SSO)]]
*[[External database authentication|External database]]
*[[FirstClass authentication|FirstClass server]]
*[[IMAP authentication|IMAP server]]
*[[LDAP authentication|LDAP server]]
*[[Moodle Network|Moodle Network authentication]]
*[[NNTP authentication|NNTP server]]
*[[No authentication]]
*[[PAM (Pluggable Authentication Modules)]]
*[[POP3 server]]
*[[RADIUS authentication|RADIUS server]]
*[[Shibboleth]]
*[[NTLM authentication|NTLM/Integrated Authentication (3rd party plugin)]]

==Setting the authentication method==
[[Image:authentication plugins.png|thumb|Choosing an authentication plugin, (only shows top of Authentication page)]]
To set the authentication method:

#Click on Authentication in the Site Administration block.
#On the authentication page, click on the closed eye icon to enable your chosen authentication plugin. In Moodle 1.8 onwards, you can choose to use more than one authentication method. Use the up/down arrow icons to arrange the plugins in order, with the plugin handling the most logins at the top of the page. This will minimise authentication server load.
#If you have chosen [[Email-based self-registration]], select "Email-based self-registration" from the self registration drop-down menu in the common settings section. Potential users will then be presented with a "Create new account" button on the login page.
#If you have courses with guest access, set the Guest login button to show.
#Click the "Save changes" button.
#Click on Settings opposite the authentication plugin(s) you have chosen.
#Configure the required settings and click the "Save changes" button.

==Multi-authentication==
{{Moodle 1.8}}From Moodle 1.8 onwards, multi-authentication is supported. Simply click on the closed eye icon to enable a particular plugin.

Each authentication plugin may be used to find a username/password match. Once found, a user is logged in and alternative plugins are not used. Therefore the plugin which handles the most logins should be moved to the top of the page in order that less load is put on authentication servers.

==Self registration==
If you wish users to be able to create their own user accounts, i.e. self-register, then select Email-based self-registration from the drop-down menu.

==Guest login button==
You can hide or show the guest login button on the login page.

==Alternate login URL==
This should be used with care, since a mistake in the URL or on the actual login page can lock you out of your site. If you do mess it up, you can remove the entry from your database (table mdl_config) using, e.g., phpmyadmin for mysql.

==Forgotten password URL==
{{Moodle 1.9}}If your lost password handling is performed entirely outside of Moodle (for example, only by a help desk), you can set the url of that service here. Anybody pressing a "lost password" link in Moodle will be redirected to this URL. Note that this will disable '''all''' of Moodle's lost password recovery options regardless of authentication method(s) in use.

==ReCAPTCHA==
[[Image:New account form with captcha element.png|thumb|New account form with CAPTCHA element]]
A CAPTCHA is a program that can tell whether its user is a human or a computer. CAPTCHAs are used by many websites to prevent abuse from bots, or automated programs usually written to generate spam. No computer program can read distorted text as well as humans can, so bots cannot navigate sites protected by CAPTCHAs.

{{Moodle 1.9}}From Moodle 1.9.1 onwards, spam protection may be added to the [[Email-based self-registration]] new account form with a CAPTCHA element - a challenge-response test used to determine whether the user is human.

ReCAPTCHA keys can be obtained from http://recaptcha.net by [https://admin.recaptcha.net/accounts/signup/?next= signing up for an account] (free) then entering a domain. The public and private keys provided can then be copied and pasted into the ''recaptchapublickey'' and ''recaptchaprivatekey'' fields in the manage authentication common settings, and the changes saved.

In addition to setting reCAPTCHA keys, email-based self-registration should be set as the self registration authentication plugin in the manage authentication common settings and the reCAPTCHA element should be enabled in the [[Email-based self-registration]] settings.

==Locking profile fields==
To prevent users from altering some fields (e.g. students changing profile information to inappropriate or misleading information), the site administrator can lock profile fields.

[[Image:Authent-data-map-fname.jpg|Data Mapping Options]]
*These fields are optional. You can choose to pre-fill some Moodle user fields with information from the LDAP fields that you specify here. If you leave these fields blank, then nothing will be transferred from LDAP and Moodle defaults will be used instead. In either case, the user will be able to edit all of these fields after they log in.
*'''Update local''': If enabled, the field will be updated (from external auth) every time the user logs in or there is a user synchronization. Fields set to update locally should be locked.
*'''Lock value''': If enabled, will prevent Moodle users and admins from editing the field directly. Use this option if you are maintaining this data in the external auth system.
*'''Update external''': If enabled, the external auth will be updated when the user record is updated. Fields should be unlocked to allow edits. Note: Updating external LDAP data requires that you set '''binddn''' and '''bindpw''' to a bind-user with editing privileges to all the user records. It currently does not preserve multi-valued attributes, and will remove extra values on update.

If you are using a mixture of authentication types (such as IMAP and manual), then the fields you lock in the authentication options will only apply to the type of authentication indicated by the drop down box at the top of the screen. Remember to test the field locking by logging in with the proper type of account! If you test with a manual account but have set the field locking to apply to IMAP accounts, you will not be able to tell if it worked!

==See also==
*Multi authentication in [[Upgrading to Moodle 1.8]]
*[http://moodle.org/mod/forum/view.php?id=42 Using Moodle: User authentication] forum
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=95559 Do users need e-mail addresses?] forum discussion
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97938 Admin approving self registrations?] forum discussion

[[Category:Authentication]]

[[fr:Authentification]]

Autenticació

2008-06-26T12:57:03Z

Bawjaws: /* Forgotton password URL */ typo forgotton -> forgotten

Location: ''Administration > Users > Authentication > Manage authentication''

==Authentication methods==

One of the first things you need to consider when setting up your Moodle site is user authentication i.e. enabling people to login to your Moodle site.

Authentication methods (also known as authentication plugins) include:

*[[Manual accounts]]
*[[No login]]
*[[Email-based self-registration]]
*[[CAS server (SSO)]]
*[[External database authentication|External database]]
*[[FirstClass authentication|FirstClass server]]
*[[IMAP authentication|IMAP server]]
*[[LDAP authentication|LDAP server]]
*[[Moodle Network|Moodle Network authentication]]
*[[NNTP authentication|NNTP server]]
*[[No authentication]]
*[[PAM (Pluggable Authentication Modules)]]
*[[POP3 server]]
*[[RADIUS authentication|RADIUS server]]
*[[Shibboleth]]
*[[NTLM authentication|NTLM/Integrated Authentication (3rd party plugin)]]

==Setting the authentication method==
[[Image:authentication plugins.png|thumb|Choosing an authentication plugin, (only shows top of Authentication page)]]
To set the authentication method:

#Click on Authentication in the Site Administration block.
#On the authentication page, click on the closed eye icon to enable your chosen authentication plugin. In Moodle 1.8 onwards, you can choose to use more than one authentication method. Use the up/down arrow icons to arrange the plugins in order, with the plugin handling the most logins at the top of the page. This will minimise authentication server load.
#If you have chosen [[Email-based self-registration]], select "Email-based self-registration" from the self registration drop-down menu in the common settings section. Potential users will then be presented with a "Create new account" button on the login page.
#If you have courses with guest access, set the Guest login button to show.
#Click the "Save changes" button.
#Click on Settings opposite the authentication plugin(s) you have chosen.
#Configure the required settings and click the "Save changes" button.

==Multi-authentication==
{{Moodle 1.8}}From Moodle 1.8 onwards, multi-authentication is supported. Simply click on the closed eye icon to enable a particular plugin.

Each authentication plugin may be used to find a username/password match. Once found, a user is logged in and alternative plugins are not used. Therefore the plugin which handles the most logins should be moved to the top of the page in order that less load is put on authentication servers.

==Self registration==
If you wish users to be able to create their own user accounts, i.e. self-register, then select Email-based self-registration from the drop-down menu.

==Alternate login URL==
This should be used with care, since a mistake in the URL or on the actual login page can lock you out of your site. If you do mess it up, you can remove the entry from your database (table mdl_config) using, e.g., phpmyadmin for mysql.

==Forgotten password URL==
{{Moodle 1.9}}If your lost password handling is performed entirely outside of Moodle (for example, only by a help desk), you can set the url of that service here. Anybody pressing a "lost password" link in Moodle will be redirected to this URL. Note that this will disable '''all''' of Moodle's lost password recovery options regardless of authentication method(s) in use.

==ReCAPTCHA==
[[Image:New account form with captcha element.png|thumb|New account form with CAPTCHA element]]
A CAPTCHA is a program that can tell whether its user is a human or a computer. CAPTCHAs are used by many websites to prevent abuse from bots, or automated programs usually written to generate spam. No computer program can read distorted text as well as humans can, so bots cannot navigate sites protected by CAPTCHAs.

{{Moodle 1.9}}From Moodle 1.9.1 onwards, spam protection may be added to the [[Email-based self-registration]] new account form with a CAPTCHA element - a challenge-response test used to determine whether the user is human.

ReCAPTCHA keys can be obtained from http://recaptcha.net by [https://admin.recaptcha.net/accounts/signup/?next= signing up for an account] (free) then entering a domain. The public and private keys provided can then be copied and pasted into the ''recaptchapublickey'' and ''recaptchaprivatekey'' fields in the manage authentication common settings, and the changes saved.

In addition to setting reCAPTCHA keys, email-based self-registration should be set as the self registration authentication plugin in the manage authentication common settings and the reCAPTCHA element should be enabled in the [[Email-based self-registration]] settings.

==Locking profile fields==
To prevent users from altering some fields (e.g. students changing profile information to inappropriate or misleading information), the site administrator can lock profile fields.

[[Image:Authent-data-map-fname.jpg|Data Mapping Options]]
*These fields are optional. You can choose to pre-fill some Moodle user fields with information from the LDAP fields that you specify here. If you leave these fields blank, then nothing will be transferred from LDAP and Moodle defaults will be used instead. In either case, the user will be able to edit all of these fields after they log in.
*'''Update local''': If enabled, the field will be updated (from external auth) every time the user logs in or there is a user synchronization. Fields set to update locally should be locked.
*'''Lock value''': If enabled, will prevent Moodle users and admins from editing the field directly. Use this option if you are maintaining this data in the external auth system.
*'''Update external''': If enabled, the external auth will be updated when the user record is updated. Fields should be unlocked to allow edits. Note: Updating external LDAP data requires that you set '''binddn''' and '''bindpw''' to a bind-user with editing privileges to all the user records. It currently does not preserve multi-valued attributes, and will remove extra values on update.

If you are using a mixture of authentication types (such as IMAP and manual), then the fields you lock in the authentication options will only apply to the type of authentication indicated by the drop down box at the top of the screen. Remember to test the field locking by logging in with the proper type of account! If you test with a manual account but have set the field locking to apply to IMAP accounts, you will not be able to tell if it worked!

==See also==
*Multi authentication in [[Upgrading to Moodle 1.8]]
*[http://moodle.org/mod/forum/view.php?id=42 Using Moodle: User authentication] forum
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=95559 Do users need e-mail addresses?] forum discussion
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97938 Admin approving self registrations?] forum discussion

[[Category:Authentication]]

[[fr:Authentification]]

Plan to improve ability to delegate administer tasks to course category level

2007-07-19T09:20:16Z

Bawjaws: Development:Plan to improve ability to delegate administer tasks to course category level moved to Development:Plan to improve ability to delegate administrator tasks to course category level: typo

#redirect [[Development:Plan to improve ability to delegate administrator tasks to course category level]]

Plan to improve ability to delegate administrator tasks to course category level

2007-07-19T09:20:16Z

==Motivation==

In a large organisation it is likely that course categories will repesent (in some sense) departments. It would be useful to be able to, effectively, have administrators assigned at the category context and to expect them to have rights to create/delete/edit subcategories and create/delete/edit courses. Some parts of this work, but a lack of underlying original functionality make this inconsistent and incomplete. Roles was mostly a wrapper around existing functionality, so the concept of being able to administer all the courses within a particular role didn't exist but now it becomes possible (and desirable) to assign the administrator role in the Category context.

The main problem area is in the course and category editing screen. This is split across two scripts - course/index.php and course/category.php. The former displays the entire tree and allows new categories to be added and existing ones to be moved, deleted and edited. The latter shows the contents of categories (and subcategories) but allows no editing. It does, however, allow new courses to be added. In an ideal world this would have been a single script providing editing ability within any category level but this would now require a substantial rewrite.

This plan is to make a few small changes to provide a better level of functionality without major changes, rewrites, or refactoring.

==Partial Workaround==

Creating a new role with a single capability allowed - moodle/category:update - and assigning the user to this at the site level gives them access the category and course editing screen (or it should). They will *also* be assigned to the administrator (or equivalent) role in the appropriate category context.

This gives them access to the course/index.php screen enabling them to manipulate categories. The roles system (mostly) controls the rights appropriately to the category editing functions.

==Issues==

Some of these were clearly bugs anyway and have been fixed, but they are noted for completeness.

===Courses item in Administration not tied to capability===

''This has been fixed''

Giving somebody the capability moodle/category:update did not give the option in the Administration menu. This has been fixed.

===No capability for moving categories===

Creating and deleting categories are both covered by capabilities and this is correctly reflected in the course/index.php code. However, the ability to move categories is only controlled by the moodle/category:update capability - the same one that gives you access to the page at all. There is no finer grain control available.

'''Proposal:''' Add a new capability '''moodle/category:move''' along with apropriate code in course/index.php to enforce it.

===No ability to add subcategories directly===

You can only add a new category at the top level even though you can assign the create permission at the category context.

'''Proposal:''' Factor out the code for this out of course/index.php into course/lib.php (functions exist for display already) and add aditionaly to course/category.php with appropriate permissions checking.

'''Caveat"''' This isn't ideal as the course/category.php script does not allow further manipulation of the category; you would have to return to the course/index.php page. However, it's much better than nothing and is an order of magnitude easier to do than a complete rewrite of the two scripts to combine them (which would be the ideal solution)

==Scope==

I don't think there's anything too complex or critical in here and would like to get this into 1.8.3.

==See Also==

The following tracker reports are related:
* [http://tracker.moodle.org/browse/MDL-10049 MDL-10049]
* [http://tracker.moodle.org/browse/MDL-10496 MDL-10496]
* [http://tracker.moodle.org/browse/MDL-10093 MDL-10093]
* [http://tracker.moodle.org/browse/MDL-10031 MDL-10031]
* [http://tracker.moodle.org/browse/MDL-10029 MDL-10029]

Discussion
* [http://moodle.org/mod/forum/discuss.php?d=76226 http://moodle.org/mod/forum/discuss.php?d=76226]

MP3 player

2007-03-30T13:58:18Z

Bawjaws: it's best to ask questions in the forums, and add them here once you have an answer

The multimedia filter embeds MP3 files in a streaming player made with Flash. The big MP3 player is used when an MP3 file is added as a [[Resources|resource]] e.g. [http://moodle.org/mod/resource/view.php?id=2296 Moodle Features Demo: MP3 file]. The small player is used when an MP3 file is linked to from within a forum post or another resource or activity using the [[HTML editor]].

==MP3 player rates==

To ensure that MP3 files are played at the correct rate, sample rates of 11, 22 or 44 kHz should be used. Constant Bit Rate (CBR) files are also recommended over Variable Bit Rate (VBR) files.

==Flash security settings==

Security changes in Flash player 7 may result in the MP3 player not playing MP3 files hosted on a remote server. This issue may be resolved by writing a cross-domain policy for the remote server and/or each user changing their global security settings in the Flash player settings manager.

===Cross-domain policy===

To create a cross-domain policy, save the code below as ''crossdomain.xml'' and place the file at the root of the remote server.

<cross-domain-policy>
<allow-access-from domain="www.yourmoodlesite.org" />
</cross-domain-policy>

Please refer to [http://www.macromedia.com/devnet/flash/articles/fplayer_security.html Macromedia - Developer Center: Security Changes in Macromedia Flash Player 7] for further details.

===Global security settings===

Please refer to [http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager02.html Macromedia - Flash Player Help: Global Privacy Settings Panel].

==MP3 player colours==

''theme/yourtheme/config.php'' contains options for changing the default colours (black, white and grey) of the MP3 player.

$THEME->resource_mp3player_colors =
'bgColour=000000&btnColour=ffffff&btnBorderColour=cccccc&iconColour=000000&'.
'iconOverColour=00cc00&trackColour=cccccc&handleColour=ffffff&loaderColour=ffffff&'.
'font=Arial&fontColour=3333FF';
/// With this you can control the colours of the "big" MP3 player
/// that is used for MP3 resources.

$THEME->filter_mediaplugin_colors =
'bgColour=000000&btnColour=ffffff&btnBorderColour=cccccc&iconColour=000000&'.
'iconOverColour=00cc00&trackColour=cccccc&handleColour=ffffff&loaderColour=ffffff&';
/// ...And this controls the small embedded player

==MP3 playback options==

''theme/yourtheme/config.php'' contains options for changing the playback options of the MP3 player.

* <code>waitForPlay</code> determines whether the MP3 file starts downloading as soon as the player appears on the page (<code>waitForPlay=no</code>), or whether the play button must be pressed before the MP3 file starts downloading (<code>waitForPlay=yes</code>).

* <code>autoPlay</code> determines whether the MP3 player starts playing the MP3 as soon as the player appears on the page (<code>autoPlay=yes</code>), or whether it must be fully downloaded before playing (<code>autoPlay=no</code>).

* <code>buffer</code> determines how many seconds of the MP3 file must be downloaded before the MP3 starts playing e.g. 10 seconds (<code>buffer=10</code>).

'''Default playback options'''

* Big MP3 player: <code>buffer=10&waitForPlay=no&autoPlay=yes</code>
* Small MP3 player: <code>waitForPlay=yes&autoPlay=no</code>

==Inserting sounds into questions==
[http://moodle.org/mod/forum/discuss.php?d=33335 In a forum, Joseph Rézeau] offer this

There are various ways to insert links to media files in Moodle.
You can
*(1) insert a link which when clicked will open a new window activating your computer's default media player (e.g. quicktime, realaudio, windows media player, etc.)
*(2) OR rely on the automatic insertion of the small Flash player built-in Moodle
*(3) OR both!

The [[filter]] for multimedia must be on and Flash enabled. The HTML editor needs to be active for the question content.
#In the question text, type "Listen to this sound and select your answer."
#Select by highlighting "this sound"
#Click on the Insert Web Link button
#Give the address of your MP3 file, either a web address or an internal address of a file located in the moodledata directory of your Moodle course.
#Toggle HTML source and view the result, something like this: Listen to <nowiki> < a href="http://moodle/file.php/2/audio/trumpet.mp3" >this sound< /a > </nowiki>and say what you heard.
#Now type in the rest of your question data, depending on its type (MCQ, short answer, etc.).
#The result will look something like (3) in screen dump below.
#The student has a choice of using the Flash player (with its minimum buttons) or clicking on the link, which will open the computer's default media player, with all its buttons.

(2) Method to get the Flash player only, and no link to open an external player

#In the question text, type "Listen to this sound xxx and say what you heard."
#Select xxx
#Click on the Insert Web Link button
#Give the address of your MP3 file, either a web address or an internal address of a file located in the moodledata directory of your Moodle course.
#Toggle HTML source and view the result, something like this: Listen to <nowiki>< a href="http://moodle/file.php/2/audio/trumpet.mp3" >xxx< /a > </nowiki> and say what you heard.
#Delete xxx
#The result will look something like (2) in screen dump below.
#The student can only use the Flash player.

[[Image:Quiz question MP3 example.JPG|thumb|center|Example of Quiz Question with Sound]]

== Temporarily disable the MP3 player ==
* You can surround your link with <nowiki><nolink></nolink></nowiki> tags to stop any kind of processing including the multimedia filters that create the MP3 player. This may be useful when linking to external MP3 files with characters in their name that Flash cannot understand.

==See also==

* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=43297 Multimedia resource filtering on the course page] forum discussion
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=14663 mp3 player rates] forum discussion
* [[Podcasting]]

[[Category:Administrator]]
[[Category:Teacher]]
[[Category:Filter]]
[[Category:Audio]]

Recording audio for Moodle

2007-03-06T14:26:46Z

Bawjaws: /* Sanyo Digital MP3 recorder ICR-B170NX */ minor typo

If you are '''recording audio for Moodle''' the following guide will helpful. It suggests a route to record and upload simple audio into Moodle, where editing of the audio file is neither required or desired.

=== Introduction ===
The [[Audio in Moodle]] page explains that although you can use almost any audio file with Moodle, one particular type of MP3 file allows for maximum compatibility while also allowing for more flexible usage within Moodle.

Similarly though there are several methods available for creating these files there is one method that allows staff and students to create such files with ease. The right kind of digital voice (or memo-) recorder, familiar to many, can allow recordings in a variety of situations without the need for extensive technical knowledge or training and with minimal outlay that could potentially pay for itself in saved staff time after one use.

=== Requirements ===
The ideal requirements for such a device are:

* a USB connection
* no need to install any software
* records in an appropriate mp3 format

Combined, these requirements allow someone with minimal technical skills to record audio and have it uploaded and playing via Moodle within minutes.

=== Potential Devices ===

However, this short list of requirements reduces the field of potential purchases from hundreds to a handful. The following appear, based on information from their manuals, to fit the bill. Some have provisos or other useful info listed below, click to read it.

* Phillips Digital Voice Tracer, 7790 or 7890
* Sanyo ICR-S250RM

The following have been tested and found to work

* [[#Sanyo Digital MP3 recorder ICR-B170NX|Sanyo Digital MP3 recorder ICR-B170NX]]
* [[#Sanyo Digital MP3 recorder ICR-A190 / ICR-B190|Sanyo Digital MP3 recorder ICR-A190 / ICR-B190]]

==== Sanyo Digital MP3 recorder ICR-B170NX ====

Has 4 quality modes SHQ, HQ, SP, LP. Only the HQ mode (64kbps, 22.1kHz) is suitable for these purposes and it can record up to 2 hours 10 minutes. Takes replaceable AAA batteries.

==== Sanyo Digital MP3 recorder ICR-A190 / ICR-B190 ====
Has 4 quality modes XHQ, HQ, SP, LP. the longer /lower quality recording times of the LP and SP modes are not suitable. Has up to 4 hours 20 minutes recording time in HQ mode (64kbps, 22.1kHz) and 2 hours, 10 minutes in XHQ mode (128kbps, 44.1kHz). Takes replaceable AAA batteries.

[[Category:Teacher]]
[[Category:Administrator]]
[[category:Audio]]

Categoria:Feedback

2007-03-06T14:13:06Z

Bawjaws:

Pages about the [[Feedback module]], one of the [[:Category:Modules (non-standard)|Non-standard modules]].

Viewing Feedback responses

2007-03-06T14:11:12Z

Bawjaws: + cat: Feedback

{{Feedback}}

You can view responses both anonymously or not.

[[Category:Feedback]]
[[Category:Teacher]]

Building Feedback

2007-03-06T14:10:48Z

Bawjaws:

{{Feedback}}

After setting a new Feedback you design it by '''adding questions'''. Select the type of question from the drop down list in the top left corner then click the ''Add question to activity'' button.

=== Standard options ===

The following apply to all or most question types.

==== Position ====

This number controls the order of the questions. You can also rearrange questions by clicking the position up and down arrows.

==== Required ====

These questions are required to be answered and will prompt the user if they are left unaswered. These questions are highlighted with a red star for users, and have a yellow exclamation point beside them when editing Feedback questions.

=== Available question types ===

==== Multiple choice - multiple answers ====

==== Multiple choice - single answer allowed (dropdownlist) ====

==== Dropdownlist (rated) ====

==== Label ====

Similarly to a standard Moodle label, this allows you to add abritrary text between questions allowing for extra explanation or to divide the Feedback into sections.

==== Numeric answer (added in Moodle 1.7) ====

==== Picture ====

This question type allows you to choose from a range of images to display to the user, who can then select from the shortlist you present.

==== Multiple choice - single answer ====

==== Radiobutton (rated) ====

==== Longer Text Answer ====

==== Short Text Answer ====

[[Category:Feedback]]
[[Category:Teacher]]

Feedback settings

2007-03-06T14:10:24Z

Bawjaws: + cat: Feedback

{{Feedback}}After selecting Feedback from the Activities menu, you will be presented with a list of options for '''setting up a Feedback'''.

=== Name ===

Give your Feedback a title.

=== Description ===

This text will be displayed to users before they enter the feedback.

=== Open and Close Feedback ===

This allows you to set a time period during which the Feedback will be available to responses.

=== Record User Names ===

Choose from the following options:
* Anonymous
* Users' Names Will Be Logged and Shown With Answers

=== Show analysis to students ===

Yes/No. The summary results can be shown to respondents, or shown only to teachers.

=== Send E-Mail-Notifications ===

Yes/No. Notifications will be sent to the Moodle site administrators upon the submission.

=== Multiple submit ===

Yes/No, for anonymous polls allow unlimited answers for every user, for polls where the user name is logged this allow users to resubmit their answers.

=== Page after submit ===

This allows you to present users with a message after completion.

=== Group mode ===

The group mode can be one of three levels:

* No groups - There are no sub groups, everyone is part of one big community
* Separate groups - Each group can only see their own group, others are invisible
* Visible groups - Each group works in their own group, but can also see other groups

The group mode can be defined at two levels:

* Course level - The group mode defined at the course level is the default mode for all activities defined within that course
* Activity level - Each activity that supports groups can also define its own grouping mode. If the course is set to [[Force group mode|"force group mode"]] then the setting for each activity is ignored.

=== Visible to students ===

You can hide the activity from students by selecting "Hide" here. It is useful if you wouldn't like to make the activity available immediately.

[[Category:Feedback]]
[[Category:Teacher]]

Mòdul Realimentació

2007-03-06T14:09:57Z

Bawjaws: + cat: Feedback

{{Feedback}}

The '''Feedback module''' allows you to create and conduct surveys to collect feedback from [[Student]]s. It is smaller in scope and therefore easier to use than the [[Questionnaire module]], and unlike the [[Survey module|Survey]] tool allows you to write your own questions, rather than choose from a list of pre-written survey instruments. It is currently an optional module though it may become part of the standard install for version 1.9 of Moodle.

== See also ==

* [http://moodle.org/mod/data/view.php?d=13&rid=95 Discuss and/or download this module]

[[Category:Teacher]]
[[Category:Modules (non-standard)]]
[[Category:Feedback]]

Plantilla:Feedback

2007-03-06T14:07:44Z

Bawjaws:

<div class="sideblock right" style="width: 12em;">
<div class="header">[[Feedback module]]</div>
<div class="content">
* [[Adding/editing a feedback form]]
* [[Adding Feedback questions|Adding questions]]
* [[Viewing Feedback responses|Viewing responses]]
</div>
</div>

Viewing Feedback responses

2007-03-06T13:39:56Z

Bawjaws:

{{Feedback}}

You can view responses both anonymously or not.

Viewing Feedback responses

2007-03-06T13:39:41Z

Bawjaws:

{{feedback}}

You can view responses both anonymously or not.

Viewing Feedback responses

2007-03-06T13:39:13Z

Bawjaws: just starting, no content as yet

Building Feedback

2007-03-06T13:32:04Z

Bawjaws:

Plantilla:Feedback

2007-03-06T13:28:04Z

Bawjaws:

mod/feedback/analysis

2007-03-06T13:23:33Z

Bawjaws:

#REDIRECT [[Viewing Feedback responses]]

mod/feedback/edit item

2007-03-06T13:15:53Z

Bawjaws:

#REDIRECT [[Adding Feedback questions]]

mod/feedback/edit

2007-03-06T13:08:57Z

Bawjaws:

#REDIRECT [[Adding Feedback questions]]

Building Feedback

2007-03-06T13:06:43Z

Bawjaws: creating

{{Feedback}}

After setting a new Feedback you design it by '''adding questions'''. Select the type of question from the drop down list in the top left corner then

=== Standard options ===

The following apply to all or most question types.

==== Position ====

This number controls the position
=== Available question types ===

==== Multiple choice - multiple answers ====

==== Multiple choice - single answer allowed (dropdownlist) ====

==== Dropdownlist (rated) ====

==== Label ====

Similarly to a standard Moodle label, this allows you to add abritrary text between questions allowing for extra explanation or to divide the Feedback into sections.

==== Numeric answer (added in Moodle 1.7) ====

==== Picture ====

This question type allows you to choose from a range of images to display to the user, who can then select from the shortlist you present.

==== Multiple choice - single answer ====

==== Radiobutton (rated) ====

==== Longer Text Answer ====

==== Short Text Answer ====

Setting up a Feedback

2007-03-06T13:04:13Z

Bawjaws: Setting up a Feedback moved to Adding/editing a feedback form: adding Moodledocs redirects

#redirect [[Adding/editing a feedback form]]

Feedback settings

2007-03-06T13:04:13Z

Bawjaws: Setting up a Feedback moved to Adding/editing a feedback form

mod/feedback/mod

2007-03-06T13:03:08Z

Bawjaws:

#REDIRECT [[Adding/editing a feedback form]]

Feedback settings

2007-03-06T12:40:32Z

Bawjaws: adding template

Feedback settings

2007-03-06T12:03:48Z

Bawjaws:

After selecting Feedback from the Activities menu, you will be presented with a list of options for '''setting up a Feedback'''.

=== Name ===

Give your Feedback a title.

=== Description ===

This text will be displayed to users before they enter the feedback.

=== Open and Close Feedback ===

This allows you to set a time period during which the Feedback will be available to responses.

=== Record User Names ===

Choose from the following options:
* Anonymous
* Users' Names Will Be Logged and Shown With Answers

=== Show analysis to students ===

Yes/No. The summary results can be shown to respondents, or shown only to teachers.

=== Send E-Mail-Notifications ===

Yes/No. Notifications will be sent to the Moodle site administrators upon the submission.

=== Multiple submit ===

Yes/No, for anonymous polls allow unlimited answers for every user, for polls where the user name is logged this allow users to resubmit their answers.

=== Page after submit ===

This allows you to present users with a message after completion.

=== Group mode ===

The group mode can be one of three levels:

* No groups - There are no sub groups, everyone is part of one big community
* Separate groups - Each group can only see their own group, others are invisible
* Visible groups - Each group works in their own group, but can also see other groups

The group mode can be defined at two levels:

* Course level - The group mode defined at the course level is the default mode for all activities defined within that course
* Activity level - Each activity that supports groups can also define its own grouping mode. If the course is set to [[Force group mode|"force group mode"]] then the setting for each activity is ignored.

=== Visible to students ===

You can hide the activity from students by selecting "Hide" here. It is useful if you wouldn't like to make the activity available immediately.

Feedback settings

2007-03-06T11:57:22Z

Bawjaws:

After selecting Feedback from the Activities menu, you will be presented with a list of options for '''setting up a Feedback'''.

=== Name ===

Give your Feedback a title.

=== Description ===

This text will be displayed to users before they enter the feedback.

=== Open and Close Feedback ===

This allows you to set a time period during which the Feedback will be available to responses.

=== Record User Names ===

Choose from the following options:
* Anonymous
* Users' Names Will Be Logged and Shown With Answers

=== Show analysis to students ===

Yes/No. The summary results can be shown to respondents, or shown only to teachers.

=== Send E-Mail-Notifications ===

Yes/No. Notifications will be sent to the Moodle site administrators upon the submission.

=== Multiple submit ===

Yes/No, for anonymous polls allow unlimited answers for every user, for polls where the user name is logged this allow users to resubmit their answers.

=== Page after submit ===

This allows you to present users with a message after completion.

=== Group mode ===

The group mode can be one of three levels:

* No groups - There are no sub groups, everyone is part of one big community
* Separate groups - Each group can only see their own group, others are invisible
* Visible groups - Each group works in their own group, but can also see other groups

The group mode can be defined at two levels:

* Course level - The group mode defined at the course level is the default mode for all activities defined within that course
* Activity level - Each activity that supports groups can also define its own grouping mode. If the course is set to [[Force group mode|"force group mode"]] then the setting for each activity is ignored.

=== Visible to students ====

You can hide the activity from students by selecting "Hide" here. It is useful if you wouldn't like to make the activity available immediately.

Feedback settings

2007-03-06T11:52:05Z

Bawjaws:

=== Name ===

=== Description ===

Please read each comment and choose the appropriate option

=== Open and Close Feedback ===

This allows you to set a time period during which the Feedback will be available to responses.

=== Record User Names ===

Choose from the following options:
* Anonymous
* Users' Names Will Be Logged and Shown With Answers

=== Show analysis to students ===

Yes/No. The summary results can be shown to respondents, or shown only to teachers.

=== Send E-Mail-Notifications ===

Yes/No. Notifications will be sent to the Moodle site administrators upon the submission.

=== Multiple submit ===

Yes/No, for anonymous polls allow unlimited answers for every user, for polls where the user name is logged this allow users to resubmit their answers.

=== Page after submit ===

This allows you to present users with a message after completion.

=== Group mode ===

The group mode can be one of three levels:

* No groups - There are no sub groups, everyone is part of one big community
* Separate groups - Each group can only see their own group, others are invisible
* Visible groups - Each group works in their own group, but can also see other groups

The group mode can be defined at two levels:

* Course level - The group mode defined at the course level is the default mode for all activities defined within that course
* Activity level - Each activity that supports groups can also define its own grouping mode. If the course is set to [[Force group mode|"force group mode"]] then the setting for each activity is ignored.

=== Visible to students ====

You can hide the activity from students by selecting "Hide" here. It is useful if you wouldn't like to make the activity available immediately.

Feedback settings

2007-03-06T11:48:52Z

Bawjaws:

=== Name ===

=== Description ===

Please read each comment and choose the appropriate option

=== Open and Close Feedback ===

This allows you to set a time period during which the Feedback will be available to responses.

=== Record User Names ===

Choose from the following options:
* Anonymous
* Users' Names Will Be Logged and Shown With Answers

=== Show analysis to students ===

Yes/No,

=== Send E-Mail-Notifications ===

Yes/No. Notifications will be sent to the Moodle site administrators upon the submission.

=== Multiple submit ===

Yes/No, for anonymous polls allow unlimited answers for every user, for polls where the user name is logged this allow users to resubmit their answers.

=== Page after submit ===

This allows you to present users with a message after completion.

=== Group mode ===

The group mode can be one of three levels:

* No groups - There are no sub groups, everyone is part of one big community
* Separate groups - Each group can only see their own group, others are invisible
* Visible groups - Each group works in their own group, but can also see other groups

The group mode can be defined at two levels:

* Course level - The group mode defined at the course level is the default mode for all activities defined within that course
* Activity level - Each activity that supports groups can also define its own grouping mode. If the course is set to [[Force group mode|"force group mode"]] then the setting for each activity is ignored.

=== Visible to students ====

You can hide the activity from students by selecting "Hide" here. It is useful if you wouldn't like to make the activity available immediately.

Choice settings

2007-03-06T11:48:17Z

Bawjaws: /* Group mode */ tidying up

{{Choices}}

==Select choice==

Log in as the course teacher and turn on editing. Then select ''Choice'' from the drop down ''Add an activity'' menu.

[[image:Choice_1.gif|frame|left|choose ''choice'' from the menu]]
<br style="clear:both;">

==Choice name==

A short name of the choice (e.g. "Favourite colour"). This will be displayed on the course's homepage.
[[image:Choice_2.gif|frame|left|this will become a link on the course page]]
<br style="clear:both;">

==Choice text==

Type the description of the choice activity here. It should contain the question that you want your students to answer. An example of the choice text could be "What is your favourite colour?"

[[image:Choice_3.gif|frame|left|what do you want the students to tell you?]]
<br style="clear:both;">

==Choice 1 ~ Choice 10==

Here is where you specify the options that participants have to choose from. In our example, the numbered options could be e.g. "blue", "green", "red", "yellow", etc.

You can fill in any number of these: if you leave some of the options blank, they will not be displayed.

[[image:Choice_4.gif|frame|none|Choice input text boxes]]

{{Moodle 1.8}}
Moodle 1.8 includes a "Add 3 fields to form" button for adding another 3 choices and another 3 and another 3...

==Limit the number of responses allowed==

This option allows you to limit the number of participants who can select each particular option.

Once Limits have been enabled, each option can be assigned a limit. When the limit is reached then no-one else can select that option. A limit of zero (0) means that no-one can select that option.

If Limits are disabled then any number of participants can select any of the options.

==Restrict answering to this time period==

This setting allows you to define a time window within which participants are allowed to make a choice.

To set an open-ended close date just set the time very far in the future.

If you don't need this at all then uncheck the box.

[[image:Choice_5.gif|frame|left|this is optional, of course]]
<br style="clear:both;">

==Display Mode==

This setting allows you to choose how the choices will be displayed to the participants: horizontally, or vertically.

'''Hint''': In most cases, if there are only a few choices with little text, they may be positioned horizontally. However, if there are more than 5-6 choices or if the text of the choices is longer than 2-3 words, it should be better to display them vertically. (red arrow, below)

[[image:Choice_6.gif|frame|left|just a few more parameters]]
<br style="clear:both;">

==Publish results==

This setting determines whether (and when) the students will be able to view the results of the choice activity. They may:

* never see the results of the choice
* see the results only after they have given the answer themselves
* see the results only after the closing date of the choice
* always see the results

'''(teal arrow, above)'''

==Privacy of results==

If the choice results are shown to students, this setting determines whether the results will be anonymous.

'''(orange arrow, above)'''

==Allow choice to be updated==

If this is set to "Yes", students can change their mind after they have voted. If it's set to "No", students cannot change their choice.
'''
(lime green arrow, above)'''

==Show column for unanswered==

If set to "Yes", this will display a column showing how many participants have not answered the choice activity yet. If set to "No", the results will only include the participants who have already voted.

'''(purple arrow, above)'''

==Group mode==

The group mode can be one of three levels:

* No groups - There are no sub groups, everyone is part of one big community
* Separate groups - Each group can only see their own group, others are invisible
* Visible groups - Each group works in their own group, but can also see other groups

The group mode can be defined at two levels:

* Course level - The group mode defined at the course level is the default mode for all activities defined within that course
* Activity level - Each activity that supports groups can also define its own grouping mode. If the course is set to [[Force group mode|"force group mode"]] then the setting for each activity is ignored.

'''(pink arrow, above)'''

==Visible to students==

You can hide the activity from students by selecting "Hide" here. It is useful if you wouldn't like to make the activity available immediately.

'''(black arrow, above)'''

==See also==
* [[course/groups|Groups]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=59837 More than 10 choices??] forum discussion

[[Category:Teacher]]
[[Category: Choice]]

[[fr:Ajouter/modifier un sondage]]

Mòdul Realimentació

2007-03-06T11:35:56Z

Bawjaws:

Plantilla:Feedback

2007-03-06T11:34:40Z

Bawjaws:

<div class="sideblock right" style="width: 12em;">
<div class="header">[[Feedback module]]</div>
<div class="content">
* [[Setting up a Feedback]]
* [[Adding Feedback questions|Adding questions]]
* [[Viewing Feedback responses|Viewing responses]]
</div>
</div>

Questionnaire module

2007-03-06T11:33:48Z

Bawjaws:

{{Questionnaire}}

The '''Questionnaire module''' allows users to complete online feedback style forms using a variety of user input methods. It allows you to create your own questions, unlike the [[Survey module]] which has presets to choose from, and it allows for more advanced questionnaires than the simpler and easier [[Feedback module]].

[[Category:Teacher]]
[[Category:Modules (non-standard)]]

Plantilla:Questionnaire

2007-03-06T11:31:00Z

Bawjaws:

<div class="sideblock right" style="width: 12em;">
<div class="header">[[Questionnaire module]]</div>
<div class="content">
* [[Adding/editing a questionnaire]]
* [[Setting up a questionnaire]]
* [[Adding Questionnaire questions|Adding questions]]
* [[Viewing Questionnaire responses|Viewing responses]]
</div>
</div>

Adding questions

2007-03-06T11:29:48Z

Bawjaws: Adding questions moved to Adding Questionnaire questions: clarity with multiple modules that have 'questions' and 'responses'

#redirect [[Adding Questionnaire questions]]

Adding Questionnaire questions

2007-03-06T11:29:48Z

Bawjaws: Adding questions moved to Adding Questionnaire questions

{{Questionnaire}}
This page is about the questions in the questionnaire feature in Moodle.

Questions are added by defining fields.

==Add/edit fields==

To add a new field click the '''New Field''' button. To edit a field click the numbered button corresponding to that field e.g. '''2''' for field 2.

==Field types==

For each field type you should use a unique Field Name that allows you to identify it. You can then select different field types from the drop-down menu. You can choose whether each field is required or optional from the Required? drop-down menu. After each field is complete either add a new field or save.

;Yes/No
:A simple YES/NO question. The Length and Precision parameters are not used so you can leave them as zero. Type your question in the text area. You do not need to supply possible answers for this field.

;Text
:Allows limited character text entry via a single line text area. Use length to define the visible width of the text box and Precision to determine the maximum number of characters allowed. If Precision is greater than Length then the text will extend within the box. Type your question or information in the Text area. You do not need to supply possible answers for this field.

;Essay
:Allows essay style responses via a multi line text area, with no character limit. Length and Precision define the size of the available text area, although this will scroll. Length determines the number of columns (character width) and Precision the number of rows (lines). This can involve trial and error, although Length: 90, Precision: 7, should be a good general starting estimate. Type your question or information in the Text area. You do not need to supply possible answers for this field.

;Radio Buttons
:Radio buttons provide the user with a choice of options from which they can pick only one. This field ignores the Length and Precision parameters so you can leave them. Type your question or information in the Text area and the list of available options in the boxes underneath. You can add more possibilities using the ''Add another answer line'' button and add an other text field using '''!other''' as a possible answer.

;Check Boxes
:Check boxes allow the user to select multiple answers from a list of options. Length determines the minimum number of answers require and Precision the maximum number of selections allowed (these may not function fully as implemented). Type your question or information in the Text area and the list of available options in the boxes underneath. You can add more possibilities using the ''Add another answer line'' button and add an other text field using '''!other''' as a possible answer.

;Dropdown Box
:Users select one option from a drop-down list. This field ignores the Length and Precision parameters so you can leave them. Type your question or information in the Text area and the list of available options in the boxes underneath. You can add more possibilities using the ''Add another answer line'' button and add an other text field using '''!other''' as a possible answer.

;Rate (scale 1..5)
:Allows users to rate statements on a scale from 1 to N, where N is determined by the Length value. If you wish to include a N/A option set Precision to 1 (any non-zero number may work). Type your question or information in the Text area and the list of available statements to be rated in the boxes underneath. You can add more statements using the ''Add another answer line'' button.

;Date
:Requires users to submit a date. This field ignores the Length and Precision parameters so you can leave them. Type your question or information in the Text area. You do not need to supply possible answers for this field.

;Numeric
:Require users to submit a numeric response. This field ignores the Length and Precision parameters so you can leave them. Type your question or information in the Text area. You do not need to supply possible answers for this field.

;Section Text
:This is a text field that allows you to present information in between different fields. It does not offer user feedback.

==Arrangement==

The buttons underneath the field setup options, allow you to preview the current status of your questionnaire and reorder the question fields.

==See also==
[[Question_types]] and the "[[Question bank]]" index on that page for questions used in a lesson or quiz.

[[Category:Teacher]]

Viewing responses

2007-03-06T11:29:23Z

Bawjaws: Viewing responses moved to Viewing Questionnaire responses: clarity with multiple modules that have 'questions' and 'responses'

#redirect [[Viewing Questionnaire responses]]

Viewing Questionnaire responses

2007-03-06T11:29:23Z

Bawjaws: Viewing responses moved to Viewing Questionnaire responses

{{Questionnaire}}

If you click on a questionnaire on a course to which you have editing access, you recieve the option to '''View 'n' responses''' in the top-right corner, where 'n' refers to the number of completed surveys. Clicking this will take you to the ''Survey Reports'' page which gives you a graphical (bar chart) and numerical breakdown of responses using both total and percentage results.

There is no mechanism to automatically make the results available to [[Student|students]] who have taken the questionnaire. You could however save the displayed results as an HTML file and upload that as a [[resource]].

At the bottom of this page you have the option to switch your view between individual responses and all responses and/or download a [[CSV]] version of the responses. In the CSV file fields are identified by the name you entered when creating them.

[[Category:Teacher]]

Mòdul Realimentació

2007-03-06T11:07:43Z

Bawjaws:

The '''Feedback module''' allows you to create and conduct surveys to collect feedback from [[Student]]s. It is smaller in scope and therefore easier to use than the [[Questionnaire module]], and unlike the [[Survey module|Survey]] tool allows you to write your own questions, rather than choose from a list of pre-written survey instruments.

== See also ==

* [http://moodle.org/mod/data/view.php?d=13&rid=95 Discuss and/or download this module]

[[Category:Teacher]]
[[Category:Modules (non-standard)]]

Recording audio for Moodle

2007-03-01T16:56:04Z

Bawjaws:

If you are '''recording audio for Moodle''' the following guide will helpful. It suggests a route to record and upload simple audio into Moodle, where editing of the audio file is neither required or desired.

=== Introduction ===
The [[Audio in Moodle]] page explains that although you can use almost any audio file with Moodle, one particular type of MP3 file allows for maximum compatibility while also allowing for more flexible usage within Moodle.

Similarly though there are several methods available for creating these files there is one method that allows staff and students to create such files with ease. The right kind of digital voice (or memo-) recorder, familiar to many, can allow recordings in a variety of situations without the need for extensive technical knowledge or training and with minimal outlay that could potentially pay for itself in saved staff time after one use.

=== Requirements ===
The ideal requirements for such a device are:

* a USB connection
* no need to install any software
* records in an appropriate mp3 format

Combined, these requirements allow someone with minimal technical skills to record audio and have it uploaded and playing via Moodle within minutes.

=== Potential Devices ===

However, this short list of requirements reduces the field of potential purchases from hundreds to a handful. The following appear, based on information from their manuals, to fit the bill. Some have provisos or other useful info listed below, click to read it.

* Phillips Digital Voice Tracer, 7790 or 7890
* Sanyo ICR-S250RM

The following have been tested and found to work

* [[#Sanyo Digital MP3 recorder ICR-B170NX|Sanyo Digital MP3 recorder ICR-B170NX]]
* [[#Sanyo Digital MP3 recorder ICR-A190 / ICR-B190|Sanyo Digital MP3 recorder ICR-A190 / ICR-B190]]

==== Sanyo Digital MP3 recorder ICR-B170NX ====

Has 4 quality modes SHQ, HQ, SP, LP. Only the HQ mode (64kbps, 22.1kHz) is suitable for these purposes and it can record up to 2 hours 20 minutes. Takes replaceable AAA batteries.

==== Sanyo Digital MP3 recorder ICR-A190 / ICR-B190 ====
Has 4 quality modes XHQ, HQ, SP, LP. the longer /lower quality recording times of the LP and SP modes are not suitable. Has up to 4 hours 20 minutes recording time in HQ mode (64kbps, 22.1kHz) and 2 hours, 10 minutes in XHQ mode (128kbps, 44.1kHz). Takes replaceable AAA batteries.

[[Category:Teacher]]
[[Category:Administrator]]
[[category:Audio]]

Categoria:Audio

2007-03-01T10:11:09Z

Bawjaws:

Moodle provides a variety of tools and methods for integrating audio.

Speech tools

2007-03-01T10:10:41Z

Bawjaws: + categories

Moodle has no built-in tools for speech messaging or audioconferencing. However, there are some interesting projects which are working towards enabling the use of voice tools within Moodle, at various stages of maturity:

==Free tools==

* '''[http://www.covell.org COVCELL]''', an EU-funded project to provide various enhancements for online language learning, including audio conferencing. See also [http://moodle.org/mod/forum/view.php?id=5368 COVCELL discussion forum on moodle.org] The audio conferencing will use a RED5 Flash-based server.
* Integration of Moodle with '''[http://gong.ust.hk/ Gong]''' (requires a Java server)
* Integration of Moodle with '''[http://www.dimdim.com/ dimdim]''' open-source webconferencing system. (Not sure what the server requirements are.)
* '''[http://moodle.org/mod/forum/discuss.php?d=50265 MoodleSpeex]''' Java applets for voice messaging (note: does not require any modifications/additions to the server setup)

==Commercial tools==

* The '''Horizon Wimba''' company provides a subsription-based service providing [http://www.horizonwimba.com/products/voicetools/ voice tools] for use in VLEs. Moodle integration of these tools is forthcoming.

[[Category:Administrator]]
[[Category:Teacher]]
[[Category:Audio]]

MP3 player

2007-03-01T10:09:38Z

Bawjaws: + categorie: Audio