February 2019 - Pharo-users

Re: [Pharo-users] Running test

by Hilaire

I have been able to test the VM referenced bellow with drgeo image: drgeo starts but the VM suffers this libgit plugin error, as it is the case for the Linux VM. Is there another working VM to look at? I could try to fetch one from PharoLuncher on Mac OSX, but I only have intermittent access to mac computer. Hilaire Le 09/02/2019 Ã 17:58, Hilaire a Ã©critÂ : > Guys, I am voiceless but thanks for your feedback! > > Regarding some of your feedbacks (plugin error with libgit), I have > doubt about this Mac OS VM[1]. Will you be kind enough to confirm this > VM works on your system? So I can stand on a solid ground to find a > solution for the DrGeo bundle. > > Thanks > > Hilaire > > [1] https://files.pharo.org/get-files/70/pharo-mac-stable.zip > > PS: I have no Mac or Windows so I am proceeding blindly, as I always did > by the way. -- Dr. Geo http://drgeo.eu

Feb. 12, 2019

Re: [Pharo-users] Calypso documentation? Or understanding menu building

by Denis Kudriashov

Hi Tim Ð²Ñ, 12 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 13:42, Tim Mackinnon <tim(a)testit.works>: > Is there any documentation on Calypso application contexts? I am trying > to add a menu item to a package tag (the bit underneath a package - which I > often call a sub-package). > Only class comments are available for Calypso. Also there are a Commander booklet <https://github.com/SquareBracketAssociates/Booklet-Infrastructure>which describes contexts and ClassAnnotation github readme <https://github.com/pharo-ide/ClassAnnotation> (together with class comments). > > Iâve specified: > > ^CmdContextMenuActivation > byItemOf: ClyQueryMenuGroup for: RPackage > asCalypsoItemContext > > The #for: argument of command activations is a context where command should be available. Context describes condition where given command (its activation strategy) should be visible for users. In your example "RPackage asCalypsoItemContext" is an instance of ClyBrowserItemContext which matches any selected package in the browser (when a kind of RPackage is selected). And that's why you do not see it on selected tag because the tag is not a package. But that puts my menu on the package and not the tag - and if I use the inspect extra menu in calypso, I get what looks to be > something that could help me determine what I want but Iâm struggling to > understand what ClyTaggedClassGroup does, and what a context is all about. > Inspect command opens inspector of actually selected object which is an instance of ClyTaggedClassGroup in that case (try inspect selected method and you will get a CompiledMethod). Children of package in browser are instances of ClyClassGroup and subclasses. So they are not raw tags. If you need a command for a tag you should add a command for ClyTaggedClassGroup items: ^CmdContextMenuActivation byItemOf: ClyQueryMenuGroup for: ClyTaggedClassGroup asCalypsoItemContext Look for example at SycPromotePackageFromTagCommand class>>#fullBrowserMenuActivation which is defined this way. There are other kind of contexts which can be used in command annotations. For example if you want a command for selected method only in full browser then you should use ClyMethodContextOfFullBrowser: ^CmdContextMenuActivation byItemOf: ClyQueryMenuGroup for: ClyMethodContextOfFullBrowser it can be confusing that simple class is used in this case. But underhood it is converted to the instance of context where command should be available. > > Has anyone else played around with this at all? > > Ideally I want to have a menu appear on all the tags underneath a > particular package - and possibly including that package (or maybe not - I > havenât decided as I want to try it in the wild). > > While Iâm at it - I have quite understood how to create submenuâs either - > as Iâd like to have several commands all as sub items of a menu item > âExercismâ. > Look at commander booklet. It includes example. > > Tim > > > >

Feb. 12, 2019

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

by Esteban Maringolo

Maybe it's just a matter of importing the latest Bootstrap files (v3.3.7) into the the corresponding FileLibrary. Regards, El lun., 11 feb. 2019 a las 18:51, TomaÅ¾ Turk (<tomaz.turk(a)ef.uni-lj.si>) escribiÃ³: > I'm sorry, I should be more clear - I copy&pasted the Bootstrap 3.3.7 code > from here <https://getbootstrap.com/docs/3.3/getting-started/#download>, > since 3.3.7 solved the issue I mentioned. The result is that mouse clicks > behave as they should, and there is no error on browser's console anymore. > > 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. 12, 2019

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

by Johan Brichau

For the future, the intention is to decouple the Seaside and Seaside-JQuery projects, so you can easily switch JQuery versions. However, for now, a version of Seaside comes together with a fixed version of jQuery. You can, however, easily switch jQuery versions yourself by replacing the jQuery st code in the JQDeploymentLibrary/JQDevelopmentLibrary or by creating another WAFileLibrary subclass and loading that one in your application. The Seaside binding for jQuery (i.e. the JQueryInstance class) will not correspond 100% with the version of jQuery that you use, but the differences will be small. cheers Johan Ps: use the seaside mailinglist for seaside questions ;) > On 11 Feb 2019, at 22:50, TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> wrote: > > I'm sorry, I should be more clear - I copy&pasted the Bootstrap 3.3.7 code from here <https://getbootstrap.com/docs/3.3/getting-started/#download>, since 3.3.7 solved the issue I mentioned. The result is that mouse clicks behave as they should, and there is no error on browser's console anymore. > > Tomaz > >> >> >> ------ Original Message ------ >>> From: "sergio ruiz" <sergio.rrd(a)gmail.com <mailto:sergio.rrd@gmail.com>> >>> To: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org <mailto:pharo-users@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 <mailto:dom@dartois.org>) wrote: >>>> >>>>> Hi all >>>>> I installed seaside + Bootstrap from the Â« Catalog Browser Â», following the tips at http://smalltalkhub.com/#!/~TorstenBergmann/ <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. 12, 2019

Re: [Pharo-users] [ANN] P3 version 1.2

by Norbert Hartl

Cool. Makes me wanna use postgres ð Norbert > Am 12.02.2019 um 15:22 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > Hi, > > There is a new release of P3, the modern, lean and mean PostgreSQL client for Pharo. > > https://github.com/svenvc/P3 > > Version 1.2 contains the following changes: > > - P3PreparedStatement is now joined by a polymorphic P3FormattedStatement working client side on text strings > - P3PreparedStatement & P3FormattedStatement now share the same double dispatch mechanism to process argument binding > - Added convenience methods #listDatabases #listSchemas & #listTablesInSchema: to P3Client > - Added convenience methods #firstColumnData & #firstFieldOfFirstRecord to P3Result > - Added dynamic ENUM support via #loadEnums in P3Client > - Add support for the 7 geometric types POINT, CIRCLE, LINE, LSEG, POLYGON & PATH with corresponding objects P3Point, P3Circle, P3Line, P3LineSegment, P3Polygon & P3Path > - Add support for the INTERVAL type with P3Interval object > - Added P3Client>>#serverVersion accessor > - Add support for BIT & VARBIT types with P3FixedBitString & P3BitString objects > - Add TIMETZ support > - Organised P3 package with tags > - More & better documentation & unit tests > > https://github.com/svenvc/P3/releases/tag/v1.2 > > The quality of open source software is determined by it being alive, supported and maintained. > > The first way to help is to simply use P3 in your projects and report back about your successes and the issues that you encounter. You can ask questions on the Pharo mailing lists. > > Enjoy, > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Feb. 12, 2019

Re: [Pharo-users] Pharo 7 crashes on OSX when unsuspending laptop?

by Tim Mackinnon

Itâs really bad for me - its just crashed again in an image that I loaded up when I reported this, this morning. Again it had been suspended over lunch but my laptop was running another program when it crashed in the backgroundâ¦ This is from a zero conf image downloaded on Friday - so its pretty fresh. As Iâm not working on anything crucial its not killing me - but Iâd be pretty peeved off if I was using the new release for real and it was dying like this all of the time. Tim > On 12 Feb 2019, at 13:12, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On Tue, Feb 12, 2019 at 1:53 PM Tim Mackinnon <tim(a)testit.works> wrote: >> >> Ok- Iâve attached my crash.dmp file to that issue - for others that got it, was it launched from the terminal? Thatâs been my use case 2 days in a row, on a very minimal image - fresh with a small amount of code loaded into it, and a tiny bit of playing around before leaving it. >> > > I launch my Pharo Launcher via the app icon and the other images via > the PharoLauncher. > >> Tim >> >> > > > -- > Cyril Ferlicot > https://ferlicot.fr >

Feb. 12, 2019

Re: [Pharo-users] Loading TelePharo on Pharo 7

by Denis Kudriashov

Try it with closed browsers because it loads different version and it will break live instances of browser components. Better to do it from scratch image to avoid cached instances 12 ÑÐµÐ²Ñ. 2019 Ð³. 16:18 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "sergio ruiz" <sergio.rrd(a)gmail.com> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: Hmmm.. I am getting this: On February 12, 2019 at 3:42:06 AM, Denis Kudriashov (dionisiydk(a)gmail.com) wrote: Following script will load TelePharo without error: Metacello new baseline: 'TelePharo'; repository: 'github://pharo-ide/TelePharo'; onUpgrade: [:ex | ex useIncoming]; onConflictUseIncoming; load. Ð¿Ð½, 11 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 09:11, Denis Kudriashov <dionisiydk(a)gmail.com>: > 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 > > > ---- 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. 12, 2019

Re: [Pharo-users] Loading TelePharo on Pharo 7

by sergio ruiz

Hmmm.. I am getting this: On February 12, 2019 at 3:42:06 AM, Denis Kudriashov (dionisiydk(a)gmail.com) wrote: Following script will load TelePharo without error: Metacello new baseline: 'TelePharo'; repository: 'github://pharo-ide/TelePharo'; onUpgrade: [:ex | ex useIncoming]; onConflictUseIncoming; load. Ð¿Ð½, 11 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 09:11, Denis Kudriashov <dionisiydk(a)gmail.com>: > 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 > > > ---- 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. 12, 2019

Re: [Pharo-users] Loading TelePharo on Pharo 7

by sergio ruiz

Thanks, Denis.. Will try this in a minute.. On February 12, 2019 at 3:42:06 AM, Denis Kudriashov (dionisiydk(a)gmail.com) wrote: Following script will load TelePharo without error: Metacello new baseline: 'TelePharo'; repository: 'github://pharo-ide/TelePharo'; onUpgrade: [:ex | ex useIncoming]; onConflictUseIncoming; load. Ð¿Ð½, 11 ÑÐµÐ²Ñ. 2019 Ð³. Ð² 09:11, Denis Kudriashov <dionisiydk(a)gmail.com>: > 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 > > > ---- 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. 12, 2019

[ANN] P3 version 1.2

by Sven Van Caekenberghe

Hi, There is a new release of P3, the modern, lean and mean PostgreSQL client for Pharo. https://github.com/svenvc/P3 Version 1.2 contains the following changes: - P3PreparedStatement is now joined by a polymorphic P3FormattedStatement working client side on text strings - P3PreparedStatement & P3FormattedStatement now share the same double dispatch mechanism to process argument binding - Added convenience methods #listDatabases #listSchemas & #listTablesInSchema: to P3Client - Added convenience methods #firstColumnData & #firstFieldOfFirstRecord to P3Result - Added dynamic ENUM support via #loadEnums in P3Client - Add support for the 7 geometric types POINT, CIRCLE, LINE, LSEG, POLYGON & PATH with corresponding objects P3Point, P3Circle, P3Line, P3LineSegment, P3Polygon & P3Path - Add support for the INTERVAL type with P3Interval object - Added P3Client>>#serverVersion accessor - Add support for BIT & VARBIT types with P3FixedBitString & P3BitString objects - Add TIMETZ support - Organised P3 package with tags - More & better documentation & unit tests https://github.com/svenvc/P3/releases/tag/v1.2 The quality of open source software is determined by it being alive, supported and maintained. The first way to help is to simply use P3 in your projects and report back about your successes and the issues that you encounter. You can ask questions on the Pharo mailing lists. Enjoy, Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Feb. 12, 2019