..hamid..
Registered User
- تاریخ عضویت
- 6 فوریه 2005
- نوشتهها
- 341
- لایکها
- 0
- سن
- 42
Stop watch
Version: 1.1
symbian s60 (Nokia 6600,7610,6630,..)
Size: 97 KB
Date: 18/09/2006
Sent by: admin
Supports up to 5 simultaneous stopwatches each with up to 40 split/lap times and average lap time. Persistent settings for time and split/lap times. Allows stopwatch to continue to run even when exiting Java application. Simple and efficient user interface, no fancy graphics. Embedded "user manual". For more details see: www.tevero.no/espace/stopwatch, especially for comments on issues that may affect accuracy of a Java stopwatch utility. Picture shows use on Nokia E70. Look will vary with device type. Both split/lap times only shown at same time if screen can fit both. Free use, as is.
Features :
*Up to 5 individual stopwatches each with up to 40 cumulative split and lap times.
*Stopwatch up to max 999 hours 59 minutes 59.99 seconds with 1/100 of a second accuracy. You may argue; what is the point with an accuracy of 1/100 of a second when measuring 100s of hours? And my answer is laziness, I didn't bother to strip away those decimals for you with the impact it may have on layout/alignment. Accuracy admittedly also depends on the system timer of the device, which has not been tested on any device. And it depends on system latency when pressing a button. Design considerations have been given to ensure minimum delay from pressing button until stopwatch is started/stopped etc., but you never know what is going on in there. Don't worry too much, it seems to do the job.
*Persistent saving of data for all stopwatch instances (but nothing saved for a stopwatch instance in reset state, which probably is the most common thing).
*Simple key interface with what I believe is convenient use of the keys for fast and accurate use. Based on assumption that most common use is start/stop/reset. Can be used with joystick/soft buttons and/or numeric keypad.
*Stopwatch will "keep" running even if closing the Java application when running. Saves battery if required to run the stopwatch for a long time.
*Designed with low CPU/power usage in mind. That is, update to display (which is the main CPU intensive activity) is only done as required by state of shown stopwatch instance.
Supported devices :
Both MIDP1.0 and MIDP2.0 type devices are supported (by different JAR files). This should cover most Java enabled devices. Minimum screen width is 128 pixels. This is not a commercial application, and it hasn't been tested on all sorts of devices. In fact, it was developed and tested for the Nokia E70 (MIDP2.0 352x416 pixels) and also tested on a SE K300i (MIDP2.0 128x128 pixels) and Nokia 6800 (MIDP1.0 128x128). Your device should probably have a color screen.
Version: 1.1
symbian s60 (Nokia 6600,7610,6630,..)
Size: 97 KB
Date: 18/09/2006
Sent by: admin
Supports up to 5 simultaneous stopwatches each with up to 40 split/lap times and average lap time. Persistent settings for time and split/lap times. Allows stopwatch to continue to run even when exiting Java application. Simple and efficient user interface, no fancy graphics. Embedded "user manual". For more details see: www.tevero.no/espace/stopwatch, especially for comments on issues that may affect accuracy of a Java stopwatch utility. Picture shows use on Nokia E70. Look will vary with device type. Both split/lap times only shown at same time if screen can fit both. Free use, as is.
Features :
*Up to 5 individual stopwatches each with up to 40 cumulative split and lap times.
*Stopwatch up to max 999 hours 59 minutes 59.99 seconds with 1/100 of a second accuracy. You may argue; what is the point with an accuracy of 1/100 of a second when measuring 100s of hours? And my answer is laziness, I didn't bother to strip away those decimals for you with the impact it may have on layout/alignment. Accuracy admittedly also depends on the system timer of the device, which has not been tested on any device. And it depends on system latency when pressing a button. Design considerations have been given to ensure minimum delay from pressing button until stopwatch is started/stopped etc., but you never know what is going on in there. Don't worry too much, it seems to do the job.
*Persistent saving of data for all stopwatch instances (but nothing saved for a stopwatch instance in reset state, which probably is the most common thing).
*Simple key interface with what I believe is convenient use of the keys for fast and accurate use. Based on assumption that most common use is start/stop/reset. Can be used with joystick/soft buttons and/or numeric keypad.
*Stopwatch will "keep" running even if closing the Java application when running. Saves battery if required to run the stopwatch for a long time.
*Designed with low CPU/power usage in mind. That is, update to display (which is the main CPU intensive activity) is only done as required by state of shown stopwatch instance.
Supported devices :
Both MIDP1.0 and MIDP2.0 type devices are supported (by different JAR files). This should cover most Java enabled devices. Minimum screen width is 128 pixels. This is not a commercial application, and it hasn't been tested on all sorts of devices. In fact, it was developed and tested for the Nokia E70 (MIDP2.0 352x416 pixels) and also tested on a SE K300i (MIDP2.0 128x128 pixels) and Nokia 6800 (MIDP1.0 128x128). Your device should probably have a color screen.
