- Pharo-users - lists.pharo.org

Re: Recovering old images in mac

by Noury Bouraqadi

Insead of loading an image, try dropping the .change file on an another running image. This will open the change browser that allow explore/load the code. Noury On Oct 30 2022, at 2:15 pm, Pierre Misse Chanabier <pierre.misse-chanabier(a)inria.fr> wrote: > Carolina use to be able to do this during her PhD. > Always assumed it was with Espell, but I have never tried. > > https://github.com/carolahp/espell2 > Pierre > On 10/30/2022 11:30 AM, Steffen MÃ¤rcker wrote: > > Is there a way to save / convert such an image to 64 Bit? > > > > Best, Steffen >

Oct. 30, 2022

Re: Recovering old images in mac

by Pierre Misse Chanabier

Carolina use to be able to do this during her PhD. Always assumed it was with Espell, but I have never tried. https://github.com/carolahp/espell2 Pierre On 10/30/2022 11:30 AM, Steffen MÃ¤rcker wrote: > Is there a way to save / convert such an image to 64 Bit? > > Best, Steffen

Oct. 30, 2022

Re: Recovering old images in mac

by Steffen MÃ¤rcker

Is there a way to save / convert such an image to 64 Bit? Best, Steffen

Oct. 30, 2022

Re: Recovering old images in mac

by Jupiter Jones

I had a similar issue since you can no longer run 32bit application on MacOS. So, easiest solution is to run a Linux VM and open it there. You may also be able to open an older image on: http://try.squeak.org/ <http://try.squeak.org/> Though that server doesnât seem to be online at the moment. Best of luck. Cheers, J > On 30 Oct 2022, at 7:52 pm, Arturo Zambrano <arturo.zambrano(a)gmail.com> wrote: > > > Hi Everyone, > I have some old images (around 2017) that I would like to load. > Pharo Launcher downloaded a VM but while trying to launch it > complains with the following message. > > Error: Error: posix_spawn(), code: 86, description: Bad CPU type in executable > > Which is the same message I get when trying to use the VM I found in a backup of that time. > > Is there a way of opening such an old image in MacOs Monterrey (running on top of the same machine this image was originally built)? If I am not mistaken it is Pharo 6. > > Best regards > Arturo > > > > -- > Arturo Zambrano > LinkedIn: https://www.linkedin.com/in/arturozambrano/ <https://www.linkedin.com/in/arturozambrano/>

Oct. 30, 2022

Recovering old images in mac

by Arturo Zambrano

Hi Everyone, I have some old images (around 2017) that I would like to load. Pharo Launcher downloaded a VM but while trying to launch it complains with the following message. Error: Error: posix_spawn(), code: 86, description: Bad CPU type in executable Which is the same message I get when trying to use the VM I found in a backup of that time. Is there a way of opening such an old image in MacOs Monterrey (running on top of the same machine this image was originally built)? If I am not mistaken it is Pharo 6. Best regards Arturo -- Arturo Zambrano LinkedIn: https://www.linkedin.com/in/arturozambrano/

Oct. 30, 2022

Re: How to handle conflict resolution in baselines?

by Jonathan van Alteren

Hi Eric, This is something I ran into a while ago as well. Since then, I load all my (top level) project baselines using #onConflictUseLoaded. So in your case, I would load Profeos with something like the following: Metacello new repository: 'github://ericbmerritt/profeos:main'; baseline: 'Profeos'; onWarningLog; onConflictUseLoaded; load. Does that work for you? Kind regards, Jonathan van Alteren Guild Member | Object Guild Software that works with you jonathan(a)objectguild.com On 25 Oct 2022, 00:42 +0200, Eric Merritt <eric(a)merritt.tech>, wrote: > Everyone, > > Â In a baseline in a project I am working on I have a dependency on both Magritte and Seaside. Magritte loads fine, but when Seaside loads, Monticello declares a conflict on the Grease package. You can see the WIP baseline here: https://github.com/ericbmerritt/profeos/tree/feat/working-goals/BaselineOfP…. > > So far, I haven't found a solution to resolve conflicts in the spec. The closest solution I have found is here: https://github.com/CCMi-FIT/kendrick-modeller/blob/9c76ff8170c67d5472cc1e1b… > > It works but seems to be stepping out of the declarative form of baseline definition. Is there another solution? > > Thanks, > Eric

Oct. 27, 2022

Re: [Ann] Bloc v1.0

by StÃ©phane Ducasse

> On 26 Oct 2022, at 13:25, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi all > > At ESUG and after about a year of development, the Pharo consortium was happy to announce > a first version of the Bloc graphics framework as available in > > https://github.com/pharo-graphics/bloc <https://github.com/pharo-graphics/bloc> > > Here is the video of the ESUG presentation > > https://rmod-files.lille.inria.fr/Videos/2022-ESUG/Day2/2f-esug-v3.mp4 <https://rmod-files.lille.inria.fr/Videos/2022-ESUG/Day2/2f-esug-v3.mp4> > > We are now opening the internal mailing-list and feel free to join. > We will be soon describing the roadmap for the next 6 months. > > https://sympa.inria.fr/sympa/info/lse-bloc <https://sympa.inria.fr/sympa/info/lse-bloc> In fact > https://sympa.inria.fr/sympa/info/lse-openbloc <https://sympa.inria.fr/sympa/info/lse-openbloc>

Oct. 26, 2022

[Ann] Bloc v1.0

by stephane ducasse

Hi all At ESUG and after about a year of development, the Pharo consortium was happy to announce a first version of the Bloc graphics framework as available in https://github.com/pharo-graphics/bloc <https://github.com/pharo-graphics/bloc> Here is the video of the ESUG presentation https://rmod-files.lille.inria.fr/Videos/2022-ESUG/Day2/2f-esug-v3.mp4 We are now opening the internal mailing-list and feel free to join. We will be soon describing the roadmap for the next 6 months. https://sympa.inria.fr/sympa/info/lse-bloc <https://sympa.inria.fr/sympa/info/lse-bloc> S

Oct. 26, 2022

Re: mapping CamelCase to <custom-tag-name>

by Kasper Osterbye

> > What's wrong with > > $- join: (s cutCamelCase collect: [ :each | each asLowercase]) There is no method called cutCamelCase in Pharo. If there was, this was exactly the right solution to use something existing. Best, Kasper

Oct. 26, 2022

Re: mapping CamelCase to <custom-tag-name>

by Richard O'Keefe

The important thing is that there is no NEED to write a new method to split a Smalltalk identifier into pieces, because there already *IS* such a method. Only write a new method if the existing one doesn't actually work for you. For example, what do you want to be done with strings or symbols that contain non-alphanumeric characters, like #== ? What do you want done with underscores and digits in strings like 'INTL_61_123_456'? On Wed, 26 Oct 2022 at 22:41, Richard O'Keefe <raoknz(a)gmail.com> wrote: > What's wrong with > > $- join: (s cutCamelCase collect: [ :each | each asLowercase]) > > where s is the string you want to transform? > I'm sure you're aware of the proverb: > You have a problem and you decide to solve it with > a regular expression. Now you have TWO problems. > > MYWeirdName and MyWeirdName both map to my-weird-name, > but perhaps you are happy with that. > > On Sat, 22 Oct 2022 at 21:57, Siemen Baader <siemenbaader(a)gmail.com> > wrote: > >> Hi, >> >> I'm looking for an elegant way to convert class names with optional >> namespace prefixes to names for custom html elements. >> >> MYCustomElement and CustomElement >> >> to >> <my-custom-element> and <custom-element> >> >> There must be an elegant way to do it with regex or inject, but I'm >> embarrassed to say I can't get my head around it. I can get it to match the >> regex '((:isUppercase:+)*)((:isUppercase::isLowercase:+)*)', (if I recall >> correctly) but can't get a collection of the individual elements 'MY' >> 'Custom" 'Element' to lowercase and join. >> >> Thanks for any hints! >> >> cheers >> Siemen >> >

Oct. 26, 2022