• last updated 19 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
guarantee uniqueness of IDs when multiple aggregated forms are used in one page (e.g. exam protocol)

Constrain the language we return for the connection to the ones we support: could happen on system that have supposted a language in the past and still have users set it as their preferred language

Additional CSP exceptions for Xinha

improve class diagram drawing logic

- Draw always the superclass of the object of

interest, which might in the case of multiple

inheritance not in the "things" variable.

- don't draw lines twice in cases of multiple inheritance

include DB interface classes in API-doc

pass "hide methods" to svg generation

switch from xo::db::sql to acs::dc interface

Make the initial population of the request-monitor counters more robust

simplify logic

Fix variable name

switch from xo::db::sql to acs::dc interface

    • -3
    • +2
    /openacs-4/packages/chat/tcl/chat-procs.tcl
    • -2
    • +3
    /openacs-4/packages/xooauth/xooauth.info
    • -1
    • +1
    /openacs-4/packages/xowf/tcl/xowf-procs.tcl
Basic test of the proctoring upload endpoint

Switch to a select widget to keep a more predictable vertical size in case of many time presets

Prefer "::acs::dc call ..." over "::xo::db::sql::..."

Use the common new acs interface rather than the xotcl-core variant.

Goal should be on the medium time range to replace all of the

"::xo::db::sql::*" interface.

    • -123
    • +136
    /openacs-4/packages/xotcl-core/tcl/05-db-procs.tcl
Align names used in utility db functions in Oracle and PostgreSQL

Over the years, the names used in the function for PostgreSQL and

Oracle drifted away, which is a problem when using call-by-name

convention for stored procedures. Furthermore, recent Oracle versions

do not allow attributes named "table" (for table_name). So the longer

version is now used uniformily. Fortunately, nsf allow abbreviation

for named parameters (like Tcl does), such one can use both

"-table_name" and "-table".

Bumped version number to 5.10.1d7.

file upgrade-5.10.1d6-5.10.1d7.sql was initially added on branch oacs-5-10.

Notify new revisions on a proctoring artifact on the object's websocket, in a way that the users list, already designed to refresh in case on messages, will display new information when the revision is proceeding

Fix typos

Generate the fullscreen preview element in javascript and make it a child of the body, so that it can expand to the full page also when the include itself would be rendered in a smaller container

Implement a pre-selection filter for timeframes, which can be extended using downstream specific logics

make sure, the dependencies are aligned (drop of xo::site_node)

    • -2
    • +2
    /openacs-4/packages/acs-tcl/acs-tcl.info
remove call of xo::site_node

make sure not to swallow error conditions, as the previous changes did.

This change will report an error in the systemlog when called on invalid objects/data

Various changes on the proctoring artifacts users list:

- display some statistics on the collected artifacts for each user: count, number of reviewed, number of flagged, plus a colored progress bar indicating the review status, orange when in progress, red when completed with flags and green when everything is ok

- switched to a template::list to avoid too much handcrafting

- removed the red delete button from the top of the page, redundant, since we have the bulk actions on the list

- refined the behavior of the bulk-action delete button: it will be disabled when nothing is selected

- now we always trigger a reload when new artifacts are received for this object, but we cap it to 60 seconds

Store the string "false", not the boolean false

Improve spelling

Fine-tuning the new db function interface

#

# Check, wether we have to regenerate the database function interface.

#

# - During initial setup, there are no db-functions, so nothing has to

# be done.

#

# - During regular startup of the server, the generation of the stub

# interface happens in the *init procs (hopefully this is always

# sufficient, but seems so)

#

# - During reloads of acs-db-*-procs, the base classes are interface

# objects are recreated and cleaned up from all prior definitons,

# which means that in this situations, we have to regeneate the

# interface.

#

# - One might call manually the regeneration, when database functions

# have been altered and no restart is desired.

#

Use a full join so that in case of (normally minimal) unalignment between camera and desktop, we still display every artifact

avoid dead operations

Keep making sure permission exists