February 2019 - Pharo-users

Re: [Pharo-users] Running test

by Hilaire

Windows part is fine now, although no signed build. Hilaire Le 10/02/2019 Ã 02:00, Ben Coman a Ã©critÂ : > I've not tried it directly, but an option could be remoting to a > Windows cloud box... > https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/connecting_to_window… > -- Dr. Geo http://drgeo.eu

Feb. 10, 2019

Re: [Pharo-users] Trying to understand Developing with Pharo, Deploying with Gemstone/s

by Hilaire

Are you starting from a minimal pharo image (the ~5MB)? Le 09/02/2019 Ã 20:35, sergio ruiz a Ã©critÂ : > Yes.. > > I created a little script I can run, minus the parts to load up the > iceberg projectâ¦ > -- Dr. Geo http://drgeo.eu

Feb. 10, 2019

Tonel vs Filetree

by Richard70nl

Feb. 10, 2019

glamorous toolkit v0.5.1

by Tudor Girba

Hi, 2019 is here, and so is a new release of Glamorous Toolkit, the moldable development environment based on the freshly released Pharo 7: https://gtoolkit.com Quite a few things are new. The most important highlights are: - initial support for native windows for Mac and Linux, - initial XDoc support, - Debugger reimplementation, and - text editor deep surgery. Learn more about the release here: https://medium.com/feenk/glamorous-toolkit-v0-5-1-4c8757d58310 Take a look, and please do not be shy. Tell us know what you think and feel about it. Have fun, The feenk team -- www.feenk.com âHow do you feenk today?"

Feb. 10, 2019

Re: [Pharo-users] Trying to understand Developing with Pharo, Deploying with Gemstone/s

by sergio ruiz

Ah.. i think i get it. I just want to get this image running on the web.. I think thatâs a little bit more rabbit hole than I want to tackle right now. On February 9, 2019 at 7:58:04 PM, Pierce Ng (pierce(a)samadhiweb.com) wrote: Gemstone has Gofer. I develop on Pharo, save to .mcz using Monticello and then 'Gofer it' via a Pharo 3 image running Tode to load into Gemstone. Dale is updating Tode so that Pharo versions 6 and 7 should now or soon run Tode. ---- 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. 10, 2019

Re: [Pharo-users] Running test

by Ben Coman

On Sun, 10 Feb 2019 at 00:59, Hilaire <hilaire(a)drgeo.eu> wrote: > 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. > I've not tried it directly, but an option could be remoting to a Windows cloud box... https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/connecting_to_window… Free tier - 750 hours a month for 12 months... https://aws.amazon.com/ec2/?ft=n cheers -ben

Feb. 10, 2019

Re: [Pharo-users] Trying to understand Developing with Pharo, Deploying with Gemstone/s

by Pierce Ng

On Sat, Feb 09, 2019 at 01:15:43PM +0100, Petr Fischer via Pharo-users wrote: > Loading code and projects into Gemstone - it's more like "do it > yourself" or use tODE from GsDevKit_home (open source project, but > completely unofficial, supported by "Dale"). Gemstone has Gofer. I develop on Pharo, save to .mcz using Monticello and then 'Gofer it' via a Pharo 3 image running Tode to load into Gemstone. Dale is updating Tode so that Pharo versions 6 and 7 should now or soon run Tode. Gemstone also does Git. Pierce

Feb. 10, 2019

Re: [Pharo-users] Loading an iceberg repo from in the playground

by Cyril Ferlicot D.

Le 09/02/2019 Ã 20:36, sergio ruiz a Ã©critÂ : > Iâd like to pull my iceberg projects inside the playground, so that I > can automate the loading on the command line. > > Is there any documentation on how to do this? Hi, I don't know if there is documentation. I did some things in some of my scripts around that. It's not much but it can get you started: https://github.com/jecisc/pharo-scripts/blob/master/settings/PharoSettings6… https://github.com/jecisc/pharo-scripts/blob/master/settings/PharoSettings7… https://github.com/jecisc/pharo-scripts/blob/master/settings/PharoSettings.… > > Thanks! > > ---- > 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 -- Cyril Ferlicot https://ferlicot.fr

Feb. 10, 2019

Loading TelePharo on Pharo 7

by sergio ruiz

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. 9, 2019

Loading an iceberg repo from in the playground

by sergio ruiz

Iâd like to pull my iceberg projects inside the playground, so that I can automate the loading on the command line. Is there any documentation on how to do this? Thanks! ---- 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. 9, 2019