- Pharo-dev - lists.pharo.org

[ANN] Public Pharo Sprint in Lille

by Marcus Denker

Hi, We are often doing Sprints the friday afternoon here in the team. For the following dates we plan to have larger sprints (e.g. with food organised): Friday, Feb 14 Friday, March 7 Friday, April 11 Friday, May 23 Where? Inria Lille, Building B If you happen to be close some other Friday, feel free to join the smaller sprint, too. And people can organise sprints everywhere, so feel free to organise one yourself at your location. The idea of the sprint is to do either boring or complex things that nobody found the energy to do alone. On the last Sprint before Christmas we killed 30 bugs, for example. Marcus

Feb. 4, 2014

[pharo-project/pharo-core]

by GitHub

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

Feb. 4, 2014

[pharo-project/pharo-core] 40149a: 30740

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 40149a5353962a3d1d74c32ca80d50062b860726 https://github.com/pharo-project/pharo-core/commit/40149a5353962a3d1d74c32c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-04 (Tue, 04 Feb 2014) Changed paths: M Compression.package/CRCError.class/README.md R Compression.package/CRCError.class/instance/as yet unclassified/isResumable.st A Compression.package/CRCError.class/instance/testing/isResumable.st M Compression.package/TarArchiveMember.class/README.md M Compression.package/ZLibReadStream.class/README.md M Compression.package/ZipEncoder.class/README.md M Compression.package/ZipWriteStream.class/README.md M CompressionTests.package/ZipArchiveTest.class/README.md M Deprecated30.package/FtpUrl.class/README.md M Deprecated30.package/HttpsUrl.class/README.md M Deprecated30.package/InvalidDirectoryError.class/README.md M Deprecated30.package/MailSender.class/README.md M Files.package/CannotDeleteFileException.class/README.md M Files.package/FileDoesNotExistException.class/README.md M Files.package/FileExistsException.class/README.md M Files.package/FileStreamException.class/README.md M Files.package/FileWriteError.class/README.md M Fuel.package/FLNegative16SmallIntegerCluster.class/README.md M Fuel.package/FLNegative24SmallIntegerCluster.class/README.md M Fuel.package/FLNegative32SmallIntegerCluster.class/README.md M Fuel.package/FLNegative8SmallIntegerCluster.class/README.md M Fuel.package/FLPositive16SmallIntegerCluster.class/README.md M Fuel.package/FLPositive24SmallIntegerCluster.class/README.md M Fuel.package/FLPositive32SmallIntegerCluster.class/README.md M Fuel.package/FLPositive8SmallIntegerCluster.class/README.md M Fuel.package/ManifestFuel.class/README.md M FuelTests.package/FLBasicSerializationTest.class/README.md M FuelTests.package/FLBlockClosureSerializationTest.class/README.md M FuelTests.package/FLClassWithRecursiveSubstitution.class/README.md M FuelTests.package/FLGZippedBasicSerializationTest.class/README.md M FuelTests.package/FLGlobalEnvironmentTest.class/README.md M FuelTests.package/FLGlobalSendMock.class/README.md M FuelTests.package/FLGlobalSendNotPresentMock.class/README.md M FuelTests.package/FLGlobalSendSerializationTest.class/README.md M FuelTests.package/FLHashedCollectionSerializationTest.class/README.md M FuelTests.package/FLHeaderSerializationTest.class/README.md M FuelTests.package/FLHookedSubstitutionTest.class/README.md M FuelTests.package/FLIgnoredVariablesTest.class/README.md M FuelTests.package/FLInMemoryBasicSerializationTest.class/README.md M FuelTests.package/FLIndexStreamTest.class/README.md M FuelTests.package/FLMethodContextSerializationTest.class/README.md M FuelTests.package/FLMigrationTest.class/README.md M FuelTests.package/FLNotSerializableMock.class/README.md M FuelTests.package/FLPair.class/README.md M FuelTests.package/FLPluggableSubstitutionTest.class/README.md M FuelTests.package/FLSerializationTest.class/README.md M FuelTests.package/FLSignatureTest.class/README.md M FuelTests.package/FLSingletonMock.class/README.md M FuelTests.package/FLSingletonMockEnforced.class/README.md M FuelTests.package/FLSingletonTest.class/README.md M FuelTests.package/FLSortedCollectionSerializationTest.class/README.md M FuelTests.package/FLUserGuidesTest.class/README.md M FuelTests.package/FLVersionTest.class/README.md M FuelTests.package/FLWeakClassMock.class/README.md M FuelTests.package/FLWeakObjectsTest.class/README.md M Morphic-Core.package/Morph.class/instance/event handling/mouseUp_.st M Morphic-Core.package/Morph.class/instance/events-processing/handleMouseUp_.st M Morphic-Examples.package/ClassListNodeExample.class/README.md M Morphic-Examples.package/ClassTreeNodeExample.class/README.md M Morphic-Examples.package/PackageAbstractNodeExample.class/README.md M Morphic-Examples.package/PackageClassNodeExample.class/README.md M Morphic-Examples.package/PackageMethodCategoryNodeExample.class/README.md M Morphic-Examples.package/PackageMethodNodeExample.class/README.md M Morphic-Examples.package/PackageNodeExample.class/README.md M Morphic-Examples.package/PersonDataExample.class/README.md M Morphic-Examples.package/SimpleGridNodeExample.class/README.md M Morphic-Examples.package/SimplestPaginatedClassListExample.class/README.md M Morphic-Examples.package/WidgetExamples.class/README.md M NativeBoost-Core.package/NBExternalArray.class/class/private/installAccessors.st M NativeBoost-Core.package/NBExternalStructure.class/class/managing accessors/createAccessorsFor_.st M NativeBoost-Core.package/NBExternalTypeValue.class/class/private/installAccessors.st R Network-Protocols.package/ProtocolClient.class/class/retrieval/retrieveMIMEDocument_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script393.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30740.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M SmartSuggestionsTests.package/SugsContextTest.class/README.md M SmartSuggestionsTests.package/SugsMenuBuilderTest.class/README.md M SmartSuggestionsTests.package/SugsSuggestionCreateAccessorsTest.class/README.md M SmartSuggestionsTests.package/SugsSuggestionDelegateTest.class/README.md M SmartSuggestionsTests.package/SugsSuggestionExtractLocalTest.class/README.md M SmartSuggestionsTests.package/SugsSuggestionPushDownTest.class/README.md M SmartSuggestionsTests.package/SugsSuggestionRemoveArgTest.class/README.md M SmartSuggestionsTests.package/SugsSuggestionSwapMethodTest.class/README.md M SmartSuggestionsTests.package/SugsSuggestionTest.class/README.md Log Message: ----------- 30740 12778 NB generated code user initials https://pharo.fogbugz.com/f/cases/12778 12788 Please review ProtocolClient(class)>>retrieveMIMEDocument: https://pharo.fogbugz.com/f/cases/12788 12781 Class comment missing for package Compression https://pharo.fogbugz.com/f/cases/12781 12787 Class comment missing in package Morphic-Examples https://pharo.fogbugz.com/f/cases/12787 12785 Class comment missing in Smart suggestions package https://pharo.fogbugz.com/f/cases/12785 12784 Class comment missing in File package https://pharo.fogbugz.com/f/cases/12784 12737 Morph sends mouseUp twice to handlers https://pharo.fogbugz.com/f/cases/12737 12782 Class comments missing in Deprecated package https://pharo.fogbugz.com/f/cases/12782 12783 Class comments missing in Fuel package https://pharo.fogbugz.com/f/cases/12783 http://files.pharo.org/image/30/30740.zip

Feb. 4, 2014

[Pharo3] Must fix issue at 36

by Marcus Denker

The list of issues that are tagged âMust fixâ or higher has now 36 entries: https://pharo.fogbugz.com/f/filters/64/3-0-TODO PLEASE -> if an issue is not a show stopper, we should lower the priory -> if there are issues that need to be fixed to be able to release, they should be in this list And please do not put issues in âmust fixâ that you think "would be nice" to have in Pharo3â¦ those should be tagged : âwould be niceâ. The idea of the list is to have a criterium when we can releaseâ¦ one can always do better, so we need to stop at some point. Marcus

Feb. 4, 2014

Re: [Pharo-dev] test failures in downloaded image 30733

by Goubier Thierry

Le 04/02/2014 09:48, Usman Bhatti a Ã©crit : > > > > On Tue, Feb 4, 2014 at 9:29 AM, Goubier Thierry <thierry.goubier(a)cea.fr > <mailto:thierry.goubier@cea.fr>> wrote: > > > > Le 04/02/2014 09:23, Usman Bhatti a Ã©crit : > > > > > Yes, I use that already with Glamour and Roassal, and other morph > widgets that I have. > The harder part for me so far is responding to dialog boxes e.g. > answer > the user questions automatically and once I have that, I'd be > able to > completely test my current set of UIs automatically. > > > What about writing a Shim over the dialog creator with a catalog of > predefined answers that could be picked by each dialog creation? > When calling a dialog, we're usually going through a factory > interface usually. > > > I do not know what is a Shim. From Wikipedia: In computer programming, a shim (from shim) or shiv is a small library that transparently intercepts an API and changes the parameters passed, handles the operation itself, or redirects the operation elsewhere. > Sometimes, we would like to provide our own answers to the dialogue to > see if the tests pass in different configurations (e.g. when we have two > or more checkboxes, to see if we get different results selecting > different boxes). > > Or may be we can start with a simpler solution and then evolve towards a > completely customizable one. My simple approach would be : in normal code, instead of calling UIManager directly as in: UIManager default chooseFrom: aCollection title: aString withCRs. use a shim (self class myUIManager ....). In the test case, setup so that: `self class myUIManager` returns a shim over UIManager capturing the chooseFrom:title: and containing a dictionary with 'title' -> value to choose. You preload the shim with the right answers and the keys for the shim to find to which dialog this refers (it could be ordered: answer for first dialog, answer for second dialog, etc...). The shim, instead of creating the dialog, returns the value it already has (or an error if it hasn't, which will help you fill the needed values !). For stuff not related to dialogs you are using the shim for, you can just do a passthrough (i.e. UIManager default perform: ) which can even be handled automagically via doesNotUnderstand:. As you can see, there isn't much to it. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 4, 2014

Re: [Pharo-dev] test failures in downloaded image 30733

by Usman Bhatti

On Tue, Feb 4, 2014 at 9:29 AM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > > > Le 04/02/2014 09:23, Usman Bhatti a Ã©crit : > > >> >> >> Yes, I use that already with Glamour and Roassal, and other morph >> widgets that I have. >> The harder part for me so far is responding to dialog boxes e.g. answer >> the user questions automatically and once I have that, I'd be able to >> completely test my current set of UIs automatically. >> > > What about writing a Shim over the dialog creator with a catalog of > predefined answers that could be picked by each dialog creation? When > calling a dialog, we're usually going through a factory interface usually. I do not know what is a Shim. Sometimes, we would like to provide our own answers to the dialogue to see if the tests pass in different configurations (e.g. when we have two or more checkboxes, to see if we get different results selecting different boxes). Or may be we can start with a simpler solution and then evolve towards a completely customizable one. > > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > >

Feb. 4, 2014

Re: [Pharo-dev] PharoProjectCatalog for Pharo 3?

by Damien Cassou

On Tue, Feb 4, 2014 at 12:42 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > If you want to integrate, I have attached changes to CatalogBuilder methods > for redirecting to MetaRepoForPharo3. > I don't know the proper way to test it yet I just gave Torsten and you write access. > CatalogBuilder new generateAll ?? that should work. But this will take quite some time. Another solution is to write something like (untested): CatalogBuilder new generateCardFor: ConfigurationOfPillar > but gives me a MessageNotUnderstood: GoferResolvedReference>>load :-( -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 4, 2014

Re: [Pharo-dev] test failures in downloaded image 30733

by Goubier Thierry

Le 04/02/2014 09:23, Usman Bhatti a Ã©crit : > > > > Yes, I use that already with Glamour and Roassal, and other morph > widgets that I have. > The harder part for me so far is responding to dialog boxes e.g. answer > the user questions automatically and once I have that, I'd be able to > completely test my current set of UIs automatically. What about writing a Shim over the dialog creator with a catalog of predefined answers that could be picked by each dialog creation? When calling a dialog, we're usually going through a factory interface usually. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 4, 2014

Re: [Pharo-dev] test failures in downloaded image 30733

by Usman Bhatti

On Tue, Feb 4, 2014 at 9:08 AM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > > > Le 03/02/2014 21:41, Usman Bhatti a Ã©crit : > >> >> >> >> On Sun, Feb 2, 2014 at 2:43 PM, Marcus Denker <marcus.denker(a)inria.fr >> <mailto:marcus.denker@inria.fr>> wrote: >> >> >> On 02 Feb 2014, at 14:31, btc(a)openinworld.com >> <mailto:btc@openinworld.com> wrote: >> >> > For diligence and curiosity leading up to the Pharo3 release, I >> downloaded build image 30733 (with PharoLauncher) >> >> Getting an image green is a lot of little, trivial, hard work... and >> green always means "Green in this context". Just headless vs. >> non-headless >> changes a lot, for example. >> >> Another wonderful thing is that tests are fine when run >> individually, but fail when running all tests. >> >> We need to think about automatic UI testing... >> >> >> It will be awesome to have automatic UI tests. >> > > Well, it can be done as it is now. > > It's fairly easy in Pharo to write tests that open a GUI, test a few > things in it, and close it. There, you can already test automatically that > your gui updates correctly when the model change. > Yes, I use that already with Glamour and Roassal, and other morph widgets that I have. The harder part for me so far is responding to dialog boxes e.g. answer the user questions automatically and once I have that, I'd be able to completely test my current set of UIs automatically. > > It may be a bit harder to trigger events on specific positions, but not > that much difficult. A way to write a test method out of Sean event > recorder would be nice there. > > > Currently, I can go as far as invoking the UI but then to complete the >> fields in another process/thread, I haven't really spent enough time. I >> think that's already discussed on the mailing list but some time I >> should have a look. Automated tests before a release/roll-out will be a >> dream coming true ;-). >> > > Yes. Especially on all the gui parts: drag and drop for example. > > But, technically, we're not very far. It's just that nobody writes tests > that way. > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > >

Feb. 4, 2014

Re: [Pharo-dev] test failures in downloaded image 30733

by Goubier Thierry

Le 03/02/2014 21:41, Usman Bhatti a Ã©crit : > > > > On Sun, Feb 2, 2014 at 2:43 PM, Marcus Denker <marcus.denker(a)inria.fr > <mailto:marcus.denker@inria.fr>> wrote: > > > On 02 Feb 2014, at 14:31, btc(a)openinworld.com > <mailto:btc@openinworld.com> wrote: > > > For diligence and curiosity leading up to the Pharo3 release, I > downloaded build image 30733 (with PharoLauncher) > > Getting an image green is a lot of little, trivial, hard workâ¦ and > green always means âGreen in this contextâ. Just headless vs. > non-headless > changes a lot, for example. > > Another wonderful thing is that tests are fine when run > individually, but fail when running all tests. > > We need to think about automatic UI testingâ¦ > > > It will be awesome to have automatic UI tests. Well, it can be done as it is now. It's fairly easy in Pharo to write tests that open a GUI, test a few things in it, and close it. There, you can already test automatically that your gui updates correctly when the model change. It may be a bit harder to trigger events on specific positions, but not that much difficult. A way to write a test method out of Sean event recorder would be nice there. > Currently, I can go as far as invoking the UI but then to complete the > fields in another process/thread, I haven't really spent enough time. I > think that's already discussed on the mailing list but some time I > should have a look. Automated tests before a release/roll-out will be a > dream coming true ;-). Yes. Especially on all the gui parts: drag and drop for example. But, technically, we're not very far. It's just that nobody writes tests that way. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 4, 2014