| Christian's Vim Page For Programmers | Vim - I love it |
|
DevStopWatch - The Developer's Stop Watch
DevStopWatch is a simple stop watch. The intended use of DevStopWatch is to support software developers when it comes to measure time manually. For this use case the specific requirements are:
No installation is required. Just start DevStopWatch.exe from
any directory. An INI file is expected in the same directory
from which DevStopWatch.exe has been started. The INI file
will be updated if DevStopWatch shuts down (this can be
disabled in the INI file). So the user should have
write permission for this file.
Microsoft .NET Framework 2.0 DevStopWatch has been tested under Windows XP SP3.
To move the DevStopWatch window, left click into the text and move. The visible text must be hit. Several instances of DevStopWatch can be started, but only the first one will get the hot keys. The other instances must be controlled via the menu of the appropriate system tray icon.
A good old classic INI file is used to configure DevStopWatch. The INI file is DevStopWatch.ini. It will be created/updated when exiting DevStopWatch. A commented example is part of the release.
A hot key is defined by a string, e.g. "Alt+Ctrl+S". The syntax is [modifiers]+keyCode.
Because of the same reason why all the other stop watches had been developed: There are plenty of stop watch applications available in the Internet, but I found none which fulfills all my requirements listed above. So DevStopWatch was born. ;-)
DevStopWatch is a C# application which is developed using Visual Studio 2008 Standard edition. Maybe the following C# classes are useful for others:
Some Notes: There are very good reasons why it is recommended to store application and data in different directories with appropriate access permissions. But for small portable utilities like DevStopWatch I prefer to have both files, the exe and the config file, close together. This allows to install and update the utility without installer and to start it from wherever you want (even a memory stick would do it). Another thing I like is the INI file. The syntax of the file is very simple, the user can easily read and edit it on demand. So I did two things by right mind which are not modern: I decided to keep application and config file in the same directory and I decided to use an INI file instead of XML. I'm aware that this is not the best solution for each type of application, but I believe for this one it is.
This software is released under the MIT (X11) license. The license terms are: Copyright (c) 2009 by Christian Habermann. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |