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

Re: [Pharo-dev] Some segfault crashes and freezes when trying to re-run saved pharo 7 images

by Eliot Miranda

Hi Holger, On Mon, Mar 26, 2018 at 8:32 AM, Holger Freyther <holger(a)freyther.de> wrote: > > > > On 26. Mar 2018, at 00:00, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > > > > Hi Holger, > > Hey! > > > > Is the intent of CCallOut with: aBlock to collect and defer > deallocations until the block completes? I think it's nice but complex and > wonder how general it is. But it seems like it would impact a lot of code > and require a lot of effort changing existing code bases. My handle scheme > is only intended to fix the issue of images crashing on startup. The > problems with crashing on startup being a) one loses one's work and b) the > issue is hard to debug. That, for me, motivates something like the simple > fix I p[roposed. I'm not standing in the way of something more beautiful, > but I do believe that one shouldn't make the perfect the enemy of the good. > > By all means, let's have a smart pointer! It will be beneficial for > freetype and many other places. Nobody likes crashing images (for a mistake > made in a previous run). > > > My intent with the CCallOut is inhibit image saving until the code is > outside a sequence of (interruptible, hence the backward jump int the > example) C calls working with one or more pieces of manually managed > memory. But maybe it is best to call it by what it does instead of finding > a name of where it is used. > > I can't come up with a better example right now. But I think a > Smartpointer wouldn't be of much help with a sequence of strtok calls. > > word := CStringAPI strtok: cStringPtr safeBytes separator: '\r'. > [word isNil] whileFalse: [ > word = 'Foo'... > word = 'Bla'... > word := CStringAPI strtok: nil separator: '\r' > ------------- Image Save happening right here and word is not nil ----- > ]. > > I hope this is more clear. > Right. So the VM could have a flag that, when set, causes the snapshot primitive to fail, and that flag would be cleared only when all FFI cals had unwound. Would that be enough? What would you have the image do if snapshot fails because FFI calls are in progress? > holger > _,,,^..^,,,_ best, Eliot

March 28, 2018

Re: [Pharo-dev] [ANN] HighchartsSt and ba-st Web Stack new versions available

by Sean P. DeNigris

gcotelli wrote > We're happy to announce a new version of the Highcharts JS Wrapper and the > Web Stack hosted at https://github.com/ba-st/. Sounds great, thanks! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 28, 2018

[ANN] HighchartsSt and ba-st Web Stack new versions available

by Gabriel Cotelli

Hi, We're happy to announce a new version of the Highcharts JS Wrapper and the Web Stack hosted at https://github.com/ba-st/. This is a multi-release announcement of the following related project versions: - HighchartsSt <https://github.com/ba-st/HighchartsSt> v6.0.0 - Updated Highcharts and Highstock JS libraries to version 6.0.3 - Improved Importing Tools - Improved Travis CI integration - Willow <https://github.com/ba-st/Willow> v7.0.0. Changes since latest announcement: - Added composition of table row commands - Refactored a bunch of common utilities into it's own project - Improved JSScript extensions - Willow-Bootstrap <https://github.com/ba-st/Willow-Bootstrap> v7.0.0 - Updated Willow base support to v7.0.0 - Improved Radio Web Views - Willow-JQueryUI <https://github.com/ba-st/Willow-JQueryUI> v6.0.0 - Updated Willow base support to v7.0.0 - Improved Radio Web Views - Willow-SpinKit <https://github.com/ba-st/Willow-SpinKit> v4.0.0 - Updated Willow base support to v7.0.0 - Willow-Playground <https://github.com/ba-st/Willow-Playground/> v3.0.0 - Updated dependencies to the latest versions - You can now grab a ready to use image from the releases page - RenoirSt <https://github.com/ba-st/RenoirSt> v4.1.0 - Add another way of creating descendant combinators for cases when the right part of the expression needs parenthesis - Updated dependencies SemanticUI <https://github.com/ba-st/Willow-SemanticUI> and Materialize CSS <https://github.com/fortizpenaloza/Willow-Materialize> integration are still a work in progress. Find a more detailed changelog and migration instructions on the release pages of each repository. Special thanks to Ignacio Martinez <https://github.com/nachomf> and Juan Escalada <https://github.com/JuanEscalada> for contributing some of the new features. Also to Maxi Tabacman and Mariano Martinez Peck for the Highcharts update. Anyone interested in joining our ba-st projects <https://github.com/ba-st/> is welcomed, and you can also get some interesting ideas in crafting lint rules to support team coding standards <https://medium.com/mercap-tech-blog/supporting-team-coding-standards-af2701…> . Regards, Gabriel Cotelli, Maxi Tabacman and all the contributors.

March 28, 2018

[Pharo 7.0-dev] Build #739: 21620-Modularize-Pharo-Launcher-dependent-Baselines

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

There is a new Pharo build available! The status of the build #739 was: SUCCESS. The Pull Request #1130 was integrated: "21620-Modularize-Pharo-Launcher-dependent-Baselines" Pull request url: https://github.com/pharo-project/pharo/pull/1130 Issue Url: https://pharo.fogbugz.com/f/cases/21620 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 28, 2018

[Pharo 7.0-dev] Build #738: 21655-MetaLinks-should-by-default-not-announce-a-MetaLinkChanged-only-when-option-is-set

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

There is a new Pharo build available! The status of the build #738 was: SUCCESS. The Pull Request #1160 was integrated: "21655-MetaLinks-should-by-default-not-announce-a-MetaLinkChanged-only-when-option-is-set" Pull request url: https://github.com/pharo-project/pharo/pull/1160 Issue Url: https://pharo.fogbugz.com/f/cases/21655 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 28, 2018

[Reflectivity] change regarding announcement in Pharo7

by Marcus Denker

Hi, One questionable (but practical) thing that MetaLinks have is that they announce (MetalinkChanged) when they are installed or uninstalled. This is nice for being able to show them in the UI (and e.g. the Watcher implemented with them). But it is very very slowâ¦ so I now made it an option: https://github.com/pharo-project/pharo/pull/1160 <https://github.com/pharo-project/pharo/pull/1160> it is by default off, but can be turned on reflectively at any point. e.g. the link of the execution counter now looks like this: link := MetaLink new metaObject: self; selector: #increase; optionAnnounce: true. It has announcing enable so that the browser refreshes when it gets added or removed. Marcus

March 28, 2018

[Pharo 7.0-dev] Build #737: 21573-Remove-unused-variables-from-Behavior-hierarchy

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

There is a new Pharo build available! The status of the build #737 was: SUCCESS. The Pull Request #1095 was integrated: "21573-Remove-unused-variables-from-Behavior-hierarchy" Pull request url: https://github.com/pharo-project/pharo/pull/1095 Issue Url: https://pharo.fogbugz.com/f/cases/21573 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 28, 2018

Re: [Pharo-dev] Slot Questions

by Marcus Denker

> On 24 Mar 2018, at 21:21, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Stateful traits inspired me to reread the flexible object layout paper and I > came up with a few questions about slots: > - What is the plan for tool support? For example, it seems that to make > slots discoverable like any other class or message, "References to it" > should include class definitions, which should be the primary slot client. Yes, these things need to be done.. I have a very large TODO list for this but it is hard to find time > - Why does IndexedSlot have a #name slot? I thought the index and name were > "either or" for instVars. This is the name of the variable. Even though an init-var is accessed by index, it still has a name (e.g. #x in Point). Marcus

March 28, 2018

Re: [Pharo-dev] Why calypso inverse the hierarchy?

by Denis Kudriashov

Hi Stef 2018-03-27 23:11 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi denis > > Calypso asked me where I want to install a method. > Normally this dialog appears when you edit a method which class is not selected in the browser. For example if you enable superclass method visibility and edit one of inherited methods. But give me your scenario. > And I do not really appreciate that I get the inheritance tree reserved. > There is setting for this. And I am not against to change default value or hardcode this part. Originally it was simple list with selected class at the bottom. Then there was issue The currently edited class should be the first option when overriding methods <https://github.com/dionisiydk/Calypso/issues/163>. Idea that first item should be the most common case which is selected class. At the end I realized that I can easily show hierarchy which I though is better than simple list. And I reused existing hierarchy from method visibility list. So there are two points for this dialog: - do we want selected class to be first? - do we want hierarchical view? Best regards, Denis To me it will destroy students. > On my own code which is super stupid I had to think twice. I cannot > image students. > > Then when working on code that is not ours it is be super difficult to > understand anything. > > How can I set that superclass should be higher than subclasses? > > Stef >

March 27, 2018

Re: [Pharo-dev] Calypso: how to see two different methods (without diff) side by side?

by Denis Kudriashov

Hi Stef. I found very simple way how to support it. So maybe next release if there will be time. Best regards, Denis 2018-03-27 21:15 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi denis > > I do not really use a method diff but I would love to be able to see > two methods > side by side. > > Stef > >

March 27, 2018