February 2019 - Pharo-users

Re: [Pharo-users] Boostrap for seaside : incorrect JQuery version

by TomaÅ¾ Turk

I found a possible solution. The Bootstrap v3.3.6 had a compatibility issue with jQuery 3.0 (please see this issue <https://github.com/twbs/bootstrap/issues/16834>). I tested a possible workaround with copy & pasting the bootstrap.js code into TBSDevelopmentLibrary>>jsbootstrapJsContent. This method just returns the whole bootstrap.js as a string, IMHO. Important are also methods TBSDevelopmentLibrary>>cssbootstrapCssContent, TBSDevelopmentLibrary>>cssbootstrapthemeCssContent and others, since they include the code from BS v3.3.6. As I see, the TBSDeploymentLibrary differs from TBSDevelopmentLibrary in that it uses minimized versions (i.e. bootstrap.min.js). I'm not sure about other possible dependencies, though. Best wishes, Tomaz ------ Original Message ------ >From: "sergio ruiz" <sergio.rrd(a)gmail.com> >To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> >Sent: 8. 02. 2019 21:22:39 >Subject: Re: [Pharo-users] Boostrap for seaside : incorrect JQuery >version > >>Just for the record, I am having the same problem.. >> >> >>On February 8, 2019 at 3:20:18 PM, Dominique Dartois (dom(a)dartois.org) >>wrote: >> >>>Hi all >>>I installed seaside + Bootstrap from the Â« Catalog Browser Â», >>>following the tips at http://smalltalkhub.com/#!/~TorstenBergmann/ >>>I run Pharo 7 64bits on MacOS. >>>The demo doesnât react to the mouse clicks. In fact Firefox debugger >>>showed an incompatibility between Bootstrap and JQuery versions : >>>

Feb. 11, 2019

Re: [Pharo-users] Traits for class methods?

by Cyril Ferlicot

On Mon 11 Feb 2019 at 20:36, Hilaire <hilaire(a)drgeo.eu> wrote: > With singleton you will access class variable, which you can't with a > trait, so you will need a setter, but should work I guess Hi, Since Pharo 7, Traits are statefuls. See documentation at: https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > > > -- Cyril Ferlicot https://ferlicot.fr

Feb. 11, 2019

Re: [Pharo-users] Traits for class methods?

by Hilaire

With singleton you will access class variable, which you can't with a trait, so you will need a setter, but should work I guess Hilaire -- Dr. Geo http://drgeo.eu

Feb. 11, 2019

Re: [Pharo-users] Traits for class methods?

by Vitor Medina Cruz

Rectifying, It does as expected and self points to the target class. This odd behavior happened to me when I implemented the initialize method on the class side of a Trait and then clicked the 'Run Script' Button on the target class. On Mon, Feb 11, 2019 at 4:52 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > It seems, however, that self points to the trait class, instead of the > target object class. Is that correct? Instance side methods behave as > expected and self points to the target object. > > On Mon, Feb 11, 2019 at 2:19 PM Cyril Ferlicot <cyril.ferlicot(a)gmail.com> > wrote: > >> On Mon, Feb 11, 2019 at 4:50 PM Konrad Hinsen >> <konrad.hinsen(a)fastmail.net> wrote: >> > >> > Hi everyone, >> > >> > A quick question: is it possible to use traits to define class methods? >> > >> > For example, could the popular singleton pattern consisting of the >> > three class methods #uniqueInstance, #new, and #reset plus the instance >> > variable uniqueInstance be packaged as a trait? >> >> Hi, >> >> Yes it is possible. >> >> > >> > Konrad. >> > >> >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >>

Feb. 11, 2019

Re: [Pharo-users] Traits for class methods?

by Vitor Medina Cruz

It seems, however, that self points to the trait class, instead of the target object class. Is that correct? Instance side methods behave as expected and self points to the target object. On Mon, Feb 11, 2019 at 2:19 PM Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > On Mon, Feb 11, 2019 at 4:50 PM Konrad Hinsen > <konrad.hinsen(a)fastmail.net> wrote: > > > > Hi everyone, > > > > A quick question: is it possible to use traits to define class methods? > > > > For example, could the popular singleton pattern consisting of the > > three class methods #uniqueInstance, #new, and #reset plus the instance > > variable uniqueInstance be packaged as a trait? > > Hi, > > Yes it is possible. > > > > > Konrad. > > > > > -- > Cyril Ferlicot > https://ferlicot.fr > >

Feb. 11, 2019

Re: [Pharo-users] [ANN] Pharo Launcher 1.6 released

by Ben Coman

On Mon, 11 Feb 2019 at 18:19, Christophe Demarey < christophe.demarey(a)inria.fr> wrote: > Hi Ben, > > Le 8 fÃ©vr. 2019 Ã 15:23, Ben Coman <btc(a)openinworld.com> a Ã©crit : > > > > On Fri, 1 Feb 2019 at 21:28, Christophe Demarey < > christophe.demarey(a)inria.fr> wrote: > >> Hi all, >> >> Pharo Launcher 1.6 has just been released! It is available from >> http://pharo.org/download. >> >> This new version introduces two major changes: >> >> - the list of template sources is now externalized as a Ston file. >> Pharo Launcher will check regularly (at startup and each day) if there are >> changes between your local source of templates and the one hosted in Pharo >> file server. If so, Pharo Launcher will propose you to update your template >> sources. It is a way to automatically get new official sources or to keep >> stable, dev versions up to date. >> - a small UI is now available to manage VMs of PharoLauncher (update, >> remove, list). >> >> Also, this is the first release done with all sources coming from GitHub ( >> https://github.com/pharo-project/pharo-launcher) >> >> Big thanks to all contributors, including issue reports. >> >> Here is the changelog: >> Pharo Launcher v1.6 >> <https://github.com/pharo-project/pharo-launcher/releases/tag/1.6> >> >> New features: >> >> - #172 <https://github.com/pharo-project/pharo-launcher/issues/172> Provide >> a way to update / remove VMs >> >> Thanks for this. Its nice to be able to easily reference this info. > Is "last update" the date the VM was changed on the local system, or the > build date reported by the VM? > > > It is the build date reported by the system (modificationTime of the vm > binary). > It could be better by providing the VM version but it is a start. To > provide VM version, we should probably add metadata for each VMs. > > Seeing this new interface sparks a ideas (you probably already considered > some of them): > - show the commit hash of each VM > - have a history log tab - so if an Image stops working between last week > and now, I can review to > be confident it wasn't a VM update behind the scenes and if there was I > can identify the old VM and > be able to test against it to isolate a problem. > - be able to edit the Download URL > > This one is redundant with the next one, no? > Maybe yes. cheers -ben > Or do you just want to override the default VM download? > If so, it will be a bit difficult because we expect to find vms with > specific names / folders, dependening on your OS, Pharo version. > > - be able to add additional custom VMs, e.g for latest VM snapshots > > > yes, all this is nice. You could add feature requests for them to PL issue > tracker. > > > >> >> - #131 <https://github.com/pharo-project/pharo-launcher/issues/131> Display >> date for "Last Modified" on the form of "X day/month/year ago >> >> Love this!! especially sorting by it. > Also the Template column is cool. I used to include the number in the > name of the image but this is so much more informative. > The Arch column is cool. The VM Name would be useful in addition, or as a > replacement for Arch. might e.g. 70-x86. > > Right > > And dreaming of this being a pulldown menu to select from custom VMs > defined in the VM-management window. > > > It is in the plan but we need to change a lot of logic in PL so that each > image has its own metadata, including the VM to run it that you could > customize. > > Thanks for the feedback, > Christophe > >

Feb. 11, 2019

Re: [Pharo-users] Traits for class methods?

by Cyril Ferlicot

On Mon, Feb 11, 2019 at 4:50 PM Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: > > Hi everyone, > > A quick question: is it possible to use traits to define class methods? > > For example, could the popular singleton pattern consisting of the > three class methods #uniqueInstance, #new, and #reset plus the instance > variable uniqueInstance be packaged as a trait? Hi, Yes it is possible. > > Konrad. > -- Cyril Ferlicot https://ferlicot.fr

Feb. 11, 2019

Traits for class methods?

by Konrad Hinsen

Hi everyone, A quick question: is it possible to use traits to define class methods? For example, could the popular singleton pattern consisting of the three class methods #uniqueInstance, #new, and #reset plus the instance variable uniqueInstance be packaged as a trait? Konrad.

Feb. 11, 2019

[ANN] Registration for Pharo Days 2019 open!

by Esteban Lorenzano

Dear all, I am pleased to announce that registration for Pharo Days 2019 is now open! Pharo days is a gathering of the Pharo community to exchange, discuss and code with your online colleagues. Join us to share your experiences and help to make a better Pharo! To register, please proceed to the Pharo Days 2019 web page: https://pharo.org/2019PharoDays <https://pharo.org/2019PharoDays>, or go directly to the association event: https://association.pharo.org/event-3255426 <https://association.pharo.org/event-3255426>. (Yes, the schedule is still to be defined, stay tuned). If there are any questions or problems, I am happy to answer them. Esteban Ps: Iâm sorry for multiple posts ;)

Feb. 11, 2019

Re: [Pharo-users] #pathString: sent to nil when loading with Metacello

by Tim Mackinnon

I will log this as a bug - unless someone has any other thoughts. It looks to me that Iceberg incorrectly ignores the full path of a repository, meaning that other projects could equally collide with each other by virtue of having the same name? (e.g. #guessRegisteredRepository is guessing wrong0 Tim > On 8 Feb 2019, at 10:28, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi - Iâm trying to pick up the Exercism project again - and when trying to come up with instructions for students to load a clean image from the command line (to fit in with their expectations from other tracks and show that Pharo is also capable of great command line foo) I get the error: > > #pathString: was sent to nil - when I do: > > ./pharo-ui Pharo.image eval " > Metacello new > baseline: 'Exercism'; > repository: 'github://exercism/pharo:master/dev/src <github://exercism/pharo:master/dev/src>'; > load." > > Ben Coman mentioned to me that this has something to do with the "pharo-project/pharo" repository being pre-defined in Pharo 7? > > What does this mean? The repo //exercism/pharo was given to us by the Exercism team to match repoâs of other languages like //exercism/ruby etc. > > So is this really what the problem is - we canât have a repo that includes the name pharo - or have I misunderstood this? Is there a workaround I can put in the do-it to bypass this somehow? > > Iâm hoping we might have a good answer, as it was going so well in Pharo 6. > > Tim

Feb. 11, 2019