Some of my thoughts on this

• I think it could take third parameter $iec like

  When $iec is true this would produce KiB instead of KB, MiB instead of MB and so on.
  These are IEC standard binary prefixes that were introduced to prevent confusion with SI prefixes.
  SI states that kilo is 1000 and mega is 1000000 and these are also used in computer industry for hard disk capacity on customer boxes whilst Windows uses it in differnt meaning. Certainly there is a confusion. I think including binary prefixes an an option would be good addition as they are widespread in some communities and even some companies embraced it.

For further information please see http://en.wikipedia.org/wiki/Binary_prefix#IEC_standard_prefixes.

• I think that it would be also useful to include a possibility to pass string path like fileSize("/home/user/file") on Unices and fileSize("C:\\x\\y
  z") on Windows boxes or even Zend_Uri instances beginning with file:// to this and make this automatically read apropriate info from filesystem and display in user friendly manner

This is a much needed addition IMO.

It'd be useful to be able to specify which unit that should be used. This would make possible, for example, displaying a list of files with all sizes in MB even if some files are >1GB or <1MB for visual consistency.

I also noticed you do divide stuff inside your helper. I think you could reuse Zend_Measure_Binary as it already supports both SI and IEC.

Marthin, Zend_Measure_Binary has corresponding bi IEC suffixes
eg MEGABYTE -> MEBIBYTE
and looking at code now I would say it uses base 10 SI now not IEC
well actually it would be useful to have three state ('traditional', 'si', 'iec')
and have $norm parameter instead of $iec taking one of these strings.

traditional [KILOBYTE...] would mean base 2 and KB (^10), MB (^20), GB (^30)| si [KILOBYTE_SI...] meaning base 10 and KB (^3) MB | iec [KIBIBYTE...] meaning base 2 KiB (^10) MiB (^20) and GiB (^30)

and also I would like to see is_string($fileSize) -> stat FS and get info out of there

Looks nice, but what about possibility of passing a string as first parameter that would be interpreted as file path to read file size from file system?

This could be sth like

Within your code you use Zend_Measure_Binary.
Nice to see that my component is reused
But you miss some things:

1.) When you use a other component you must also write this within your proposal, section 4 dependencies.

2.) Zend_Measure_Binary allows also to use localized input. Which means it would recognise "1,000.00" in german as "1 000,00" in french or "1.000,00" in english. You should also support this possibility when using Zend_Measure. Therefor you must integrate a locale (getLocale/setLocale) or/and use a generalised Zend_Locale instance from registry when available. This way all components which are localizable use the same locale.

3.) Zend_Measure_Binary COULD convert from/to for you. You stated that this component will not do this within your initial description. The possibility is available through Zend_Measure_Binary.

Greetings
Thomas

I have refactored it not to use any Locale component except Zend_Measure_Binary, which is essentially important

Great!

And is there a way to automatically determine the iec or si, based on Zend_Locale.
Where can I learn this information?
Could it be a part of this component?

Why the name is fileSize if it doesn't get the size of a file.
This component only format binary sizes.

I think it would better to rename this component to Zend_View_Helper_FormatBinary or Zend_View_Helper_FormatBytes

Archived.