types/selectors/SizeSelector.php
inherited
Classes
Selector that filters files based on their size.
- Author
- Hans Lellelid
- Author
- Bruce Atherton
- Package
- phing.types.selectors
\SizeSelector
Selector that filters files based on their size.
- Parent(s)
- \BaseExtendSelector < \BaseSelector < \DataType < \ProjectComponent
- Author
- Hans Lellelid
- Author
- Bruce Atherton
Constants
Properties
$byteUnits= 'array("K"'
array("K"Details- Type
- n/a
$cmp= '2'
2Details- Type
- n/a
$multiplier= '1'
1Details- Type
- n/a
$size= '-1'
-1Details- Type
- n/a
$sizeComparisons= 'array("less"'
array("less"Details- Type
- n/a
$sizelimit= '-1'
-1Details- Type
- n/a
Methods
circularReference(
)
:
voiddieOnCircularReference(
)
:
voidgetCheckedRef(
)
:
voidgetDescription(
)
:
voidgetError(
)
:
voidgetParameters(
)
:
voidgetProject(
)
:
voidisReference(
)
:
voidisSelected(
\basedir $basedir, \filename $filename, \file $file
)
:
\whetherThe heart of the matter. This is where the selector gets to decide on the inclusion of a file in a particular fileset.
| Name | Type | Description |
|---|---|---|
| $basedir | \basedir | A PhingFile object for the base directory |
| $filename | \filename | The name of the file to check |
| $file | \file | A PhingFile object for this filename |
| Type | Description |
|---|---|
| \whether | the file should be selected or not |
log(
)
:
voidnoChildrenAllowed(
)
:
voidparsingComplete(
)
:
voidsetDescription(
)
:
voidsetError(
)
:
voidsetParameters(
\parameters $parameters
)
:
voidWhen using this as a custom selector, this method will be called.
It translates each parameter into the appropriate setXXX() call.
| Name | Type | Description |
|---|---|---|
| $parameters | \parameters | the complete set of parameters for this selector |
setProject(
)
:
voidsetRefid(
)
:
voidsetUnits(
\$units $units
)
:
voidSets the units to use for the comparison. This is a little complicated because common usage has created standards that play havoc with capitalization rules. Thus, some people will use "K" for indicating 1000's, when the SI standard calls for "k". Others have tried to introduce "K" as a multiple of 1024, but that falls down when you reach "M", since "m" is already defined as 0.001.
<
p> To get around this complexity, a number of standards bodies have proposed the 2^10 standard, and at least one has adopted it. But we are still left with a populace that isn't clear on how capitalization should work.
<
p> We therefore ignore capitalization as much as possible. Completely mixed case is not possible, but all upper and lower forms are accepted for all long and short forms. Since we have no need to work with the 0.001 case, this practice works here.
<
p> This function translates all the long and short forms that a unit prefix can occur in and translates them into a single multiplier.
| Name | Type | Description |
|---|---|---|
| $units | \$units | The units to compare the size to. |
setValue(
\size $size
)
:
voidA size selector needs to know what size to base its selecting on.
This will be further modified by the multiplier to get an actual size limit.
| Name | Type | Description |
|---|---|---|
| $size | \size | the size to select against expressed in units |
setWhen(
\cmp $cmp
)
:
voidThis specifies when the file should be selected, whether it be when the file matches a particular size, when it is smaller, or whether it is larger.
| Name | Type | Description |
|---|---|---|
| $cmp | \cmp | The comparison to perform, an EnumeratedAttribute |
toString(
)
:
voidtooManyAttributes(
)
:
voidvalidate(
)
:
voidverifySettings(
)
:
voidChecks to make sure all settings are kosher. In this case, it means that the size attribute has been set (to a positive value), that the multiplier has a valid setting, and that the size limit is valid. Since the latter is a calculated value, this can only fail due to a programming error.
If a problem is detected, the setError() method is called.