Next | Query returned 34 messages, browsing 21 to 30 | Previous

History of commit frequency

CVS Commit History:


   2004-12-30 14:39:12 by Thomas Klausner | Files touched by this commit (2)
Log message:
Update to 10.14:
This release changes some computations to make the nutrient values for
packaged foods added from food labels more accurate.
   2004-12-26 16:11:22 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Update to 10.13.
New in 10.13:
This release fixes the incorrect "Analyze Meals" screen header that says
"Record Meals". It fixes the function that guesses recipes of packaged \ 
foods,
which worked properly but had a variable and a constant of the same value
reversed so that user modifications to increase the precision would fail.

New in 10.12:
The function that guesses the recipes of packaged foods based on the
nutrition and ingredient statements has been rewritten. A much faster
implementation is achieved by quantizing all the values. This algorithm is a
search through all possible recipes because simultaneous equations do not
work for this problem.

New in 10.11:
This release contains a fix for bad Pumpkin Pie values, specifically, null
"carb/prot/fat" values for foods for which the USDA does not supply this
data.

New in 10.10:
This release fixes a bug in the function that allows foods to be added from
food labels. The carb/protein/fat field was not correct because
calories-per-gram fields were not explicitly set.

New in 10.9:
This release contains a fix for wrong calories-per-gram values when the
program starts because it read a float as an integer from the options file.

New in 10.8:
This release contains many small changes, among them an update of the fatty
acid reference values, a removal of the hard-to-obtain "Alaska Native" \ 
foods
as food suggestions, and a closer approximation when protein or carbs are
expressed as a percentage of calories.

New in 10.7:
This release changes how personal options are saved to disk so that personal
options will never be lost across program upgrades. Changes have also been
made to how the program upgrades itself on dual-boot systems, and levels of
the Omega-3 reference values have been modified.

New in 10.6:
This release fixes minor bugs related to the "Carb/Prot/Fat" field. Values
for alcoholic beverages have been corrected. Also, an error was fixed that
led to different fat values based on whether the user input changes to the
protein and carb "Daily Values" in percentages or grams. If the two
operations led to the same number of grams of protein and carbs, there should
have been no difference in the fat value.

New in 10.5:
This release adjusts the Omega-3 default reference values, for which there are
no U.S.A. Daily Values, so that EPA and DHA will be higher and alpha-linolenic
acid a little lower.

New in 10.4:
This release contains two minor design changes to the new feature of the last
release, which automatically chooses a meal analysis period. Always choosing
integer days, the new version picks the day closest to the target rather than
the day before; and allows no period shorter than five days, instead of four.

New in 10.3: don't know.
   2004-12-03 16:15:13 by Thomas Klausner | Files touched by this commit (409)
Log message:
Rename ALL_TARGET to BUILD_TARGET for consistency with other *_TARGETs.
Suggested by Roland Illig, ok'd by various.
   2004-08-18 13:22:36 by Thomas Klausner | Files touched by this commit (2)
Log message:
Update to 10.2:
This release fixes a computation error in the value for monounsaturated fat
when the user sets a fat level higher than the Daily Value.
   2004-08-15 14:06:34 by Thomas Klausner | Files touched by this commit (4) | Package updated
Log message:
Update to 10.1:
10.1:
This release adds a fix for zero values that display as no data.
10.0:
This release updates the USDA Nutrient Database to version SR17, and allows
current NUT installations to have their existing meal records reinterpreted
with the new database.
9.20:
This release optimizes the new code of the last release, the focus of which
was distinguishing no data from zero in the USDA database.
9.19:
The program now distinguishes between zero values and no data in the USDA
database, and uses this information to produce a new screen that lists foods
high in some nutrient while minimizing some other nutrient.
9.18:
This release contains revisions to the polyunsaturated fatty acid reference
values and how they scale up as fats increase and carbs decrease.
9.17:
This release provides what may be more reasonable or optimal default settings
for fat percentages when the user sets the program for low carb.
9.16:
This release contains bugfixes for a segmentation fault which occurred when
entering a control-D and a monounsaturated fat reference value that was too
high.
9.15:
This release makes serving sizes more consistent among food groups. It adds
functions to change the default serving size, and to sort foods by nutrients
per serving.
9.14:
This release adds support for an optional database subdirectory, allowing the
user to easily maintain multiple databases, for multiple family members, for
instance. It also adds display of non-fiber carbohydrate grams ("net \ 
carbs")
on the main analysis screen.
9.13:
The program now allows commercial foods that have a nutrition label and an
ordered ingredients statement to be added to the food database. An
approximation to a food's recipe is found that best fits the criteria and the
recipe is analyzed to provide information about the additional nutrients not
stated on the nutrition label.
9.12:
[unknown]
   2004-08-14 17:51:37 by Soren Jacobsen | Files touched by this commit (1)
Log message:
Use buildlink3.  Requested by Georg Schwarz in PR pkg/26654.
   2004-03-10 19:37:49 by Thomas Klausner | Files touched by this commit (3)
Log message:
Update to 9.11:
New in 9.11:
Because the program uses the approximation of 4 calories per gram
for carbohydrate and protein to analyze meals according to the
"Daily Value" -- although real food has various values for calories
per gram -- the program now refigures fat percentage values at each
analysis so that when calories, carbs, and protein are each at
exactly 100%, fat will be also.
New in 9.10:
This release fixes a buffer overflow in the food selection function
which caused the program to not find certain foods even though they
existed in the database.
New in 9.9:
A bug has been fixed in which during food selection, the program
lost the value of the food name key. Also, some of the program's
reference values for the essential fatty acids have been modified.
New in 9.8:
The program now defaults to either grams or ounces, depending on
the weight unit the user enters to specify servings. A bug in
handling customary meal names that are too long has been fixed.
New in 9.7:
The program computes essential fatty acid reference values based
on the user's diet. Prior releases aimed toward a particular balance
of Omega-6 and Omega-3. This release allows the user to specify
the balance between Omega-6 and Omega-3 without having to determine
the amount of the individual fatty acids.
New in 9.6:
The program is now capable of understanding food names in simple
English, such as "fried chicken" and "mashed potatoes." This is
accomplished by including the list of abbreviations the USDA uses
and by successively searching for each tokenized term, whatever
the order in the USDA name.
   2004-01-22 08:20:07 by grant beattie | Files touched by this commit (2)
Log message:
replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.
   2003-12-25 15:46:17 by Thomas Klausner | Files touched by this commit (2)
Log message:
Update to 9.5:
9.5:
The last release introduced a bug when adding customary meals to
regular meals. The program now adds the foods without the additional
prompt screen.
9.4:
This release changes the method of searching for foods to a substring
search. The narrowing-down of food categories to a unique food is
the same as in prior releases.
   2003-12-13 11:44:06 by Thomas Klausner | Files touched by this commit (2)
Log message:
Update to 9.3:
This release fixes a bug in the graphs where the "Daily Value" was
such a small percentage of the values graphed that the DV line
indicator exceeded the graph width.

Next | Query returned 34 messages, browsing 21 to 30 | Previous