|#2||16213||perforce_software||Move files to proper depot path to view files correctly from project page.|
|#1||14756||tjuricek||p15.1 branch of p4ruby.|
Rework P4Ruby unit tests so they they are actually units. Now the
test order is irrelevant as all tests are standalone. Tidied up
the code formatting as well and removed all the tabs from the ruby
sources files. Added a modeline for vim users so consistent
indentation will be used.
Fix progress unit test
Quiet sync surpressed all output, even in tagged mode, between P4D 2012.2 and
2013.3. Updated the unit test to skip these server versions, so we only do
progress test with a quiet sync on 2014.1 (and newer) servers.
Progress indicator for P4Ruby.
There is a new class P4::Progress that is set up to be subclassed by a user.
It has the following interface and P4Ruby expects the following class methods to
be defined by the user (even if it's an empty implementation):
def description(description, units )
def total( total )
def update( position )
def done( fail )
Users need to create a subclass of P4::Progress and assign an instance to P4
to enable the progress indicator:
class MyProgress < P4::Progress
# do something with the value here
# other methods
p4 = P4.new
p4.progress = MyProgress.new
New feature to be documented in the release notes.