Activity OpenACS/openacs-4/packages/xowiki/tcl

Tree
Accordion

Stats

Commits this week: 0

Total Committers:	11
Last Commit:	26 Apr
Commits this week:	0
Total Lines of Code (LoC):	29,976
Net change in LoC this week:	0

Commit Activity

last updated 5 hours ago

Constraints

Constraints: committers

Committer:

Log Comment:

Constraints: files

File Extension:

File Name:

Constraints: dates

Start Date:

End Date:

Tuesday 30 Jan

10:35 am

antoniop

Cleanup leftover library: latest javascript assumes XMLHttpRequest is supported

- -3
- +1
./chat-procs.tcl
- History
- Source
- Diff
./chat-procs.tcl

Friday 26 Jan

5:37 pm

antoniop

Chat reform

The goal of these changes is to reduce the "mode" specific javascript code in the chat implementation and reduce server-side guessing of browser capabilities.

- In the MessageRelay class from xotcl-core, we rework the javascript code sent to the connection when doing scripted streaming to make less assumptions about the functions defined in the parent scope

- In the chat code from xowiki, we move most of the logics to guess the mode into javascript, where we can test the actual capabilities of the browser without relying on the user agent

- The previously 4 javascript files dependant on the chat mode have been made into one

- -112
- +17
./chat-procs.tcl
- History
- Source
- Diff
./chat-procs.tcl
… 7 more files in changeset.

2:14 pm

antoniop

When the mode is "streaming", use Server Sent Events instead of a "plain" endless request

This has the advantage of a clearer, less hacky api, which, for instance, does not require manual parsing of the partial response.

- -10
- +9
./chat-procs.tcl
- History
- Source
- Diff
./chat-procs.tcl
… 4 more files in changeset.

11:30 am

antoniop

Cleanup leftover method: its logics were moved to the MessageRelay class

- -15
- +1
./chat-procs.tcl
- History
- Source
- Diff
./chat-procs.tcl

Thursday 25 Jan

12:44 pm

antoniop

Cleanup commented code

- -11
- +1
./xowiki-form-procs.tcl
- History
- Source
- Diff
./xowiki-form-procs.tcl

Tuesday 23 Jan

2:20 pm

antoniop

Revert to an approach that will not change the [self] object, which has unexpected consequences

- -2
- +9
./xowiki-www-procs.tcl
- History
- Source
- Diff
./xowiki-www-procs.tcl

Monday 22 Jan

3:52 pm

antoniop

Use a better idiom to revert changes on the object, that e.g. will handle the same arrays and variables

- -4
- +2
./xowiki-www-procs.tcl
- History
- Source
- Diff
./xowiki-www-procs.tcl

Tuesday 16 Jan

6:35 pm

antoniop

Ensure we are still connected before we try to render the error to the user

For instance, the error may have beeen triggered by unexpected lack of connection, e.g. when we try to return content after a redirect has already been issued.

- -4
- +12
./package-procs.tcl
- History
- Source
- Diff
./package-procs.tcl

Monday 15 Jan

12:42 pm

antoniop

Extend test: edit a different component of repeated compound 3 to also test that old and new values are stored as expected

- -0
- +6
./test/xowiki-test-procs.tcl
- History
- Source
- Diff
./test/xowiki-test-procs.tcl

Tuesday 09 Jan

5:17 pm

antoniop

Extend and fix xowiki.create_form_with_form_instance automated test with respect to checkbox behavior

- simple checkboxes (normal and repeated): as we do not specify a value for those, the default should be expected, not the last option

- checkboxes in repeated compound fields: upon triavial re-editing, the values should stay the same

This change exposes a bug in acs::test::xpath::get_form_values

- -8
- +56
./test/xowiki-test-procs.tcl
- History
- Source
- Diff
./test/xowiki-test-procs.tcl

Wednesday 20 Dec 2023

2:13 pm

antoniop

Port of downstream modification:

do not restrict the format the user can supply. Sanitize the filename later and complain only if this is made exclusively of invalid characters.

- -2
- +12
./xowiki-www-procs.tcl
- History
- Source
- Diff
./xowiki-www-procs.tcl

12:04 pm

antoniop

get_form_data reform:

when validation fails, revert all changes performed on the object while filling up the form fields.

Rationale: when validation fails, we do not persist the data. The same we should not let unvalidated data sneak into the object, as this may be e.g. displayed on the page or be otherwise used by the system.