- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Autonomous Shark-Monitoring Drone

by Serge Stinckwich

On Wed, Oct 7, 2015 at 5:54 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Dear Friends and Colleagues, Hi Eliot, > as you may know, Sharks, as apex predators, are vital to maintaining > healthy marine ecosystems, and at the same time, their populations are > plummeting due to human actions. It is estimated for example that the > population of pelagic oceanic white tip sharks is reducing by 17% per year > [1] and I've heard (can't find a reference) that populations in the eastern > indian/western pacific are at 1% of normal levels. Such reductions in > populations create "trophic cascades" that produce wide-ranging changes in > populations of different species all the way down the food chain [2]. And > the marine ecosystem is a key source of human nutrition; it comprises > between 13% and 17% of global human protein intake [3]. Recently, I talk with some people from my research institute who are working on Shark behavior modeling in the CHARC program : http://www.la-reunion.ird.fr/le-programme-charc Sorry this is in French only They use acoustic marks on sharks in order to locate them thanks to a surveillance network. The idea is not only to manage the risks regarding sharks but also to use them to have information about ocean's environment parameters. I start to discuss a little bit with them in order to model sharks behavior. > As you may also know, there is currently a shark attack crisis in New > South Wales [4]. While most people in the region oppose killing sharks in > response to the crisis, existing solutions, netting and culling reduce those > same threatened populations of sharks upon which the sustainability of > marine food supply d ecosystems depend [5], and are arguably ineffective > [6]. Apparently the most successful approach at avoiding attacks is the use > of human spotters, as used in Cape Town, where people in tall towers scan > the sea close to shore [6]. > > But please watch this Youtube video [7] from Pismo Beach, California. The > shark is spotted at about 1:20 into the video. This drone, a phantom 3, is > sending live video back to the operators, who are using remote control. > What we can see from this video is that the point of view of drones is far > superior to that of spotters. > > My first thought is that autonomous drones could provide a cheap and > scalable solution to patrolling beaches to prevent shark attacks. I expect > that processors like the Pi 2 have easily enough processing power to both > plan and execute search patterns along beaches, and perform the image > recognition necessary to reliably detect potentially dangerous sharks. A > drone might also be able autonomously to visit surfers and swimmers near to > the shark and warn them, either by some signal such as flashing red LEDs or > an audible message (language issues notwithstanding). The drone would have > to be able to identify swimmers and surfers in the water (not easy; sharks > confuse seals and surfers all the time), but computing an optimal route to > visit suspected swimmers should be relatively easy :-). > > I imagine that sooner or later it will be possible to construct cheap > rugged solar powered docking/charging shelters that drones could depart from > and return to, to charge and shelter from the elements after patrols. > Satellite communications could provide status reports for maintenance. This is a really interesting project. My lab is also interested by using drones for environmental surveillance. I can talk with my colleagues working on sharks if this is something that they envision for the future. Another idea is to use marine drones. Regards -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Oct. 15, 2015

Re: [Pharo-dev] Storing System Settings using STON

by stepharo

Cool! Could you send an example of the file contents? Stef Le 12/10/15 21:45, Juraj Kubelka a Ã©crit : > Hi, > > we have a slice that introduce new storage solution for System > Settings. See: > https://pharo.fogbugz.com/f/cases/16681/Storing-System-Settings-using-STON > > > You can load it using: > > Gofer it > smalltalkhubUser: 'Pharo' project: 'Pharo50Inbox'; > package: 'SLICE-Issue-16681-Storing-System-Settings-using-STON'; > load. > > When you open the Setting Browser, you can see that every setting has > new items in context menu: > > > Thanks for reviewing it. > Cheers, > Juraj

Oct. 15, 2015

Re: [Pharo-dev] Random forest in Pharo

by stepharo

We do not want to be bound to install and maintain connection with fifteen different libs. Stef Le 14/10/15 18:01, philippe.back(a)highoctane.be a Ã©crit : > > Not sure you would get enough performance on Pharo per se. Xe may be > better off leveraging a multicore enabled external lib. Like caret and > doMC on R. > > Le 14 oct. 2015 17:49, "Serge Stinckwich" <serge.stinckwich(a)gmail.com > <mailto:serge.stinckwich@gmail.com>> a Ã©crit : > > I don't think so. > > I followup your message on SciSmalltalk mailing-list. > This is something that might interested us ;-) > > > > On Wed, Oct 14, 2015 at 4:54 PM, Damien Cassou > <damien.cassou(a)inria.fr <mailto:damien.cassou@inria.fr>> wrote: > > Hi, > > > > did anyone implement a Random Forest algorithm in Pharo? > > > > https://en.wikipedia.org/wiki/Random_forest > > > > -- > > Damien Cassou > > http://damiencassou.seasidehosting.st > > > > "Success is the ability to go from one failure to another without > > losing enthusiasm." --Winston Churchill > > > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

Oct. 15, 2015

Re: [Pharo-dev] GTools merging configurations

by stepharo

I can imagine that well. Up to you but I think that having modular parts is nice too. What we should is a way to automatically update configurations. Stef Le 14/10/15 22:20, Andrei Chis a Ã©crit : > Hi, > > For the GTInspector, GTPlayground and GTSpotter we now have distinct > configurations. > However, this complicates the integration process with Pharo as a lot > of configurations need to be updated. > So we'd like to merge them in ConfigurationOfGToolkitCore. > > What do you think? > This will simplify a lot the integration process. > > Cheers, > Andrei

Oct. 15, 2015

[pharo-project/pharo-core]

by GitHub

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

Oct. 15, 2015

[pharo-project/pharo-core] 4b94be: 50385

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 4b94be1f472909b6628f145ea97f8ff0148efe3f https://github.com/pharo-project/pharo-core/commit/4b94be1f472909b6628f145e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-10-15 (Thu, 15 Oct 2015) Changed paths: M Nautilus.package/AbstractNautilusUI.class/instance/accessing/model_.st M Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/registerToAnnouncements.st R Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/registerToMCAnnouncements.st M Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/registerToSystemAnnouncements.st M Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/registerToTestAnnouncements.st A Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/unregisterToAnnouncements.st A Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/unregisterToGroupAnnouncements.st A Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/unregisterToSystemAnnouncements.st A Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/unregisterToTestAnnouncements.st M Nautilus.package/AbstractNautilusUI.class/instance/displaying/open.st M OpalTools.package/GTBytecodeBrowser.class/instance/building/sourceIn_.st M OpalTools.package/GTIRBrowser.class/instance/building/sourceIn_.st M OpalTools.package/GTOpalScopeBrowser.class/instance/building/sourceIn_.st M OpalTools.package/extension/IRInstruction/instance/gtInspectorSourceCodeIn_.st M OpalTools.package/extension/IRSequence/instance/gtInspectorSourceCodeIn_.st M OpalTools.package/extension/OCAbstractScope/instance/gtInspectorSourceCodeIn_.st M OpalTools.package/extension/OCClassScope/instance/gtInspectorSourceCodeIn_.st M OpalTools.package/extension/OCInstanceScope/instance/gtInspectorSourceCodeIn_.st M OpalTools.package/extension/SymbolicBytecode/instance/gtInspectorSourceCodeIn_.st A Refactoring-Critics.package/RBAddRemoveDependentsRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBAddRemoveDependentsRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBAddRemoveDependentsRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBAssignmentOnBlockArgumentRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBAssignmentOnBlockArgumentRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBBadMessageRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBBadMessageRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBBadMessageRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBClassInstVarNotInitializedRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBClassNameInSelectorRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBClassNameInSelectorRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBClassNameInSelectorRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBClassNotReferencedRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBClassNotReferencedRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBClassNotReferencedRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBClassVariableCapitalizationRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBClassVariableCapitalizationRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBCollectionCopyEmptyRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBCollectionCopyEmptyRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBCollectionCopyEmptyRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBCompositeLintRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBDefinesEqualNotHashRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBDefinesEqualNotHashRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBDefinesEqualNotHashRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBEquivalentSuperclassMethodsRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBEquivalentSuperclassMethodsRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBEquivalentSuperclassMethodsRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBExcessiveArgumentsRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBExcessiveArgumentsRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBExcessiveArgumentsRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBExcessiveInheritanceRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBExcessiveInheritanceRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBExcessiveInheritanceRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBExcessiveMethodsRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBExcessiveMethodsRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBExcessiveMethodsRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBExcessiveVariablesRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBExcessiveVariablesRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBExcessiveVariablesRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBExplicitRequirementMethodsRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBExplicitRequirementMethodsRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBExplicitRequirementMethodsRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBImplementedNotSentRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBImplementedNotSentRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBImplementedNotSentRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBInconsistentMethodClassificationRule.class/class/testing/checksMethod.st R Refactoring-Critics.package/RBInconsistentMethodClassificationRule.class/instance/accessing/resultClass.st A Refactoring-Critics.package/RBInconsistentMethodClassificationRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBInconsistentMethodClassificationRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBInstVarInSubclassesRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBInstVarInSubclassesRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBInstanceVariableCapitalizationRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBInstanceVariableCapitalizationRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBJustSendsSuperRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBJustSendsSuperRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBJustSendsSuperRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBLintRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBLintRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBLintRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBLiteralArrayContainsCommaRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBLiteralArrayContainsCommaRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBLiteralArrayContainsCommaRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBLiteralArrayContainsSuspiciousTrueFalseOrNilRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBLiteralArrayContainsSuspiciousTrueFalseOrNilRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBLiteralArrayContainsSuspiciousTrueFalseOrNilRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBLocalMethodsOfAClassNotInItsTraitComposition.class/class/testing/checksClass.st A Refactoring-Critics.package/RBLocalMethodsOfAClassNotInItsTraitComposition.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBLongMethodsRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBLongMethodsRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBLongMethodsRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBMethodHasNoTimeStampRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBMethodHasNoTimeStampRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBMethodHasNoTimeStampRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBMethodSourceContainsLinefeedsRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBMethodSourceContainsLinefeedsRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBMethodSourceContainsLinefeedsRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBMissingSubclassResponsibilityRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBMissingSubclassResponsibilityRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBMissingSuperSendsRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBMissingSuperSendsRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBMissingSuperSendsRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBNoClassCommentRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBNoClassCommentRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBNoClassCommentRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBOnlyReadOrWrittenVariableRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBOnlyReadOrWrittenVariableRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBOverridesSpecialMessageRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBOverridesSpecialMessageRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBParseTreeLintRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBParseTreeLintRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBParseTreeLintRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBRefersToClassRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBRefersToClassRule.class/instance/running/basicCheck_.st R Refactoring-Critics.package/RBRefersToClassRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBRefersToClassRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBReturnsBooleanAndOtherRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBReturnsBooleanAndOtherRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBReturnsBooleanAndOtherRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBSendsDifferentSuperRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBSendsDifferentSuperRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBSendsMethodDictRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBSendsMethodDictRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBSendsMethodDictRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBSentNotImplementedRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBSentNotImplementedRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBSubclassResponsibilityNotDefinedRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBSubclassResponsibilityNotDefinedRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBSubclassResponsibilityNotDefinedRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBSuperSendsNewRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBSuperSendsNewRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBSuperSendsNewRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBTempVarOverridesInstVarRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBTempVarOverridesInstVarRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBTempVarOverridesInstVarRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBTemporaryVariableCapitalizationRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBTemporaryVariableCapitalizationRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBTempsReadBeforeWrittenRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBTempsReadBeforeWrittenRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBTransformationRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBTransformationRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBTransformationRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBUnaryAccessingMethodWithoutReturnRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBUnaryAccessingMethodWithoutReturnRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBUnaryAccessingMethodWithoutReturnRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBUnclassifiedMethodsRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBUnclassifiedMethodsRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBUnclassifiedMethodsRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBUncommonMessageSendRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBUncommonMessageSendRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBUndeclaredReferenceRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBUndeclaredReferenceRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBUnpackagedCodeRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBUnpackagedCodeRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBUnpackagedCodeRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBUnpackagedCodeRule.class/instance/running/checkClass_.st M Refactoring-Critics.package/RBUnpackagedCodeRule.class/instance/running/checkMethod_.st R Refactoring-Critics.package/RBUnpackagedCodeRule.class/instance/running/isUnpackaged_.st A Refactoring-Critics.package/RBUnreferencedVariablesRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBUnreferencedVariablesRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBUsesTrueRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBUsesTrueRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBUsesTrueRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBUtilityMethodsRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBUtilityMethodsRule.class/instance/running/basicCheck_.st M Refactoring-Critics.package/RBUtilityMethodsRule.class/instance/running/checkMethod_.st A Refactoring-Critics.package/RBVariableAssignedLiteralRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBVariableAssignedLiteralRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBVariableNotDefinedRule.class/class/testing/checksMethod.st A Refactoring-Critics.package/RBVariableNotDefinedRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBVariableReferencedOnceRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBVariableReferencedOnceRule.class/instance/running/basicCheck_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50384.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50385.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50384.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50385.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50385 16770 Create a basic version of checking methods in LintRules https://pharo.fogbugz.com/f/cases/16770 16785 Replace the usages of #smalltalkCode in OpalTools https://pharo.fogbugz.com/f/cases/16785 16525 Nautilus leaking SystemAnnouncements https://pharo.fogbugz.com/f/cases/16525 http://files.pharo.org/image/50/50385.zip

Oct. 15, 2015

Re: [Pharo-dev] tests should be green

by Marcus Denker

Yes, -> there is a bug somewhere that flattens traits in some cases -> we need to write a script to delete all the wrong methods. > On 14 Oct 2015, at 17:16, Nicolai Hess <nicolaihess(a)web.de> wrote: > > Please, someone can look at the Collections-Tests > The ReleaseTest complains about > > testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits > (These are all Test-subclasses that use traits, but all(!) trait method are > compiled in the class instead, this happened after someone moved the Test > packages (for bootstrap?) > > OrderedCollectionTest > FloatArrayTest > ArrayTest > DateTest > HeapTest > MorphicTextAdapter > LinkedListTest > DatePrintFormatTester > StackTest > CheckboxButtonMorph > IntervalTest > DateAndTimeTest > SimpleButtonMorph > MethodDictionaryTest > SetTest > DictionaryTest > BagTest > SymbolTest > StringTest > CollectionRootTest > SortedCollectionTest >

Oct. 15, 2015

Re: [Pharo-dev] TestPGConnection>>testNotify2 fails

by Levente Uzonyi

Notices and notifications are entirely different things in Postgresql, so I guess something got mixed up here. Levente On Wed, 14 Oct 2015, Esteban A. Maringolo wrote: > Problem Â¿solved? > > I ran the test against a PostgreSQL 9.2 and the test passed. > > However the test passes... but it is failing silently, because it > should raise a NoticeResponse and it's throwing a PGErrorResponse > instead. > > It seems like this has been buried for years, and because nobody ever > complained about it I guess nobody uses it. > > Regards! > > Esteban A. Maringolo > > > 2015-10-14 14:20 GMT-03:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: >> I have a failing test in my computer when running the test mentioned >> in the subject, I get the following error: "PGConnection has a >> defective state machine" >> >> Stack: >> PGConnection(Object)>>error: >> PGConnection(PGActiveObject)>>stCantHappen: >> PGConnection>>stCantHappen: >> PGConnection(PGActiveObject)>>processEvent: >> PGConnection(PGActiveObject)>>generateEvent:to: >> PGConnection(PGActiveObject)>>saProcessEventsUntil: >> PGConnection>>copy:withStream: >> TestPGConnection>>testNotify2 >> >> I tested in my computer with Pharo4, Pharo3 and Pharo2, and I get the >> same error in all the images with the latest version of it, and also >> with the oldest I could load (in Pharo 2, Name: PostgresV2-Maiano.24). >> >> My PostgreSQL server version is 9.3.7. >> >> Does it fail for you too? >> >> Regards! >> >> Esteban. > >

Oct. 14, 2015

GTools merging configurations

by Andrei Chis

Hi, For the GTInspector, GTPlayground and GTSpotter we now have distinct configurations. However, this complicates the integration process with Pharo as a lot of configurations need to be updated. So we'd like to merge them in ConfigurationOfGToolkitCore. What do you think? This will simplify a lot the integration process. Cheers, Andrei

Oct. 14, 2015

Re: [Pharo-dev] About Magritte Seaside

by Dale Henrichs

On 10/14/2015 01:00 AM, Christophe Demarey wrote: > > Le 12 oct. 2015 Ã 19:53, Dale Henrichs a Ã©crit : > >> >> >> On 10/12/2015 02:58 AM, Christophe Demarey wrote: >>> >>> Le 11 oct. 2015 Ã 22:32, Dale Henrichs a Ã©crit : >>> >>>> When you talk about "virtual packages", I would say that a >>>> BaselineOf is pretty much a "virtual package" already. >>> >>> I don't think BaselineOf could be seen as a virtual package. >>> In package A, you tell that A depends on V. >>> In package B, you simply tell that B provides V. Many other packages >>> could also provide V. >>> Then, it is the solver's job to take the most relevant package >>> providing V. >> >> ah ... I had a different definition of "virtual package" in mind:) >>> >>>> When it comes to cross-platform support there are several factors >>>> that were built into Metacello from the very beginning: >>>> >>>> - it should be possible to USE a package on a different platform >>>> than it was >>>> originally written for without modifying the package itself >>> >>> +1 >>> TBH, it is not yet implement in Cargo because I have a dilemnia: >>> once you release a version, you should not edit it anymore. >>> On another hand, you would like to say that this package released >>> and validated on Pharo 4 is also valid for Pharo5. >>> A good compromise would be to be able to edit *only *some metadata >>> of a released package. >> This is another reason why I think that embedded package dependency >> is a bad idea .... who controls what meta data gets modified and how >> do you guarantee integrity. > > The same concern applies for non-embedded package dependency. You need > to control who can modify and who cannot. I do not see your point. > >> As I consider my response I think I am beginning to see where the >> difference in our thought processes lie ... >> >> For example my "virtual package" is defined as a specific commit in a >> git repository (or any other disk-based SCM) ... the version of the >> release is defined as the SHA of the commit, or a tag, or a branch >> name ... > > in Cargo, I call that an Assembly. It is a set of package units > working together. > >> The components of this virtual package are one or more monticello >> packages and a BaselineOf.. > > these components in cargo are package units. > >> One uses the virtual package by cloning the git repository to the >> local disk or by using a `github://` description ... >> >> I choose this approach, because in Smalltalk we typically deal with >> source code that has to be compiled into our working image ... >> >> I think that with your "virtual package", you are taking the approach >> where you are treating the Smalltalk source code as if it were a >> pre-compiled entity (like linux packages) and the dependencies >> between projects is more difficult to deal with because you have to >> worry about the compatibility exeutable binaries ... In the linux >> world these binary packages need their own dependency mechanisms >> independent of a development environment so indeed there are very >> different requirements involved here ... including the need to have >> dependency specifications independent of the dependency >> specifications used in the development environment ... >> >> If this is closer to the truth, then I will have to say that my >> primary concern today is for development time dependencies and the >> types of packages that you are talking about with the Cargo Package >> Manager are aimed at a completely different problem space altogether ... >> >> BTW, I will read your source code so that I can confirm my >> supposition ... > > I think we talk about the same packages but with different words. > Virtual packages are just there to allow low-coupling between some > packages. I think this could simplify a lot some project dependency > definition and save time when you need to update it. Maybe for now, > you could just see Cargo managing packages. There package unit and > assembly (composite pattern). I agree that at this point in time we have to move beyond descriptions and start looking at source and detailed functionality, because that is where the differences between Cargo and Metacello will manifest themselves ... they are both package managers after all:) Dale

Oct. 14, 2015