- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [gsoc] Advances in Code Quality

by Stephane Ducasse

This is a super topic. What would be good is to check the smart suggestions because they need more love. Stef On Fri, Mar 31, 2017 at 3:14 PM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: > Hello, > > I'm Myroslava and I'm studying Computer Science at the Ukrainian Catholic > University in Lviv. As part of my Google Summer of Code project I'm going > to work on the quality of code in Pharo. This > <https://docs.google.com/document/d/1cX7VJ2QZejq_Cu6Ur28UCiUwzSD-Bu8GgSDqECi…> > is my proposal draft, and I would really appreciate some feedback, > comments, suggestions and so on. > > Thanks! >

March 31, 2017

Any plans for locale-specific printing and parsing of Date, Time, Number, etc.?

by Richard Sargent

I think the title pretty well states it. I see nothing in the Pharo 5.0 download that allows locale-specific printing. Is there a well-defined API available? Is it on the road map for a future Pharo version? (If so, for any specific version?) Thanks! -- View this message in context: http://forum.world.st/Any-plans-for-locale-specific-printing-and-parsing-of… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 31, 2017

Re: [Pharo-dev] [pharo-project/pharo-core] 32b2db: 60455

by Ben Coman

Just a note, since 60455 the following Athens no longer fails 30 seconds later... | view form1 form2| view := AthensSceneView new. form1 := UIThemeWatery new scrollbarThumbHorizontalMiddleForm. form2 := UIThemeWatery new scrollbarThumbVerticalMiddleForm. view scene: [:canvas | canvas surface clear: Color black. canvas setPaint: Color white. canvas drawShape: (0@0 corner:300@300). (canvas setPaint:form1) repeat. canvas paintTransform restoreAfter:[ canvas paintTransform translateBy:10@144. canvas drawShape:(10@144 corner:290@157). ]. (canvas setPaint:form2) repeat. canvas paintTransform restoreAfter:[ canvas paintTransform translateBy:144@10. canvas drawShape:(144@10 corner:157@290). ]. ]. view openInWindow. Thanks for your efforts Eliot and Esteban. (btw That was a side issue from... https://pharo.fogbugz.com/f/cases/14813/Wrong-size-for-Athens-surface-patte…) cheers -ben On Thu, Mar 30, 2017 at 6:15 PM, GitHub <noreply(a)github.com> wrote: > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 32b2dbb8baa7c84e08ff9a363f30428147fdd3d1 > https://github.com/pharo-project/pharo-core/commit/ > 32b2dbb8baa7c84e08ff9a363f30428147fdd3d1 > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2017-03-30 (Thu, 30 Mar 2017) > > Changed paths: > M Graphics-Primitives.package/BitBlt.class/instance/copying/ > copyBits.st > A Kernel-Tests.package/TimeTest.class/instance/tests > input/testNanoConstructor.st > A Kernel.package/Time.class/class/instance > creation/hour_minute_second_nano_.st > A Refactoring-Core.package/RBRenameClassVariableRefactori > ng.class/instance/accessing/newName.st > A Refactoring-Core.package/RBRenameClassVariableRefactori > ng.class/instance/accessing/newName_.st > A Refactoring-Core.package/RBRenameInstanceVariableRefact > oring.class/instance/accessing/newName.st > A Refactoring-Core.package/RBRenameInstanceVariableRefact > oring.class/instance/accessing/newName_.st > A Refactoring-Core.package/RBRenameInstanceVariableRefact > oring.class/instance/accessing/renameAccessors.st > A Refactoring-Core.package/RBRenameInstanceVariableRefact > oring.class/instance/accessing/renameAccessors_.st > A Refactoring-Core.package/RBRenameInstanceVariableRefact > oring.class/instance/initialize-release/initialize.st > M STON-Core.package/STONReader.class/instance/private/isClassChar_.st > A STON-Tests.package/STONReaderTests.class/instance/tests/ > testClassWithUnderscore.st > R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/ > script60454.st > A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/ > script60455.st > R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/ > update60454.st > A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/ > update60455.st > M ScriptLoader60.package/ScriptLoader.class/instance/public/ > commentForCurrentUpdate.st > M System-Support.package/SmalltalkImage.class/instance/special > objects/newSpecialObjectsArray.st > > Log Message: > ----------- > 60455 > 19882 copyBits fails when showing Athens surface > https://pharo.fogbugz.com/f/cases/19882 > > 19885 STON cannot read classes with underscore in their name > https://pharo.fogbugz.com/f/cases/19885 > > 19879 Accessors for instance and class variable rename refactoring > https://pharo.fogbugz.com/f/cases/19879 > > 19881 add Time >> #hour:minute:second:nano: constructor > https://pharo.fogbugz.com/f/cases/19881 > > http://files.pharo.org/image/60/60455.zip > > >

March 31, 2017

Re: [Pharo-dev] Google Summer of Code - New Trait Implementation

by tesonep＠gmail.com

Thank you, I have submitted. Cheers, Pablo On Fri, Mar 31, 2017 at 3:29 PM, Jigyasa Grover <grover.jigyasa1(a)gmail.com> wrote: > Hey Pablo > > Great idea ! > > Submit your proposal ASAP at summerofcode.withgoogle.com for review and > feedback. > > Good luck :) > > Best > Jigyasa Grover > GSoC 2017 Org Admin, Pharo Consortium > > > > On Fri, Mar 31, 2017 at 6:26 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> go >> go go go >> >> On Fri, Mar 31, 2017 at 2:14 PM, tesonep(a)gmail.com <tesonep(a)gmail.com> >> wrote: >> >>> Hello, >>> >>> I am planning in working in a new Traits implementation, the idea is to >>> have an implementation that can work as a loadable module. So you can use >>> it or not as another library. >>> >>> Also the idea is improve the support of all the tools by improving the >>> polymorphism between traits and classes. Clean up a little the API and add >>> support to have stateful traits. >>> >>> I would like to know if you have any suggestion or have a problem that I >>> could try to solve. I have been talking with some people in the community >>> to get ideas, but always having more opinions is better. >>> >>> Thanks in advance. >>> Pablo >>> >>> >>> -- >>> Pablo Tesone. >>> tesonep(a)gmail.com >>> >> >> > -- Pablo Tesone. tesonep(a)gmail.com

March 31, 2017

Re: [Pharo-dev] Google Summer of Code - New Trait Implementation

by Jigyasa Grover

Hey Pablo Great idea ! Submit your proposal ASAP at summerofcode.withgoogle.com for review and feedback. Good luck :) Best Jigyasa Grover GSoC 2017 Org Admin, Pharo Consortium On Fri, Mar 31, 2017 at 6:26 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > go > go go go > > On Fri, Mar 31, 2017 at 2:14 PM, tesonep(a)gmail.com <tesonep(a)gmail.com> > wrote: > >> Hello, >> >> I am planning in working in a new Traits implementation, the idea is to >> have an implementation that can work as a loadable module. So you can use >> it or not as another library. >> >> Also the idea is improve the support of all the tools by improving the >> polymorphism between traits and classes. Clean up a little the API and add >> support to have stateful traits. >> >> I would like to know if you have any suggestion or have a problem that I >> could try to solve. I have been talking with some people in the community >> to get ideas, but always having more opinions is better. >> >> Thanks in advance. >> Pablo >> >> >> -- >> Pablo Tesone. >> tesonep(a)gmail.com >> > >

March 31, 2017

Re: [Pharo-dev] [gsoc] Advances in Code Quality

by Jigyasa Grover

On Fri, Mar 31, 2017 at 6:44 PM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: > Hello, > Hi Myroslava > > I'm Myroslava and I'm studying Computer Science at the Ukrainian Catholic > University in Lviv. As part of my Google Summer of Code project I'm going > to work on the quality of code in Pharo. This > <https://docs.google.com/document/d/1cX7VJ2QZejq_Cu6Ur28UCiUwzSD-Bu8GgSDqECi…> > is my proposal draft, and I would really appreciate some feedback, > comments, suggestions and so on. > Great to have your proposal, submit it as draft at https://summerofcode.withgoogle.com/dashboard/ for review and feedback. Best of luck ! Best Jigyasa Grover GSoC 2017 Org Admin, Pharo Consortium > > Thanks! >

March 31, 2017

Re: [Pharo-dev] debugger inspector pane different than inspect pane?

by Andrei Chis

Hi Stef, Thanks for sharing the image. Found and fixed the bug: https://pharo.fogbugz.com/f/cases/19897 Cheers, Andrei On Wed, Mar 29, 2017 at 7:53 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > > On Wed, Mar 29, 2017 at 6:10 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Yes doru this is when I get a node resulting from Smacc >> Andrei I can share my image >> > > Please do. > > Cheers, > Andrei > > >> >> Stef >> >> On Wed, Mar 29, 2017 at 1:53 PM, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> >>> Hi Stef, >>> >>> Does the issue relate to the SmaCC tree presentation of an AST node? >>> >>> Cheers, >>> Doru >>> >>> >>> > On Mar 29, 2017, at 10:59 AM, Andrei Chis <chisvasileandrei(a)gmail.com> >>> wrote: >>> > >>> > Not aware of this bug. I tried to debug a few other objects that have >>> custom tree presentations and they seem to work. I'll need a way to >>> reproduce this. Can you paste the code of the custom presentation that is >>> problematic. >>> > >>> > Cheers, >>> > Andrei >>> > >>> > On Wed, Mar 29, 2017 at 9:11 AM, Stephane Ducasse < >>> stepharo.self(a)gmail.com> wrote: >>> > Hi andrei >>> > >>> > I'm debugger a node of a tree and in the debugger >>> > the tree pane is empty. Now when I click on the node and inspect >>> > it I get a tree representation. >>> > >>> > I do not know if you are aware of this behavior. >>> > >>> > Stef >>> > >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Every now and then stop and ask yourself if the war you're fighting is >>> the right one." >>> >>> >>> >>> >>> >>> >> >

March 31, 2017

[gsoc] Advances in Code Quality

by Myroslava Romaniuk

Hello, I'm Myroslava and I'm studying Computer Science at the Ukrainian Catholic University in Lviv. As part of my Google Summer of Code project I'm going to work on the quality of code in Pharo. This <https://docs.google.com/document/d/1cX7VJ2QZejq_Cu6Ur28UCiUwzSD-Bu8GgSDqECi…> is my proposal draft, and I would really appreciate some feedback, comments, suggestions and so on. Thanks!

March 31, 2017

Re: [Pharo-dev] Google Summer of Code - New Trait Implementation

by Stephane Ducasse

go go go go On Fri, Mar 31, 2017 at 2:14 PM, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > Hello, > > I am planning in working in a new Traits implementation, the idea is to > have an implementation that can work as a loadable module. So you can use > it or not as another library. > > Also the idea is improve the support of all the tools by improving the > polymorphism between traits and classes. Clean up a little the API and add > support to have stateful traits. > > I would like to know if you have any suggestion or have a problem that I > could try to solve. I have been talking with some people in the community > to get ideas, but always having more opinions is better. > > Thanks in advance. > Pablo > > > -- > Pablo Tesone. > tesonep(a)gmail.com >

March 31, 2017

Re: [Pharo-dev] the new "fixed" compactor VM has FT broken...

by Stephane Ducasse

Peter I took the latest mac VM and Moose 6.1 and I used your example then I played during 15 min with all the roassal examples and I cannot reproduce but I'm on mac. On Fri, Mar 31, 2017 at 2:23 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Tx peter! > I really really sorry for this state of affair. > I would like to tell you that I thank you for all the feedback you sent. > Please continue. > I imagine what it is to get a system that blow up under your fingers. > I'm always trying to work with the alpha version (because I attract bugs) > I got some crashes playing with roassal - but I updated to the latest vm > and trying. > > Can you sync with esteban so that he can access your setup? And yes we are > burning > esteban on this.... We should pay attention that our faery does not get > too exhausted :). > > Stef > > > On Fri, Mar 31, 2017 at 1:10 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> >> >> On Wed, Mar 29, 2017 at 3:03 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> BTWâ¦ I just checked Latest VM with a Pharo 5.0 (50771), and FT2 DOES NOT >>> CRASHESâ¦ and it looks working fine, just installed somethings, etc. so I >>> cannot be sure it will remain like that, but I can tell you: FT2 fonts are >>> working fine in Windows (tested in 7) and Pharo 5.0 *with* latest VM. >>> >>> So, all this discussion is informative, but the mail that originates it >>> can be reviewed :) >>> >> >> No, this is still broken, even in Pharo 6 (with the latest VM). Maybe >> it's yet another cairo issue? But it complains about FT fonts... >> >> I did mention that it crashed on Athens canvas, so e.g. any Roassal >> presentation that contains text >> >> v := RTView new. >> v add: (RTLabel new elementOn: '-_-'). >> v >> >> >> â >> >> Or running AthensSurfaceExamples class>>exampleDrawText >> >> >> >> >> In the past 15 months there was not a single week when the VM would just >> work without crashing or failing, and seeing that Pharo 6/lastest VM one >> day before release still doesn't work makes me really question why I still >> put up with this. >> >> Peter >> >> >> >>> >>> Esteban >>> >>> >>> On 29 Mar 2017, at 14:43, phil(a)highoctane.be wrote: >>> >>> We cannot work in 5.0 professionally with the VM released at the time. >>> I am also using an intermediate VM thing to do the job. >>> >>> That is a pain. And not helping me push more Pharo to sysadmin people >>> because they cannot have a stable reference point. >>> >>> Phil >>> >>> On Wed, Mar 29, 2017 at 12:05 PM, Esteban Lorenzano <estebanlm(a)gmail.com >>> > wrote: >>> >>>> >>>> > On 29 Mar 2017, at 11:39, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>>> > >>>> > On Wed, Mar 29, 2017 at 11:05:28AM +0200, Esteban Lorenzano wrote: >>>> >> wellâ¦ >>>> >> >>>> >> Latest VM is intended to work with latest Pharo, not with older >>>> versions. >>>> >> Latest VM is *always* an experimental/unstable VM that needs to be >>>> consideredâ¦ that, experimental and unstable. Otherwise there would not be >>>> point on having the distinction between stable/latest, isnât? >>>> >> >>>> > >>>> >> So, no, Latest VM (which can also be known as âalpha vmâ) has not >>>> broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 >>>> Alphaâ). >>>> >> >>>> >> BTWâ¦ Thatâs why in zeroconf you cannot download a âlatest vm for >>>> Pharo 5â. >>>> >> >>>> >> Of course, you can live at the edge, but that doesnât means >>>> something is broken when something fails if premises are not fulfilled :) >>>> > >>>> > Well considering VM for Pharo 5 never worked for me properly, whether >>>> it was crashing on BitBlt/Cairo, FT, or who knows what, I don't really have >>>> a choice but to use the latest. If there is a better way then I am all >>>> ears, constantly dealing with crashing VM when I need to get work done is >>>> extremely frustrating... >>>> > >>>> > Also I was under the impression that newer VM should work with older >>>> images, with the only exception being Cog/Spur change. Or should I have six >>>> different VMs and Pharo Launcher with six different VM configurations? >>>> >>>> we moved the paradigm a couple of years ago: each Pharo version comes >>>> with his own VM version (Other smalltalks do that too). >>>> Being infinite backward compatible is a lot of pain :) >>>> >>>> so yes, PharoLauncher needs to adapt to itâ¦ I added that requirement >>>> for PharoLauncher: you ship with latest stable but you can always download >>>> newers or olders (this is not yet implemented, is just a requirement I >>>> addedâ¦ well, couple of years ago when we changed the way we wanted VMs to >>>> work). >>>> >>>> Esteban >>>> >>>> > >>>> > Peter >>>> > >>>> >> >>>> >> Said thatâ¦ I had no problems with Latest VM + Pharo 6.0 (and they >>>> may happen, since this is all alfa :P) >>>> >> >>>> >> I donât know if âworkarounding the VMâ (by renaming libfreetype) >>>> will work, but if that works, ONCE we move latest vm to stable status we >>>> can consider backporting it to Pharo 5. >>>> >> >>>> >> Esteban >>>> >> >>>> >>> On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>>> >>> >>>> >>> The new "fixed" compactor VM has broken FT... >>>> >>> >>>> >>> So any text drawn on Athens canvas results in red cross... >>>> >>> >>>> >>> Error in... >>>> >>> >>>> >>> CairoFontFace class>>primFtFace:loadFlags: >>>> >>> >>>> >>> 'Unable to find function address' >>>> >>> >>>> >>> Apparently because someone renamed libfreetype-6.dll to >>>> libfreetype.dll >>>> >>> >>>> >>> (Windows VM latest, Pharo 5) >>>> >>> >>>> >> >>>> >> >>>> > >>>> >>>> >>>> >>> >>> >> >

March 31, 2017