All Versions
30
Latest Version
Avg Release Cycle
117 days
Latest Release
818 days ago

Changelog History
Page 2

  • v1.7.3

    March 23, 2015
  • v1.7.2 Changes

    March 23, 2015

    โž• Added

    • rubygems config
  • v1.7.1 Changes

    December 21, 2014

    ๐Ÿ›  Bugfix

    • ETA works again, when ProgressBar is initialized with a non zero starting_at.

    Uncategorized

    • Describe the wiki link
    • Inline the cage image in the README
    • THE CAGE
    • Remove superfluous subtitle
    • Remove sections from the README that were moved to the Wiki
    • Add link to wiki
    • Update logo
  • v1.7.0 Changes

    November 04, 2014

    ๐Ÿ”‹ Feature

    • Massive internal refactoring. Now 236% faster!
    • Add Timer#restart
  • v1.6.1 Changes

    October 30, 2014

    Uncategorized

    • Update readme about output option
    • Display warnings when testing

    ๐Ÿ›  Bugfix

    • Remove warnings from uninitialized instance variable
    • Instance variable @started_at not initialized
    • Instance variable @out_of_bounds_time_format not initialized
    • Change private attributes to protected
    • `*' interpreted as argument prefix
    • Prefix assigned but unused variables with underscores
    • Ambiguous first argument
  • v1.6.0 Changes

    September 20, 2014

    ๐Ÿ”‹ Feature

    • Add ability to disable auto-finish
    • Add SCSS lint configuration
    • Update JSHint config with our custom version
    • Add right-justified percentages - Closes #77

    ๐Ÿ›  Bugfix

    • Don't allow title to change for non-TTY output
    • Percentage formatter failed when total was 0 or unknown
  • v1.5.1 Changes

    May 14, 2014

    Uncategorized

    • Make grammar and spelling corrections in the README
    • Add the ability to scale the rate component
    • Add notes to the README about the new format components
    • Add the %R flag to the formatting to show the rate with 2 decimal places of precision
    • Remove unused molecule cruft
    • Add specs to make sure that rate works even if the bar is started in the middle
    • Add base functionality for the rate component
    • Add Slack notification to Travis builds
    • Upgrade rspectacular to v0.21.6
    • Upgrade rspectacular to v0.21.5
    • Upgrade rspectacular to v0.21.4
    • Upgrade rspectacular to v0.21.3
    • Upgrade rspectacular to v0.21.2
    • Add badges to the README
    • Upgrade rspectacular to v0.21.1
    • Lower Timecop version for Ruby 1.8 compatibility
    • Lower rake version to 0.9.6 so that it will be compatible with Ruby 1.8
    • Update rspectacular to 0.21
    • Add CODECLIMATE_REPO_TOKEN as a secure Travis ENV variable
    • Upgrade rspectacular to v0.20
    • Add the Code Climate test reporter gem
    • Add Ruby 2.1 to Travis
    • Convert to RSpec 3

    ๐Ÿ”‹ Feature

    • The running average is always set back to 0 when the bar is reset
  • v1.4.2 Changes

    March 01, 2014
    • Improve estimated timer for short durations
    • Remove useless protection
    • README Update
    • Slight formatting changes on the PACMAN example to make it consistent with the others
    • Pacman-style progressbar
  • v1.4.1 Changes

    January 26, 2014
    • Change from 'STDOUT.puts' to the more appropriate 'Kernel.warn'
    • Add another spec which tests this in a different way
    • Add an acceptance spec to mimic running fuubar with no specs
    • Makes Timer#stop a no-op unless it has first been started.
  • v1.4.0 Changes

    December 28, 2013
    • Displaying the call stack was probably too much
    • Upgrade fuubar
    • Add an error specifically for invalid progress so that, in parent libraries, it can be caught properly
    • Use the splat operator just to be clear
    • Fix an issue with the estimated timers blowing up if the total was nil - Closes #62
    • Changed my mind. Rather than checking if the bar is stopped/started just blow up when the attempt is made to increment/decrement the bar to an invalid value
    • Remove the CannotUpdateStoppedBarError
    • Changes to the total should also be considered a change in progress and should therefore not be allowed for a stopped bar
    • Add a warning that any changes to progress while the bar is stopped, will eventually be an exception
    • Use the helper to divide the seconds. Don't know why I didn't do this before
    • When finishing the bar, we also should stop the timers
    • When checking 'finished?' make sure we check all progressables
    • Always thought it was weird that the 'finished?' check was in the update method
    • Move the 'finished' logic into the progressable
    • Rather than specifying @elapsed_time explicitly, use the with_timers helper
    • Add a method to check to see whether the bar has been started
    • Extract logic for updating progress into a 'update_progress' method
    • Add placeholder for an Error which will be used in v2.0.0
    • Update the copyright in the README to 2014 (we're almost there :)
    • Add 'Zero dependencies' to the README as a beneifit of using ruby-progressbar