- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Issue Tracker] Help needed: 623 open issues

by Marcus Denker

> On 31 Aug 2015, at 19:15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 31 Aug 2015, at 11:41, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hello, >> >> We have 623 open issues on the issue tracker. >> > > Down to 619. > Down to 610. It would be really nice if people could look at their old reports. With >600 open issues, I see it very very often that even if an issue has been already reported, people just never look for the old reports. They open new ones. Even if the existing one they open themselves a year ago. And it is me that then closes duplicates. We need to get that number down to a manageable size. Keep in mind that *every* open issue has a cost: it takes away man power form the others. Marcus

Sept. 1, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 1, 2015

[pharo-project/pharo-core] e696be: 50294

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: e696bef9b5a93f3ce46d14946e67a3171d28f5fc https://github.com/pharo-project/pharo-core/commit/e696bef9b5a93f3ce46d1494… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-01 (Tue, 01 Sep 2015) Changed paths: M ConfigurationOfShoreLineReporter.package/ConfigurationOfShoreLineReporter.class/instance/versions/stable_.st A ConfigurationOfShoreLineReporter.package/ConfigurationOfShoreLineReporter.class/instance/versions/version020_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50293.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50294.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50293.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50294.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M ShoreLine-Report-UI.package/SlReportPreDebugAction.class/instance/testing/appliesToDebugger_.st M ShoreLine-Report-UI.package/SlReportWindow.class/class/instance creation/forDebugger_.st M ShoreLine-Report-UI.package/SlReportWindow.class/instance/accessing/reportSummary.st R ShoreLine-Report-UI.package/SlReportWindow.class/instance/initialization/generateReport.st M ShoreLine-Report-UI.package/SlReportWindow.class/instance/initialization/initializeWidgets.st A ShoreLine-Report-UI.package/SlReportWindow.class/instance/initialization/updateReport.st M Slot.package/SlotClassBuilder.class/instance/private validating/validateClassName.st Log Message: ----------- 50294 16442 ShoreLine Reporter version 0.2.0 https://pharo.fogbugz.com/f/cases/16442 15307 Error message not clear when trying to create a class with a name without the first letter in upper case https://pharo.fogbugz.com/f/cases/15307 http://files.pharo.org/image/50/50294.zip

Sept. 1, 2015

Re: [Pharo-dev] Image used for 4.0 -> 5.0 (Build 50000) transition

by Ben Coman

Looks to me like 50000 branched from 40609... 40610 2015-04-23 50000 2015-04-16 40609 2015-04-15 40608 2015-04-14 40609 Log Message: * 15341 remove download sources setting https://pharo.fogbugz.com/f/cases/15341 * Deleted SmalltalkImage >> shouldDownloadSourcesFile 40608 shouldDownloadSourcesFile exists 40609 shouldDownloadSourcesFile does not exist 50000 shouldDownloadSourcesFile does not exist 40610 Log Message: * 15349 The menu in the PharoTutorial has an erroneous label https://pharo.fogbugz.com/f/cases/15349 * HelpBrowser>>menu "inspect it (p)" --> "inspect it (i)" 40609 has "(p)" 40610 has "(i)" 50000 has "(p)" cheers -ben On Tue, Sep 1, 2015 at 1:33 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Stef, hi Mariano, > > Yes, maybe it is a cleanup issue. But before we should deeper invest into this we must be sure if #40608 was the base for > building #50000. Anyone able to confirm? Currently it is hard to reproduce from what 40xxx number the initial 5.0 > image was built. > > Also I thought #cleanupForRelease and #cleanupForProduction is always done on the CI images after > applying each update. So any image is a production candidate/production release? Or is this only done for the backports? > Havent checked yet - but maybe someone can answer this as well. > > Thanks > T. > > > > Gesendet: Montag, 31. August 2015 um 14:08 Uhr > Von: "Mariano Martinez Peck" <marianopeck(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] Image used for 4.0 -> 5.0 (Build 50000) transition > > Torsten, maybe it's related to ImageCleaner #cleanupForRelease and cleanupForProduction ? > > > On Mon, Aug 31, 2015 at 3:42 AM, stepharo <stepharo(a)free.fr> wrote: > yes may be a cleanup. > > Le 31/8/15 01:00, Nicolai Hess a Ã©crit : > > Oh, thats funny.Maybe this comes from the release buidling process, (condense changes / sources) anything thatresets some world state? > > > 2015-08-30 22:29 GMT+02:00 Torsten Bergmann <astares@gmx.de[astares@gmx.de]>:Nicolai Hess wrote: >>What does not work in 40608? > > What Julien describes in [1] when he uses Pharo 4 with DesktopManager. I use Pharo 5 > and did not have this effect. > > To reproduce I used latest.zip from http://files.pharo.org/vm/pharo/win/[http://files.pharo.org/vm/pharo/win/] > one time with #40608 and one time with #50000 > > Gofer new > smalltalkhubUser: 'TorstenBergmann' project: 'DesktopManager'; > configuration; > loadDevelopment. > > 1. Hit CTRL + D and then CTRL + A (which is "D"esktop "A"dd) > 2. Hit CTRL + D and then CTRL + P (which is "D"esktop "P"revious). > > Now the windows on the first desktop are not usable anymore in 40608. They do > not repaint. > > In Pharo #50000 or any newer Pharo 5 image this works without a problem. > > Bye > T. > > [1] http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2015-August/02… > > -- > Mariano > http://marianopeck.wordpress.com[http://marianopeck.wordpress.com] >

Aug. 31, 2015

Re: [Pharo-dev] [Issue Tracker] Help needed: 623 open issues

by stepharo

Yes this is nice because I often try to find my babies but fail ;) Le 31/8/15 20:23, Peter UhnÃ¡k a Ã©crit : > Open issues grouped by project: > https://pharo.fogbugz.com/f/filters/25/Unassigned-Issues > > I also added a filter (hope it works for others): > https://pharo.fogbugz.com/f/filters/135/My-Open-Cases > It lists only open issues that you've interacted with (opened, > commented, changed) > > It is not that we donât make progressâ¦ we closed 113 issues the > last 7 days, we had weeks > with >150. > > > It would be interesting to see the rate of adding vs rate of fixing > the issues (to see the current trend). > > Peter

Aug. 31, 2015

Re: [Pharo-dev] Interesting Morphic improvement

by stepharo

Hi stefan Ok let us know and once you are ok publish an issue with the slice. Stef Le 31/8/15 17:35, Stephan Eggermont a Ã©crit : > Marcel Taeumel has made a lot of improvements to Morphic Squeak. > This looks like an interesting one for us. > I tried it in 50292 (making the changes in the right order) > haven't found a problem yet. > > Stephan > > > Marcel Taeumel uploaded a new version of Morphic to project The Trunk: > http://source.squeak.org/trunk/Morphic-mt.900.mcz > > ==================== Summary ==================== > > Name: Morphic-mt.900 > Author: mt > Time: 19 April 2015, 11:27:22.653 am > UUID: 950b4378-f3fe-db4c-b054-88b646a1feb0 > Ancestors: Morphic-mt.899 > > Fix to avoid unnecessary layout computation for proportional layout. > > Note: Please report any visual glitches. Not 100% sure about the > extent of this change... > > =============== Diff against Morphic-mt.899 =============== > > Item was changed: > ----- Method: Morph>>layoutProportionallyIn: (in category 'layout') > ----- > layoutProportionallyIn: newBounds > "Layout specific. Apply the given bounds to the receiver." > | box frame | > frame := self layoutFrame ifNil:[^self]. > - "before applying the proportional values make sure the receiver's > layout is computed" > - self fullBounds. "sigh..." > "compute the cell size the receiver has given its layout frame" > box := frame layout: self bounds in: newBounds. > (box = self bounds) ifTrue:[^self]. "no change" > ^self layoutInBounds: box.! > > Item was added: > + ----- Method: PluggableTextMorph>>isAutoFit (in category > 'accessing') ----- > + isAutoFit > + > + ^ textMorph isAutoFit! > > Item was added: > + ----- Method: ScrollPane>>isAutoFit (in category 'access') ----- > + isAutoFit > + "Does this scroll pane modifies the extent of its scrollable content > when it resizes itself to avoid, for example, a horizontal or vertical > scrollbar?" > + > + ^ false! > > Item was added: > + ----- Method: ScrollPane>>layoutProportionallyIn: (in category > 'layout') ----- > + layoutProportionallyIn: newBounds > + > + self layoutFrame ifNil:[^self]. > + self isAutoFit ifTrue: [self fullBounds]. > + ^ super layoutProportionallyIn: newBounds.! > > >

Aug. 31, 2015

Re: [Pharo-dev] Nautilus and Work group

by stepharo

HI sean this is nice that you brainstorm on this because we should get smarter tools and projects :) Stef Le 31/8/15 17:48, Sean P. DeNigris a Ã©crit : > Uko2 wrote >> Would be cool if from Pharo launcher you could specify the configuration >> that you want to work with and a version of faro, then it would download >> an image, load there a configuration, and put loaded packages into a work >> group. > I implemented everything but the work group part for my personal projects. > There is a (WIP at the moment because I'm expanding it to cover git repos) > model like a personal Squeak Map, which allows you to model projects, > declaring the canonical repo, preferred version to load (e.g. always load > the bleedingEdge of Xyz project), etc. This model is integrated into the > Launcher toolbar (via override for now, but could easily make a hook). See > if it's at all helpful: > https://www.youtube.com/watch?v=oRC7-DDHmpE > > To load in a launcher image: > Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'SmallWorld'; > configurationOf: 'SmallWorld'; > load. > #ConfigurationOfSmallWorld asClass project stableVersion load: > 'launcher' > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Nautilus-and-Work-group-tp4845434p4847194.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Aug. 31, 2015

Re: [Pharo-dev] [Issue Tracker] Help needed: 623 open issues

by Marcus Denker

> > This is âopen issuesâ for the last year: > > <open cases.png> of course that looks very stagnantâ¦ but we closed 2593 issues over that 12 months.

Aug. 31, 2015

Re: [Pharo-dev] [Issue Tracker] Help needed: 623 open issues

by Marcus Denker

> On 31 Aug 2015, at 20:23, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Open issues grouped by project: https://pharo.fogbugz.com/f/filters/25/Unassigned-Issues <https://pharo.fogbugz.com/f/filters/25/Unassigned-Issues> > > I also added a filter (hope it works for others): https://pharo.fogbugz.com/f/filters/135/My-Open-Cases <https://pharo.fogbugz.com/f/filters/135/My-Open-Cases> > It lists only open issues that you've interacted with (opened, commented, changed) > > It is not that we donât make progressâ¦ we closed 113 issues the last 7 days, we had weeks > with >150. > > It would be interesting to see the rate of adding vs rate of fixing the issues (to see the current trend). > > Peter This is âopen issuesâ for the last year:

Aug. 31, 2015

Re: [Pharo-dev] [Issue Tracker] Help needed: 623 open issues

by Peter UhnÃ¡k

Open issues grouped by project: https://pharo.fogbugz.com/f/filters/25/Unassigned-Issues I also added a filter (hope it works for others): https://pharo.fogbugz.com/f/filters/135/My-Open-Cases It lists only open issues that you've interacted with (opened, commented, changed) It is not that we donât make progressâ¦ we closed 113 issues the last 7 > days, we had weeks > with >150. > It would be interesting to see the rate of adding vs rate of fixing the issues (to see the current trend). Peter

Aug. 31, 2015