|
|
83.
|
|
|
|theme| If you build your own theme for Mahara, you can now set it up to inherit from any existing core theme rather than having to base it always on the "Raw" theme. Any of the built-in themes can be parents allowing you to only make the necessary changes to your theme for a different look.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/new.rst:153
|
|
|
84.
|
|
|
Update a language pack easily
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/new.rst:156
|
|
|
85.
|
|
|
|terminal| You can use :ref:`CLI <cli>` (Command-line interface) to update language packs more easily during an update or an upgrade. Existing languages are automatically backed up and new ones downloaded.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/new.rst:158
|
|
|
86.
|
|
|
And last but not least something over which developers will rejoice:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/new.rst:160
|
|
|
87.
|
|
|
Removal of MochiKit JavaScript
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/new.rst:163
|
|
|
88.
|
|
|
|eraser| We class it as a new feature because removing MochiKit from Mahara required implementing jQuery for everything as a replacement. MochiKit JavaScript is an old JavaScript library that is not actively developed and thus doesn't receive new features.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/new.rst:165
|
|
|
89.
|
|
|
In recent years, we already implemented new JavaScript requirements via jQuery. So it was time to remove MochiKit altogether and prevent potential conflicts with other JavaScript code.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/new.rst:167
|
