- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] State of Pharo in comparison with the "Pharo vision" document

by Esteban Lorenzano

> On 20 Jul 2016, at 10:38, Guille Polito <guillermopolito(a)gmail.com> wrote: > > - 1. Bless the latest VM that has the Ephemeron fixes as stable (Esteban told me he was going to do it but I do not know the state of this). done, two or three weeks ago :P

July 20, 2016

Re: [Pharo-dev] State of Pharo in comparison with the "Pharo vision" document

by Guille Polito

Well maybe this requires an email on its own, but I can give some information on the following points: 1) Bootstrap, Small kernel, and others: - Small kernel & validated packages - Bootstrap of the Core - 64 Bits Well, it's already some time I'm working on this so here there is an executive summary: * We already know how to and can bootstrap pharo images (that is, create a new image from scratch) since some time. * Actually, we have CI jobs dedicated to this since Pharo5. The latest versions are in here: https://ci.inria.fr/pharo/view/Pharo%20bootstrap/job/60-Bootstrap-32bit-Met… https://ci.inria.fr/pharo/view/Pharo%20bootstrap/job/60-Bootstrap-32bit-Min… https://ci.inria.fr/pharo/view/Pharo%20bootstrap/job/60-Bootstrap-64bit-Met… https://ci.inria.fr/pharo/view/Pharo%20bootstrap/job/60-Bootstrap-64bit-Min… You'll see there we are building two different flavors of bootstrap: A minimal bootstrap that does not include Compression nor Monticello, and the default one (that is wrongly entitled Metacello in the CI job) that contains Minimal + Compression + Monticello. These are built in two versions: 32 and 64 bit images, for the respective VMs. And they work. You can download them and play around. You have the eval command line handler and the image is capable of compiling code. ***Disclaimer***: The image works but (a) it's not fully initialized, and (b) it contains a lot of dead code. So, (a) be careful because not everything may work correctly on that image, and (b) happens because it is complicated to remodularize some parts of Pharo => this is what actually takes most of the time from us. * We are working with Pavel and Christophe a lot on it nowadays and our short-term priorities are: - ensure the image initialization - test the bootstrap health (by running lint rulz and unit tests) - be able to reload the entire system on top of the bootstrap AND THIS IS HUGE. This means we need to understand, refactor, express and maintain package dependencies for **every** Pharo package. 2) Announcements and Ephemerons I was working on this lately. Ephemerons are already in the Image but not active. VM support seems to be ready (out of my tests). The roadmap for this is something like this: - 1. Bless the latest VM that has the Ephemeron fixes as stable (Esteban told me he was going to do it but I do not know the state of this). - 2. Activate Ephemerons on the image side - 3. Replace the WeakRegistry by Ephemeron registries. => Here we need to code. Then the other interesting question is if Ephemerons are backported or not to Pharo5. If so, we need to plan how to do it. Then I could also put some words on the other items but I have to go to work now ^^. Cheers, Guille -------- Original Message -------- > On Wed, Jul 20, 2016 at 5:59 AM, Julien Delplanque <julien(a)tamere.eu> wrote: >> Hello everyone, >> >> For a university project I need to write a little about Pharo. >> I found the "Pharo vision" document [1] and I am curious about >> the actual state of Pharo in comparison with it. >> >> I have seen some things on the mailing list but I would like some >> help to gather the state of each goal described in "Pharo vision" >> version 1.0. >> >> I made a list with the goals and wrote some of the (little) knowledge I >> have about some elements (I also joined it to this mail in case it is not >> readable): >> >> Goals -> State >> ------------------- >> 1. Creation of the Pharo Consortium -> Created >> 2. Small kernel & validated packages -> ? >> 3. A Robust and Extensible System Events -> ? >> 4. Rewrite of Filesystem/Streams -> ?/XStream? >> 5. Announcements and Ephemerons -> ? >> 6. UI Canvas for Zoomable Interfaces -> Bloc? >> 7. Bootstrap of the Core -> ? >> 8. Fully parametrized compiler tool chain -> ? >> 9. Packages as real objects -> ? >> 10. Package Meta-Data -> PackageManifest? >> 11. Less Model Clutter and Duplication -> ? >> 12. Building and Reusing UI Logic -> Spec? >> 13. New Network Layer -> ? >> 14. Serializers -> Fuel >> 15. SystemChangeNotifier replacement -> ? >> 16. Cleaning Morphic -> Still valid? (asking because of Bloc existance) >> 17. Everybody should be able to compile VMs -> ? >> 18. VMs identification and regression testing -> ? >> 19. One Unified FFI framework -> Created and still being enhanced >> 20. 64 Bits -> I saw the screenshot on Twitter but what is the state now? >> 21. New Object Formats -> ? >> >> If some of you know the state of one or many of these project and have the >> time to give me some information about it/them, I would be really grateful. >> >> Thanks in advance, >> >> Julien >> >> Links: >> [1]: https://gforge.inria.fr/frs/download.php/30434/PharoVision.pdf > You should be able to get some answers from... > https://github.com/pharo-project/pharo-changelogs > Can you fill in yourself what answers you can extract from that - for > checking, and letting people focus on where there remain gaps in your > questions. > > cheers -ben > > >

July 20, 2016

Re: [Pharo-dev] State of Pharo in comparison with the "Pharo vision" document

by Ben Coman

On Wed, Jul 20, 2016 at 5:59 AM, Julien Delplanque <julien(a)tamere.eu> wrote: > Hello everyone, > > For a university project I need to write a little about Pharo. > I found the "Pharo vision" document [1] and I am curious about > the actual state of Pharo in comparison with it. > > I have seen some things on the mailing list but I would like some > help to gather the state of each goal described in "Pharo vision" > version 1.0. > > I made a list with the goals and wrote some of the (little) knowledge I > have about some elements (I also joined it to this mail in case it is not > readable): > > Goals -> State > ------------------- > 1. Creation of the Pharo Consortium -> Created > 2. Small kernel & validated packages -> ? > 3. A Robust and Extensible System Events -> ? > 4. Rewrite of Filesystem/Streams -> ?/XStream? > 5. Announcements and Ephemerons -> ? > 6. UI Canvas for Zoomable Interfaces -> Bloc? > 7. Bootstrap of the Core -> ? > 8. Fully parametrized compiler tool chain -> ? > 9. Packages as real objects -> ? > 10. Package Meta-Data -> PackageManifest? > 11. Less Model Clutter and Duplication -> ? > 12. Building and Reusing UI Logic -> Spec? > 13. New Network Layer -> ? > 14. Serializers -> Fuel > 15. SystemChangeNotifier replacement -> ? > 16. Cleaning Morphic -> Still valid? (asking because of Bloc existance) > 17. Everybody should be able to compile VMs -> ? > 18. VMs identification and regression testing -> ? > 19. One Unified FFI framework -> Created and still being enhanced > 20. 64 Bits -> I saw the screenshot on Twitter but what is the state now? > 21. New Object Formats -> ? > > If some of you know the state of one or many of these project and have the > time to give me some information about it/them, I would be really grateful. > > Thanks in advance, > > Julien > > Links: > [1]: https://gforge.inria.fr/frs/download.php/30434/PharoVision.pdf You should be able to get some answers from... https://github.com/pharo-project/pharo-changelogs Can you fill in yourself what answers you can extract from that - for checking, and letting people focus on where there remain gaps in your questions. cheers -ben

July 19, 2016

Re: [Pharo-dev] State of Pharo in comparison with the "Pharo vision" document

by Cyril Ferlicot D.

Le 19/07/2016 Ã 23:59, Julien Delplanque a Ã©crit : Hi, I added what I know after some `>>` > Goals -> State > ------------------- > 1. Creation of the Pharo Consortium -> Created > 2. Small kernel & validated packages -> >>In progress (Bootstrap + Cargo) > 3. A Robust and Extensible System Events -> ? > 4. Rewrite of Filesystem/Streams -> ?/XStream? -> >>In progress, there was the introduction of File IIRC > 5. Announcements and Ephemerons -> >> Will be in Pharo 6 > 6. UI Canvas for Zoomable Interfaces -> Bloc? >>I think yes > 7. Bootstrap of the Core -> >>Should be for Pharo 6. The Bootstrap build pass on Jenkins but still need some love from Christophe, Guillermo and Pavel > 8. Fully parametrized compiler tool chain -> >>I think I heard that a lot of progress have been made in this area but I don't have any detail and I am not sure. > 9. Packages as real objects -> >>In progress. now package are objects but there will be improvements with Cargo > 10. Package Meta-Data -> >>PackageManifest > 11. Less Model Clutter and Duplication -> ? > 12. Building and Reusing UI Logic -> >>Spec > 13. New Network Layer -> >> I think this is Zinc but it still need some work > 14. Serializers -> Fuel >> + STON > 15. SystemChangeNotifier replacement -> ? > 16. Cleaning Morphic -> Still valid? (asking because of Bloc existance) > 17. Everybody should be able to compile VMs -> ? > 18. VMs identification and regression testing -> ? > 19. One Unified FFI framework -> Created and still being enhanced > 20. 64 Bits -> Most of the plugins works on OSX/Unix. Esteban told that it would need around a month to be usable after his holydays. > 21. New Object Formats -> >>STON ? > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

July 19, 2016

State of Pharo in comparison with the "Pharo vision" document

by Julien Delplanque

Hello everyone, For a university project I need to write a little about Pharo. I found the "Pharo vision" document [1] and I am curious about the actual state of Pharo in comparison with it. I have seen some things on the mailing list but I would like some help to gather the state of each goal described in "Pharo vision" version 1.0. I made a list with the goals and wrote some of the (little) knowledge I have about some elements (I also joined it to this mail in case it is not readable): Goals -> State ------------------- 1. Creation of the Pharo Consortium -> Created 2. Small kernel & validated packages -> ? 3. A Robust and Extensible System Events -> ? 4. Rewrite of Filesystem/Streams -> ?/XStream? 5. Announcements and Ephemerons -> ? 6. UI Canvas for Zoomable Interfaces -> Bloc? 7. Bootstrap of the Core -> ? 8. Fully parametrized compiler tool chain -> ? 9. Packages as real objects -> ? 10. Package Meta-Data -> PackageManifest? 11. Less Model Clutter and Duplication -> ? 12. Building and Reusing UI Logic -> Spec? 13. New Network Layer -> ? 14. Serializers -> Fuel 15. SystemChangeNotifier replacement -> ? 16. Cleaning Morphic -> Still valid? (asking because of Bloc existance) 17. Everybody should be able to compile VMs -> ? 18. VMs identification and regression testing -> ? 19. One Unified FFI framework -> Created and still being enhanced 20. 64 Bits -> I saw the screenshot on Twitter but what is the state now? 21. New Object Formats -> ? If some of you know the state of one or many of these project and have the time to give me some information about it/them, I would be really grateful. Thanks in advance, Julien Links: [1]: https://gforge.inria.fr/frs/download.php/30434/PharoVision.pdf

July 19, 2016

[pharo-project/pharo-core]

by GitHub

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

July 19, 2016

[pharo-project/pharo-core] 6dc224: 60150

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 6dc224a5c1ded31f5f7680919cf59c7eaded1c75 https://github.com/pharo-project/pharo-core/commit/6dc224a5c1ded31f5f768091… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-19 (Tue, 19 Jul 2016) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60149.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60150.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60149.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60150.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/AbstractWidgetModel.class/README.md M Spec-Core.package/ButtonModel.class/README.md M Spec-Core.package/CheckBoxModel.class/README.md M Spec-Core.package/ComposableModel.class/README.md M Spec-Core.package/ComposableModel.class/instance/instance creation/instantiateModels_.st M Spec-Core.package/DynamicComposableModel.class/README.md M Spec-Core.package/FastTableModel.class/class/example/example.st M Spec-Core.package/IconListModel.class/README.md M Spec-Core.package/IconListModel.class/class/example/example.st M Spec-Core.package/ImageModel.class/README.md M Spec-Core.package/LabelModel.class/README.md M Spec-Core.package/ListModel.class/README.md M Spec-Core.package/MenuGroupModel.class/README.md M Spec-Core.package/MenuItemModel.class/README.md M Spec-Core.package/MenuModel.class/README.md M Spec-Core.package/RadioButtonGroup.class/README.md M Spec-Core.package/RadioButtonModel.class/README.md M Spec-Core.package/SliderModel.class/README.md M Spec-Core.package/TabManagerModel.class/README.md M Spec-Core.package/TabModel.class/README.md M Spec-Core.package/TabModel.class/instance/private/defaultIcon.st M Spec-Core.package/TextInputFieldModel.class/README.md M Spec-Core.package/TextInputFieldModel.class/definition.st M Spec-Core.package/TextModel.class/README.md M Spec-Core.package/TreeModel.class/class/examples/exampleWithCustomColumnsAndNodes.st M Spec-Core.package/TreeModel.class/class/examples/exampleWithCustomColumnsAndNodesAndChildren.st M Spec-Debugger.package/SpecDebugger.class/class/icons/taskbarIcon.st A Spec-Examples.package/CustomerStatisfaction.class/README.md A Spec-Examples.package/CustomerStatisfaction.class/class/example/example.st A Spec-Examples.package/CustomerStatisfaction.class/class/example/exampleDialog.st A Spec-Examples.package/CustomerStatisfaction.class/class/example/exampleNewLayout.st A Spec-Examples.package/CustomerStatisfaction.class/class/specs/defaultSpec.st A Spec-Examples.package/CustomerStatisfaction.class/class/specs/layout.st A Spec-Examples.package/CustomerStatisfaction.class/definition.st A Spec-Examples.package/CustomerStatisfaction.class/instance/accessing/buttonBad.st A Spec-Examples.package/CustomerStatisfaction.class/instance/accessing/buttonHappy.st A Spec-Examples.package/CustomerStatisfaction.class/instance/accessing/buttonNeutral.st A Spec-Examples.package/CustomerStatisfaction.class/instance/accessing/screen.st A Spec-Examples.package/CustomerStatisfaction.class/instance/accessing/title.st A Spec-Examples.package/CustomerStatisfaction.class/instance/initialization/initializePresenter.st A Spec-Examples.package/CustomerStatisfaction.class/instance/initialization/initializeWidgets.st M Spec-Examples.package/DropListExample.class/instance/initialization/initializeWidgets.st A Spec-Examples.package/DynamicalPopup.class/README.md A Spec-Examples.package/DynamicalPopup.class/class/example/exampleAlternativeToolbar.st A Spec-Examples.package/DynamicalPopup.class/class/example/exampleDefaultToolbar.st A Spec-Examples.package/DynamicalPopup.class/definition.st A Spec-Examples.package/DynamicalPopup.class/instance/initialization/alternativeToolbar.st A Spec-Examples.package/DynamicalPopup.class/instance/initialization/defaultToolbarConfiguration.st A Spec-Examples.package/DynamicalPopup.class/instance/initialization/dynamicLayout.st A Spec-Examples.package/DynamicalPopup.class/instance/initialization/initialExtent.st A Spec-Examples.package/DynamicalPopup.class/instance/initialization/initializeWidgets.st M Spec-Examples.package/TabsExample.class/instance/private/browserTab.st M Spec-Examples.package/TabsExample.class/instance/private/dynamicTab.st M Spec-Examples.package/TabsExample.class/instance/private/objectClassTab.st M Spec-Examples.package/TabsExample.class/instance/private/objectInspectorTab.st M Spec-Inspector.package/EyeAbstractInspector.class/class/accessing/taskbarIcon.st M Spec-Inspector.package/EyeTreeInspector.class/instance/api/iconFor_error_.st M Spec-SelectEntity.package/SelectEntity.class/instance/initialization/initializeWidgets.st M Spec-Tools.package/DualChangeSorterApplication.class/class/icons/taskbarIcon.st M Spec-Tools.package/KeymapBrowser.class/class/accessing/taskbarIcon.st M Spec-Tools.package/KeymapBrowser.class/instance/initialization/initializeWidgets.st M Spec-Tools.package/KeymapBrowser.class/instance/private/menu_shifted_.st M Spec-Tools.package/MessageBrowser.class/instance/icons/taskbarIcon.st Log Message: ----------- 60150 18744 Improve class comments https://pharo.fogbugz.com/f/cases/18744 18787 Replace calls at Smalltalk ui icons in subclasses of ComposableModel https://pharo.fogbugz.com/f/cases/18787 http://files.pharo.org/image/60/60150.zip

July 19, 2016

Re: [Pharo-dev] [Ann] Remote debugging tools

by Ben Coman

On Tue, Jul 19, 2016 at 10:30 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2016-07-18 18:26 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > >> I've been meaning to get a BBB. I looks like bit better platform for >> an industrial controller / robotics than the Rpi - in particular its >> Programming Realtime Unit. Knowing someone else has one maybe I'll >> get one now. In the back of my mind I've been considering whether its >> PRU could be modelled as a CPU target for Slang , so Slang could be >> re-purposed from just compiling VM, to compiling embedded programs for >> the PRU, developed from within Pharo and loaded on the fly into the >> PRU. >> > > Do you have link to BBB? (google not helps with such 3 letters). > BeagleBoneBlack. btw here is a nice overview of the PRU... http://beagleboard.org/static/presentations/MakerFaireNY20140920_UsingBeagl… and some videos... http://beagleboard.org/pru cheers -ben > >> >> >> >> >> When I read "Async evaluation ... does not wait for a result" I wonder >> >> if there a particular need for the fork is used here?... >> >> debugger evaluateAsync: [ [1/0] fork ]. >> >> >> > >> > Yes, it looks strange. Now all remote requests are executed such way >> that >> > errors will be returned as SeamlessRemoteException and server signaller >> > process will die. So instead of debugger with failed remote expression >> you >> > will see debugger with local process which performed remote message send >> > (but in case of async evaluation no result will returned to client and >> error >> > will be just ignored). To escape such "exception handler" fork is >> needed. >> > Fork will lead to unhanded error which will ask registered remote >> debugger >> > to debug it. >> >> Could you not just fork at the remote side? >> Perhaps the invocation would be #evaluateFork: >> > > Here is screen which shows "evaluate: [1/0]": > > âNo remote stack here. And on remote side there is no waiting process. > > In future real exception semantics could be supported. In that case > "evaluate: [1/0]" will open debugger with half stack from local process > (doIt from workspace) and half from remote process (where ZeroDivide > happens). > > ("debugger evaluateAsync: [1/0]" will never show any error because result > is not supposed to be returned for async) > >

July 19, 2016

Re: [Pharo-dev] Pharo 5.0 Tiny Feature Request

by Sean P. DeNigris

Sean P. DeNigris wrote > Great. Done. Slice in inbox: > SLICE-Issue-18757-Simple-Shell-Command-Eval-for-50-SeanDeNigris.1 Reviewed by the monkey. Please integrate at your earliest convenience :) https://pharo.fogbugz.com/f/cases/18757/Simple-Shell-Command-Eval-for-5-0 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-5-0-Tiny-Feature-Request-tp4901682p4907129.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 19, 2016

Re: [Pharo-dev] [Ann] Remote debugging tools

by Denis Kudriashov

2016-07-18 18:26 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > I've been meaning to get a BBB. I looks like bit better platform for > an industrial controller / robotics than the Rpi - in particular its > Programming Realtime Unit. Knowing someone else has one maybe I'll > get one now. In the back of my mind I've been considering whether its > PRU could be modelled as a CPU target for Slang , so Slang could be > re-purposed from just compiling VM, to compiling embedded programs for > the PRU, developed from within Pharo and loaded on the fly into the > PRU. > Do you have link to BBB? (google not helps with such 3 letters). > > >> > >> When I read "Async evaluation ... does not wait for a result" I wonder > >> if there a particular need for the fork is used here?... > >> debugger evaluateAsync: [ [1/0] fork ]. > >> > > > > Yes, it looks strange. Now all remote requests are executed such way that > > errors will be returned as SeamlessRemoteException and server signaller > > process will die. So instead of debugger with failed remote expression > you > > will see debugger with local process which performed remote message send > > (but in case of async evaluation no result will returned to client and > error > > will be just ignored). To escape such "exception handler" fork is needed. > > Fork will lead to unhanded error which will ask registered remote > debugger > > to debug it. > > Could you not just fork at the remote side? > Perhaps the invocation would be #evaluateFork: > Here is screen which shows "evaluate: [1/0]": âNo remote stack here. And on remote side there is no waiting process. In future real exception semantics could be supported. In that case "evaluate: [1/0]" will open debugger with half stack from local process (doIt from workspace) and half from remote process (where ZeroDivide happens). ("debugger evaluateAsync: [1/0]" will never show any error because result is not supposed to be returned for async)

July 19, 2016