September 2015 - Pharo-dev - lists.pharo.org

Flattr added to pharo.org

by Marcus Denker

Hi, We added at Flattr button: http://pharo.org/contribute <http://pharo.org/contribute> Direkt link is: https://flattr.com/thing/4606474/Pharo-Welcome-to-Pharo Marcus

Sept. 1, 2015

Re: [Pharo-dev] Versionner and BaselineOf

by Christophe Demarey

Le 25 aoÃ»t 2015 Ã 04:10, Sean P. DeNigris a Ã©crit : > For projects developed with git, BaselineOfXyzs replace ConfigurationOfXyzs. > What are the plans to update Versionner for this development? I've gotten > spoiled and I'm not enjoying writing BaselineOfs by hand! :/ You're right. It would be good to have support for that. BaselineOfs are far easier to work with that ConfigurationOfs but a cool UI would be appreciated. For now, it is low-priority for me, I'm working on the bootstrap with Guillermo.

Sept. 1, 2015

Re: [Pharo-dev] No longer valid issues

by Ben Coman

On Tue, Sep 1, 2015 at 5:33 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> On 01 Sep 2015, at 10:46, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> Sometimes I encounter issue that is no longer valid (has been fixed / changed / ... ) >> >> Do I mark it as >> > I think it dependsâ¦ the strange thing that fogbugz makes âresolvingâ and âcloseâ two steps > helps here, though: we can keep issues open for some days to give the original submitter > a chance to react and âsymbolizeâ that this is not just a rude action on our partâ¦ > > So I would use ânot reproducibleâ if you canât reproduce. Then if two people canât, we close. > > And inside of âresolvedâ we have âNor reproducibleâ, âinvalidâ (e.g. if the subsystem has been removed > or changed). Or even âFixedâ. > >> There also seem to be quite large amount of stale issues... >> If someone didn't fix them nor even commented on them in years, maybe the issue should be let to die? >> If nobody is commenting on it, nobody is interested in it. >> If the issue pops up again, we can easily create fresh issue. >> > > Yes, we have a âTimeOutâ Stateâ¦ we should use that moreâ¦ it would be best to do that automatically, > so nobody can get upset against a person closing the issuesâ¦ The neutrality and consistency of this is a good idea. > 12 month after no action â> close with mail to original submitter. A two step action to close would be good. Resolve to "Stale" status while requesting an update from submitter, possibly also notifying anyone that commented. Then close it if it remains stale for some amount of time -- but we should take care that these don't end up in our release statistics as "wow look how many issue we closed." If possible, maybe there should also be a prominent message in the header or sidebar of our Fogbugz pages advising of this policy. > Re-opening is easy, and with that we > make sure that only valid issues stay in the issue tracker. > > (Many of these issues will actually be already fixed, so it will save a lot of timeâ¦) cheers -ben

Sept. 1, 2015

SpecTableLayout & TableLayoutProperties

by Peter UhnÃ¡k

Hi, it is my understanding that I should be able to change table layout properties with stuff like cellPositioning: / listCentering: / etc. However nothing I do have any change. Am I using it incorrectly, or is this not (properly) implemented? example: (the cell content is placed in #topLeft despite specifying positioning and centering) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |ui layout| ui := DynamicComposableModel new. ui instantiateModels: #( cell11 LabelModel cell12 LabelModel cell21 LabelModel cell22 LabelModel ). ui cell11 label: '1-1'. ui cell12 label: '1-2'. ui cell21 label: '2-1'. ui cell22 label: '2-2'. layout := SpecTableLayout column cellPositioning: #center; listCentering: #bottomRight; newRow: [ :r | r add: #cell11; add: #cell12 ]; newRow: [ :r | r add: #cell21; add: #cell22]; yourself. ui openWithSpecLayout: layout. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Thanks, Peter

Sept. 1, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 1, 2015

[pharo-project/pharo-core] 788aa0: 50295

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 788aa01b2e6ab1496ab2765fbe4d13539b690a04 https://github.com/pharo-project/pharo-core/commit/788aa01b2e6ab1496ab2765f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-01 (Tue, 01 Sep 2015) Changed paths: M AST-Core.package/ManifestASTCore.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st M Compression.package/ManifestCompression.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st R Jobs.package/JobTest.class/README.md R Jobs.package/JobTest.class/definition.st R Jobs.package/JobTest.class/instance/tests/tearDown.st R Jobs.package/JobTest.class/instance/tests/testChildJob.st R Jobs.package/JobTest.class/instance/tests/testCurrentJob.st R Jobs.package/JobTest.class/instance/tests/testJobAnnouncements.st R Jobs.package/JobTest.class/instance/tests/testLookupJob.st R Jobs.package/JobTest.class/instance/tests/testOwner.st R Jobs.package/JobTest.class/instance/tests/testProgress.st R Jobs.package/JobTest.class/instance/tests/testProgressChangeByCurrentValue.st R Jobs.package/JobTest.class/instance/tests/testSingleJob.st A Jobs.package/ManifestJobs.class/class/meta-data - dependency analyser/ignoredDependencies.st A JobsTests.package/JobTest.class/README.md A JobsTests.package/JobTest.class/definition.st A JobsTests.package/JobTest.class/instance/tests/tearDown.st A JobsTests.package/JobTest.class/instance/tests/testChildJob.st A JobsTests.package/JobTest.class/instance/tests/testCurrentJob.st A JobsTests.package/JobTest.class/instance/tests/testJobAnnouncements.st A JobsTests.package/JobTest.class/instance/tests/testLookupJob.st A JobsTests.package/JobTest.class/instance/tests/testOwner.st A JobsTests.package/JobTest.class/instance/tests/testProgress.st A JobsTests.package/JobTest.class/instance/tests/testProgressChangeByCurrentValue.st A JobsTests.package/JobTest.class/instance/tests/testSingleJob.st M Monticello.package/ManifestMonticello.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st A OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/code-critics/rejectRules.st A OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/code-critics/ruleAssignmentInIfTrueRuleV1TruePositive.st A OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/code-critics/ruleBadMessageRuleV1FalsePositive.st A OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/code-critics/ruleMethodHasNoTimeStampRuleV1TruePositive.st A OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/code-critics/ruleTempsReadBeforeWrittenRuleV1FalsePositive.st A OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/code-critics/ruleToDoCollectRuleV1FalsePositive.st A OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/code-critics/ruleVariableAssignedLiteralRuleV1FalsePositive.st R OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta data/rejectRules.st R OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta data/ruleAssignmentInIfTrueRuleV1TruePositive.st R OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta data/ruleBadMessageRuleV1FalsePositive.st R OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta data/ruleMethodHasNoTimeStampRuleV1TruePositive.st R OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta data/ruleTempsReadBeforeWrittenRuleV1FalsePositive.st R OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta data/ruleToDoCollectRuleV1FalsePositive.st R OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta data/ruleVariableAssignedLiteralRuleV1FalsePositive.st A OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta-data - dependency analyser/ignoredDependencies.st M Ring-Monticello.package/ManifestRingMonticello.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50294.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50295.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50294.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50295.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/ManifestSlot.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st M System-Changes.package/ManifestSystemChanges.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st M System-FileRegistry.package/ManifestSystemFileRegistry.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st M System-Sources.package/ManifestSystemSources.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st R System-Support.package/ClassQueryTest.class/README.md R System-Support.package/ClassQueryTest.class/definition.st R System-Support.package/ClassQueryTest.class/instance/tests/testAllCallsOn.st R System-Support.package/ClassQueryTest.class/instance/tests/testAllCallsOnASymbol.st R System-Support.package/ClassQueryTest.class/instance/tests/testReferencedClasses.st M System-Support.package/ManifestSystemSupport.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st R System-Support.package/MethodQueryTest.class/README.md R System-Support.package/MethodQueryTest.class/definition.st R System-Support.package/MethodQueryTest.class/instance/tests/testReferencedClasses.st A System-SupportTests.package/ClassQueryTest.class/README.md A System-SupportTests.package/ClassQueryTest.class/definition.st A System-SupportTests.package/ClassQueryTest.class/instance/tests/testAllCallsOn.st A System-SupportTests.package/ClassQueryTest.class/instance/tests/testAllCallsOnASymbol.st A System-SupportTests.package/ClassQueryTest.class/instance/tests/testReferencedClasses.st A System-SupportTests.package/MethodQueryTest.class/README.md A System-SupportTests.package/MethodQueryTest.class/definition.st A System-SupportTests.package/MethodQueryTest.class/instance/tests/testReferencedClasses.st M Traits.package/ManifestTraits.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st M Transcript.package/ManifestTranscript.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st A UIManager.package/ManifestUIManager.class/class/meta-data - dependency analyser/ignoredDependencies.st M UIManager.package/ManifestUIManager.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st Log Message: ----------- 50295 Jobs-Tests http://files.pharo.org/image/50/50295.zip

Sept. 1, 2015

Re: [Pharo-dev] No longer valid issues

by Marcus Denker

> On 01 Sep 2015, at 10:46, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Sometimes I encounter issue that is no longer valid (has been fixed / changed / ... ) > > Do I mark it as > I think it dependsâ¦ the strange thing that fogbugz makes âresolvingâ and âcloseâ two steps helps here, though: we can keep issues open for some days to give the original submitter a chance to react and âsymbolizeâ that this is not just a rude action on our partâ¦ So I would use ânot reproducibleâ if you canât reproduce. Then if two people canât, we close. And inside of âresolvedâ we have âNor reproducibleâ, âinvalidâ (e.g. if the subsystem has been removed or changed). Or even âFixedâ. > There also seem to be quite large amount of stale issues... > If someone didn't fix them nor even commented on them in years, maybe the issue should be let to die? > If nobody is commenting on it, nobody is interested in it. > If the issue pops up again, we can easily create fresh issue. > Yes, we have a âTimeOutâ Stateâ¦ we should use that moreâ¦ it would be best to do that automatically, so nobody can get upset against a person closing the issuesâ¦ 12 month after no action â> close with mail to original submitter. Re-opening is easy, and with that we make sure that only valid issues stay in the issue tracker. (Many of these issues will actually be already fixed, so it will save a lot of timeâ¦) Marcus

Sept. 1, 2015

No longer valid issues

by Peter UhnÃ¡k

Sometimes I encounter issue that is no longer valid (has been fixed / changed / ... ) Do I mark it as a) Work Needed (Not Reproducible) but there's no more work needed b) Resolved (Fix Review Needed) with a comment that's no longer reproducible c) Resolved (Invalid) since it's no longer valid d) something else? Option b) makes probably most sense since someone just needs to review that it's truly not reproducible and close it. Or maybe option a), and change the "To Review" filter to also include this. There also seem to be quite large amount of stale issues... If someone didn't fix them nor even commented on them in years, maybe the issue should be let to die? If nobody is commenting on it, nobody is interested in it. If the issue pops up again, we can easily create fresh issue. Peter

Sept. 1, 2015

[Pharo4] Issues for review for Pharo4

by Marcus Denker

Hello, There are 4 issues for Pharo4 that need input: https://pharo.fogbugz.com/f/filters/45/Review <https://pharo.fogbugz.com/f/filters/45/Review> Marcus

Sept. 1, 2015

Re: [Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

by Stephan Eggermont

On 01-09-15 08:35, Marcus Denker wrote: > But just think how much this simplifies the experience of people loading old code into a new > Pharo version: it just keeps running and fixes itself! Itâs that kind of things we need to be > able to evolve the system. This is a crucial step to support continuous improvement indeed. Just-in-time repeatable refactoring, reducing the cost of change Stephan

Sept. 1, 2015