January 2021 - Pharo-users - lists.pharo.org

What is the practice to update Pharo 9 image during development

by Sanjay Minni

Hi What is the good practice to update Pharo 9 images that are being released while I am developing code for my application. Currently make a fresh install, reload all required packages (Seaside, Magritte ...), reload my code, configure blah blah .... is there a better way ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 27, 2021

Re: Why does Iceberg duplicate my Project when loading a baseline?

by Sanjay Minni

it has been happening, I have raised an issue in https://github.com/pharo-vcs/iceberg/issues/1404 On Wed, 27 Jan 2021 at 04:30, Tim Mackinnon <tim(a)testit.works> wrote: > Hi guys - its been a while since Iâve had chance to code in Pharo - but I > found a moment to pick up an old project - but when I load it into a fresh > P8 image using a baseline - it seems to duplicate my project in iceberg? > Whats up with that - is this a regression, or is it something abnormal > about my project? > > -- --- Sanjay Minni +91-9900-902902

Jan. 27, 2021

Re: Is there a way to load a dependent repository of assets that doesn't have a baseline - in my Metacello baseline?

by HernÃ¡n Morales Durand

You mean something like this? https://github.com/hernanmd/MetacelloFileDownload El mar, 26 ene 2021 a las 23:57, Tim Mackinnon (<tim(a)testit.works>) escribiÃ³: > Hi - Iâm trying to create a baseline for my project so that it includes a > dependent repository that has some assts but no code. Is there a way to do > this in Metacello - I have a baseline dependencies like the following - and > its the last line that fails as it not really a repo with a baseline in it > - so Metacello signals an error - but Iâm wondering if there is something I > can do to just load that repo without considering it as a baseline - Iâm > after something like: > > spec resources: 'CP-ClientEnvironment' with: [ spec > repository: > 'github://ErikOnBike/CP-ClientEnvironment' ]. > > > This is what I have to give an idea - possibly I could catch the exception > and resume - or is there some cunning way (maybe even a post load script or > something)? > > setUpDependencies: spec > > spec > baseline: 'ZincHTTPComponents' with: [ spec > repository: 'github://svenvc/zinc'; > loads: #('Core' 'WebSocket') ]. > > spec > baseline: 'CodeParadise' with: [ spec > repository: > 'github://ErikOnBike/CodeParadise/repository' ]. > > spec > baseline: 'CP-ClientEnvironment' with: [ spec > repository: > 'github://ErikOnBike/CP-ClientEnvironment' ]. > > > > > Tim > >

Jan. 26, 2021

Why does Iceberg duplicate my Project when loading a baseline?

by Tim Mackinnon

Hi guys - its been a while since Iâve had chance to code in Pharo - but I found a moment to pick up an old project - but when I load it into a fresh P8 image using a baseline - it seems to duplicate my project in iceberg? Whats up with that - is this a regression, or is it something abnormal about my project?

Jan. 26, 2021

Is there a way to load a dependent repository of assets that doesn't have a baseline - in my Metacello baseline?

by Tim Mackinnon

Hi - Iâm trying to create a baseline for my project so that it includes a dependent repository that has some assts but no code. Is there a way to do this in Metacello - I have a baseline dependencies like the following - and its the last line that fails as it not really a repo with a baseline in it - so Metacello signals an error - but Iâm wondering if there is something I can do to just load that repo without considering it as a baseline - Iâm after something like: spec resources: 'CP-ClientEnvironment' with: [ spec repository: 'github://ErikOnBike/CP-ClientEnvironment' ]. This is what I have to give an idea - possibly I could catch the exception and resume - or is there some cunning way (maybe even a post load script or something)? setUpDependencies: spec spec baseline: 'ZincHTTPComponents' with: [ spec repository: 'github://svenvc/zinc'; loads: #('Core' 'WebSocket') ]. spec baseline: 'CodeParadise' with: [ spec repository: 'github://ErikOnBike/CodeParadise/repository' ]. spec baseline: 'CP-ClientEnvironment' with: [ spec repository: 'github://ErikOnBike/CP-ClientEnvironment' ]. Tim

Jan. 26, 2021

Re: Magritte Meta Data at work - Tutorial a clarity reqd

by StÃ©phane Ducasse

probably a mistake :( send a PR when you find the solution. > On 26 Jan 2021, at 10:31, Sanjay Minni <sm(a)planage.com> wrote: > > From pg 16 of "meta data at work with Magritte - Tutorial", Stef > > how are these to be entered since both method codes are in the same object > and methodName > > MAAddress >> descriptionEndDate > > ^ MADateDescription new > accessor: #endDate; > label: 'End Date'; > addCondition: [ :value | value > Date today ]; > beRequired; > yourself > > MAAddress >> descriptionEndDate > > ^ super descriptionContainer > addCondition: [ :object | > (object readUsing: self descriptionEndDate) > > (object readUsing: self descriptionStartDate)] > labelled: 'End date must be after start date'; > yourself > > > > ----- > cheers, > Sanjay > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Jan. 26, 2021

Re: join

by StÃ©phane Ducasse

Hello and welcome Yuriy can you tell us what is your problem? S > On 26 Jan 2021, at 12:32, Yuriy Babah <babah.yuriy06(a)gmail.com> wrote: > > FFIStructure questions: > following page 40 of the 2020-02-12-uFFI-V1.0.1.pdf booklet: > > FFIStructure subclass: #RsnStructure > instanceVariableNames: '' > classVariableNames: '' > package: 'LiraRSN' > > RsnStructure class >> fieldsDesc [ > ^ #( > int ke; > int node; > float rz; > float x; > float y; > ) ] > > RsnStructure rebuildFieldAccessors >> resulted: > > "Instance of RsnStucture class did not undestand #readStream", > in FFIExternalStructureFieldParser class >> parseField:structure: > <LiraRSN.st> -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Jan. 26, 2021

Re: Happy New Year and Pharo 90 good news.

by Offray Vladimir Luna CÃ¡rdenas

Congratulations! It makes me happy and proud to be part of this community in the big efforts like this one and in the small interactions, like answers and good wishes in mail and cha. Seems a good call for rewriting Grafoscopio's UI from scratch in Spec2, as now I have a better grasp of Pharo and first code writing, while learning to code, while making the PhD, while making the internship, was like a crazy party code writing methodology. Cheers, Offray On 25/01/21 6:26 a.Â m., StÃ©phane Ducasse wrote: > Dear happy Pharoers, > > First we wish you a good 2021 year. We really hope that we will get > out of this situation. > > On the Pharo side we have excellent news.Â > > Pharo 90 is continuing to follow its roadmap and it will be another > version a massive amount ofÂ > improvements. We will mention them in the Pharo 90 announce but we can > cite a few: Spec2, new tools, new debugger framework, > better parser, general speedup, new optimisations, full block and > clean block closures, support for large images, new fluid class > syntax, ... > > The Â key and important advance is that the VM roadmap is delivering. > We have been working on the implementation of a MIT-licensed ARMv8 > Just-In-Time compiler for Â Pharo VM. We are Â very happy with the > Â advance on this subject, as Â we have not only implemented a new > backend but weÂ > added more than 2500 tests Â to the JIT, the primitives, code > generation, plugins and the VM in general. In the process we fixed > many problems.Â > We are currently fixing ephemerons since they never really worked in > Pharo. We are stressing the infrastructure with more than 50000Â > ephemerons. Also, we are improving and cleaning up the primitive > invocation scheme to fix heap corruption issues, and fixing many open > issues in the VM.Â > Finally, we are working a lot to have a reproducible build in all the > platforms and easing the path to VM development,Â > we are still far from our objective but the improvements are starting > to show. > > We are happy that following the roadmap that was decided during > General assembly Â of PharoDays is successful. > We have been investing in the Pharo VM and that our efforts are > greatly paying off. > > This is the current status around the VM > - We implemented a full backend for the JIT compiler targeting Â ARMv8 > (AARCH64) > - We launched the beta version for Windows, Linux and raspberry of the > new 64 JIT ARM. > - We are waiting to receive a new mac machine to be able to test our > new JIT on it. > - All the image side was adapted to run on it, tested on Ubuntu ARM 64 > bits and Windows ARM. > - We have support for all third party libraries in these platforms: > Iceberg (Libgit) / Athens (Cairo) / SDL / GTK. > - We implemented a LibFFI-based FFI backend as the default one for > Pharo 9 in aarch64 (It is also present in other platforms, keeping the > existing one as fallback, e.g. used when the VM is not the latest). > - We revisited the complete compilation chain on Windows to use CMake > and avoid Cigwin dependency. > - We are starting to use OBS to build for multiple Unix and Linux > distributions (Debian-like is Done, More distributios to come).Â > - Many bugs on the VM have been fixed, for all these bugs tests have > been written to detect regressions and to to document the solution. > - We are always performing clean-ups of the VM base code: removing > dead-code and experiments from the main branch. All removed code is > kept in the history and it is accessible to revisit or to improve to > the level that is required to be integrated (e.g., Newspeak Support, > Lowcode) > - We improved the implementation of Windows Network primitives, and we > have done a clean-up of the event handling code allowing an IDLE VM. > - We are starting to improve the JIT compiler. We are applying some > approaches developed in modern compiler such as bloc representation. > - We are working in statistics collection to characterize the behavior > of different components of the VM. > - We are planning to generate a set of benchmarks that correctly > represents the workload of applications using the VM (e.g, Web Server, > Interactive Applications, FFI intensive applications). > > It means that in the near future we expect to be able to improve even > more our VM applying a scientific approach: measure, assess, improve. > - We expect that for Pharo 10, we will continue to clean the VM code > and be more agile. > - We will able to look again at Sista. > All these steps show that we are in much better situation. We > drastically reduce the truck factor around the VM. > It particularly means that the consortium now does not depend of the > good will and knowledge of other people. > > We want to thank every member of the consortium.Â > Now we have a particular thank to Lifeware that renewed their contract > and Schmidt Buro for their original contract.Â > > A last word â do not hesitate to contact us, we are here to help you > growing your business. > > S. Ducasse on the behalf of the Pharo consortium > > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > <http://stephane.ducasse.free.fr>Â /Â http://www.pharo.org > <http://www.pharo.org>Â > 03 59 35 87 52 > Assistant: Aurore DalleÂ > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley,Â > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr> / > http://www.pharo.org <http://www.pharo.org>Â > 03 59 35 87 52 > Assistant: Aurore DalleÂ > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley,Â > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France >

Jan. 26, 2021

Re: join

by Yuriy Babah

ran on Pharo 8.0x64 on Windows 10

Jan. 26, 2021

Re: join

by Yuriy Babah

*FFIStructure questions*: following page 40 of the 2020-02-12-uFFI-V1.0.1.pdf booklet: FFIStructure subclass: #RsnStructure instanceVariableNames: '' classVariableNames: '' package: 'LiraRSN' RsnStructure class >> fieldsDesc [ ^ #( int ke; int node; float rz; float x; float y; ) ] RsnStructure rebuildFieldAccessors >> resulted: "Instance of RsnStucture class did not undestand #readStream", in FFIExternalStructureFieldParser class >> parseField:structure:

Jan. 26, 2021