November 2021 - Pharo-users

Re: Autocomplete typing

by TomaÅ¾ Turk

Hi Guille, I have the same Pharo build, 64-bit on 64-bit Windows 10: I tried it on three different computers with Win10 with the same image. If I get a new image, it behaves the same. Thanks and best wishes, Tomaz ------ Original Message ------ From: "Guillermo Polito" <guillermopolito(a)gmail.com> To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> Sent: 16. 11. 2021 09:59:53 Subject: [Pharo-users] Re: Autocomplete typing >Hi Tomaz, > >Iâm interested in this kind of feedback. >I cannot however reproduce the issue, maybe youâre doing something >else? >Below a GIF showing what happens to me in haro-9.0.0+build.1565 > > >Cheers, >Guille > >>El 15 nov 2021, a las 21:27, tomazz.turk(a)gmail.com escribiÃ³: >> >>Hi, >> >>Yet another question about autocomplete >>:-) >> >>In Pharo 9.0, when you type the first characters of a method selector >>and then choose one of them and press tab or enter, the characters >>that you typed in stay in the editor, but also the method selector is >>repeated in full. Thus, you have to go back and remove unnecessary >>characters to avoid repetition. >> >>Pharo 8.0 is better in this sense, the characters that you typed are >>âtyped overâ by the selection that you make, so the editing is smooth. >> >>Is there anything that can be done? >> >>Best wishes, >>Tomaz >> >

Nov. 16, 2021

UK Smalltalk User Group Meeting - Wednesday 24 November

by Giovanni Corriga

This month, the UKSTUG will take a look at Objective-S ( http://objective.st/ ), an architecture-oriented programming language based on Smalltalk and Objective-C, by hosting his creator Marcel Weheir. As per Alan Kay, âCode seems large and complicated for what it doesâ. Objective-S addresses one source of this accidental complexity: using software architectural abstraction to directly expresses the much wider variety of architectural styles typical of modern software systems, compared to traditional programming languages that still follow the call/return architectural style of scientific programs from the early days of computing. Marcel Weheir ( https://twitter.com/mpweiher ) started his forays into dynamic object-oriented computing by implementing Objective-C on his Amiga 35 years ago and hasnât stopped since. Stops on the way have been at Apple, the BBC, Microsoft and various startups, as well as contributing to Squeak. He is currently a principal software engineer at Citymapper and PhD student at HPI, where he is trying to distill some of the lessons learned from over a quarter century of industry experience into Objective-S. This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/UKSTUG/events/cbklbryccpbgc/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

Nov. 16, 2021

Re: Autocomplete typing

by Guillermo Polito

Hi Tomaz, Iâm interested in this kind of feedback. I cannot however reproduce the issue, maybe youâre doing something else? Below a GIF showing what happens to me in haro-9.0.0+build.1565 Cheers, Guille > El 15 nov 2021, a las 21:27, tomazz.turk(a)gmail.com escribiÃ³: > > Hi, > > Yet another question about autocomplete :-) > > In Pharo 9.0, when you type the first characters of a method selector and then choose one of them and press tab or enter, the characters that you typed in stay in the editor, but also the method selector is repeated in full. Thus, you have to go back and remove unnecessary characters to avoid repetition. > > Pharo 8.0 is better in this sense, the characters that you typed are âtyped overâ by the selection that you make, so the editing is smooth. > > Is there anything that can be done? > > Best wishes, > Tomaz >

Nov. 16, 2021

Autocomplete typing

by tomazz.turk＠gmail.com

Hi, Yet another question about autocomplete :-) In Pharo 9.0, when you type the first characters of a method selector and then choose one of them and press tab or enter, the characters that you typed in stay in the editor, but also the method selector is repeated in full. Thus, you have to go back and remove unnecessary characters to avoid repetition. Pharo 8.0 is better in this sense, the characters that you typed are âtyped overâ by the selection that you make, so the editing is smooth. Is there anything that can be done? Best wishes,\ Tomaz

Nov. 15, 2021

Re: Access to old image / source

by Tim Mackinnon

That is impressive ... good tip for the future. On Fri, 12 Nov 2021, at 11:17 AM, Jupiter Jones wrote: > Wow! Thatâs crazy - it just opened. > > Thanks Dave for the link. It was getting painful digging through changes. > >> On 9 Nov 2021, at 8:31 am, David T. Lewis <lewis(a)mail.msen.com> wrote: >> >> On Mon, Nov 08, 2021 at 07:31:12PM +1100, Jupiter Jones wrote: >>> I have an old image I???d like to recover some code from. >>> >>> When I try to launch in Pharo 2 (from memory it was written in Pharo 2) I get this error: >>> >>> This interpreter (vers. 6505) cannot read image file (vers. 6502). >>> >>> It looks close :) >>> >>> How do I go about finding a VM that will open that image? >>> >>> Thanks in advance. >> >> Hi Jupiter, >> >> You probably can run your old image in a web browser at http://try.squeak.org/ >> Just drag and drop the image, changes and source files onto the web page. >> >> HTH, >> Dave

Nov. 12, 2021

Re: Access to old image / source

by Jupiter Jones

Wow! Thatâs crazy - it just opened. Thanks Dave for the link. It was getting painful digging through changes. > On 9 Nov 2021, at 8:31 am, David T. Lewis <lewis(a)mail.msen.com> wrote: > > On Mon, Nov 08, 2021 at 07:31:12PM +1100, Jupiter Jones wrote: >> I have an old image I???d like to recover some code from. >> >> When I try to launch in Pharo 2 (from memory it was written in Pharo 2) I get this error: >> >> This interpreter (vers. 6505) cannot read image file (vers. 6502). >> >> It looks close :) >> >> How do I go about finding a VM that will open that image? >> >> Thanks in advance. > > Hi Jupiter, > > You probably can run your old image in a web browser at http://try.squeak.org/ > Just drag and drop the image, changes and source files onto the web page. > > HTH, > Dave

Nov. 12, 2021

[ANN] Registration Reminder for Camp Smalltalk

by horrido.hobbies＠gmail.com

Just a reminder to everyone that they should register their presentation at Camp Smalltalk byÂ **March 13**, 2022. Here's the registration link:Â <https://campsmalltalksupreme.wordpress.com/registration-for-presenters/>. Please spread the word. Thanks.

Nov. 9, 2021

One PhD and two internships offers on object-centric debugging at Inria Lille

by Steven Costiou

Hello, Inria Lille is recruiting one phd student and two interns to work on object-centric debugging within the OCRE project (ANR). DESCRIPTION OF THE PROJECT Debugging is difficult and costly. Object-centric debugging is a young technique arguing that focusing the scope of debugging on specific objects considerably eases the tracking and the understanding of hard bugs in Object-Oriented Programs (OOP). But it lacks fundamental bricks to be applicable in practice. Therefore, it has never been empirically evaluated. The objectives of the OCRE project are to study the fundamental and practical limits that hinder the implementation, the evaluation, and the adoption of object-centric debugging. We propose to build the first generation of object-centric debuggers, in order to identify and evaluate its real benefits to OOP debugging. We argue that these debuggers have the potential to drastically lower the cost (time and effort) of tracking and understanding hard bugs in OOP. PHD TOPIC The goal of this PhD is to understand and to achieve the full potential of object-centric debugging by: - identifying the precise scenarios for object-centric debugging, - studying means to obtain objects to debug, - studying the implementation requirements for object-centric debuggers and to implement prototypes, - evaluate empirically object-centric debugging using these prototypes. The full detailed offer is available here: https://jobs.inria.fr/public/classic/fr/offres/2021-04101 INTERNSHIPS These two internships aim at helping the design and the implementation of an object-centric debugger, by unveiling knowledge without which object-centric debuggers cannot be built and evaluated, or cannot be used in practice. Internship 1 - Identifying and acquiring objects to debug The objective of this internship is to study the practical problems of acquiring objects to debug. The intern will characterize the scenarios in which developers need to identify objects to debug and explore these scenarios by implementing prototypes. Internship 2 - Evaluating object-centric debugging scenarios The objective of this internship is to identify and to evaluate the debugging scenarios that are the most likely to benefit from object-centric debugging. The intern will interrogate real developers about object-centric debugging scenarios, then implement prototypes and evaluate them empirically with developers to validate these scenarios. ADMINISTRATIVE DETAILS Location: Lille, France Phd: - starting date: preferably october 2022, but it can start before. - duration: 3 years (fully funded) - the candidate must hold a Master or an equivalent degree Internships: - starting date: anytime - duration: 4-6 months - the candidate must be studying for a Master degree or equivalent (1st or 2nd year, equivalent to M1 or M2 in France)

Nov. 9, 2021

Re: Access to old image / source

by David T. Lewis

On Mon, Nov 08, 2021 at 07:31:12PM +1100, Jupiter Jones wrote: > I have an old image I???d like to recover some code from. > > When I try to launch in Pharo 2 (from memory it was written in Pharo 2) I get this error: > > This interpreter (vers. 6505) cannot read image file (vers. 6502). > > It looks close :) > > How do I go about finding a VM that will open that image? > > Thanks in advance. Hi Jupiter, You probably can run your old image in a web browser at http://try.squeak.org/ Just drag and drop the image, changes and source files onto the web page. HTH, Dave

Nov. 8, 2021

Re: GTPlayground or STPlayground

by Esteban Lorenzano

Hello, Sorry I somehow missed the exchange until now. GTPlayground will be removed and I do not recommend doing any development on top of it. StPlayground is the replacement and is very simple to use and extent. However, to do what you want I didn't think in an "default" way of doing it, and you will need to override a method: StPlaygroundPagePresenter class>>defaultSpec ^ SpBoxLayout newTopToBottom spacing: 3; add: #toolbar expand: false; add: #text; add: #statusbar expand: false; yourself you just need to change it with: StPlaygroundPagePresenter class>>defaultSpec ^ SpBoxLayout newTopToBottom spacing: 3; add: #text; add: #statusbar expand: false; yourself then you will have removed the toolbar. Of course, maybe you do not want to override all playgrounds but just open your version some times. In that case, path is longer (I will think on how to optimise this). To get a "clean" new version of the playground modified you will need to: Extend StPlayground and override newDefaultPlaygroundPage Extend StPlaygroundPage and override defaultObjectInspectorClass Finally, extent StPlaygroundPagePresenter and override defaultSpec there. cheers, Esteban On Nov 8 2021, at 8:43 pm, mspgate(a)gmail.com wrote: > Thanks for your reply Guillermo! > > I think that the GTPlayground is already a good âminimalâ solution for me. But I would like to make it appear without all the button icons on the upper right side > Also, I will start reading the Spec2 book tonight. :0 > peace. > d

Nov. 8, 2021