April 2020 - Pharo-users - lists.pharo.org

[ANN] RewriteTool has successfully ported to Spec2
by stephan April 8, 2020

April 8, 2020

Thanks. I've done a PR and also one in Matchtool Stephan

1 0

Re: [Pharo-users] [Pharo-dev] Cover for PBE8
by Sven Van Caekenberghe April 8, 2020

April 8, 2020

Not bad at all, made me smile. > On 7 Apr 2020, at 12:21, Nicolas Anquetil <nicolas.anquetil(a)inria.fr> wrote: > > > :-) > > > > > On Tue, 2020-04-07 at 09:45 +0200, StÃ©phane Ducasse wrote: >> Hello >> >> We are working on PBE80 and we are looking for a new cool cover. >> If you think that you can do this we are all ears. >> >> S >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> 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 >> > -- > Nicolas Anquetil > RMod team -- Inria Lille > <pbe.png>

2 1

Hi-DPI Support
by Steffen MÃ¤rcker April 7, 2020

April 7, 2020

Hi, I'd like to ask about the state of Hi-DPI support for Pharo. I already found two related GitHub issues which where inconclusive so far. Does the discussion take place elsewhere? If so, where? If not: - What is the current state? - Does a plan exist how to get there? - What are the missing pieces? - How can I support this endeavor in practice? Best, Steffen

4 5

Can't able to understand the code
by shawon58 April 7, 2020

April 7, 2020

I try to run the code which attached below. But i dont have idea what i need to write on playground to run the code. can anyone explain what happen actually using this class>>primImage: aFormat width: aWidth height:aHeight <http://forum.world.st/file/t372453/prob.png> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

2 1

Re: [Pharo-users] [Pharo-dev] Cover for PBE8
by Tim Mackinnon April 7, 2020

April 7, 2020

Not an artist, and shamefully ripping off Nicolas, but how about something future lookingâ¦ > On 7 Apr 2020, at 11:21, Nicolas Anquetil <nicolas.anquetil(a)inria.fr> wrote: > > > :-) > > > > > On Tue, 2020-04-07 at 09:45 +0200, StÃ©phane Ducasse wrote: >> Hello >> >> We are working on PBE80 and we are looking for a new cool cover. >> If you think that you can do this we are all ears. >> >> S >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> 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 >> > -- > Nicolas Anquetil > RMod team -- Inria Lille > <pbe.png>

3 2

[ANN] RewriteTool has successfully ported to Spec2
by Juan Pablo Sandoval Alcocer April 6, 2020

April 6, 2020

Dear friends, I would like to announce that Sebastian, an intern of my company, just ported the RewriteTool to Spec2. You may find the install instructions in the following link :) https://github.com/jordanmontt/RewriteTool-Spec2 Please, help us to test it, any feedback is welcome. Regards, Juan P. SEMANTICS SRL http://semantics.bo/ https://jpsandoval.github.io/

1 0

Re: [Pharo-users] Latest PharoJS Success Story; Wasm/WASI; very keen on Pony for the Pharo VM
by Shaping April 6, 2020

April 6, 2020

All: > Brain Treats got stuck during launch on my LG. > Which android version are you using ? The phone is old and this is likely the problem. Android version: 4.4.2 Kernel version: 3.4.0 > Is there a plan to move PharoJS to Wasm/WASI? > Dave and I talked about it a long time ago. This sounds like a good idea. Actually, Dave has a very ambition idea = turn PharoJS into Pharo* where * can be different targets. But, there's a lot to do before reaching this goal. So, don't expect it any time soon. Not to change the topic too much, but the following is related and I often think of it. Consider writing the pharo VM in Wasm or, better, with Pony (which can emit Wasm, as needed). Pony's reference-capability-based (ref-cap) concurrency-model guarantees provably that no data-races or deadlocks can happen if the code compiles; this solves a very large class of extremely ugly concurrency problems that no one ever wants to face. Pony gives high-performance concurrency (5 to 15 ns actor-thread switching time, depending on platform), and solves the most difficult class of synchronization problems at compile time. It runs as fast as C. It runs faster than C, as concurrency scales. You can't scale a highly concurrent app efficiently in C, and really shouldn't try if you wish to remain happy and mentally healthy. Pony is still pre-1.0, but the group is very active and competent. I think we should consider using it to build the VM. Have a look. Some videos for your amusement and information: https://www.youtube.com/watch?v=ODBd9S1jV2s https://www.youtube.com/watch?v=u1JfYa413fY https://www.youtube.com/watch?v=fNdnr1MUXp8 https://www.ponylang.io/ There are many others. I mentioned the Pony concurrency architecture around the holidays, but there was no interest from the list-not a good time perhaps. The tentative plan is to do what Google does with Flutter: have the JIT in support of the usual dynamicity a Smalltalker needs for rapid development; and have AOT, fully optimized compiling for production or speed-related reality checks, presumably needed less often during development. There are other possibilities. Anyone interested? I have some ideas for simplifying use of the six ref caps in the context of Pharo/Smalltalk. If this path is chosen, one must commit to strict state-machine-based algorithm development, without exception. This should have happened anyway by now, broadly in the programming space, but didn't. I'm working on a programming graphical tool and associated grammar (in VW) that make state-machine development easy and attractive. This , besides efficient use of machine resources, is the other reason for pushing in this direction. A Pony program is built from a net of asynchronously communicating actors. You change the state of your program with asynchronous messaging between actors. There is no blocking--no mutexes or semaphores-and therefore no wasted CPU cycles or mushrooming program complexity, as you try to use mutexes in a fine-grained way (a very bad idea). And as mentioned, there are never deadlocks or data-races. All cores on all CPUs stay busy, always, until the program goes idle or exits. The Pony group is also working on extending the model to the network level, so that all machine nodes in the network stay busy. In the round, as a start, think of Pony as Erlang/OTP, but much faster, with no legacy bugs, and provably no-deadlocking on compile. The asynchronous actor model is the programming pattern that Kay had in mind when he said "object-oriented." It's the one I want to implement in Pharo. The green threads are light, but don't efficiently use the cores, and a net of VMs with their respective images still communicate too slowly. I your time permits, please study Pony for a bit, before rejecting the idea as too big a change in direction or too complicated. Using Pony looks like the ideal VM simplification strategy, if our aim is efficient use of networks of machines, each with at least one CPU (often more), each, in turn, with many cores (whose numbers are still increasing). This pattern in hardware probably won't be changing much, now that speeds are topping out. Winning the performance game is therefore about efficiently using many cores at once, without burdening the programmer. I don't see a better way to do this now than with Pony. Thoughts and suggestions are welcome. Shaping > -----Original Message----- > From: Pharo-users [ <mailto:pharo-users-bounces@lists.pharo.org> mailto:pharo-users-bounces@lists.pharo.org] On > Behalf Of N. Bouraqadi > Sent: Tuesday, 28 January, 2020 12:18 > To: Any question about pharo is welcome < <mailto:pharo-users@lists.pharo.org> pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] Latest PharoJS Success Story > > The latest PharoJS-powered smartphone app is now live. > Development has been made using Pharo. > Then, javascript code is generated using PharoJS. > Last, the app is built to target both iOS and Android thanks to Apache > Cordova. > > Learn more and Download at > <https://nootrix.com/projects/brain-treats-app/> https://nootrix.com/projects/brain-treats-app/ > > Noury > >

2 1

Re: [Pharo-users] Test Completion has been added to Pharo 8 - please test!
by shaunalan April 6, 2020

April 6, 2020

sdfsdfdsf -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

Re: [Pharo-users] Test Completion has been added to Pharo 8 - please test!
by shaunalan April 6, 2020

April 6, 2020

The sale was moving along smoothly for Redondo Beach-based land agent App Design Companies <https://www.cmolds.com/> , mobile game apps development <https://www.cmolds.com/game-app-development> and her client earlier this month until the COVID-19 pandemic and stay-at-home orders hit. a few of weeks into escrow, the customer dropped out and Martini scrambled to seek out a replacement. âIt was due to the coronavirus and therefore the fear and instability of whatâs to return ,â said Martini, a Movoto agent. âThe buyer backed out due to job instability. With the stock exchange tanking and thousands of layoffs, most are quite afraid to form the move.â -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

What Effect Will COVID-19 and the Stay-At-Home Order Have on the Real Estate Market?
by shaunalan April 6, 2020

April 6, 2020

The sale was moving along smoothly for Redondo Beach-based land agent App Design Companies <https://www.cmolds.com/> , mobile game apps development <https://www.cmolds.com/game-app-development> and her client earlier this month until the COVID-19 pandemic and stay-at-home orders hit. a few of weeks into escrow, the customer dropped out and Martini scrambled to seek out a replacement. âIt was due to the coronavirus and therefore the fear and instability of whatâs to return ,â said Martini, a Movoto agent. âThe buyer backed out due to job instability. With the stock exchange tanking and thousands of layoffs, most are quite afraid to form the move.â -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0