February 2019 - Pharo-users

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

by Christophe Demarey

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 <mailto:christophe.demarey@inria.fr>> wrote: > Hi all, > > Pharo Launcher 1.6 has just been released! It is available from http://pharo.org/download <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 <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? 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] Loading TelePharo on Pharo 7

by Denis Kudriashov

Hi Serge. You need to add option to metacello script onConflict: or onUpgrade: with block [:warn | warn useIncoming]. I do not have computer now to give you exact code. Problem that telepharo depends on old version of Calypso but image includes the latest one. It needs to be fixed. I will look at it. And we should fix install scripts in readme page. It still references my repo but it was moved to pharo-ide org 9 ÑÐµÐ²Ñ. 2019 Ð³. 8:05 PM Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "sergio ruiz" <sergio.rrd(a)gmail.com> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: Hi, all.. I am looking to install TelePharo on my 7.01 image using the setup found at : https://github.com/pharo-ide/TelePharo like Metacello new baseline: 'TelePharo'; repository: 'github://dionisiydk/TelePharo'; load: 'Serverâ. and running into the following error. Any ideas? Thanks! MetacelloAllowConflictingProjectUpgrade>>defaultAction UndefinedObject>>handleSignal: Context>>handleSignal: Context>>handleSignal: MetacelloAllowConflictingProjectUpgrade(Exception)>>pass [ ^ exception pass ] in MetacelloScriptEngine>>handleConflict: in Block: [ ^ exception pass ] Dictionary>>at:ifAbsent: MetacelloScriptEngine>>handleConflict: MetacelloAllowConflictingProjectUpgrade>>handleResolutionFor: [ :ex | "option handlers need to be outermost set of handlers ... last line of defense before users are involved" ex handleResolutionFor: self ] in [ [ actionBlock on: MetacelloLookupProjectSpec , MetacelloLookupProjectSpecForLoad , MetacelloProjectSpecLoadedNotification , MetacelloScriptEnsureProjectLoadedForDevelopment , MetacelloLookupBaselineSpecForEnsureLoad do: [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] ] on: MetacelloAllowProjectDowngrade , MetacelloAllowProjectUpgrade , MetacelloAllowConflictingProjectUpgrade do: [ :ex | "option handlers need to be outermost set of handlers ... last line of defense before users are involved" ex handleResolutionFor: self ] ] in [ [ [ actionBlock on: MetacelloLookupProjectSpec , MetacelloLookupProjectSpecForLoad , MetacelloProjectSpecLoadedNotification , MetacelloScriptEnsureProjectLoadedForDevelopment , MetacelloLookupBaselineSpecForEnsureLoad do: [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] ] on: MetacelloAllowProjectDowngrade , MetacelloAllowProjectUpgrade , MetacelloAllowConflictingProjectUpgrade do: [ :ex | "option handlers need to be outermost set of handlers ... last line of defense before users are involved" ex handleResolutionFor: self ] ] on: MetacelloAllowLockedProjectChange do: [ :ex | "MetacelloAllowLockedProjectChange need to be outermost handler ... since it is signaled from second line of handlers" ex handleResolutionFor: self ] ] in MetacelloScriptEngine>>handleNotificationsForAction: in Block: [ :ex | "option handlers need to be outermost set ...etc... BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: MetacelloAllowConflictingProjectUpgrade(Exception)>>signal [ :existing :new | (existing hasLoadConflicts: new) ifTrue: [ ((existing canUpgradeTo: new) ifTrue: [ MetacelloAllowProjectUpgrade new ] ifFalse: [ (existing canDowngradeTo: new) ifTrue: [ MetacelloAllowProjectDowngrade new ] ifFalse: [ MetacelloAllowConflictingProjectUpgrade new ] ]) existingProjectRegistration: existing; newProjectRegistration: new; signal ] ifFalse: [ new ] ] in MetacelloScriptEngine>>lookupProjectSpecFor: in Block: [ :existing :new | ... [ :existing | ^ presentBlock value: existing value: newRegistration ] in MetacelloProjectRegistration class>>registrationForProjectSpec:ifAbsent:ifPresent: in Block: [ :existing | ^ presentBlock value: existing value...etc... [ :existing | ^ presentBlock value: existing ] in MetacelloProjectRegistry>>registrationFor:ifPresent:ifAbsent: in Block: [ :existing | ^ presentBlock value: existing ] BlockClosure>>cull: Dictionary>>at:ifPresent: MetacelloProjectRegistry>>registrationFor:ifPresent:ifAbsent: MetacelloProjectRegistration class>>registrationForProjectSpec:ifAbsent:ifPresent: MetacelloScriptEngine>>lookupProjectSpecFor: MetacelloScriptEngine>>handleLookupProjectSpec: MetacelloLookupProjectSpec>>handleResolutionFor: [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] in [ actionBlock on: MetacelloLookupProjectSpec , MetacelloLookupProjectSpecForLoad , MetacelloProjectSpecLoadedNotification , MetacelloScriptEnsureProjectLoadedForDevelopment , MetacelloLookupBaselineSpecForEnsureLoad do: [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] ] in [ [ actionBlock on: MetacelloLookupProjectSpec , MetacelloLookupProjectSpecForLoad , MetacelloProjectSpecLoadedNotification , MetacelloScriptEnsureProjectLoadedForDevelopment , MetacelloLookupBaselineSpecForEnsureLoad do: [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] ] on: MetacelloAllowProjectDowngrade , MetacelloAllowProjectUpgrade , MetacelloAllowConflictingProjectUpgrade do: [ :ex | "option handlers need to be outermost set of handlers ... last line of defense before users are involved" ex handleResolutionFor: self ] ] in [ [ [ actionBlock on: MetacelloLookupProjectSpec , MetacelloLookupProjectSpecForLoad , MetacelloProjectSpecLoadedNotification , MetacelloScriptEnsureProjectLoadedForDevelopment , MetacelloLookupBaselineSpecForEnsureLoad do: [ :ex | "lookup and registration handlers need to be innermost set of handlers ...they may throw option notifications" ex handleResolutionFor: self ] ] on: MetacelloAllowProjectDowngrade , MetacelloAllowProjectUpgrade , MetacelloAllowConflictingProjectUpgrade do: [ :ex | "option handlers need to be outermost set of handlers ... last line of defense before users are involved" ex handleResolutionFor: self ] ] on: MetacelloAllowLockedProjectChange do: [ :ex | "MetacelloAllowLockedProjectChange need to be outermost handler ... since it is signaled from second line of handlers" ex handleResolutionFor: self ] ] in MetacelloScriptEngine>>handleNotificationsForAction: in Block: [ :ex | "lookup and registration handlers need to ...etc... BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: Context>>handleSignal: Context>>handleSignal: ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Feb. 11, 2019

Re: [Pharo-users] Tonel vs Filetree

by Julien

It is. It makes contribution to the wiki directly from GitHub's web application easy and fast. Cheers, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > Le 11 fÃ©vr. 2019 Ã 08:54, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : > > The whole pharo-wiki is awesome ð I wonder is everything written in markdown directly? Looks like > > Am 11.02.2019 um 08:38 schrieb Richard Sargent <richard.sargent(a)gemtalksystems.com <mailto:richard.sargent@gemtalksystems.com>>: > >> Yes! Kudos to the authors for excellent documentation. >> >> On Sun, Feb 10, 2019, 18:19 Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com> wrote: >> CyrilFerlicot wrote >> > https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… <https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/…> >> >> Wow! Great doc :) >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> >>

Feb. 11, 2019

Re: [Pharo-users] Tonel vs Filetree

by Norbert Hartl

The whole pharo-wiki is awesome ð I wonder is everything written in markdown directly? Looks like > Am 11.02.2019 um 08:38 schrieb Richard Sargent <richard.sargent(a)gemtalksystems.com>: > > Yes! Kudos to the authors for excellent documentation. > >> On Sun, Feb 10, 2019, 18:19 Sean P. DeNigris <sean(a)clipperadams.com wrote: >> CyrilFerlicot wrote >> > https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… >> >> Wow! Great doc :) >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>

Feb. 11, 2019

Re: [Pharo-users] Tonel vs Filetree

by Richard Sargent

Yes! Kudos to the authors for excellent documentation. On Sun, Feb 10, 2019, 18:19 Sean P. DeNigris <sean(a)clipperadams.com wrote: > CyrilFerlicot wrote > > > https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… > > Wow! Great doc :) > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Feb. 11, 2019

Re: [Pharo-users] Tonel vs Filetree

by Richard70nl

> On 10 Feb 2019, at 12:43, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Some informations here: > > https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… <https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/…> Exactly what I needed. Thanks so much!

Feb. 11, 2019

Re: [Pharo-users] Tonel vs Filetree

by Sean P. DeNigris

CyrilFerlicot wrote > https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… Wow! Great doc :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 11, 2019

Re: [Pharo-users] seaside jquerywidget pharo

by PAUL DEBRUICKER

Hi Pierre, The BaselineOfJQueryWidgetBox had an error. I've fixed it and you should be able to load TableSorter and an example of how to use it with: Metacello new baseline:'JQueryWidgetBox'; repository:'http://smalltalkhub.com/mc/Seaside/JQueryWidgetBox/main'; load: 'JQWidgetBox-Tablesorter-Dev' Once it loads you can browse the JQTablesorterExample class & go to http://localhost:8080/jquery-widgets/tablesorter to see the example in action. IF you're using TableSorter than maybe you'd rather use DataTables (https://www.datatables.net smalltalk interface is here: http://smalltalkhub.com/#!/~emaringolo/DataTables) For Seaside tips & questions the mailing list is the best place. You should sign up for it. This site has a searchable archive http://forum.world.st and the Seaside mailing list is here: http://forum.world.st/Seaside-General-f86180.html There's also the seaside book at http://book.seaside.st which covers using JS with Seaside among otherthings. Hope this helps > On Feb 10, 2019, at 4:41 AM, Pierre HÃ©ricourt <pierre.hericourt(a)laposte.net> wrote: > > Hello, > > I'm Pierre from Creuse/France and I travelled in Oregon/USA last year to watch solar eclipse (near Mitchell) ... I found a diversity of landscapse and now I love Oregon ! In Creuse we have forest but don't have any desert or seaside ! > > Seaside ! Now, I remember : I was primarily writing to you to get some informations about JqueryWidget/Seaside/Pharo ;) > > Sorry for this direct mail but I didn't find any forum like on git ... > > I'm new to smalltalk and seaside. I wrote last week a little application which helps to follow products in my labs. Not very sexy job then I choose to write this in Pharo ;) > > Now, I'd like to play with JQueryWidget (TableSorter) but installation doesn't run to the end (grumbles for version 3.1)... and I don't understand how JavaScript runs on top of Seaside nor mcz ... > > You seems to be fluent in seaside : could you, please, point me some recipes or link ? > > Many thanks > > Regards > > Pierre > > on Pharo 6.1/Seaside 3.2 >

Feb. 10, 2019

Re: [Pharo-users] Tonel vs Filetree

by Cyril Ferlicot D.

Le 10/02/2019 Ã 07:37, Richard70nl a Ã©critÂ : > Hi all, > > [learning Pharoâ¦] > > What is the general preference for using Tonel or Filetree if I want to > put my packages in Github? Is it just purely developer preference or are > there technical considerations? > Hi, Some informations here: https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… > Cheers, > Richard -- Cyril Ferlicot https://ferlicot.fr

Feb. 10, 2019

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

by TomaÅ¾ Turk

It's happening to me, too, on Pharo 7.0 32-bit on Windows. The versions in respective deployment libraries are: JQDeploymentLibrary>>jQueryJs jQuery v3.3.1 JQUiDeploymentLibrary>>jQueryUiJs jQuery UI - v1.12.1 - 2016-09-14 TBSDeploymentLibrary>>jsbootstrapminJsContent Bootstrap v3.3.6 Strangely, the browser console reports: 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. 10, 2019