<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="ru">
	<id>http://wiki.mipt.ru/index.php?action=history&amp;feed=atom&amp;title=Development%3ALinked_activities</id>
	<title>Development:Linked activities - История изменений</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.mipt.ru/index.php?action=history&amp;feed=atom&amp;title=Development%3ALinked_activities"/>
	<link rel="alternate" type="text/html" href="http://wiki.mipt.ru/index.php?title=Development:Linked_activities&amp;action=history"/>
	<updated>2026-05-07T18:42:57Z</updated>
	<subtitle>История изменений этой страницы в вики</subtitle>
	<generator>MediaWiki 1.42.1</generator>
	<entry>
		<id>http://wiki.mipt.ru/index.php?title=Development:Linked_activities&amp;diff=11302&amp;oldid=prev</id>
		<title>Олег Давидович: 1 версия импортирована</title>
		<link rel="alternate" type="text/html" href="http://wiki.mipt.ru/index.php?title=Development:Linked_activities&amp;diff=11302&amp;oldid=prev"/>
		<updated>2024-10-21T08:51:24Z</updated>

		<summary type="html">&lt;p&gt;1 версия импортирована&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;ru&quot;&gt;
				&lt;td colspan=&quot;1&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Предыдущая версия&lt;/td&gt;
				&lt;td colspan=&quot;1&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Версия от 08:51, 21 октября 2024&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-notice&quot; lang=&quot;ru&quot;&gt;&lt;div class=&quot;mw-diff-empty&quot;&gt;(нет различий)&lt;/div&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;</summary>
		<author><name>Олег Давидович</name></author>
	</entry>
	<entry>
		<id>http://wiki.mipt.ru/index.php?title=Development:Linked_activities&amp;diff=11301&amp;oldid=prev</id>
		<title>1&gt;Oasychev: /* Interface */</title>
		<link rel="alternate" type="text/html" href="http://wiki.mipt.ru/index.php?title=Development:Linked_activities&amp;diff=11301&amp;oldid=prev"/>
		<updated>2011-05-04T20:31:54Z</updated>

		<summary type="html">&lt;p&gt;&lt;span dir=&quot;auto&quot;&gt;&lt;span class=&quot;autocomment&quot;&gt;Interface&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Новая страница&lt;/b&gt;&lt;/p&gt;&lt;div&gt;In large courses we often find a sets of similar activities (quizzes, assignments and so on), which share many settings (i.e. module settings) - but not all, of course. Maintaining of such sets is quite a pain: imagine youself adding a new IP range on 6-10 quizzes. So we need an usable and robust way to handle such sets - linked activities.&lt;br /&gt;
&lt;br /&gt;
This page is to discuss and find a better way to do so.&lt;br /&gt;
&lt;br /&gt;
Let&amp;#039;s call the &amp;#039;&amp;#039;&amp;#039;setting&amp;#039;&amp;#039;&amp;#039; some parameter of course module instance. Setting isn&amp;#039;t necessary one control on the form (it may be a group of related controls, check boxes for example). Setting may be a field in db, or not - needs thinking.&lt;br /&gt;
&lt;br /&gt;
A &amp;#039;&amp;#039;&amp;#039;set&amp;#039;&amp;#039;&amp;#039; is a group of course module instances, that share common settings.&lt;br /&gt;
&lt;br /&gt;
== Issues ==&lt;br /&gt;
* linked activities may need to response on editing one of them (and deleting), so they need an events on these occasion. Anyone interested please vote for MDL-16203.&lt;br /&gt;
* modules now handle settings (from form to db and from db to form) in a bulk, there is no way to say the module &amp;quot;please save in db (or show on the form) this setting and not leave others be&amp;quot;. It&amp;#039;s possible to do this without module help, but if module can map individual settings to db/form(controls) it would help.&lt;br /&gt;
&lt;br /&gt;
== Interface ==&lt;br /&gt;
&lt;br /&gt;
=== Level 0: Save as another ===&lt;br /&gt;
Done in Moodle 2.1 as copy acitivity.&lt;br /&gt;
&lt;br /&gt;
=== Level 1: Bulk activities editing ===&lt;br /&gt;
This doesn&amp;#039;t require DB change, and hopefully can be done in 1.9 too.&lt;br /&gt;
Block bulk_module_edit is intented to be placed in a course page.&lt;br /&gt;
&lt;br /&gt;
==== Step 1: Select a module type to edit ====&lt;br /&gt;
[[File:Bulk_edit1.JPG]]&lt;br /&gt;
&lt;br /&gt;
==== Step 2: Select instances to edit ====&lt;br /&gt;
[[File:Bulk_edit2.JPG]]&lt;br /&gt;
&lt;br /&gt;
==== Step 3: Select fields to edit ====&lt;br /&gt;
[[File:Bulk_edit3.JPG]]&lt;br /&gt;
Sorry, quiz has quite a long list of form fields which doesn&amp;#039;t fit in screenshot.&lt;br /&gt;
&lt;br /&gt;
==== Step 4: Edit and save form ====&lt;br /&gt;
[[File:Bulk_edit4.JPG]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Level 2: Sets of activities ===&lt;br /&gt;
On this level system would be able to store sets of related instances and provide a one-click link to edit them. This&amp;#039;ll require new db tables, so it probably 2.0 only.&lt;br /&gt;
&lt;br /&gt;
There must be a block which displays a sets as a links to edit them, and new controls on index.php page to create (manage?) sets.&lt;br /&gt;
&lt;br /&gt;
If events on update instance would be fired, than it is possible to have sets which are automatically update some settings whenever one of the activities in set are updated.&lt;br /&gt;
&lt;br /&gt;
== Architecture ==&lt;/div&gt;</summary>
		<author><name>1&gt;Oasychev</name></author>
	</entry>
</feed>