June 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Introduction GSoC 2019

by Nina Medic

For those interested in reading about progress on my project and some topics connected to it, here is a link: https://pharokeepers.github.io/ As I mentioned before, Smiljana and I, are posting to the same blog, therefore each post is tagged with the writer`s name. On Sat, 11 May 2019 at 12:17, Nina Medic <medicka992(a)gmail.com> wrote: > Hello, > I am Nina, and I am a student from Serbia. Currently I am on the second > year, of my master studies in Computer science. I have been working with > Pharo for more than a year now. As a project in one of my classes, I was > implementing a program that parses graphs and makes a visualization of > them. Last semester I followed MOOC for Pharo. > > A couple of days ago, I was fortunate enough to be accepted for this year > Google Summer of Code. The project I will be working on is called *Graph > library with layouting algorithm*. What I will do is implement the graph > structure with all necessary parts in one separate library. Beside that I > will include layouthing algorithms. Some of which are already implemented > as a part of some other projects and packages, those I will pull out. For > the other ones, I will be using doctoral dissertation from Vaderna Renata > titled *Algorithms and a language for the support of automatically laying > out diagram elements*. You can find my proposal here: > > https://docs.google.com/document/d/1V8_HaZnxYsCfaiZs4vI1C5Dh4TvRPz-H51aYOuY… > > I would like to know, what are you thinking about this project. How > important is for the community? > > One of fellow students from GSoC (we are both working for Pharo > consortium) and I are considering using the same blog. What do you think > about that? I will be also posting about my progress on Twitter: > https://twitter.com/medicka992 which will make it easy for everybody to > follow my work. > > I am looking forward to working on this project and with all of you. > > Sincerely, > Nina. >

June 17, 2019

Re: [Pharo-users] Autocompletion

by eftomi

I found the cause - I created the #buttonBad accessing methods with code (re)factoring (generate accessors), and in this case the accessors are made in this fashion: CustomerSatisfaction >> buttonBad: *anObject *buttonBad := *anObject *It's better to use CustomerSatisfaction >> buttonBad: *aComposablePresenterClass *buttonBad := *aComposablePresenterClass *as this method is doing: ComposablePresenter >> instantiate: aComposablePresenterClass "Instantiate a ComposablePresenter subclass and set its instance owner" ^ aComposablePresenterClass owner: self To find the cause, I used the debugger extensively and found the core logic in ECInstVarTypeGuesser >> perform method - it was quite an exercise! Best wishes, Tomaz -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 16, 2019

Re: [Pharo-users] Can I code a web browser in a Pharo GUI window (Morphic or other)?

by Arie van Wingerden

At this time I'd say that PharoJS would probably my first choice to check out for such project in the future. Given my Pharo n00bness however I have decided to stick with C# for this project for now to avoid (too) long implementation times. But I'll definitely dive into the options you tell me about, specifically PharoJS. Thx to you all! /Arie Op vr 14 jun. 2019 om 14:57 schreef Noury Bouraqadi <bouraqadi(a)gmail.com>: > Hi Arie, > > Do you really need to code web browser, or is it acceptable to control a > web browser from Pharo. > This is what we do in PharoJS (http://pharojs.org) for running tests. > We also have a custom playground, so evaluate pharo expressions that are > translated to javascript and executed by the web browser. > > Noury > > On 14 Jun 2019, at 09:45, Arie van Wingerden <xapwing(a)gmail.com> wrote: > > Hi, > > for a project I need this kind of program: > > 1. client side only > 2. must be able to programmatically show a web browser in a window > (Morphic??); only local content will be shown > 3. must also be able to show other windows, containing simple games > > Now, I guess that 1 and 3 are possible straight away, but I am unsure > about option 2. > > I found out that there are a few ways to do it: > > - using C#, which has: > - standard web browser control out-of-the-box > - third-party open source chromium web browser component > - using Java, which (afaict) is a coding effort, but possible anyway > > > That saiud, since I'd very much like to start using Pharo for more tasks > (just starting) I wonder if Pharo has something to offer in this case. > > Many thx! > /Arie > > >

June 15, 2019

Issues with build: 160, commit: b84a1e1 of the Pharo 7.0.3 image?

by Alejandro Fernandez

Hi, I just launched a new Pharo 7.0 - 32bit (stable) from the pharo launcher. Got back an image from build: 160, commit: b84a1e1 First issue I noticed was a broken (?) component in the Wellcome screen (red block with yelllow border and diagonals). Then, after insalling Seaside and trying to add a new adaptor (via the Seaside launcher), an instance of MenuItemPresenter did not understand #isEnabled. No of these issues are present in a clean image obtained with the zeroconf script (build: 158, commit: 0903ade image). Is anyone else experiencing the same problem? Do templates update automatically when a new build is available? Yours, Alejandro

June 15, 2019

Re: [Pharo-users] Loading Gettext on already installed Seaside

by Johan Brichau

Iâm afraid the Gettext-Seaside integration is broken in current Seaside versions. Johan > On 15 Jun 2019, at 00:18, BrunoBB <smalltalk(a)adinet.com.uy> wrote: > > Well, > > This method exist on GetText GemStone version. > > So i'm not quite sure what is going on. Maybe GS and Pharo version are not > synchronized. > > regards, > bruno > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

June 15, 2019

Re: [Pharo-users] Loading Gettext on already installed Seaside

by BrunoBB

Well, This method exist on GetText GemStone version. So i'm not quite sure what is going on. Maybe GS and Pharo version are not synchronized. regards, bruno -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 14, 2019

Re: [Pharo-users] Loading Gettext on already installed Seaside

by BrunoBB

Paul, Thanks for the pointer now i have passed the conflict. But i got a DNU: NaturalLanguageTranslator>>domainRegistered: This method does not exist. It seems that the following entry hsa the fix: http://forum.world.st/Error-loading-Seaside-Gettext-support-td4980855.html Close the walkback and evaluate: WAGettextExample initialize. Maybe NaturalLanguageTranslator>>domainRegistered: was present in Pharo early version but not in Pharo 7. This should be fixed. regards, bruno -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 14, 2019

Re: [Pharo-users] Loading Gettext on already installed Seaside

by Paul DeBruicker

Hi Add onConflict: [ :ex | ex allow ]; To your Metacello load instructions BrunoBB wrote > Hi, > > I have a Pharo 7.0 image with Seaside installed on it. > > Now i want to add Gettext but i'm not able to do it yet. > > Metacello new > baseline:'Seaside3'; > repository: 'github://SeasideSt/Seaside:master/repository'; > load: #('Seaside-Gettext-Core' 'Seaside-Gettext-Examples') > > Fail because 'Seaside-Gettext-Core' name not found. > > More likely because BaselineOfSeaside3>>baselinegettext: does not include > a > tag for Pharo 7. > > If i add (to include Pharo7): > spec for: #(#'pharo1.x' #'pharo2.x' #'pharo3.x' #'pharo4.x' #'pharo7.x') > > I got a conflict error: > 'MetacelloConflictingProjectError: Load Conflict between existing > BaselineOf...igurationOfGrease stable from > http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'" > > The same result with: > Metacello new > baseline:'Seaside3'; > repository: 'github://SeasideSt/Seaside:master/repository'; > load: #('Gettext' 'Gettext-Examples') > > If i have Seaside already in my image how i should load Gettext ? > > regards, > bruno > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 14, 2019

Autocompletion

by TomaÅ¾ Turk

I managed to find some time to progress with my Smalltalk / Pharo learning and am going through the Spec booklet. I noticed that autocompletion most of the times works excellent, sometimes it struggles. For instance, if you prepare CustomerSatisfaction >> initializeWidgets buttonBad := self instantiate: ButtonPresenter. and then start to write buttonBad label: ... in the same method, the #label: selector is found immediately. However, if you say CustomerSatisfaction >> initializeWidgets buttonBad := self newButton. where ComposablePresenter >> newButton ^ self instantiate: ButtonPresenter and inherited by CustomerSatisfaction, then the #label: selector is not found by autocompleter (in the menu of choices). I'm just curious why is that so. For a novice, autocompleter is a life saver :-) Best wishes, Tomaz

June 14, 2019

Loading Gettext on already installed Seaside

by BrunoBB

Hi, I have a Pharo 7.0 image with Seaside installed on it. Now i want to add Gettext but i'm not able to do it yet. Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load: #('Seaside-Gettext-Core' 'Seaside-Gettext-Examples') Fail because 'Seaside-Gettext-Core' name not found. More likely because BaselineOfSeaside3>>baselinegettext: does not include a tag for Pharo 7. If i add (to include Pharo7): spec for: #(#'pharo1.x' #'pharo2.x' #'pharo3.x' #'pharo4.x' #'pharo7.x') I got a conflict error: 'MetacelloConflictingProjectError: Load Conflict between existing BaselineOf...igurationOfGrease stable from http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'" The same result with: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; load: #('Gettext' 'Gettext-Examples') If i have Seaside already in my image how i should load Gettext ? regards, bruno -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 14, 2019