I'm also in favor to have it as default in the core. It is a so basic thing. I was also searching for this feature a few days ago. On another hand, one could also argue that 12/100 does the job but is less intention revealing.
Another thing that I find is missing in the core is the support for currency (with a nice formatting and round: 2) Le 16 févr. 2015 à 22:55, Sven Van Caekenberghe a écrit : > I like it, it is just one method. > >> On 16 Feb 2015, at 22:41, Sean P. DeNigris <[email protected]> wrote: >> >> Guillermo Polito wrote >>> Sean, but if you need something like that, why wouldn't you load >>> aconcagua? >>> >>> I'm just in the crusade of putting less in the kernel by default ^^. >> >> Good question! The little project I was working on when I implemented that >> method /was/ using Aconcagua! But: >> 1. This is a simple, common conversion which >> a. could make the kernel itself a bit more intention revealing >> Job>>#progress >> ^ min >= max ifTrue: [ 1 ] ifFalse: [ (currentValue - min) / (max - >> min) ] >> could become: >> ^ min >= max ifTrue: [ 100 percent ] ifFalse: [ (currentValue - min) / >> (max >> - min) ] >> b. would've made my life a bit easier on several occasions, but feels much >> too lightweight to load a library for. There doesn't seem to be an entire >> domain behind it. One method gets you the whole thing. >> 2. AFAICT, Aconcagua doesn't really solve this problem. It defines families >> of units and conversions between them, but here there's just one concept as >> mentioned in 1.b. above >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Number-percent-tp4805988p4806047.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >
smime.p7s
Description: S/MIME cryptographic signature
