Skylog Documentation

Change Log

Introduction

Below are notes on changes contained in each revision of Skylog that is made publicly available. The most recent changes are listed first.

Aril 30, 2011

skylog.php revision 1.30 on live.skylog.net and demo.skylog.net

Station Summary: Checked-out stations now display their station notes.

Aril 29, 2011

skylog.php revision 1.29 on live.skylog.net and demo.skylog.net

All changes from 1.27.4.x below are merged in to production.

Tips and tricks documentation has been updated:

Added Edit Incident tip for Mac users regarding keyboard access.
Updated list of station statuses to include recently-added items.

Aril 22, 2011

skylog.php revision 1.28 on live.skylog.net

All changes from 1.27.2.2 below are included in this revision.
:SN command can also clear a station's note. Simply omit the note argument.

skylog.php revision 1.27.4.x on demo.skylog.net

Group-level administration: If a user doesn't already exist on the system, it can now be created. (Formerly, only top-level admin could create users.)

Aril 10, 2011

skylog.php revision 1.27.2.2 on demo.skylog.net

Added the ability to put notes on stations. Examples of potential uses:
- When stations are entered with tactical calls, make notes of the real operators' callsigns.
- Have a game plan for the station? Note it here.
- Make a note of when the station needs to go off duty.
:SN command added to set a station's note.
Station summary: Display station notes when they are set.
Incident summary: Stations assigned to open incidents now have a non-breaking space between the callsign and status.

August 16, 2010

skylog.php revision 1.26 on live.skylog.net and demo.skylog.net

:IRC command to cancel a station's In-Route status
:AS command to change a station back to Assigned status (without having to unassign and re-assign)
Many screens: Decrease the amount of top/bottom padding on many screen elements, so that more information is viewable without scrolling.
Incident summary: Open incidents sort by priority and then event time
Calling station: In addition to the station's callsign, the station's status is also displayed in the header.
Edit incident: A warning is displayed if the reporting station is checked out.
Dump: Fixed bug where non-acknowledged messages would claim to be received at a fictional time.

May 30, 2010

skylog.php revision 1.23 on live.skylog.net and demo.skylog.net

:LU command to enter a Location Update for a station

May 29, 2010

skylog.php revision 1.22 on live.skylog.net and demo.skylog.net

In order to save space, screen titles now appear at the top of the screen, rather than below the header line.
Calling Station, Incident Summary, Log, Station Summary: IE users can now press enter while typing in the text field at the top, rather than having to explicitly hit the Submit button.

May 5, 2010

skylog.php revision 1.19 on live.skylog.net and demo.skylog.net

Calling Station: Station mentions that are associated with incidents used to display/sort by the incident's even time. Skylog now keeps track of when the mention was actually entered and displays/sorts according to that time.
Edit Incident: When creating a new incident from the Calling Station screen, the reporting station was not getting properly recorded as a station mention. Thus, future uses of the Calling Station were not mentioning the newly created incident. This has been fixed.

May 1, 2010

skylog.php revision 1.17 on live.skylog.net and demo.skylog.net

The goal of this revision is to make it easier to react to a station that's calling in.
Added Calling Station screen to display all incidents and status changes that a station is mentioned in.
New colon command :CS can be used to access the Calling Station screen. It accepts one argument, which is the callsign of the calling station.
Incident Summary, Station Summary and Log screens: If a valid callsign is entered in the Command field at the top, the Calling Station screen is brought up.
When on Calling Station screen, creation of a new incident assumes that the calling station becomes the reporting station.

November 15, 2009

skylog.php revision 1.16 on live.skylog.net and demo.skylog.net

Group-level Administration screen has been implemented to allow designated Group Masters to add/remove members and set privileges.
Top-level Administration: Fixed bug that lost the enabled and TLA flags on a newly created user.

September 26, 2009

skylog.php revision 1.15 on live.skylog.net and demo.skylog.net

Switchboard: Fixed forgotten feature of putting a "logged in" message in the log when a user selects a group to use
Edit Incident and numerous colon commands: Truncate callsigns to the 20-character limit before doing comparisons

September 24, 2009

skylog.php revision 1.14 on live.skylog.net and demo.skylog.net

Switchboard: Fixed bug that prevented a user from selecting a group to work with
Edit User: Fixed bug in handling newly created user due to lack of group memberships

September 24, 2009

skylog.php revision 1.13 on live.skylog.net and demo.skylog.net
skylog.css revision 1.7 on live.skylog.net and demo.skylog.net
assist/mysql-setup.sql revision 1.28

Add the concepts of "top-level admin" and "group chief" access levels.
The Group Selection screen has been replaced with the Switchboard screen.
Switchboard allows a user to select the group to work within, or access top-level admin (if permitted) or access group-level admin (if permitted).
Group-Level Admin has not been written yet - selection of Group-level Admin options from Switchboard has no effect.
User editing has been moved out of the Top-Level Admin screen to its own Edit User screen with record locking.

March 13, 2009

skylog.php revision 1.12 on live.skylog.net
assist/mysql-setup.sql revision 1.27

This is a major revision that includes all of the changes noted for revision 1.11.2.13 below.

March 6, 2009

skylog.php revision 1.11.2.13 on demo.skylog.net
assist/mysql-setup.sql revision 1.26.2.1

Added Documentation screen - provides access to the docs without having to log back out.
Change Password: Automatically put the input focus on the New Password field.
Dump: When displaying user-to-user messages, display the sending user's name and the time it was marked as received.
Dump: Performed some code optimizations.
Edit Incident: The Close Time field now accepts "open" as a synonym for "none"
Edit Incident: If the user only added notes (made no other changes), avoid generating an excess meaningless log entry.
Edit Incident: Moved the station location update code so that it always runs and updates a station's location when appropriate.
Edit Incident: Unassign stations from the incident if there is a close time - even if it's in the future.
Messaging: Display users according to whether they are logged in, then by login name. The old order (last seen) was confusing.
Messaging: When sending message, don't excessively escape the message text when adding it to the log. (Ditto for :SEND)
New lock conflict checking code for the status change colon commands (:CI/:CO/:IR/:IS/:OL). Now also checks if the station is the reporting station of a locked incident.

May 20, 2008

skylog.php revision 1.10 on demo.skylog.net and live.skylog.net

This is a major revision that includes all of the changes noted for the 1.9.2.x revisions below, plus the changes included in this list.
Incident Summary, Station Summary, Log: Command field reacts to IE user simply pressing ENTER (without having to click on Submit).
Incident Summary, Station Summary, Log: When the user types, the auto-reload timer gets reset to 60 seconds.
Incident Summary, Edit Incident: When an incident has stations assigned to it, the statuses of the assigned stations are displayed.
Edit Incident: If a station is assigned to an incident when it was already in IR status, the user is notified to review the station's new status. In many such cases, the user will need to make a decision on how they want the station to look at that point.

May 14, 2008

skylog.php revision 1.9.2.13 on demo.skylog.net

Edit Incident: Fixed SQL error when clicking Cancel or Hold. (Bug introduced in 1.9.2.10.)
Edit Incident: If the close time is changed to show that the incident is now closed AND this resulted in unassigning a station from the incident, that station's INROUTE TO field now gets cleared.
:CI command: Now clears station's INROUTE TO field
:CL command: If closing the incident also means unassigning a station, the station now gets its INROUTE TO field cleared

May 1, 2008

skylog.php revision 1.9.2.10 on demo.skylog.net
skylog.css revision 1.6 on demo.skylog.net

Edit Incident: Reformatted display of assigned stations to a table with links for changing station statuses. These links post the entire form in order to prevent accidental loss of data entry.
Edit Incident: Fixed a bug dealing with an incident getting closed and saved while there's still a station assigned to it
Edit Incident: If a colon command is entered in the new notes field, whitespace and newlines are stripped off
Edit Incident: Changed the format of the log message that gets generated from creating or updating an incident
Edit Incident: Reduced screen space consumed by the new notes field
Edit Incident: Added a note that the Cancel button does not undo changes to station statuses or assignments
Log: Fixed how a close time of "none" gets saved in log entries
Station Summary: If a station is In Route to a particular destination, display the destination
Station Summary: The bottom part of the page now displays only checked-out stations
:CL command: Log messages resulting from unassigning stations now correctly associate both the station and the incident
:IR command: New command to set a station In Route
:IS command: Added a variant of this command that takes arguments and sets a station to In Service
:OL command: New command to set a station On Location
Fixed some general problems handling error conditions with colon commands. Original field content was not always getting restored.
Updated various log messages regarding station status changes to be more consistent with each other

February 25, 2008

skylog.php revision 1.9 on live.skylog.net and demo.skylog.net
skylog.css revision 1.5 on live.skylog.net and demo.skylog.net

Dump: Fixed reload problem that made this screen inaccessible
Dump: Fixed indent alignment for log entries
User Messaging: Text of messages sent using this screen was not showing up in the associated log message.
Time stamps embedded in log entry text now get translated per the user's time offset (except for log entries created before this revision)
Incident notes are now stored in the log. Log entries for a given incident now display with the rest of the incident's info.

February 21, 2008

skylog.php revision 1.8 on live.skylog.net and demo.skylog.net

If the user experiences a browser crash or otherwise bails without logging out properly, they can now clean up stale locks the next time they log in. If potentially stale locks are detected, the user is prompted after group selection to delete them.
Edit Incident: The :NI command now properly allows for immediate entry of a new incident.

November 28, 2007

skylog.php revision 1.6.2.13 on demo.skylog.net
skylog.php revision 1.8 on live.skylog.net

Edit Incident: Fixed bug that lead to losing lock on incident if two page loads happened in rapid succession
Group Selection: After the user selects their group, a log messages is added to note that the user has logged in.
User Messaging: Newly created screen w/ status of users and ability to send/receive messages with other users.
User Preferences: Added setting for how many incoming messages get displayed at top of screen
:ACK command added - acknowledges incoming message and removes it from the screen.
:SEND command added - send a message to another user or all currently logged in users
Added redirect immediately after any user actions (posting a form or clicking on a link) to prevent a subsequent page reload from attempting to repeat the user's action.
Auto-refresh mechanism now avoids refreshing while user is actively entering data in fields.
Log Out link now generates a log message to note that the user has logged out.
Incoming messages from other users display at the top of all screens (except when on User Messaging or Edit Incident screens
Sending a message to another user (either from User Messaging screen or using :SEND) generates a log message.

September 26, 2007

skylog.php revision 1.6 on live.skylog.net

Edit Incident: Added :CAN command
Edit Incident: If the station is not changed, don't change its status to Checked In
Edit Incident: Issuing :EI or :VI now places the current incident on hold and then properly loads the newly requested incident.
Edit Incident: When resuming an incident where the lock has expired, the resulting spank message used to show up above the page header. It now lands in the usual callback text area.
Incident Summary: Display stations that are assigned to open incidents.
Whenever an incident is loaded for editing or viewing (for example, by clicking on it in Incident Summary, by issuing :EI or by issuing :VI), Skylog checks to see if the requested incident is on hold. If it's on hold, the held copy is resumed. If not, it gets loaded from the database.
:CO command now checks to see if the station is assigned to an incident and unassigns it

September 1, 2007

skylog.php revision 1.5

Edit Incident: Fixed string vs. numeric comparison bug
Edit Incident: When re-opening a closed incident AND assigning a station at the same time, the warning about the incident being closed will not be displayed.
Incident Summary: Recent Incidents header now shows the user's configured max number of incidents
User Preferences: Focus defaults to hours offset field
User Preferences: Fixed string vs. numeric comparison bugs

August 24, 2007

skylog.php revision 1.4.2.3

This is an experimental version for beta testing of a complex new feature.
User Preferences screen sets an offset between the server's time and the time the user wants displayed. See Tips and Tricks for important caveats.

July 29, 2007

skylog.php revision 1.4

Added User Preferences screen
:PREFS command jumps to the User Preferences Screen
User Preferences screen controls how many Recent Incidents are displayed on the Incident Summary screen

July 16, 2007

skylog.php revision 1.3

Dump screen: Completed initial development for full text dump of all data
First "production" release version!

June 8, 2007

skylog.php revision 1.2.2.66

Administration screen: The circonline.org version of MySQL doesn't support subselects. Changed the group association functionality to use multiple separate queries instead of a subselect.
Log screen: If a given log entry doesn't have an incident associated with it, it will no longer have a View link

June 3, 2007

skylog.php revision 1.2.2.64

Login screen: If an experimental version of Skylog is being used, a banner now appears to notify the user.
On all screens where a link to edit an incident appears: Added a link to view the incident without locking it for editing.
Added new colon command: :VI is used to view an incident read-only.
Edit incident: Fixed bug where new notes would be deleted/dropped if an assignment is changed at the same time.

doc/colon-commands.php revision 1.6

Added documentation for new colon command :VI

May 30, 2007

Changed setting on circonline.org web server to prevent multiple escaping of quotes in user input

May 24, 2007

skylog.php revision 1.2.2.60

Edit incident: Reporting station field no longer creates new stations by default. Tack on a period to get the old behavior of creating a station if it no longer exists.
Edit incident: In the Location field, enter a period all by itself and Skylog will automatically fill in the Reporting station's last known location.
Tips and tricks: Added documentation to go along with the above two changes.
Edit incident: When saving an incident that is closed, unassign all stations from it.
The page headers now display the time at which the page was loaded.
Assigning stations: If assigning to a closed incident, you are warned that the station may be instantly unassigned.
:CL command: Unassign any stations that are assigned to the incident that is being closed.