After almost 3 years with no release a new version of phpRunMan is out:
- A sweedish translation has been added
- Support a configurable DB table prefix to adapt to mutualized hosting environment with several applications using the same DB
- Several bug fixes
I'm pleased to release a new phpRunMan version with following important changes:
Enhancements:
- added in the run entry page a possibility to repeat more than one previous segments (very very useful for interval training entry).
- redesigned the calculator page to make it more intuitive.
- added a new type of year graph on the main page: the X axis represents days (like the usual one) but the Y axis shows hours of the day so you can see the time of your run and its length, instead of the distance on the default graph.... read more
This release contains 2 small changes:
Added "isActive" flag to the segments to mark the unused segments. These segments can still be used but for quicker input the combo boxes show first all active, then all inactive segments.
The size of the idSegment fields increased to 64 characters.
This patch corrects the bug in end date management: the last day in the period (ex: 31/12) was never taken into account.
Some protections against zero division have been added in index and detail_run scripts.
After almost 3 years of [not so active] development I'm proud to present the more or less stable and finalized version of PHP Running Management: 1.0
In particular this version adds some more new features:
Added management of equipment (shoes, watch, or any other kind of gear you use while running). You can
attach to every run one equipment of every kind, then you can see the total time/distance spent with
your gear, which can be a good indicator for the correct moment for changing your shoes for example.... read more
Big change in the database: idRun is [finally!] numeric and calculated automatically when you insert
a new run so you don't have to enter it manually any more.
Small change in the database: the run description field's size has been increased.
It is now possible to choose if the intermediate times are lap times (like before) or split times.
A german translation has been kindly provided by Marcus Schopen (marcus@localguru.de).
The spanish translation has been kindly updated by Josep M. Torne (author of the original one).... read more
This version brings mainly technical changes such as encrypted
passwords in the database, theme support, JSCalendar dependency, and
database structure changes. The application supports different run
types. Presentation has also been enhanced, for example user can reduce the amount
of information shown on the screen for more readability.
The changes in this release are as follows:
- The ability to edit runs or segments that already exist was added.
- The summary on the bottom of the run list now displays statistics by run type.
- Some basic documentation (install and quick start) was started
Added support for images describing different run segments (like photos or maps).
Added translation to Spanish (thanks to Josep M. Torne)
Added a basic javascript calculator to convert "on the fly" between speed, time and distance.
Improved the code quality ;-)
Bug fix: detail view config was applying changes to ALL users.
Small changes:
- Run list configuration page added.
- User list page added.
This release brings the project from a not very stable mono-user thing to a classy and functionality rich project, useable even by computer newbies who do not want to manage their data using SQL.
In particular this release included:
- More user-friendly pages for editing the data.
- New view (aggregated by month) was added.
- Many calculation and report presentation parameters became customizable.
- The design was improved a lot by using stylesheets.
This version of the project comes with first data entry pages (more to come soon) and user management (a run now belongs to a user so several people can enter their running events into the same database).
All scripts are now fully internationalized (french and english translations exist).
Some minor calculation bugs were also corrected.
This first released version contains only the visualization scripts, so all the data entry must be done manually using SQL. The entry forms are currently in development and should be available in upcoming weeks.