Commit ea4dc989 authored by Neil Turton's avatar Neil Turton
Browse files

Import from cleaned 360 CD

parents
| Copyright 1996 Acorn Computers Ltd
|
| Licensed under the Apache License, Version 2.0 (the "License");
| you may not use this file except in compliance with the License.
| You may obtain a copy of the License at
|
| http://www.apache.org/licenses/LICENSE-2.0
|
| Unless required by applicable law or agreed to in writing, software
| distributed under the License is distributed on an "AS IS" BASIS,
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
| See the License for the specific language governing permissions and
| limitations under the License.
|
Dir <Obey$Dir>
amu_machine all
| Copyright 1996 Acorn Computers Ltd
|
| Licensed under the Apache License, Version 2.0 (the "License");
| you may not use this file except in compliance with the License.
| You may obtain a copy of the License at
|
| http://www.apache.org/licenses/LICENSE-2.0
|
| Unless required by applicable law or agreed to in writing, software
| distributed under the License is distributed on an "AS IS" BASIS,
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
| See the License for the specific language governing permissions and
| limitations under the License.
|
Dir <Obey$Dir>
amu_machine clean
| Copyright 1996 Acorn Computers Ltd
|
| Licensed under the Apache License, Version 2.0 (the "License");
| you may not use this file except in compliance with the License.
| You may obtain a copy of the License at
|
| http://www.apache.org/licenses/LICENSE-2.0
|
| Unless required by applicable law or agreed to in writing, software
| distributed under the License is distributed on an "AS IS" BASIS,
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
| See the License for the specific language governing permissions and
| limitations under the License.
|
Dir <Obey$Dir>
amu_machine install INSTDIR=<obey$dir>
| Copyright 1996 Acorn Computers Ltd
|
| Licensed under the Apache License, Version 2.0 (the "License");
| you may not use this file except in compliance with the License.
| You may obtain a copy of the License at
|
| http://www.apache.org/licenses/LICENSE-2.0
|
| Unless required by applicable law or agreed to in writing, software
| distributed under the License is distributed on an "AS IS" BASIS,
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
| See the License for the specific language governing permissions and
| limitations under the License.
|
Dir <Obey$Dir>
amu_machine resources
| Copyright 1996 Acorn Computers Ltd
|
| Licensed under the Apache License, Version 2.0 (the "License");
| you may not use this file except in compliance with the License.
| You may obtain a copy of the License at
|
| http://www.apache.org/licenses/LICENSE-2.0
|
| Unless required by applicable law or agreed to in writing, software
| distributed under the License is distributed on an "AS IS" BASIS,
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
| See the License for the specific language governing permissions and
| limitations under the License.
|
Dir <Obey$Dir>
amu_machine rom
s/** gitlab-language=armasm linguist-language=armasm linguist-detectable=true
awk/** gitlab-language=awk linguist-language=awk linguist-detectable=true
*,ffb gitlab-language=bbcbasic linguist-language=bbcbasic linguist-detectable=true
Additional Alarm documentation (2.09)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In addition to the "normal" user facilities of !Alarm as documented in the
User Guide, it is also possible for applications to set and receive alarms
by using some WIMP messages. These are as follows:
To set an application alarm, send the following message.
block+16 &500 indicate message to !Alarm
+20 0/1 indicate set an alarm (1 if 5 byte format)
+24 date/time
+30 name of application sender, terminated by 0
+n application-specific unique alarm identifier, terminated by 0
Date & time must be given in standard 5 byte format if +20 is 1, otherwise
the layout is:
+24 year as low-byte/high-byte
+26 month
+27 date
+28 hour
+29 minutes
Neither the name nor the alarm identifier may be longer than 40 chars each.
To cancel the alarm, use the following message block:
block+16 &500 indicate message to !Alarm
+20 2 indicate cancel an alarm
+24 name of application, terminated by 0
+n application-specific unique alarm identifier, terminated by 0
The name & identifier must match exactly for the alarm to be successfully
cancelled. It is not necessary to specify the time of the alarm, as this may
have changed due to being deferred by Alarm.
If these messages are sent recorded, !Alarm will acknowledge with 0 if
successful, or a 0 terminated error string.
When an alarm goes off, the format of the block sent by !Alarm as a
broadcast is:
block+16 &501 indicate an alarm has gone off
+20 name of application sender, terminated by 0
+n application-specific unique alarm identifier, terminated by 0
If the named application recognises the identifier, it must acknowledge this
message, otherwise !Alarm will ask the user to install the named
application. If the latter occurs, the alarm is deferred for one minute to
allow the application to be installed.
All alarms set are stored in <Alarm$Dir>.!Alarm. This is a data file
containing a linked list of alarms as follows:
PTR Contents
~~~ ~~~~~~~~
0 PTR to first alarm, -1 if none set
5 PTR to first free space, -1 if none available
...
For each alarm or free space block:
n PTR to next alarm/free space block, -1 if last
n+5 PTR to previous alarm/free space block, -1 if first
n+10 set alarm time stored as five byte format plus urgent flag (as a string)
n+17 alarm text
contains 3 strings, each a maximum of 40 characters
if a task alarm then the 3 strings are concatenated to form the command
if an application alarm then string 1 is the task name
string 2 is the unique indentifier
n+144 flags:
bit 0 = application alarm
1 = normal repeating alarm
2 = task alarm
3 = 5 day week
4 = special repeating alarm
If a normal repeating alarm then
n+145 repeat period:
bit 0 = minutes
1 = hours
2 = days
3 = weeks
4 = months
5 = years
n+146 repeat multiplier (1 byte)
else
n+145 bits 0 to 3: day in the week to repeat on (1-7)
bits 4 to 7: offset within month (0-5)
n+146 number of months of skip (1-12)
endif
* when an alarm is loaded into memory from an alarm file, it is validated to
ensure that the alarm is falling into a valid day of the week
(PROCvalidate_alarm). This is achieved by making the alarm go BACKWARDS
until it is valid.
* when the user manipulates the alarm/clock windows,
PROCchange_date/month/year are called as appropriate. These all work the
same way - the five byte time is broken down into its cardinal parts, the
appropriate cardinal is changed and the five byte time is reconsituted.
* special repeating alarms
* calculating when an alarm repeats:
PROCincrement_alarm for normal repeating alarms - works by just adding the
appropriate value to the appropriate cardinal. Possible problems: assumes
adding 2 will get it into a valid day of the week.
PROCincrement_special_alarm for special repeating alarms - works by first
of all seeing if the alarm will go off in this month, if so, we are OK.
* the guts of this system, PROCencode_time, does assume that there are 12
months in the year. However, if Ran implements an alternative, we may have
a way out.
* FNvalid_day_of_week needs to know which days are working days.
* deferring alarms works like normal repeating alarms - the appropriate
offset is added to the appropriate cardinal.
* calculating when an alarm has gone off: this works by turning the
current five byte time into a string and then comparing that against the
five byte time of the alarm.
;>!Alarm log file
PColmer 28-Feb-90 Created.
PColmer 01-Mar-90 Changes between 2.00 and 2.01 entered.
PColmer 06-Mar-90 Changes between 2.02 and 2.01 entered.
PColmer 22-Mar-90 Changes between 2.05 and 2.02 entered.
PColmer 03-Apr-90 Changes between 2.06 and 2.05 entered.
PColmer 04-Apr-90 Changes between 2.07 and 2.06 entered.
PColmer 07-Apr-90 Changes between 2.08 and 2.07 entered.
PColmer 13-Apr-90 Changes between 2.09 and 2.08 entered.
PColmer 19-Apr-90 Changes between 2.10 and 2.09 entered.
PColmer 29-May-90 Changes between 2.11 and 2.10 entered.
PColmer 22-Jun-90 Changes between 2.12 and 2.11 entered.
Functionality Changes
---------------------
Version 2.00
* Derived from version 1.00x (Development)
Version 2.01
* Added code to allow international date and time strings
* Added "TaskID" to messages file
Version 2.02
* Moved the date and time messages to the beginning of the file to make it faster
Version 2.03
* Didn't exist
Version 2.04
* Didn't exist
Version 2.05
* Improved null event handling if seconds aren't required
Version 2.06
* Fixed bug in setting clock (display didn't get updated)
* Clicking ADJUST on the icon allows the clock to be set
Version 2.07
* Fixed bug in changing display format (ignored seconds)
Version 2.08
* Added check for correct !Run file
* !Alarm file no longer present in ROM image
* Changed check for FS 21 to FS 46
Version 2.09
* Now possible to set alarms of the type "last Thursday of every month"
Version 2.10
* Fixed broken deferred alarms
Version 2.11
* RO and RO2+ versions diverge in the message handling
* If the required message cannot be found, the tag is displayed instead
* Attempt at doing a 3D alarm display
Version 2.12
* Fixed bug where task alarms stopped the display getting updated
* Changed the default beep timeout from -1 to 10 seconds
New !Alarm file format (v2.19 +)
================================
Offset Contents
0 Identifier - "ALRM" (&4D524C41)
4 Ptr to first alarm as a BASIC integer
-1 if none set
9 Ptr to first free space as a BASIC integer
-1 if none available
14 First record
n Version number for this record as a BASIC integer
(currently only 100 is recognised)
n+5 Ptr to next alarm or free space block as a BASIC integer
-1 if last record
n+10 Ptr to previous alarm or free space block as a BASIC integer
-1 if first record
n+15 Alarm time:
+15: year high byte
+16: year low byte
+17: month
+18: date
+19: hours
+20: minutes
+21: urgency flag
n+22 Alarm text:
Each string is a maximum of 40 characters, stored as BASIC strings
(0 identifier, length byte then string). If alarm is a task alarm,
the three strings are concatenated to form the command. If alarm
is an application alarm, string 1 is the task name, string 2 is
the task's unique identifier.
+22: string 1 (1+1+40)
+64: string 2 (1+1+40)
+106: string 3 (1+1+40)
n+148 Flags:
bit 0 = application alarm
1 = normal repeating alarm
2 = task alarm
3 = working week schedule
4 = special repeating alarm
If a normal repeating alarm then
n+149 Repeat period:
bit 0 = minutes
1 = hours
2 = days
3 = weeks
4 = months
5 = years
n+150 Repeat multiplier
else
n+149 Bits 0 to 3: day in week to repeat on (1-7)
4 to 7: offset within month (0-5, corresponding to
SR messages)
0000: 0: first
0001: 1: second
0010: 2: third
0011: 3: last
0100: 4: penultimate
0101: 5: third to last
n+150 Number of months to skip
Daylight saving is achieved through the use of application alarms to itself.
There are three application alarms initially set - one for going into DST,
one for coming out and one for reminding the user to reset the dates. The
alarms have similar task unique identifiers:
<alarm number>ddmmDDMMYYYY
where ddmm is the date and month of going into DST, DDMM is the date and
month of coming out of DST and YYYY is the year for these values. Alarm 3 is
always set on 1/1/YYYY+1
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
# Copyright 1996 Acorn Computers Ltd
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Makefile for Alarm
#
# ***********************************
# *** C h a n g e L i s t ***
# ***********************************
# Date Name Description
# ---- ---- -----------
# 05-Nov-94 AMcC Updated for Black build
#
#
# Program specific options:
#
COMPONENT = Alarm
APP = !${COMPONENT}
ROM_MODULE = rm.${COMPONENT}
RDIR = Resources
LDIR = ${RDIR}.${LOCALE}
#
# Export Paths for Messages module
#
RESDIR = <resource$dir>.Resources2.${COMPONENT}
RESAPP = <resource$dir>.Apps.${APP}
#
# Generic options:
#
MKDIR = cdir
AS = aasm
CP = copy
RM = remove
SQUISH = squish
WIPE = -wipe
AFLAGS = ${THROWBACK} -depend !Depend -nocache -stamp -quit -module
CPFLAGS = ~cfr~v
SQFLAGS = -nolist
WFLAGS = ~c~v
FILES =\
${RDIR}.!Boot \
${LDIR}.!Help \
${RDIR}.!Run \
${RDIR}.!RunImage \
${RDIR}.Alarms \
${RDIR}.Code \
${LDIR}.Messages \
${LDIR}.Templates
# Resources to be included in the ROM module (not in Messages module}
RESFILES =\
${RDIR}.code \
${RDIR}.!RunImage
#
# Main rules:
#
all: ${FILES}
@echo ${COMPONENT}: Application built (Disc}
rom: ${ROM_MODULE}
@echo ${COMPONENT}: Module built (ROM}
install: ${FILES}
${MKDIR} ${INSTDIR}.${APP}
|
${CP} ${RDIR}.!Boot ${INSTDIR}.${APP}.!Boot ${CPFLAGS}
${CP} ${LDIR}.!Help ${INSTDIR}.${APP}.!Help ${CPFLAGS}
${CP} ${RDIR}.!Run ${INSTDIR}.${APP}.!Run ${CPFLAGS}
${CP} ${RDIR}.!RunImage ${INSTDIR}.${APP}.!RunImage ${CPFLAGS}
${CP} ${RDIR}.Alarms ${INSTDIR}.${APP}.Alarms ${CPFLAGS}
${CP} ${RDIR}.Code ${INSTDIR}.${APP}.Code ${CPFLAGS}
${CP} ${LDIR}.Messages ${INSTDIR}.${APP}.Messages ${CPFLAGS}
${CP} ${LDIR}.Template3D ${INSTDIR}.${APP}.Templates ${CPFLAGS}
|
Access ${INSTDIR}.${APP}.* lr/r
Access ${INSTDIR}.${APP}.Alarms wr/r
|
@echo ${COMPONENT}: Application installed {Disc}
install_rom: ${ROM_MODULE}
${CP} ${ROM_MODULE} ${INSTDIR}.${COMPONENT} ${CPFLAGS}
@echo ${COMPONENT}: Module installed {ROM}
resources: ${LDIR}.!RunLink ${RDIR}.Code