May 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #949: 21965-SmaltlalkImagecompiler--use-globals-as-default-environment-not-just-self

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #949 was: FAILURE. The Pull Request #1416 was integrated: "21965-SmaltlalkImagecompiler--use-globals-as-default-environment-not-just-self" Pull request url: https://github.com/pharo-project/pharo/pull/1416 Issue Url: https://pharo.fogbugz.com/f/cases/21965 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 25, 2018

Re: [Pharo-dev] feenk log

by Denis Kudriashov

Hi Tudor. Very impressive progress. I have one question about scrolling support. How it works or is it works with elements which are based on infinite layout like mentioned grid widget? Does grid implemented with PannableElement too? 2018-05-25 14:30 GMT+03:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > We were a bit silent the last couple of months. Quite a bit happened in > the meantime, so here is a summary (for more fine grained announcements, > you can follow us on Twitter): > > ---- > Bloc > ---- > > - Scrolling. We finally have a good scrolling support: > https://twitter.com/feenkcom/status/991690465224331264 > This might sound like a trivial feature, but it turns out it is not. We > had a bug that forced us to rethink the support quite deeply in order to be > able to debug it. To do this, we now can simulate time in Bloc, which is > really cool: > https://twitter.com/feenkcom/status/989797367523233797 > https://twitter.com/feenkcom/status/988753142299938817 > (as a side note, the bug we fought with was the last > > - Pannable element is a combination of a scrollable element with a > scalable element, and it offers the possibility either to zoom in/out + > scroll, or to fit screen and resize when the parent resizes. > > - PDF, SVG, PNG, JPG export (based on the underlying Moz2D support): > https://twitter.com/feenkcom/status/976580153802358786 > https://twitter.com/feenkcom/status/976578060429484032 > > - Better curve support: > https://twitter.com/feenkcom/status/990967109193781249 > https://twitter.com/feenkcom/status/990971530615107584 > > - Better debugging support for understanding bounds: > https://twitter.com/feenkcom/status/989138457288167424 > > ---- > Brick > ---- > > - We now have simple list and columned list widgets. The list is both fast > and scalable and supports rows of variable heights: > https://twitter.com/feenkcom/status/984744251920658432 > https://twitter.com/feenkcom/status/984143821192744961 > > - Basic tab widget: > https://twitter.com/feenkcom/status/974420432240685062 > > - Looks: a mechanism for specifying element-specific composition and > interaction. > > ---- > GT > ---- > > - Documenter saw some major improvements. Just a reminder, Documenter is > the tool that enables live programming and previews directly within Pillar > documents. > We now have a capability similar to notebooks like Jupyter: > https://twitter.com/feenkcom/status/996310432225820672 > We use it extensively to document our code. For example, here is a > tutorial about playing with looks in Bloc: > https://twitter.com/feenkcom/status/973899862482866176 > And we can also express whole tutorials based on Epicea: > https://twitter.com/feenkcom/status/999975333972541440 > > - Diagrammer. We now have better editing support for detailed things such > as arrow head: > https://twitter.com/feenkcom/status/976341449267531776 > While Diagrammer is apparently a tool for diagrams, it has a rather > generic design that can be utilized for all sorts of use cases. For > example, one side effect is that now all elements can be visually edited: > https://twitter.com/feenkcom/status/982656456968241152 > > - Mondrian: Using the new pannable element, we can now zoom in/out and > scroll, and we can also set element to fit screen. We can also drag > elements around. > > - Inspector: we now have an initial support for multiple views associated > with an object. The support is similar to the one from the current > inspector. > > > Have fun, > The feenk team > > -- > www.tudorgirba.com > www.feenk.com > > "What is more important: To be happy, or to make happy?" > > >

May 25, 2018

feenk log

by Tudor Girba

Hi, We were a bit silent the last couple of months. Quite a bit happened in the meantime, so here is a summary (for more fine grained announcements, you can follow us on Twitter): ---- Bloc ---- - Scrolling. We finally have a good scrolling support: https://twitter.com/feenkcom/status/991690465224331264 This might sound like a trivial feature, but it turns out it is not. We had a bug that forced us to rethink the support quite deeply in order to be able to debug it. To do this, we now can simulate time in Bloc, which is really cool: https://twitter.com/feenkcom/status/989797367523233797 https://twitter.com/feenkcom/status/988753142299938817 (as a side note, the bug we fought with was the last - Pannable element is a combination of a scrollable element with a scalable element, and it offers the possibility either to zoom in/out + scroll, or to fit screen and resize when the parent resizes. - PDF, SVG, PNG, JPG export (based on the underlying Moz2D support): https://twitter.com/feenkcom/status/976580153802358786 https://twitter.com/feenkcom/status/976578060429484032 - Better curve support: https://twitter.com/feenkcom/status/990967109193781249 https://twitter.com/feenkcom/status/990971530615107584 - Better debugging support for understanding bounds: https://twitter.com/feenkcom/status/989138457288167424 ---- Brick ---- - We now have simple list and columned list widgets. The list is both fast and scalable and supports rows of variable heights: https://twitter.com/feenkcom/status/984744251920658432 https://twitter.com/feenkcom/status/984143821192744961 - Basic tab widget: https://twitter.com/feenkcom/status/974420432240685062 - Looks: a mechanism for specifying element-specific composition and interaction. ---- GT ---- - Documenter saw some major improvements. Just a reminder, Documenter is the tool that enables live programming and previews directly within Pillar documents. We now have a capability similar to notebooks like Jupyter: https://twitter.com/feenkcom/status/996310432225820672 We use it extensively to document our code. For example, here is a tutorial about playing with looks in Bloc: https://twitter.com/feenkcom/status/973899862482866176 And we can also express whole tutorials based on Epicea: https://twitter.com/feenkcom/status/999975333972541440 - Diagrammer. We now have better editing support for detailed things such as arrow head: https://twitter.com/feenkcom/status/976341449267531776 While Diagrammer is apparently a tool for diagrams, it has a rather generic design that can be utilized for all sorts of use cases. For example, one side effect is that now all elements can be visually edited: https://twitter.com/feenkcom/status/982656456968241152 - Mondrian: Using the new pannable element, we can now zoom in/out and scroll, and we can also set element to fit screen. We can also drag elements around. - Inspector: we now have an initial support for multiple views associated with an object. The support is similar to the one from the current inspector. Have fun, The feenk team -- www.tudorgirba.com www.feenk.com "What is more important: To be happy, or to make happy?"

May 25, 2018

[Pharo 7.0-dev] Build #948: 21956-tiny-cleanup-simplify-methods-related-to-pools-in-Class

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #948 was: FAILURE. The Pull Request #1409 was integrated: "21956-tiny-cleanup-simplify-methods-related-to-pools-in-Class" Pull request url: https://github.com/pharo-project/pharo/pull/1409 Issue Url: https://pharo.fogbugz.com/f/cases/21956 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 25, 2018

Re: [Pharo-dev] [Pharo-users] pharo location include korean charactor then look is not good.

by Sven Van Caekenberghe

I made the following quick changes: UnixEnvironment>>#environAt: index ^ (self environ at: index) ifNotNil: [ :string | string asByteArray utf8Decoded ] OSPlatform>>#currentWorkingDirectoryPathWithBuffer: aByteString <primitive: 'primitiveGetCurrentWorkingDirectory' module: '' error: ec> ^ (self getPwdViaFFI: aByteString size: aByteString size) ifNotNil: [ :string | string asByteArray utf8Decoded ] ifNil:[ self error:'Insufficient buffer size to read current working directory: ' , aByteString size asString] But actually almost any string coming from the VM seems wrong (i.e. should be further UTF-8 decoded): SmalltalkImage>>#[prim]ImagePath and #vmFileName basically probably every call VirtualMachine>>#getSystemAttribute: what a mess ... > On 25 May 2018, at 10:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > We looked at this before, but came to no conclusion. > > The problem lies with OS environment variable decoding. > > I created a 64-bit Pharo 7 in /tmp/Ã©tÃ© on macOS. > > FileLocator imageDirectory resolve. > "File @ /private/tmp/Ã©tÃ©" > > Smalltalk os environment at: 'PWD'. > "'/tmp/ÃÂ©tÃÂ©'" > > (Smalltalk os environment at: 'PWD') asByteArray utf8Decoded. > "'/tmp/Ã©tÃ©'" > > Smalltalk os environment asDictionary. > > FileBrowser works OK too but starts up with a wrong window title. > > I believe the real issue is that we are not 100% sure that it is always UTF8 on all platforms all the time (i.e. apparently users can put their (Windows) OS in a different encoding). > >> On 25 May 2018, at 10:28, Hilaire <hilaire(a)drgeo.eu> wrote: >> >> I second you on this issue. Something went wrong in the encoding in the path in your window title. Ã smells like UTF-8 issue. >> >> Looks like Pharo7 still has some issue(s) when handling UTF-8 characters used in modern Operating System filling system. >> >> Another example of this problem, with DrGeo copied in a path with UTF-8 characters, for example ÃtÃ© folder. When DrGeo is started, Pharo creates a folder ÃÂtÃÂ© where it creates some locale/ folder >> >> I see this problem on ubtuntu 17.10 and Mac OSX at my school. >> >> We have this problem for years, I was believing it was fixed, but apparently not. >> >> Hilaire >> >> >> Le 25/05/2018 Ã 04:09, peter yoo a Ã©crit : >>> so.. application location include korean charactor then broken title string in pharo window. >>> (of course ubuntu 18.04 with gnome env) >>> >>> broken title is "ë°ííë©´". it's ok? or where to report? >>> >>> look a attached file please. >>> >>> -- >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> <P7-utf8.png> >

May 25, 2018

[Pharo 7.0-dev] Build #947: 21781-trait-composition-should-not-copy-slots-everytime-it-is-asked

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #947 was: SUCCESS. The Pull Request #1253 was integrated: "21781-trait-composition-should-not-copy-slots-everytime-it-is-asked" Pull request url: https://github.com/pharo-project/pharo/pull/1253 Issue Url: https://pharo.fogbugz.com/f/cases/21781 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 25, 2018

[Pharo 7.0-dev] Build #946: 21954-cleanup-copyOfMethodDictionary-and-copyMethodDictionaryFrom

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #946 was: FAILURE. The Pull Request #1408 was integrated: "21954-cleanup-copyOfMethodDictionary-and-copyMethodDictionaryFrom" Pull request url: https://github.com/pharo-project/pharo/pull/1408 Issue Url: https://pharo.fogbugz.com/f/cases/21954 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 25, 2018

Crash on GC garbageCollect

by Andreas Brodbeck

Hi all I have a 6.0 image which crashes on garbage collect. If I run "Smalltalk garbageCollect" it crashes. The crash log is attached. But I don't really understand that crash log. I run it with a 6.0 VM, tried it also with newest 6.1 VM and 7.0 VM, but always the same error. I read here in the list about crash problems with GC, memory leaks and similar, but I really don't see what I could do. Any pointers in which direction I could investigate? Thanks and cheers, Andreas -- Andreas Brodbeck www.mindclue.ch

May 25, 2018

Re: [Pharo-dev] files.pharo.org, get.pharo.org problems?

by Tim Mackinnon

S3 is a great suggestion - but if we are part of google summer of code and an active open source platform - canât they give a free reliable platform? Possibly amazon does similar? Given we are often the source of so many formative ideas, canât someone will help us sort the infrastructure? If not, should one of us ask Martin Fowler or other Smalltalk advocates to help take this funding problem away. We need to pay engineers for the next generation of improvements? Tim Sent from my iPhone > On 24 May 2018, at 17:49, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > If it is a static site you can use this to manage it and host it on S3 > > > https://github.com/laurilehmijoki/s3_website > > > > This is S3 pricing: > > https://aws.amazon.com/s3/pricing/ > > > & calculator > > > http://calculator.s3.amazonaws.com/index.html > > > > > > > > > Marcus Denker-4 wrote >>> On 24 May 2018, at 14:19, Sean P. DeNigris < > >> sean@ > >> > wrote: >>> >>> Marcus Denker-4 wrote >>>> We need to think about finding another. >>> >>> I've had success with https://www.siteground.com/ and >>> http://www.namecheap.com for personal hosting, but can't say about bulk >>> downloadingâ¦ >>> >> >> we use OVH, it is a web hosting contract. Maybe we need to use something >> more expensive >> (e.g. machine with certain bandwidth). >> >> Marcus > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

May 24, 2018

Re: [Pharo-dev] Pharo 7 Launch Failure - Freetype Problem?

by Eliot Miranda

Hi Sean, On Sun, May 20, 2018 at 7:53 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Guillermo Polito wrote > > I've just downloaded the image in [3] and was able to open it with some > > old > > vm and with a freshly downloaded stable vm > > Weird. If I open it via CLI with either a fresh stable VM or the one for > Pharo 7 that launcher dl-ed, it works fine, but if I drop the image file > onto the same VM (which is what I did in my OP), it doesn't open. Anyway, > no > big deal if I can open it somehow - just strange! > So this could be a current directory problem. When one launches from the CLI the VM is in the current directory that the shell is in. When one drops an image onto a VM one is in whatever directory the GUI launches desktop apps in. These differ and hence that may cause problems. > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > _,,,^..^,,,_ best, Eliot

May 24, 2018