December 2018 - Pharo-users

Re: [Pharo-users] Spec + Graphics?

by Sean P. DeNigris

Dan Wilczak wrote > I think I've found the adapter you referred to I think you send #asSpecAdapter to your Morph, which returns an instance of MorphicGenericAdapter. HTH ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 2, 2018

Re: [Pharo-users] Spec + Graphics?

by Dan Wilczak

Thanks, Sean! I think I've found the adapter you referred to - MorphicTickingWindowAdapter. It seems that TickingSpecWindow and TickingWindowModel would be used in conjunction with it. Cheers, Dan On Fri, Nov 30, 2018 at 11:13 PM Sean P. DeNigris via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Dan Wilczak wrote > > I'm interested in using Pharo to create a simulation > > Sounds like a cool project! > > > Dan Wilczak wrote > > Can I use Spec for such a thing? > > Yes, for the vanilla parts you described e.g. toolbar > > > Dan Wilczak wrote > > I don't see any way to embed a graphical > > pane in a Spec application > > There is a Morphic adapter, but I don't have an image at hand to give you > more detail. > > > Dan Wilczak wrote > > Bloc and Sparta look very appealing but aren't officially released yet. > > Yes, ATM Morphic is the standard option. Hopefully, Bloc will be ready to > replace it soon. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Dec. 1, 2018

Re: [Pharo-users] Unable to compile myself Pharo

by Ben Coman

On Sat, 1 Dec 2018 at 02:19, Alexandre Garreau <galex-713(a)galex-713.eu> wrote: > Hi, > > I tried to compile itself because Iâm usually uncomfortable with using > binaries downloaded from the internet whose sources couldnât be checked > afterwards. I donât know the status of Pharo regarding Deterministic > Builds, but I have come anyway to become more comfortable in trusting > what comes from the distro I use and only thatâ¦ > > But I saw the bootstrap process involve redownloading a binary image > anywayâ¦ Iâd have just prefered to recompile it to be sure, as Iâm > usually more comfortable with this idea. Normally compiling a new > language is âthough longâ not that difficult. > Traditional Smalltalk systems don't do a bootstrap. Indeed its conceivable(?) that there exist some objects floating around in Images distributed by vendors today that were created in the 1980s. In spite of the advantages of the Image concept saving the whole system state, it does impact reproducability, and is one of the common criticisms of Smalltalk. Pharo has put a lot of effort into producing a bootstrap system run by CI every commit, but there may still be some rough edges when used outside the CI. You sound like you may have already looked into these, but anyway you may get some hints from... * https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… * https://github.com/pharo-project/pharo/blob/development/Jenkinsfile cheers -ben

Dec. 1, 2018

Re: [Pharo-users] Unable to compile myself Pharo

by Alexandre Garreau

Le 01/12/2018 Ã 09h34, Pierce Ng a Ã©critÂ : > On Fri, Nov 30, 2018 at 07:15:22PM +0100, Alexandre Garreau wrote: >> But I saw the bootstrap process involve redownloading a binary image >> anywayâ¦ Iâd have just prefered to recompile it to be sure, as Iâm >> usually more comfortable with this idea. Normally compiling a new >> language is âthough longâ not that difficult. > > For Pharo (and relatives like Squeak and Cuis) there are two parts: VM > and image. To build your own VM, follow the README's instructions for > the OpenSmalltalk VM: > > https://github.com/OpenSmalltalk/opensmalltalk-vm Wait if itâs the same than for squeakâ¦ knowing thereâs a âsqueak-vmâ package in debian that claim to be able to run several imagesâ¦ could it be that it could be used to run pharo?

Dec. 1, 2018

Re: [Pharo-users] What is the actual way of managing code in Pharo

by Vitor Medina Cruz

Best documentation I have seen is this one: https://github.com/pharo-tips-and-tricks/pharo-tips-and-tricks/blob/master/… <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Livre de vÃrus. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…>. <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sat, Dec 1, 2018 at 11:20 AM Ben Coman <btc(a)openinworld.com> wrote: > > > On Sat, 1 Dec 2018 at 09:05, Ichiseki <is076(a)outlook.com> wrote: > >> Hi there, >> I am trying the new Pharo 7 and a very elemental question arose. >> What I should use to manage my code? >> >> Monticello > > Metacello > > Iceberg >> > It seems I am quite confused regarding the role of each of these tools. >> >> > Monticello is a "package manager" that defines which package that classes > below to. > One way to consider it, is that it consists of three main parts. > 1. An internal representation - all the "MC" classes that make up its > in-Image representation. > 2. An external representation - a number of different repo systems, > traditionally MCZ on a http server, but also disk-based MCZ files, but also > disk-based Filetree files and recently git based repos. Use Spotter to > search for "MC' the drill in and search for "Repo" > 3. A tool for managing the link the previous two - showing what packages > are available in repos, their commit messages, which packages are loaded > and their ancestry. > > Iceberg is a tool that replaces part 3 of Monticello when working with Git > repos. > IIUC, Part 1 remains very much operational and Iceberg makes use of it. > Sorry I'm not clear on how Iceberg overlaps Part 2. > > Metacello is a package "dependency manager". > It defines which packages depends on which packages. > Before git, it also had to manage its own versioning and both these were > defined together in a ConfigurationOfxxxxx. > But with git branching and tagging, storing a ConfigurationOfxxxxx means > its versioning info is at best redundant, and at worst confusing and > contradictory. > Like the saying... "man with one watch knows the time, man with two > watches is never sure." > So the ConfigurationOfxxxx was trimmed down to a BaselineOfxxxxx. > > Now I haven't played with BaselineOf's yet myself, but my understanding is > that > in summary, in Pharo 7 you should use a git repo with Iceberg, with > BaselineOfxxxx's stored in that git repo. > ConfigurationOf's may still have some role in linking to older Monticello > repos, but sorry I'm not sure on that. > > cheers -ben > > > > > > > > >> Documentation, I am afraid, does not apply to Pharo 7. >> >> The chapters covering Monticello and Metacello in Deep in to Pharo, are >> still relevant in Pharo 7? >> Please I need profound and detailed help on this. >> Thanks so much >> best >> Ichi >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >>

Dec. 1, 2018

Re: [Pharo-users] What is the actual way of managing code in Pharo

by Ben Coman

On Sat, 1 Dec 2018 at 09:05, Ichiseki <is076(a)outlook.com> wrote: > Hi there, > I am trying the new Pharo 7 and a very elemental question arose. > What I should use to manage my code? > > Monticello Metacello Iceberg > It seems I am quite confused regarding the role of each of these tools. > > Monticello is a "package manager" that defines which package that classes below to. One way to consider it, is that it consists of three main parts. 1. An internal representation - all the "MC" classes that make up its in-Image representation. 2. An external representation - a number of different repo systems, traditionally MCZ on a http server, but also disk-based MCZ files, but also disk-based Filetree files and recently git based repos. Use Spotter to search for "MC' the drill in and search for "Repo" 3. A tool for managing the link the previous two - showing what packages are available in repos, their commit messages, which packages are loaded and their ancestry. Iceberg is a tool that replaces part 3 of Monticello when working with Git repos. IIUC, Part 1 remains very much operational and Iceberg makes use of it. Sorry I'm not clear on how Iceberg overlaps Part 2. Metacello is a package "dependency manager". It defines which packages depends on which packages. Before git, it also had to manage its own versioning and both these were defined together in a ConfigurationOfxxxxx. But with git branching and tagging, storing a ConfigurationOfxxxxx means its versioning info is at best redundant, and at worst confusing and contradictory. Like the saying... "man with one watch knows the time, man with two watches is never sure." So the ConfigurationOfxxxx was trimmed down to a BaselineOfxxxxx. Now I haven't played with BaselineOf's yet myself, but my understanding is that in summary, in Pharo 7 you should use a git repo with Iceberg, with BaselineOfxxxx's stored in that git repo. ConfigurationOf's may still have some role in linking to older Monticello repos, but sorry I'm not sure on that. cheers -ben > Documentation, I am afraid, does not apply to Pharo 7. > > The chapters covering Monticello and Metacello in Deep in to Pharo, are > still relevant in Pharo 7? > Please I need profound and detailed help on this. > Thanks so much > best > Ichi > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Dec. 1, 2018

Re: [Pharo-users] Iceberg + BaselinOf + Metacello - how to manage interdependencies ?

by Ichiseki

Hi, You are not alone. I have the same impression that Metacello+Git+Iceberg is something very difficult to grasp. It is getting hard to keep the pace with a constant evolving Pharo system. best ichi -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 1, 2018

Re: [Pharo-users] What is the actual way of managing code in Pharo

by Ichiseki

Sean, Thank you very much for your prompt response. Do you know, or have a reference to, some documentation on Iceberg? Pharo is evolving really fast, that is a good thing. But it seems that the community is formed, largely, by developers of the Pharo ecosystem and not actual plain vanilla users. I am not saying that as criticism or in any chance, trying to smear the work of the community. What I am trying to say is that I found that the whole system is become extremely complex for a non-core developer. I am trying to jump from pharo 5 to 7 and believe me, it is getting really hard to. thanks so much again best ichi -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 1, 2018

Re: [Pharo-users] What is the actual way of managing code in Pharo

by Sean P. DeNigris

Monticello - packages code Metacello - dependency management between packages Iceberg - GUI for loading code via git Currently, the cutting edge is to use Iceberg to load Metacello projects which load Monticello packages, although there are other options (e.g. old-school MCZ repos instead of git) Ichiseki wrote > The chapters covering Monticello and Metacello in Deep in to Pharo, are > still relevant in Pharo 7? Yes, but... Configurations are for applying Metacello to MCZ repos. These are replaced by Baselines for git. The API is very similar, but Config #baseline *methods* are reified into Baseline *objects* ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 1, 2018

Re: Spec + Graphics?

by Sean P. DeNigris

Dan Wilczak wrote > I'm interested in using Pharo to create a simulation Sounds like a cool project! Dan Wilczak wrote > Can I use Spec for such a thing? Yes, for the vanilla parts you described e.g. toolbar Dan Wilczak wrote > I don't see any way to embed a graphical > pane in a Spec application There is a Morphic adapter, but I don't have an image at hand to give you more detail. Dan Wilczak wrote > Bloc and Sparta look very appealing but aren't officially released yet. Yes, ATM Morphic is the standard option. Hopefully, Bloc will be ready to replace it soon. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 1, 2018