• last updated 18 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
allow to specify witdget type alternatively via "_type" in the form field dict

This change makes it possible to specify the whole widget spec part in a single dict

  1. … 1 more file in changeset.
added range checking for page_size and page_number for weblog-portlet

modernized weblog-portlet code

moved weblog-portlet to the right place

bumped version number to 5.10.1d1

  1. … 5 more files in changeset.
fix release dates in .info files

  1. … 82 more files in changeset.
release work

  1. … 204 more files in changeset.
bump version numbers of 5.9|5.10 packages to 5.10.0b1

adjust dependencies

  1. … 87 more files in changeset.
New CSS abstraction: xowiki::CSS

Before this change, the application developer was responsible to

initialize the CSS-speficic settings (such as setting default values

for parameter classes). The new object xowiki::CSS is initialized

automatically, when an xowiki class (or one of its subclasses) is

initialized. Furthermore, it provides a per-thread caching to reduce

double work. Furthermore, the xowiki::CSS provides a mapping between

abstract and concrete CSS class names, such that switching between

different CSS toolkits becomes easier (e.g. upgrade from bootstrap 3

to newer versions).

xowiki::CSS initialize ;# make sure, everything is in line with PreferredCSSToolkit

xowiki::CSS clear ;# reset the mapping

xowiki::CSS toolkit ;# return the toolkit name

xowiki::CSS class /classname/ ;# perform CSS class name mapping

The methods "setCSSDefaults" and "preferredCSSToolkit" as deprecated.

The version number was bumped to 5.10.0d81

  1. … 7 more files in changeset.
prefer usage of "xo::write_tmp_file" over "xo::write_file" for writing tmp files

  1. … 4 more files in changeset.
parameterize xowiki::test::edit_form_page with -next_page_must_contain

This changes supports more flexible checking of expected content on page after editing.

Default is backwards compatible

  1. … 1 more file in changeset.
- Added new method extra_html_fields to provide an easy means to add

extra HTML fields to the form autogenerated for form pages

- bump version number to 5.10.0d79

  1. … 1 more file in changeset.
added support for avoiding quoting of labels (e.g. in buttons)

  1. … 1 more file in changeset.
added utility function xowiki::filter_option_list to select a subset from an option list

added form.form to ease creation of forms as form pages (important for using forms from global instance as form pages in workflows)

  1. … 3 more files in changeset.
Update italian localization

  1. … 1 more file in changeset.
added function "xowiki::randomized_index"

extended regression test

bumped version to 5.10.0d75

  1. … 2 more files in changeset.
added storage_type to xowiki_form_instance_item_view

  1. … 2 more files in changeset.
form-field "range": added optional output text box for displaying the actual value

  1. … 1 more file in changeset.
added new form-field type: comp_correct_when

added conjunctive answer-check

adde answer-check "contains-not"

The new form-field type offers a graphical user interface for input of

correct when clauses. When comp_correct_when is used with the repeat

flag it produces conjunctive (AND connected) clauses. The answer-check

"contains-not" is more or less the same a "contains", but highlights

such words in red.

bump version number to 5.10.0d71

  1. … 3 more files in changeset.
cache failed name lookups in a per-request cache (flushing maybe overly conservative)

  1. … 3 more files in changeset.
bump version number to force update of message catalog

Improved handling of link and child resources of forms

- test-item-procs: use resolve context to resolve e.g. images in the context of the original form

(many thanks to Thomas Renner for the suggestion)

- added extra argument "-context_obj" to substitute_markup to ease client code

- inclass-exam-answer.wf: reduced the db interactions by using form_info for form generation

  1. … 4 more files in changeset.
new form-field class: boolean_checkbox

behaves like boolean, but provdes just a single checkbox instead of yes/no radio in "boolean"

the output is full compatible with "boolean".

The boolean_checkbox is used in test-item procs for a more slim correct/incorrect specification

  1. … 4 more files in changeset.
move xowiki::test::get_url_from_location to automated testing

handle updaed query-handling in ns_parseurl

remoe dependency from file-storage tests to xowiki

  1. … 5 more files in changeset.
added value checker from page filters to slots: "nohtml" and "html"

Made flowplayer more secure by reject markup in argument

  1. … 3 more files in changeset.
get rid of ancient parameters BootstrapCSS BootstrapJS, if these still exist

  1. … 1 more file in changeset.
fix message key

  1. … 5 more files in changeset.
switch to simple new group::update call with dict as argument

This change fixes as well a bug in install::xml::action::set-join-policy

since group::get returns a member "text" which is not accepted by

group::update.

  1. … 5 more files in changeset.
Added points in addition to minutes to test items and inclass-exam workflows

  1. … 6 more files in changeset.
make "instantiate_forms" a method of packages

this reads better than the previous variant based on the Weblog class.

  1. … 14 more files in changeset.
MenuBar reform

- MenuBars are now easier programmatically extensible (easier to maintain)

- refactored code, reduced scatted definitions (all configurations

at the same place)

- unified templating:

use body property @body.folderHTML@ instead of @folderhtml@

From the former API calls only "update_items" has changed,

all existing configurations (i.e. via folders or package parameter)

should continue to work.

== Changes:

One can now extend menubars via menu entry definition

{config -use YOURCONFIG -class YOURCLASS}

in two directions:

a) subclassing

define your own menubar class YOURCLASS, which should

be a subclass of ::xowiki::MenuBar

b) provide your own configuration method to provide

a more tailored configuration. This is performed

by defining a method "config=YOURCONFIG" for ::xowiki::MenuBar

The latter method is used for test-items, which can define a

test item folder by using

-- extra_menu_entries ---

{config -use test-items}

instead of

-- extra_menu_entries ---

{entry -name New.Item.TextInteraction -form en:edit-interaction.wf -query p.item_type=Text}

{entry -name New.Item.ShortTextInteraction -form en:edit-interaction.wf -query p.item_type=ShortText}

{entry -name New.Item.SCInteraction -form en:edit-interaction.wf -query p.item_type=SC}

{entry -name New.Item.MCInteraction -form en:edit-interaction.wf -query p.item_type=MC}

{entry -name New.Item.ReorderInteraction -form en:edit-interaction.wf -query p.item_type=Reorder}

{entry -name New.Item.UploadInteraction -form en:edit-interaction.wf -query p.item_type=Upload}

{entry -name New.App.OnlineExam -form en:online-exam.wf}

{entry -name New.App.InclassQuiz -form en:inclass-quiz.wf}

{entry -name New.App.InclassExam -form en:inclass-exam.wf}

See below for the definition of the "test-items" configuration method,

which is based on the default definitions. In general, the definition

in this method can be performed via menu-entries (same syntax as in

other menu entries) or via the MenuBar API (e.g. calling

":add_menu_item ...").

All configurations follow the following definition order

where later entries can refine earlier entries:

- package level: package parameter ExtraMenuEntries

- configuration method: use standard or tailored confguration methods

- per-folder definition: content of the extra_menu_entries

Note that the menu entry definition language supports as well

adding/clearing menus, etc., so almost everything can be refined.

I've noticed that the tlf* code has several scattered menu

definitions, which are as well done in every case differently.

By these definition one can define e.g. a learning-app folder (where

"New" can be used to define new app folders), and the app folders can

provide their own "New" entries, e.g. for clickers and

others. E.g. For "clickers" there is already on non-oo definition to

achieve similar things (which should be altered to the new method),

but on other places, there are some hard-coded definitions for root

folders, etc. The menubars of the learning-apps should be made this

way more consistent with the rest (e.g. using "New", supporting "table

of contents" for clipboard interactions, etc.)

namespace eval ::xowiki {

::xowiki::MenuBar instproc config=test-items {

{-bind_vars {}}

-current_page:required

-package_id:required

-folder_link:required

-return_url

} {

:config=default \

-bind_vars $bind_vars \

-current_page $current_page \

-package_id $package_id \

-folder_link $folder_link \

-return_url $return_url

return {

{clear_menu -menu New}

{entry -name New.Item.TextInteraction -form en:edit-interaction.wf -query p.item_type=Text}

{entry -name New.Item.ShortTextInteraction -form en:edit-interaction.wf -query p.item_type=ShortText}

{entry -name New.Item.SCInteraction -form en:edit-interaction.wf -query p.item_type=SC}

{entry -name New.Item.MCInteraction -form en:edit-interaction.wf -query p.item_type=MC}

{entry -name New.Item.ReorderInteraction -form en:edit-interaction.wf -query p.item_type=Reorder}

{entry -name New.Item.UploadInteraction -form en:edit-interaction.wf -query p.item_type=Upload}

{entry -name New.App.OnlineExam -form en:online-exam.wf}

{entry -name New.App.InclassQuiz -form en:inclass-quiz.wf}

{entry -name New.App.InclassExam -form en:inclass-exam.wf}

}

}

}

  1. … 16 more files in changeset.
- added support for personal notifications (as used by inclass exam):

The notification system has the following features:

. lecturer can send individual messages to participants of an ongoing exam

. message is sent by clicking on a participants name in the participant list

. student can receive one or many notification messages

. notification messages have to be confirmed, otherwise they are displayed always

. non-confirmed notification messages are sticky, i.e. the are displayed also

when a user changes to some other question.

. three different urgency levels for messages

. built around an includelet

- bumped version number to 5.10.0d59

  1. … 3 more files in changeset.
added the flag "-language_specific" to child-resources to support differnt content per folder for user with different language settings

  1. … 1 more file in changeset.