October 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] roundTo: strange behavior

by test

oops, make that original number 1.19 in the example. werner

Oct. 31, 2016

Re: [Pharo-dev] roundTo: strange behavior

by test

Hi, just a simple numerical example using nicolas' implementation: 1.199999999999999999 round: 1. "1.2" i'd guess this result is more or less what a beginner would expect with this line. how would he do it with roundTo:? perhaps this way? 1.199999999999999999 roundTo: 0.1. "1.2000000000000002" i'm not so sure that he would immediately see that he'd need to do it this way: (1.199999999999999999 roundTo: (1/10))asFloat. "1.2" werner

Oct. 31, 2016

Re: [Pharo-dev] Mocks are missing in Pharo (from thread OSProcess is missing)

by Denis Kudriashov

2016-10-31 14:23 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com>: > While the bits of a BDD behavioral specification might not be > any different from the average unit test, I've found the mindset they > create > is invaluable to keeping the focus on "what should this object do" instead > of "does it work" (which comes along for free). > I would love to have something more then tests as methods. If tests are documentation then we are managing documentation with only two level of chapters: classes and methods. Not really nice book.

Oct. 31, 2016

Re: [Pharo-dev] Mocks are missing in Pharo (from thread OSProcess is missing)

by Denis Kudriashov

Hi Sean. 2016-10-31 14:23 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com>: > p.s. although I don't have a ton of experience with Mocketry, when I > shopped > around for a mock framework, I remember strongly preferring BabyMock (which > I hacked together with Phexample into BabyPhexample; so you get stacked > tests, "should" expectations, and mocks). Maybe in another thread, Denis > might explain why one might prefer Mocketry? > You can look at features here: http://dionisiydk.blogspot.fr/2016/04/new-version-of-mocketry-30.html. BabyMock could not be treated as modern mock library just because it uses symbols instead of normal message sends. Even C# and Java mocks are based on normal messages. But BabyMock implements really nice visualization of objects interaction which probably was main goal for authors. It could be done for Mocketry but with ready to use tools like Roassal. BabyMock implements all visualization by itself.

Oct. 31, 2016

Re: [Pharo-dev] Mocks are missing in Pharo (from thread OSProcess is missing)

by Sean P. DeNigris

NorbertHartl wrote > I see no reason if there is a small kernel why it cannot load additional > stuff just for testing. +1. Why would /any/ test framework (including SUnit) be included in the kernel?! And a big +1 to adding mocks to the default test framework, in whatever layer that gets loaded. Philosophical discussions about mocks aside, the programming world (full disclosure: including myself) has embraced them, and their absence seems unnecessarily restrictive and isolationist. While the bits of a BDD behavioral specification might not be any different from the average unit test, I've found the mindset they create is invaluable to keeping the focus on "what should this object do" instead of "does it work" (which comes along for free). I'd say we could use any possible help toward that paradigm shift. Some (many? most?) of our kernel tests seem brittle, duplicative, and, worst of all, of little use as documentation. p.s. although I don't have a ton of experience with Mocketry, when I shopped around for a mock framework, I remember strongly preferring BabyMock (which I hacked together with Phexample into BabyPhexample; so you get stacked tests, "should" expectations, and mocks). Maybe in another thread, Denis might explain why one might prefer Mocketry? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Mocks-are-missing-in-Pharo-from-thread-OSProcess-is-m… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 31, 2016

Re: [Pharo-dev] Mocks are missing in Pharo (from thread OSProcess is missing)

by Denis Kudriashov

2016-10-30 11:41 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > @Denis: Is this reasonable for you? It is better than nothing :).

Oct. 31, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60272 Home: https://github.com/pharo-project/pharo-core

Oct. 31, 2016

[pharo-project/pharo-core] 4536dc: 60272

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 4536dc3e395029e3048320ccb034c2e201acd22d https://github.com/pharo-project/pharo-core/commit/4536dc3e395029e3048320cc… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-31 (Mon, 31 Oct 2016) Changed paths: M ConfigurationOfTxText.package/ConfigurationOfTxText.class/instance/symbolic versions/stable_.st A ConfigurationOfTxText.package/ConfigurationOfTxText.class/instance/versions/version213_.st M Manifest-Tests.package/SmalllintManifestCheckerTest.class/instance/running/setUp.st M Manifest-Tests.package/SmalllintManifestCheckerTest.class/instance/tests/testCriticsOf.st M Manifest-Tests.package/SmalllintManifestCheckerTest.class/instance/tests/testIsFalsePositive.st M Manifest-Tests.package/SmalllintManifestCheckerTest.class/instance/tests/testIsToDo.st M Manifest-Tests.package/SmalllintManifestCheckerTest.class/instance/tests/testToDoOf.st M Nautilus.package/MethodIsExampleAction.class/instance/order/isActionHandled.st M Rubric.package/RubScrolledTextExtra.class/instance/accessing/paragraphProvider.st R Rubric.package/RubScrolledTextMorph.class/instance/testing/isParagraphProvider.st R Rubric.package/extension/Object/instance/isParagraphProvider.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60271.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60272.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60271.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60272.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot-Tests.package/ClassVariableTest.class/instance/tests - properties/testIsReadInMethod.st A Slot-Tests.package/ClassVariableTest.class/instance/tests - properties/testIsWrittenInMethod.st A Slot-Tests.package/ClassVariableTest.class/instance/tests - properties/testNotReadInMethod.st A Slot-Tests.package/ClassVariableTest.class/instance/tests - properties/testNotWrittenInMethodWhenItIsOnlyRead.st A Slot-Tests.package/GlobalVariableTest.class/instance/tests - properties/testIsReadInMethod.st A Slot-Tests.package/GlobalVariableTest.class/instance/tests - properties/testNotWrittenInMethod.st A Slot-Tests.package/SlotTest.class/instance/testing - properties/testIsReadInMethod.st A Slot-Tests.package/SlotTest.class/instance/testing - properties/testIsWrittenInMethod.st A Slot-Tests.package/SlotTest.class/instance/testing - properties/testNotReadInMethod.st A Slot-Tests.package/SlotTest.class/instance/testing - properties/testNotWrittenInMethodWhenItIsOnlyRead.st R Slot.package/IndexedSlot.class/instance/meta-object-protocol/isVirtual.st A Slot.package/IndexedSlot.class/instance/testing/isVirtual.st A Slot.package/InstanceVariableSlot.class/instance/testing/isReadIn_.st A Slot.package/InstanceVariableSlot.class/instance/testing/isWrittenIn_.st A Slot.package/LiteralVariable.class/instance/testing/isReadIn_.st A Slot.package/LiteralVariable.class/instance/testing/isWrittenIn_.st A Slot.package/Slot.class/instance/testing/isReadIn_.st A Slot.package/Slot.class/instance/testing/isWrittenIn_.st R TxText-AthensTests.package/TxAthensRenderingTest.class/README.md R TxText-AthensTests.package/TxAthensRenderingTest.class/class/as yet unclassified/newText.st R TxText-AthensTests.package/TxAthensRenderingTest.class/class/as yet unclassified/test.st R TxText-AthensTests.package/TxAthensRenderingTest.class/definition.st R TxText-AthensTests.package/TxTextPositionToViewCoordinatesTest.class/README.md R TxText-AthensTests.package/TxTextPositionToViewCoordinatesTest.class/definition.st Log Message: ----------- 60272 19255 Update TxText https://pharo.fogbugz.com/f/cases/19255 19258 Remove isParagraphProvider https://pharo.fogbugz.com/f/cases/19258 19084 SmalllintManifestCheckerTest: failing tests https://pharo.fogbugz.com/f/cases/19084 19253 Methods to check is variable, global or slot is read or modified in given CompiledCode https://pharo.fogbugz.com/f/cases/19253 19261 Enable <example> methods to be executed https://pharo.fogbugz.com/f/cases/19261 http://files.pharo.org/image/60/60272.zip

Oct. 31, 2016

Re: [Pharo-dev] Epicea user experience report

by Martin Dias

Hello Ben, About discussion points in 2 (a, b and c): I agree with your arguments... somebody that just moved from Pharo 5 to 6 and crashed an image will look for a "Recover lost changes" in the menu and can have a problem to discover it the replacement in a World->Tools->Epicea->... entry. Then, as a first step we could flatten the 2 menu entries and then at least anybody will easily find an entry related to changes in World->Tools. Second, we could try to merge both Epicea GUIs into one (suggestions are welcome). I still have to read more in detail the remaining of your report to answer. Anyway, thanks a lot for it. Cheers, Martin On Sat, Oct 29, 2016 at 5:22 AM, Ben Coman <btc(a)openinworld.com> wrote: > 1. Created fresh Pharo image (build 60269) > > > 2. Opened World > Tools > Epicea > All changes > > Points for discussion... > > a. How many submenu items are expected for Epicea? Can we push the > current ones up so the Tools menu remains a flat menu. > > b. Do we need the two current menu items? "Current session" is > encompassed by "All changes"? What expectations do people have of how > often they'll use the former rather than the latter? > > c. When people move from Pharo 5 to Pharo 6 and in a panic want to > "recover changes" for a crashed image, they'll be looking for that > familiar feature name, not a new app name. Could the app name be left > out or placed in brackets "Changes (Epicea)". > > btw, the interface looks really slick! nice work. > > > 3. Opened World > System Browser. > > 4. Added package AAA > All Changes window - no dynamic change. > On <refresh>, still no change, i.e. no sessions > #New All Changes window - not visible, no sessions. > > 5. Added class AA. > All Changes window - no dynamic change. > On <refresh>, shows new session with AAA & AA. > > 5. Added method... > AA>a > ^'something' > Prompted for author, entered 'BenComan' > All Changes window with session selected - dynamic update showing AA>>a. > > 6. Added package BBB. > All Changes window - no dynamic update. > On <refresh>, BBB still not visible in session. > > 7. Added class A to package AAA. > All Changes window - dynamic update showing A. > On <refresh>, BBB still not visible in session. > > 8. Added class BB to package BBB. > All Changes window - dynamic update showing BBB & BB. > > a. Package creation event seems not handled properly, being only > pushed through when a class is created in it. > > b. Since there is a dynamic update for class and method > modifications, could the session creation also dynamically update it > UI. > > ----------- > 9. Killed the vm from command line > $ ps -ef | grep pharo > $ kill 29349 > Restarted Pharo image > > 10. World > Tools > Epica > All changes. > Authorship is inconsistent: > * AAA and AA have blank author > * AA>>a, A, BBB, B have author 'BenComan'. > > a. I understand this follows on from Author not being requested until > the first method was defined. Did the old changes track the author of > packages and classes at all? > > b. Since Epicea can track package and class authors, can we trigger > the author prompt earlier for them? > > 11. Selected all previous changes AAA, AA, AA>>a, A, BBB, BB > and did <Apply Changes>. > Prompted for author. Entered 'DrWho' > Existing All Changes window - no change > New All Changes window - shows new session with all six changes. > Authorship is a little inconsistent: > * AAA and AA have author 'Unknown'. > * AA>>a, A, BBB, B have blank author. > > 12. Killed the vm from command line > $ ps -ef | grep pharo > $ kill 30696 > Restarted Pharo image > > 13. World > Tools > Epica > All changes. > Authorship is a little inconsistent: > First session > * AAA and AA have blank author > * AA>>a, A, BBB, B have author 'BenComan'. > Second session > * AAA and AA have blank author > * AA>>a, A, BBB, B have author 'DrWho'. > > a. Epicea changes are reapplied as the current author. This seems a > semantic change from Pharo 5 where changes were reapplied as their > original author. Is this accidental or by design? Can we have some > community discussion on this point (I don't remember seeing any)? > > cheers -ben > > P.S. I'll wait to see what arises out of discussion before creating any > issues. > >

Oct. 31, 2016

Re: [Pharo-dev] roundTo: strange behavior

by test

or perhaps it worked now, i think i uploaded SLICE-Issue-15471-Cant-round-Float-fmax-to-2-decimal-places-WernerKassens.1 <http://www.smalltalkhub.com/#%21/%7EPharo/Pharo60Inbox/versions/SLICE-Issue…> werner

Oct. 30, 2016