Index: openacs-4/packages/acs-authentication/www/doc/xml/install.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/xml/install.xml,v
diff -u -r1.6.2.1 -r1.6.2.2
--- openacs-4/packages/acs-authentication/www/doc/xml/install.xml 10 Aug 2019 15:15:49 -0000 1.6.2.1
+++ openacs-4/packages/acs-authentication/www/doc/xml/install.xml 31 Jul 2024 09:59:29 -0000 1.6.2.2
@@ -168,7 +168,7 @@
If the PAM domain defines a password command, you can set Password Management to PAM. If not, the PAM module cannot change the user's password and you should leave this option Disabled.
- Leave Account Registration disabed.
+ Leave Account Registration disabled.Configure Batch Synchronization
Index: openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth-design.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth-design.xml,v
diff -u -r1.13.2.9 -r1.13.2.10
--- openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth-design.xml 10 Jul 2023 08:36:09 -0000 1.13.2.9
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth-design.xml 31 Jul 2024 09:59:29 -0000 1.13.2.10
@@ -1375,7 +1375,7 @@
EXT
AUTH #14: Create authentication driver for LDAP
-
+ Status
ON HOLD awaiting info from clients on whether we can use PAM
@@ -1407,7 +1407,7 @@
Internal Design
- We'd look at the extisting ns_ldap module, or we'd find
+ We'd look at the existing ns_ldap module, or we'd find
someone to implement a new thread-safe ns_ldap AOLserver module in
C, which will provide a Tcl interface to the parts of LDAP which we
need.
Index: openacs-4/packages/acs-mail-lite/www/doc/inbound.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/www/doc/inbound.adp,v
diff -u -r1.2.2.3 -r1.2.2.4
--- openacs-4/packages/acs-mail-lite/www/doc/inbound.adp 27 Apr 2022 16:21:06 -0000 1.2.2.3
+++ openacs-4/packages/acs-mail-lite/www/doc/inbound.adp 31 Jul 2024 09:59:29 -0000 1.2.2.4
@@ -12,7 +12,7 @@
acs_mail_lite::maildir_check_incoming
for MailDir.
- Both schedules procs can be run simultaneously without intefering with
+ Both schedules procs can be run simultaneously without interfering with
each other.
In both cases, email is added to the same queue for processing via callbacks.
After installing nsimap, setup consists of filling out the relevant parameters in the acs-mail-lite package, mainly: BounceDomain, FixedSenderEmail and the IMAP section.
After installing and configuring Postfix, a setup consists of filling out the relevant parameters in the acs-mail-lite package.
Index: openacs-4/packages/acs-messaging/www/doc/requirements.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-messaging/www/doc/requirements.adp,v
diff -u -r1.7.2.1 -r1.7.2.2
--- openacs-4/packages/acs-messaging/www/doc/requirements.adp 3 Sep 2021 09:15:45 -0000 1.7.2.1
+++ openacs-4/packages/acs-messaging/www/doc/requirements.adp 31 Jul 2024 09:59:29 -0000 1.7.2.2
@@ -32,7 +32,7 @@
single centralized facility.
III. System/Application Overview
The ACS Messaging package defines a data model and API for the
-storage and retrieval of messages. While the package standarizes
+storage and retrieval of messages. While the package standardizes
how messages are stored, applications may use any data model they
want for higher level organization of messages into threads,
forums, and so on. ACS Messaging places no organizational
Index: openacs-4/packages/acs-service-contract/www/doc/index.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-service-contract/www/doc/index.adp,v
diff -u -r1.7.2.2 -r1.7.2.3
--- openacs-4/packages/acs-service-contract/www/doc/index.adp 13 Jul 2023 12:49:25 -0000 1.7.2.2
+++ openacs-4/packages/acs-service-contract/www/doc/index.adp 31 Jul 2024 09:59:29 -0000 1.7.2.3
@@ -36,8 +36,8 @@
containers for operations.
operation - a method of an interface. defines a method
signature, including both input and outputs as well as metadata
such as caching.
implementation - an implementation is a set of concrete
-functions that fufills an interface.
implementation alias - is the method of an implementation that
-fufills a given operation of the contract.
bindings - association between an interface and an
+functions that fulfillss an interface.
implementation alias - is the method of an implementation that
+fulfillss a given operation of the contract.
bindings - association between an interface and an
implementation.
types - define the kind of input and outputs a operation
receives.
@@ -57,7 +57,7 @@
FAQ
Why Does an implementation reference an interface?
This might seem a little strange since a binding is the official
-reference between an implementation and an interface. However it is
+reference between an implementation and an interface. However, it is
quite possible that an implementation for interface might exist
prior to the interface being defined, ie the interface defining
package is not installed. By retaining this information the
@@ -84,7 +84,7 @@
Index: openacs-4/packages/acs-service-contract/www/doc/index.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-service-contract/www/doc/index.xml,v
diff -u -r1.6 -r1.6.2.1
--- openacs-4/packages/acs-service-contract/www/doc/index.xml 18 May 2018 07:56:07 -0000 1.6
+++ openacs-4/packages/acs-service-contract/www/doc/index.xml 31 Jul 2024 09:59:29 -0000 1.6.2.1
@@ -78,10 +78,10 @@
such as caching.
implementation - an implementation is a set of concrete functions
- that fufills an interface.
+ that fulfillss an interface.
implementation alias - is the method of an implementation that
- fufills a given operation of the contract.
+ fulfillss a given operation of the contract.
bindings - association between an interface and an implementation.
@@ -138,7 +138,7 @@
This might seem a little strange since a binding is the official
- reference between an implementation and an interface. However
+ reference between an implementation and an interface. However,
it is quite possible that an implementation for interface might
exist prior to the interface being defined, ie the interface
defining package is not installed. By retaining this information
@@ -196,7 +196,7 @@
(sql):
Index: openacs-4/packages/acs-templating/www/doc/timing-3.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/timing-3.adp,v
diff -u -r1.3.2.1 -r1.3.2.2
--- openacs-4/packages/acs-templating/www/doc/timing-3.adp 3 Sep 2021 09:16:00 -0000 1.3.2.1
+++ openacs-4/packages/acs-templating/www/doc/timing-3.adp 31 Jul 2024 09:59:29 -0000 1.3.2.2
@@ -12,7 +12,7 @@
suppressed them. The log message that marks the beginning of each
phase is written in the lower right of the graphs. Each curve curve
plots 288 page requests. As I didn't back port of the
-configurable cache refreshing stragegy ('never' or
+configurable cache refreshing strategy ('never' or
'always'), I show all graphs in the 'normal'
colors. The label is 'do', though.
Prototype
- has a pair of javascript functions that alllow
+ has a pair of javascript functions that allow
programmers to use XMLHTTP. The ajax.updater and ajax.request
functions. See http://api.prototypejs.org/ajax/Ajax/Updater/
Index: openacs-4/packages/assessment/www/doc/as_items.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/as_items.adp,v
diff -u -r1.9.2.4 -r1.9.2.5
--- openacs-4/packages/assessment/www/doc/as_items.adp 13 Jul 2023 12:45:46 -0000 1.9.2.4
+++ openacs-4/packages/assessment/www/doc/as_items.adp 31 Jul 2024 09:59:29 -0000 1.9.2.5
@@ -97,7 +97,7 @@
system to grant access rights to an as_item.
Read: An assessment author (who is
granted this permission) can reuse this as_item in one of his
-sections. (NB: Usually the original author has admin privileges.).
+sections. (NB: Usually, the original author has admin privileges.).
This is a finer granulation than the previous "enabled_p"
as it allows specific access to an item.
Write: Author can reuse and change this
as_item.
Admin: Author can reuse, change and give
@@ -362,7 +362,7 @@
horizontal - all Choices are in one line
vertical - all Choices are in one column
choice_label_orientation - how shall the label be positioned in
-relation to the choice (top, left, right, buttom).
+relation to the choice (top, left, right, bottom).
sort_order_type: Numerical, alphabetic, randomized or by order
of entry (sort_order field).
As is the custom in the OpenACS framework, all RDBMS tables in
the package will be prepended with "as_" to prevent
-further prefent naming clashes. Judicious use of namespaces will
+further prevent naming clashes. Judicious use of namespaces will
also be made in keeping with current OpenACS best practice.
Several of the Metadata entities have direct counterparts in the
Data-related partition of the data model. Some standards (notably
Index: openacs-4/packages/assessment/www/doc/data_collection.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/data_collection.adp,v
diff -u -r1.5.2.3 -r1.5.2.4
--- openacs-4/packages/assessment/www/doc/data_collection.adp 3 Sep 2021 09:16:30 -0000 1.5.2.3
+++ openacs-4/packages/assessment/www/doc/data_collection.adp 31 Jul 2024 09:59:29 -0000 1.5.2.4
@@ -70,7 +70,7 @@
integration between Assessment and GC thus will need to be at the
UI level, not the data model level. Using GC will support post-test
"discussions" between student and teacher, for example,
-about inidividual items, sections or sessions.
+about individual items, sections or sessions.
Scoring-grading: This has been a rather
controversial area because of the wide range of needs for derived
calculations/evaluations that different applications need to
@@ -250,7 +250,7 @@
Signing of content
-allows to verify that the data submitted is actually from the
+allows one to verify that the data submitted is actually from the
person it is pretended to be from. This assumes a public key
environment where the public key is stored along with the user
information (e.g. with the users table) and the data stored in
Index: openacs-4/packages/assessment/www/doc/display_types.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/display_types.adp,v
diff -u -r1.7.2.5 -r1.7.2.6
--- openacs-4/packages/assessment/www/doc/display_types.adp 13 Jul 2023 12:45:46 -0000 1.7.2.5
+++ openacs-4/packages/assessment/www/doc/display_types.adp 31 Jul 2024 09:59:29 -0000 1.7.2.6
@@ -145,9 +145,9 @@
Name: text. Name of the section like "test view
sorted"
Number of questions per page: integer. THIS HAS TO BE CHANGED
IN THE DATA MODEL FROM PAGINATION_STYLE. How many questions shall
-be displayed per page in this section. Usually the answer would be
+be displayed per page in this section. Usually, the answer would be
"" for all questions on one page (default), or
-"1" for one question per page (a.k.a. one question at a
+"1" for one question per page (aka one question at a
time), but any number is imagineable.
ADP style: ADP to
choose from that will control the makeup of the section along with
@@ -167,7 +167,7 @@
display a "save" button next to each answer along with
green "V" if the answer has been already submitted. To
finish the section, you still have to click on the OK button at the
-buttom. Once the section is finished all answers that have not been
+bottom. Once the section is finished all answers that have not been
separately submitted will be treated as not being submitted at
all.
Index: openacs-4/packages/assessment/www/doc/grouping.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/grouping.adp,v
diff -u -r1.8.2.3 -r1.8.2.4
--- openacs-4/packages/assessment/www/doc/grouping.adp 13 Jul 2023 12:45:46 -0000 1.8.2.3
+++ openacs-4/packages/assessment/www/doc/grouping.adp 31 Jul 2024 09:59:29 -0000 1.8.2.4
@@ -110,7 +110,7 @@
shareable_p boolean. As with Items and Sections, we instead will
use the acs permission system:
Read: An assessment author (who is granted this permission) can
-reuse this assessment (NB: Usually the original author has admin
+reuse this assessment (NB: Usually, the original author has admin
privileges.)
Write: Author can reuse and change this assessment.
Admin: Author can reuse, change and give permission on this
assessment
Respond: The user can respond to the survey.
@@ -141,7 +141,7 @@
shareable_p boolean. As with Items and Assessments, we instead will
use the acs permission system:
Read: A section author (who is granted this permission) can
-reuse this section (NB: Usually the original author has admin
+reuse this section (NB: Usually, the original author has admin
privileges.)
Write: Author can reuse and change this section.
Admin: Author can reuse, change and give permission on this
section
Index: openacs-4/packages/assessment/www/doc/index.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/index.adp,v
diff -u -r1.5.2.2 -r1.5.2.3
--- openacs-4/packages/assessment/www/doc/index.adp 3 Sep 2021 09:16:31 -0000 1.5.2.2
+++ openacs-4/packages/assessment/www/doc/index.adp 31 Jul 2024 09:59:29 -0000 1.5.2.3
@@ -7,7 +7,7 @@
members of the OpenACS community for data collection functionality
within the OpenACS framework. We're using the term
"Assessment" instead of "Survey" or
-"Questionnaire" (or "Case Report Form" a.k.a.
+"Questionnaire" (or "Case Report Form" aka
CRF, the term used in clinical trials) because it is a term used by
IMS and because it connotes the more generic nature of the data
collection system we're focusing on.
@@ -149,7 +149,7 @@
deleting the Sections themselves. Includes the page to browse for
items to include in sections
Item Authoring and
-Catalogue: all the pages involing the item creation and the
+Catalogue: all the pages involving the item creation and the
item catalogue.
Assessment
Delivery: all the pages involved in deploying a given
Index: openacs-4/packages/assessment/www/doc/item_types.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/item_types.adp,v
diff -u -r1.4.2.3 -r1.4.2.4
--- openacs-4/packages/assessment/www/doc/item_types.adp 3 Sep 2021 09:16:31 -0000 1.4.2.3
+++ openacs-4/packages/assessment/www/doc/item_types.adp 31 Jul 2024 09:59:29 -0000 1.4.2.4
@@ -201,7 +201,7 @@
are displayed in each column.
Composite multiple choice with Fill-in-Blank item:
Multiple Choice question with an additional short_text input
-field. Usually used for the "Other" thing
+field. Usually, used for the "Other" thing
Calculation:
This type of question will not be supported. But we should make
sure we can take care of that type while importing the data from
Index: openacs-4/packages/assessment/www/doc/requirements.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/requirements.adp,v
diff -u -r1.6.2.4 -r1.6.2.5
--- openacs-4/packages/assessment/www/doc/requirements.adp 3 Sep 2021 09:16:31 -0000 1.6.2.4
+++ openacs-4/packages/assessment/www/doc/requirements.adp 31 Jul 2024 09:59:29 -0000 1.6.2.5
@@ -322,7 +322,7 @@
students or other data entry personnel. These actions potentially
will involve interfacing with other Workflow management tools (e.g.
an "Enrollment" package that would handle creation of new
-Parties (a.k.a. clinical trial subjects) in the database.
+Parties (aka clinical trial subjects) in the database.
Schedulers could also be teachers, curriculum designers, site
coordinators in clinical trials, etc.
Analyst
@@ -354,7 +354,7 @@
center around mechanisms encountered here: to prove exactly who
created any datum, when, whether it is a correct value, whether
anyone has looked at it or edited it and when, etc etc...)
-
Staff could be site coordinators in clinical trials, insurance
+
Staff could be site coordinators in clinical trials, ensurance
adjustors, accountants, tax preparation staff, etc.
System / Application Overview
@@ -529,7 +529,7 @@
Start and End Dates for an Assessment
Number of times a Subject can perform the Assessment (1-n)
Interval between Assessment completion if Subject can perform
it more than once
Whether anonymous Subjects are allowed
Text of email to Subjects to Invite, Remind and Thank them for
-performing Assessment
Text of email to Staff to Instuct, Remind and Thank them for
+performing Assessment
Text of email to Staff to Instruct, Remind and Thank them for
performing Assessment on a Subject
Provide these additional functions:
Index: openacs-4/packages/assessment/www/doc/sequencing.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/sequencing.adp,v
diff -u -r1.4.2.2 -r1.4.2.3
--- openacs-4/packages/assessment/www/doc/sequencing.adp 3 Sep 2021 09:16:32 -0000 1.4.2.2
+++ openacs-4/packages/assessment/www/doc/sequencing.adp 31 Jul 2024 09:59:29 -0000 1.4.2.3
@@ -86,7 +86,7 @@
:item_4231 == 'red'". Additionally other variables
might be defined by the API at a later stage, e.g.
":percent_score", which would be replaced by the current
-percentage value (a.k.a. score) that subject had in the test so far
+percentage value (aka score) that subject had in the test so far
(taken from the as_session_table). It might be interesting to pass
these variables along in the API, this remains to be seen when
actually implementing the system.
During its lifetime, an Assessment may undergo revisions in the
midst of data collection. These revisions may be minor (change of a
-label on an Item or adddition of a new Choice to an Item) or major
+label on an Item or addition of a new Choice to an Item) or major
(addition or deletion of an entire Section). Obviously in most
applications, such changes are undesirable and people want to avoid
them. But the reality is that such changes are inevitable and so
Index: openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp,v
diff -u -r1.5.2.1 -r1.5.2.2
--- openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp 3 Sep 2021 09:16:35 -0000 1.5.2.1
+++ openacs-4/packages/assessment/www/doc/asm_trigger_doc/ch02s01.adp 31 Jul 2024 09:59:29 -0000 1.5.2.2
@@ -19,7 +19,7 @@
administrator. This permissions can be managed follogging the
Permission link that appears in the list of assessments.
Both links will lead the user to a page where the necessary
permissions can be set.
Also the user can search for another user to manage his
-permissions:
After clicking OK, the user will appear in the list an the
+permissions:
After clicking OK, the user will appear in the list the
permissions can be set properly.
5. Action Triggers
To define an Action Trigger, the field "Type" in the
-form must be checked as "Action".
The condition field shows the question and its possible anwers,
+form must be checked as "Action".
The condition field shows the question and its possible answers,
it means that when the user is responding the assessment, if this
answer is given for this question, the action will be executed.
After the trigger is created, the action related must be chosen,
also the time when the action will be executed, and the message
Index: openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp,v
diff -u -r1.9.2.3 -r1.9.2.4
--- openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp 13 Jul 2023 12:45:46 -0000 1.9.2.3
+++ openacs-4/packages/assessment/www/doc/user_interface/assessment_creation.adp 31 Jul 2024 09:59:30 -0000 1.9.2.4
@@ -66,8 +66,8 @@
Availability: 2 date widgets (from, and to). This will set the
time the time the survey will become visible for the respondees. It
-is overridden by the parameter enabled (if a assessment is not
-enabled, it will never be visible, regardless of date).
How often can a assessment be taken: Number of times a survey
+is overridden by the parameter enabled (if an assessment is not
+enabled, it will never be visible, regardless of date).
How often can an assessment be taken: Number of times a survey
can be taken by a respondee.
How long has a user to pause: Number of hours a respondee has
to wait before he can take the assessment again.
Answer_time: integer: Time in minutes a respondee has to answer
a survey.
Download filename: short_text. Filename for the download of
the export.
Delete assessment with / without responses
Assign category to the assessment
Index: openacs-4/packages/assessment/www/doc/user_interface/index.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/index.adp,v
diff -u -r1.8.2.3 -r1.8.2.4
--- openacs-4/packages/assessment/www/doc/user_interface/index.adp 3 Sep 2021 09:16:36 -0000 1.8.2.3
+++ openacs-4/packages/assessment/www/doc/user_interface/index.adp 31 Jul 2024 09:59:30 -0000 1.8.2.4
@@ -68,7 +68,7 @@
all to all the storing of test results. In addition to this, it
will provide functionality to other packages to allow rating of
their contents (one example of this would be Lars Rating package,
-that would be used as a basis for this). In general it should
+that would be used as a basis for this). In general, it should
provide a very flexible way of adding scores into the system,
either automatically (as described above) or manually (e.g. this
student did a good oral exam).
@@ -121,7 +121,7 @@
"change basic information" as one assessment among
many.
With a little bit of tweaking and the
-possibility to add instant gratification, a.k.a. aggregated result
+possibility to add instant gratification, aka aggregated result
display, it could include the poll package and make it
redundant.
Last but not least with the ability to
Index: openacs-4/packages/assessment/www/doc/user_interface/tests.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/user_interface/tests.adp,v
diff -u -r1.8.2.4 -r1.8.2.5
--- openacs-4/packages/assessment/www/doc/user_interface/tests.adp 13 Jul 2023 12:45:46 -0000 1.8.2.4
+++ openacs-4/packages/assessment/www/doc/user_interface/tests.adp 31 Jul 2024 09:59:30 -0000 1.8.2.5
@@ -105,7 +105,7 @@
option the user choose he will get the according percentage. If
negative points are allowed, the user will get a negative
percentage. In any case, a user can never get more than 100% or
-less then -100%.
First section will be delivered to the
-user for anwering.
+user for answering.
Depending on the settings, the display of the
assessment will vary:
@@ -43,7 +43,7 @@
of the page to "hand the test to the TA" if this is
allowed
Allow for chancellation of the test with
a chancel button. The result will not be stored but the test will
-be marked as taken.
If immediate answer validation (a.k.a..
+be marked as taken.
If immediate answer validation (aka.
ad_form check) for a question is true, check the answer if it is
valid, otherwise notify the user that it is not and do not store
the result.
Index: openacs-4/packages/file-storage/www/doc/design.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/file-storage/www/doc/design.adp,v
diff -u -r1.4.2.4 -r1.4.2.5
--- openacs-4/packages/file-storage/www/doc/design.adp 13 Jul 2023 12:45:46 -0000 1.4.2.4
+++ openacs-4/packages/file-storage/www/doc/design.adp 31 Jul 2024 09:59:30 -0000 1.4.2.5
@@ -52,7 +52,7 @@
from a Web browser. The cracker is now executing arbitrary code on
your server with all the privileges that you've given your Web
server.
-
The File Storage application is not a web-based file system, and
+
The File Storage application is not a web-based filesystem, and
can not be fairly compared against such systems. The role of File
Storage is to provide a simple web location where users can share a
versioned document. It does not allow much functionality with
@@ -138,7 +138,7 @@
The main objects of File Storage are "folders" and
"files". A "folder" is analogous to a
subdirectory in the Unix/Windows-world filesystem. Folder objects
-are stored as Content Repostory folders, thus folders are stored
+are stored as Content Repository folders, thus folders are stored
"as is" in the Content Repository.
"Files", however, can cause some confusion when stored
in the Content Repository. A "file" in File Storage
@@ -207,7 +207,7 @@
Sends the requested file to the user. Note that the
-path has the original file name, so the browser will have a
+path has the original filename, so the browser will have a
sensible name if you save the file. Version downloads are supported
by looking for the form variable version_id. We don't actually
check that the version_id matches the path, we just serve it up.
@@ -325,7 +325,7 @@
improvements in Content Repository will allow archiving of the
contents instead of actually deleting them from the database.
VIII. User Interface
-
The user interface attempts to replicate the file system
+
The user interface attempts to replicate the filesystem
metaphors familiar to most computer users, with folders containing
files. Adding files and folders are hyperlinked options, and a web
form is used to handle the search function. Files and folders are
Index: openacs-4/packages/xowiki/www/xinha/insert-ilink.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xowiki/www/xinha/insert-ilink.adp,v
diff -u -r1.5 -r1.5.2.1
--- openacs-4/packages/xowiki/www/xinha/insert-ilink.adp 28 Mar 2018 23:36:17 -0000 1.5
+++ openacs-4/packages/xowiki/www/xinha/insert-ilink.adp 31 Jul 2024 09:59:30 -0000 1.5.2.1
@@ -110,17 +110,17 @@
(w < 640) ? w = 640 : w = w;
(h < 480) ? h = 480 : h = h;
- var dimensons = "width="+w+",height="+h;
+ var dimensions = "width="+w+",height="+h;
if (!document.all) {
selector_window = window.open("@file_selector_link;noquote@",
"file_selector" ,
"toolbar=no,menubar=no,personalbar=no,scrollbars=yes,resizable=yes," +
- dimensons);
+ dimensions);
} else {
selector_window = window.open("@file_selector_link;noquote@",
"file_selector",
"channelmode=no,directories=no,location=no,menubar=no,resizable=yes,scrollbars=yes,toolbar=no," +
- dimensons);
+ dimensions);
}
selector_window.moveTo(w/2,h/2);
selector_window.focus();
Index: openacs-4/packages/xowiki/www/xinha/insert-image.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xowiki/www/xinha/insert-image.adp,v
diff -u -r1.7 -r1.7.2.1
--- openacs-4/packages/xowiki/www/xinha/insert-image.adp 4 Jul 2018 10:25:22 -0000 1.7
+++ openacs-4/packages/xowiki/www/xinha/insert-image.adp 31 Jul 2024 09:59:30 -0000 1.7.2.1
@@ -85,11 +85,11 @@
(w < 640) ? w = 640 : w = w;
(h < 480) ? h = 480 : h = h;
- var dimensons = "width="+w+",height="+h;
+ var dimensions = "width="+w+",height="+h;
if (!document.all) {
- selector_window = window.open("@file_selector_link;noquote@", "file_selector" , "toolbar=no,menubar=no,personalbar=no,scrollbars=yes,resizable=yes," + dimensons);
+ selector_window = window.open("@file_selector_link;noquote@", "file_selector" , "toolbar=no,menubar=no,personalbar=no,scrollbars=yes,resizable=yes," + dimensions);
} else {
- selector_window = window.open("@file_selector_link;noquote@", "file_selector", "channelmode=no,directories=no,location=no,menubar=no,resizable=yes,scrollbars=yes,toolbar=no," + dimensons);
+ selector_window = window.open("@file_selector_link;noquote@", "file_selector", "channelmode=no,directories=no,location=no,menubar=no,resizable=yes,scrollbars=yes,toolbar=no," + dimensions);
}
// alert("HIER");
selector_window.moveTo(w/2,h/2);