• last updated 1 hour ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
whitespace changes

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

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

  1. … 3 more files in changeset.
whitespace changes

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. … 13 more files in changeset.
improve comments

  1. … 3 more files in changeset.
reduce usage of anonymous arrays

accept as page_ref for an object as well an item_id

This change simplify resolving items. raw ids seem

fine, since the listing are not persisted or moved between

OpenACS instances.

fix broken variable reference (pg changed?)

Use full URL paths for bulk actions.

This change allows one to mark items from multiple child-resources

displayed on one page and add these to the clipboard. Use the same

logic for bluk-delete and bulk adding to the clipboard.

replace array by dict

www-clipboard-add: allow object to be fully qualified

old conventions continue to work

avoid warning for "hidden" table widget columns, used e.g. for sorting

Make :folder_id available as a package instance variable immediately, in a way that if the folder instantiation needs e.g. to fetch a parameter, the folder_id will be there to determine the right parameter page, which otherwise would be looked up e.g. in the site-wide pages and cached with wrong values for the cache lifetime

Make ::xowiki::Package default_locale react to changes in the connection locale by caching only when the parameter use_connection_locale is not set, use ::xowiki::Package default_locale result instead of always the connection locale to determine nls_language for new Pages and FormPages, so that default language for a particular xowiki instance is decided by use_connection_locale parameter

reduce number of locks when NaviServer is used

improve debugging messages

  1. … 1 more file in changeset.
improve wording

move "unify_forms" to xotcl-core, rename it to "form_unify", added "form_usages"

  1. … 1 more file in changeset.
improve spelling

  1. … 1 more file in changeset.
provide better warning message

add modification_date as default hidden field for sorting of form-usages

Don't assume save_new will return an item_id, object should come out of it "already baked"

improve spelling

  1. … 6 more files in changeset.
improve spelling

  1. … 3 more files in changeset.
whitespace changes

  1. … 1 more file in changeset.
improve wording

handle toplevel and other forms as well

variable constraint "integer" not supported in xotcl

added support call for unifying forms

- 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

    • -0
    • +255
    ./personal-notification-procs.tcl
  1. … 3 more files in changeset.