• last updated 9 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
answer_manager get_wf_instances: pass "orderby" to xowiki.get_form_entries

provide simple CSS file for printing

Add plugin.jss, remove unneeded markup file

file plugin.js was initially added on branch oacs-5-10.

Render embedding editor more robust when multiple editors are present, fix readyOnly mode

improve spelling

add comment to clarify meaning of "current_position"

add support for multiple grading schemes

improve example menu in comment to include a separater after items

    • -4
    • +4
    /openacs-4/packages/xowf/lib/inclass-quiz.wf
    • -4
    • +4
    /openacs-4/packages/xowf/lib/online-exam.wf
include selected grading score in feedback

remove spurious colons

whitespace changes

use explicit "create" statments

    • -1
    • +1
    /openacs-4/packages/xowf/lib/inclass-quiz.wf
remove spurious colons

includelet form-usages: support additional button "slim_publish_status" for display similar to child-resource

improve spelling

fix for issue #3387: ad_return_complaint can reveal error call stacks to end users

remove useless semicolon

fix issue #3373

whitespace cleanup

strengthen page contracts

whitespace cleanup

provide nicer relative times

add item shuffling for test item procs and do some minor refactoring

    • -5
    • +19
    /openacs-4/packages/xowf/lib/online-exam-answer.wf
    • -2
    • +2
    /openacs-4/packages/xowiki/xowiki.info
    • -2
    • +4
    /openacs-4/packages/xowiki/tcl/package-procs.tcl
    • -3
    • +17
    /openacs-4/packages/xowiki/tcl/xowiki-procs.tcl
Whitespace changes + editor hints

Adding catalog files

added alias for package xowf-monaco-plugin

Initial import of xowf-monaco-plugin

  1. … 1050 more files in changeset.
Initial revision

    • -0
    • +111
    /openacs-4/packages/xowf-monaco-plugin/tcl/form-field-procs.tcl
    • -0
    • +140
    /openacs-4/packages/xowf-monaco-plugin/tcl/test-item-procs.tcl
  1. … 1050 more files in changeset.
Avoid looking for proc names in comments after a semicolon or an opening curly brace, so common words in comments are not included in the api-doc as calls to procs with the same name