- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #843: Opal: compiler shoud not copy AST for pluging

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

There is a new Pharo build available! The status of the build #843 was: SUCCESS. The Pull Request #4858 was integrated: "Opal: compiler shoud not copy AST for pluging" Pull request url: https://github.com/pharo-project/pharo/pull/4858 Issue Url: https://github.com/pharo-project/pharo/issues/OpalPluginNoASTCopy Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 8, 2019

[Pharo 8.0] Build #842: use #lookupVar: instead of #lookupVarForDeclaration:

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

There is a new Pharo build available! The status of the build #842 was: SUCCESS. The Pull Request #4851 was integrated: "use #lookupVar: instead of #lookupVarForDeclaration:" Pull request url: https://github.com/pharo-project/pharo/pull/4851 Issue Url: https://github.com/pharo-project/pharo/issues/useLookupVar Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 8, 2019

[Pharo 8.0] Build #841: Opal: remove #variableNamed:

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

There is a new Pharo build available! The status of the build #841 was: FAILURE. The Pull Request #4853 was integrated: "Opal: remove #variableNamed:" Pull request url: https://github.com/pharo-project/pharo/pull/4853 Issue Url: https://github.com/pharo-project/pharo/issues/Opal Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 7, 2019

[ANN] Roadmap progress report. September 2019

by Esteban Lorenzano

Hi all, Since some time we wanted to start with this report to keep you all informed on what we are doing to achieve our goals for the release. After ESUG we took some time to organise and we managed to put this in movement. The idea is to post one the first week of each month (but it may vary, as you see with this one who came a bit later :P) Actions reportes are just dots, since we do not have the time to add a big explanation and we hope you are already involved and more or less know what we are talking about. But do not hesitate to ask if you want more details :) Roadmap progress report. September 2019 Image Code Loading Profiling the time spent to load code Reimplementing a better Read/Write Buffered Stream Improving the performance of Source writing and reading, Improving in at least 20% the time of loading code using Metacello. Spec 2 Pass on SpMillerColumnPresenter to made it of general use. Implement a specific SpMillerLayout to handle Miller columns. Pass on regular input ports (transmissions subsystem) to implement activation ports. Pass on SpStyle subsystem (kind of STON based stylesheets for Morphic). Fix SpGridLayout horizontal cell calculous. (It was broken). Fix SpBoxLayout berderWith and padding. (It was broken). Added contextual menus to widgets. This functionality was completely revamped to make it work in all backends. It was generalised to all widgets (even if not all should use it!) Added focus order to presenters. This is also a full revamp of old existing functionality. it accepts you to change the default order, but it has a default order (previous implementations forced you to do the focusing by hand). Added key binding support for all widgets. This is also a full revamp of old exiting functionality. Spec2+GTK3 callbacks can now be chained. This requires some explanation: In Gtk3 you connect to signals. And you can connect just one callback to one signal. Thankfully we control the callbacks in our side, so we modified signal callbacks to accept to chain other callbacks (then we can connect several actions to one single event, for example "keypress" or âhide"). along with this, we reworked the callback hierarchy. implemented inheritance in Pharo of Gtk3 objects and interfaces (this is needed to enhance control of tables and many others). added autocompletion capabilities to SpCodePresenter. added a mechanism to avoid duplicate signalling between the backend and the adaptors. Fix an important leak on GtkFormView. NewTools Inspector it now implements Miller columns Using TaskIt as backend for stepping. extensions migrated (we are at 10% of the total of migrations needed, we will enhance this in iterative way). Debugger Almost complete revamp of UI. Fix context updating (to allow commands to actually work) Integrate new inspector. Work on new layouts for debugger Make an experimental tool: "playbook", to concentrate playgrounds and test some UI ideas. UFFI Adding Tests Support for kind of literals and support type definitions in literals Documentation Measuring performance issues on large images. TaskIT Implement a prototype of a distributed backend to execute tasks. Implement a communication layer using Rabbit MQ Implement the first version of a process manager for handling multiples images and workers. VM Fixing problem with LibGIT and Windows 1903. Fixing the performance issues of Windows 1903 with File accesses when using solid-state 4k physical sector disks. XCode integration Adding an initial version to detect invalid order in the return from concurrent callbacks. Improving the implementation of TFFI to run 50% faster in callouts. Build of StackVM

Oct. 7, 2019

[Pharo 8.0] Build #840: Simplify morph creation from Athens surface

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

There is a new Pharo build available! The status of the build #840 was: SUCCESS. The Pull Request #4846 was integrated: "Simplify morph creation from Athens surface" Pull request url: https://github.com/pharo-project/pharo/pull/4846 Issue Url: https://github.com/pharo-project/pharo/issues/4517 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 7, 2019

[Pharo 8.0] Build #839: Document and Improve TempVector Access

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

There is a new Pharo build available! The status of the build #839 was: SUCCESS. The Pull Request #4844 was integrated: "Document and Improve TempVector Access" Pull request url: https://github.com/pharo-project/pharo/pull/4844 Issue Url: https://github.com/pharo-project/pharo/issues/ImproveTempVectorAccess Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 7, 2019

[Pharo 8.0] Build #838: Remove `bounds` ivar from AthensBalloonPath

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

There is a new Pharo build available! The status of the build #838 was: SUCCESS. The Pull Request #4842 was integrated: "Remove `bounds` ivar from AthensBalloonPath" Pull request url: https://github.com/pharo-project/pharo/pull/4842 Issue Url: https://github.com/pharo-project/pharo/issues/4549 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 7, 2019

[Pharo 8.0] Build #837: Rename "Move to class package" to "Move to the defining class"

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

There is a new Pharo build available! The status of the build #837 was: FAILURE. The Pull Request #4841 was integrated: "Rename "Move to class package" to "Move to the defining class"" Pull request url: https://github.com/pharo-project/pharo/pull/4841 Issue Url: https://github.com/pharo-project/pharo/issues/4451 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 6, 2019

about common command

by ducasse

Hi I played a bit to turn smart suggestion actions into commander2 commands. It works :). Now with CM2 we do not have to have a class per command. We can create an instance. Now I was wondering what we prefer - using classes + we can dispatch later (for example suggestions dispatch on nodes message to register to specific AST node and the new behavior can be plugged modularly using extension + free registration - we create one class per command - using instances + no need to create one class. - we need to build a registration and query mechanism - extension will require to change or annotate somehow the created instances . So I have the impression that using classes is better. Setf

Oct. 6, 2019

Re: [Pharo-dev] Easy first issues for Pharo contributors?

by Cyril Ferlicot

On Sun 6 Oct 2019 at 16:12, James Foster <Smalltalk(a)jgfoster.net> wrote: > All good suggestions. I especially like the executable examples idea since > that will demonstrate understanding of the code but still be easy to > describe and easy to confirm. Thanks! > Hi, Adding method, class and package comments is also simple and great for the community :) > > > -- Cyril Ferlicot https://ferlicot.fr

Oct. 6, 2019