Version 2.0.21

There are database changes in this version that will require the database to be updated. To perform the database upgrade follow the follow instructions:

Version 2.0.20

There are database changes in this version that will require the database to be updated. To perform the database upgrade follow the follow instructions:

Version 2.0.19

• There is a new config file section named [search] and four new config file opttions named: default_column_active_employees, default_column_production_activities, default_column_setup_activities, default_column_indirect_activities. The new config file options can be used to specify what the default search look-in columns should be on the various screens.

Version 2.0.18

• Bugfix release

Version 2.0.17

• There is a new config file option named "auto_reconnect_attempts" that will control how many times the client will attempt to reconnect to the server if the connection is lost.

Version 2.0.16

• There are new features in the client which will require the server to be upgraded to 2.0.16 if you want to run the 2.0.16 client.
• There is a new config file option named "allow_operation_complete" that will control whether or not the operation complete checkbox displays on the end activity screen.

Version 2.0.15

• Bugfix release

Version 2.0.14

• Bugfix release

Version 2.0.13

• There are new features in the client which will require the server to be upgraded to 2.0.13 if you want to run the 2.0.13 client.

Version 2.0.12

• There is a new config file option named "force_end_indirect" that will force the user to see the end activity screen when ending an indirect activity if set to True.

Version 2.0.11

There are database changes in this version that will require the database to be updated. To perform the database upgrade follow the follow instructions:

Version 2.0.10

* IMPORTANT * Becuase of a bug in the way the client checked the server's version number the clients must be >= 2.0.9 to connect to a 2.0.10 server. If the client version is older than 2.0.9 then it will exit imediately when it is started (possibly ungracefully).

Version 2.0.8

• An addition column in the Active Employee screen will display the elapsed time that an employee has been logged onto their current activity. This feature can be turned on or off with a new config file setting "elapsed_time" which is in the "[gtk]" parameter group.
• A new config file group and parameter has been added to the sndcsd.conf file. It is the max_recent_activities parameter in the [history] group. If the client has the recent activity list enabled this will control the maximum number of recent activities that the server will return to the client. The default is 10.
• There have been speed optimizations made when loading up the available activity list that requires the server to be upgraded to 2.0.8 if you want to use a 2.0.8 client.
• The "resumeStamp" element has been renamed to "startStamp" in the resume events for Indirect, Production, and Setup activities.
• The notes field (if enabled) is now a multi-line TextView instead of a single line TextEntry. The size of the field can set in the config file with two new parameters "width" and "height" which are in a new parameter group "[notes]". The "show_notes" parameter which used to be in the "[gtk]" parameter group has also been moved into the new "[notes]" group and renamed to "enabled".
• There is a new graphical client configuration utility that can be used to create/edit the client's config file. In Linux it can be executed by running the configure_sndcs_client.py script. In Windows it has replaced the command line configuration utility and can be executed by clicking the "Configure SaberNet DCS Client" link in the start menu.

Version 2.0.7

• Important new indexes have been added to the database and are required for speed for some of the new features in DCS. In order to make sure that your database contains all of the necessary indexes there is a file in sndcs/sndcs.mkmodel named Indexes.sql. This file is applied when creating a new database but not necessarily when you are upgrading from a previous version. You can apply these indexes using whatever tools are available for your back end RDBMS. For example, if you are using MySQL you can use the command:

mysql -u <username> -p --force -D <database name> < sndcs/sndcs.mkmodel/Indexes.sql

i.e. mysql -u root -p --force -D sndcs2 < sndcs/sndcs.mkmodel/Indexes.sql
(The --force command will continue when there is an error because some of the indexes may already exist.)

• The 2.0.7 client requires that the server also be at version 2.0.7 due to the new recent activity list functionality.
• In the sndcsd.conf file the "cascade" parameter in the [operation] section has been split into two separate parameters: "cascade_quantity" and "cascade_complete". cascade_quantity will cascade the quantity completed to previous operations and cascade_complete will mark previous operations as complete whan an operation is completed.
• We are happy to announce that version 2.0.7 is the first release to include a Windows (win32) server installer. Previously if you wanted to run the server on a Windows system you had to install everything from source. Please keep in mind that the Windows server installer should be considered alpha software so don't be surprised if there is a bug or two in the installation process. There are currently a couple of limitations on the Windows server installer:

• It only works with MySQL as the database backend
• The database will be named "sndcs2". You cannot change it.
• The DCS Server and DCS Web are currently not Windows services so they will run in a console / command-line window.

Hosted by SourceForge