July 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] pharo bash script with startup

by HernÃ¡n Morales Durand

2018-06-27 23:21 GMT-03:00 Otto Behrens <otto(a)finworks.biz>: > Thanks for the effort guys. > > I tried to download the image, sources and vm separately (basically > extracted what https://get.pharo.org/64/61+vm does), but ran into fresh > trouble. > > Firstly, is "wget -O - https://get.pharo.org/64/61+vm | bash" not risky in > terms of security? It should be quite possible to inject a lovely trojan > horse with this, or not? Yes, this is possible: https://www.idontplaydarts.com/2016/04/detecting-curl-pipe-bash-server-side/ > > Secondly, the pharo bash script that it generates is different to the one in > the zip. The directory structure (where the image & vm goes) is also > different. Why is that? > > I started the image (http://files.pharo.org/get-files/61/pharo64.zip) with > the vm (http://files.pharo.org/get-files/61/pharo-linux-stable.zip) and got > the following, which I tried to do, but that did not take the message away: > > pthread_setschedparam failed: Operation not permitted > This VM uses a separate heartbeat thread to update its internal clock > and handle events. For best operation, this thread should run at a > higher priority, however the VM was unable to change the priority. The > effect is that heavily loaded systems may experience some latency > issues. If this occurs, please create the appropriate configuration > file in /etc/security/limits.d/ as shown below: > > cat <<END | sudo tee /etc/security/limits.d/pharo.conf > * hard rtprio 2 > * soft rtprio 2 > END > > and report to the pharo mailing list whether this improves behaviour. > > You will need to log out and log back in for the limits to take effect. > > (I did do this). > > I reverted to the deb package for now, because this have take some time and > I can't focus on it now. > > I'll give it another shot soon, I hope > > > > On Wed, Jun 27, 2018 at 8:58 PM, Tim Mackinnon <tim(a)testit.works> wrote: >> >> When we get confirmation of success - we need to make sure this gets >> applied to both zeroconf and official downloads. >> >> Anything we can do to simplify and make it robust is gratefully >> appreciated as there is nothing worse than falling at the lunch hurdle. >> >> Itâs cool to see so many clever minds on this. >> >> Tim >> >> Sent from my iPhone >> >> > On 27 Jun 2018, at 19:52, HernÃ¡n Morales Durand >> > <hernan.morales(a)gmail.com> wrote: >> > >> > 2018-06-27 10:50 GMT-03:00 K K Subbu <kksubbu.ml(a)gmail.com>: >> >>> On Wednesday 27 June 2018 06:39 PM, K K Subbu wrote: >> >>> >> >>> >> >>> The double quotes are required here to skip splitting arguments with >> >>> embedded spaces into different words. >> >>> >> >>> I suspect the error is earlier in the image=$@ assignment. This >> >>> requires >> >>> double quotes. Double quotes are also required while calling zenity to >> >>> avoid >> >>> word splitting. >> >> >> >> >> >> My earlier fix is also in error, Sorry! >> >> >> >> Essentially, we are mixing up single value variable (image) with >> >> argument >> >> array ($@). I found a cleaner fix : >> >> >> >> ```` >> >> if [ $# -eq 0 ]; then >> >> image_count=`ls "$RESOURCES"/*.image 2>/dev/null |wc -l` >> >> if [ "$image_count" -eq 1 ]; then >> >> set -- "$RESOURCES"/*.image >> >> elif which zenity &>/dev/null; then >> >> set -- "$(zenity --title 'Select an image' >> >> --file-selection >> >> --filename "$RESOURCES/" --file-filter '*.image' --file- >> >> filter '*')" >> >> else >> >> set -- "$RESOURCES/Pharo6.1-64.image" >> >> fi >> >> fi >> >> >> > >> > Use $() instead of backticks for command substitution: >> > http://mywiki.wooledge.org/BashFAQ/082 >> > >> > Cheers, >> > >> > HernÃ¡n >> > >> >> # execute >> >> exec "$LINUX/pharo" \ >> >> --plugins "$LINUX" \ >> >> --encoding utf8 \ >> >> -vm-display-X11 \ >> >> "$@" >> >> ```` >> >> >> >> HTH .. Subbu >> >> >> > >> >> >

July 17, 2018

Iceberg issue on Ubuntu 16.04.3 Pharo 6.1

by Juraj Kubelka

Hi, I am trying to build a project in ubuntu 16.04.3. To this: - I downloaded Pharo 6.1 (60541) 64bit - I open the Pharo image and execute: Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. I have the following issue: LGit_GIT_ERROR: SSL error: error:140E0197:SSL routines:SSL_shutdown:shutdown while in init The full stack is below. I can clone the repository from a terminal using: git clone git@github.com:feenkcom/gtoolkit.git I believe that my settings are correct (same that I use on macOS): Is Iceberg suppose to work on Ubuntu 16.04.3 64bit? I have noticed that it works in Pharo 7 64bit (excluding the fact gtoolkit does not work in Pharo 7 yet). I found this bug report that might be related: https://github.com/libgit2/libgit2/issues/4644 <https://github.com/libgit2/libgit2/issues/4644> Thanks! Juraj Full stack: LGitReturnCodeEnum>>handleLGitReturnCode LGitRepository(LGitExternalObject)>>withReturnHandlerDo: LGitRepository>>clone:options:to: LGitRepository>>clone:options: [ repo clone: url options: cloneOptions ] in [ | repo cloneOptions | repo := LGitRepository on: self location. cloneOptions := LGitCloneOptions withCredentialsProvider: IceCredentialsProvider default. cloneOptions checkoutOptions checkoutStrategy: LGitCheckoutStrategyEnum git_checkout_none. [ repo clone: url options: cloneOptions ] on: LGit_GIT_ERROR do: [ :e | e acceptError: IceLibgitErrorVisitor new ]. repo checkout: (aBranchName ifNil: [ self branch ifNotNil: [ :b | b name ] ifNil: [ 'master' ] ]). (LGitRemote of: repo named: 'origin') lookup; setUrl: url ] in IceLibgitLocalRepository>>cloneRepositoryFrom:branch: in Block: [ repo clone: url options: cloneOptions ] BlockClosure>>on:do: [ | repo cloneOptions | repo := LGitRepository on: self location. cloneOptions := LGitCloneOptions withCredentialsProvider: IceCredentialsProvider default. cloneOptions checkoutOptions checkoutStrategy: LGitCheckoutStrategyEnum git_checkout_none. [ repo clone: url options: cloneOptions ] on: LGit_GIT_ERROR do: [ :e | e acceptError: IceLibgitErrorVisitor new ]. repo checkout: (aBranchName ifNil: [ self branch ifNotNil: [ :b | b name ] ifNil: [ 'master' ] ]). (LGitRemote of: repo named: 'origin') lookup; setUrl: url ] in IceLibgitLocalRepository>>cloneRepositoryFrom:branch: in Block: [ | repo cloneOptions |... [ self checkInitialized. aBlock value ] in LGitGlobal class>>runSequence: in Block: [ self checkInitialized.... [ activeProcess psValueAt: index put: anObject. aBlock value ] in LGitActionSequence(DynamicVariable)>>value:during: in Block: [ activeProcess psValueAt: index put: anObject.... BlockClosure>>ensure: LGitActionSequence(DynamicVariable)>>value:during: LGitActionSequence class(DynamicVariable class)>>value:during: LGitGlobal class>>runSequence: IceLibgitLocalRepository>>cloneRepositoryFrom:branch: IceRepositoryCreator>>createRepository [ (IceRepositoryCreator new url: urlToUse; subdirectory: repoPath; branchName: self projectVersion; createRepository) register ] in [ | urlToUse | urlToUse := remote url. [ (IceRepositoryCreator new url: urlToUse; subdirectory: repoPath; branchName: self projectVersion; createRepository) register ] on: IceAuthenticationError do: [ :e | self crLog: ('I got an error while cloning: {1}. I will try to clone the HTTPS variant.' format: {e messageText}). urlToUse := remote httpsUrl. e retry ] ] in MCGitHubRepository(MCGitBasedNetworkRepository)>>getOrCreateIcebergRepository in Block: [ (IceRepositoryCreator new... BlockClosure>>on:do: [ | urlToUse | urlToUse := remote url. [ (IceRepositoryCreator new url: urlToUse; subdirectory: repoPath; branchName: self projectVersion; createRepository) register ] on: IceAuthenticationError do: [ :e | self crLog: ('I got an error while cloning: {1}. I will try to clone the HTTPS variant.' format: {e messageText}). urlToUse := remote httpsUrl. e retry ] ] in MCGitHubRepository(MCGitBasedNetworkRepository)>>getOrCreateIcebergRepository in Block: [ | urlToUse |... OrderedCollection(Collection)>>detect:ifFound:ifNone: OrderedCollection(Collection)>>detect:ifNone: MCGitHubRepository(MCGitBasedNetworkRepository)>>getOrCreateIcebergRepository IceGithubRepositoryType>>mcRepository Iceberg class>>mcRepositoryFor: IceMetacelloPharoPlatform>>createRepository: MetacelloMCBaselineProject(MetacelloMCProject)>>createRepository: MetacelloRepositorySpec>>createRepository [ aSpec createRepository ] in [ :aSpec | | description repo | description := aSpec description. (repo := repositories detect: [ :rep | rep description = description ] ifNone: [ aSpec createRepository ]) ~~ nil ifTrue: [ repos add: repo ] ] in MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: in Block: [ aSpec createRepository ] Array(Collection)>>detect:ifFound:ifNone: Array(Collection)>>detect:ifNone: [ :aSpec | | description repo | description := aSpec description. (repo := repositories detect: [ :rep | rep description = description ] ifNone: [ aSpec createRepository ]) ~~ nil ifTrue: [ repos add: repo ] ] in MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: in Block: [ :aSpec | ...

July 17, 2018

Re: [Pharo-users] Changing a BaselineOf... to include one more package

by Guillermo Polito

Hi Andrew, Sorry for the late reply, On Wed, Jul 11, 2018 at 4:31 PM Andrew P. Black <apblack(a)pdx.edu> wrote: > Hi Guillermo, > > Thanks for the explanation. I guess that I really don't have much idea > how this baseline stuff is supposed to work, so when it fails, I don't know > where to look. > > My initial question was about why iceberg (or Metacello?) was looking in > the wrong directory, but that seems to have been the wrong question. > > So, you are right; the BaselineOfSmaCC has not been updated to include the > SmaCC-Reification package, which is new (and experimental). So it seems > that I have to add it. Here is the current baseline: > > BaselineOfSmaCC >> baseline: spec > <baseline> > spec > for: #common > do: [ spec blessing: #baseline. > spec > package: 'SmaCC-Source-Editing'; > package: 'SmaCC-Runtime'; > package: 'SmaCC-GLR-Runtime' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Debugging-Support' > with: [ spec requires: 'SmaCC-Development' ]. > spec > package: 'SmaCC-Development' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]. > spec > for: #Alt > do: [ spec > package: 'SmaCC-Alt' with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Development-UI' > with: [ spec > requires: #('SmaCC-Development' 'SmaCC-Alt' 'SmaCC-Debugging-Support') ] ]. > spec > for: #NoAlt > do: [ spec > package: 'SmaCC-Development-UI' > with: [ spec requires: #('SmaCC-Development' 'SmaCC-Debugging-Support') ] > ]. > spec > package: 'SmaCC-Tests' > with: [ spec requires: 'SmaCC-Development' ]; > package: 'SmaCC-Browser' with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Parse-Tree-Comparison' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Rewrite-Engine' > with: [ spec > requires: #('SmaCC-GLR-Runtime' 'SmaCC-Source-Editing' 'SmaCC-CSV-Parser') > ]; > package: 'SmaCC-Rewrite-Engine-Tests' > with: [ spec requires: 'SmaCC-Rewrite-Engine' ]; > package: 'SmaCC-Rewrite-Engine-Command-Line' > with: [ spec requires: 'SmaCC-Rewrite-Engine' ]; > package: 'SmaCC-Rewrite-Server'; > package: 'SmaCC-Rewrite-Server-Worker' > with: [ spec requires: 'SmaCC-Rewrite-Engine' ]; > package: 'SmaCC-Swift' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-Smalltalk-Parser' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Generic-Smalltalk-Parser' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-C-Parser' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-CSV-Parser' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-CSharp' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-Cucumber' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-Javascript-Parser' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-Java' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-Python' with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Python-Tests' > with: [ spec requires: 'SmaCC-Python' ]; > package: 'SmaCC-Line-Parser' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Delphi' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-DelphiForms' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-IDL' with: [ spec requires: 'SmaCC-Runtime' ]. > spec > group: 'default' with: #('Tools'); > group: 'Runtime' with: #('SmaCC-GLR-Runtime'); > group: 'Rewrite' with: #('SmaCC-Rewrite-Engine'); > group: 'Rewrite-Server' > with: > #('SmaCC-Rewrite-Server-Worker' 'SmaCC-Rewrite-Server' 'Rewrite' > 'SmaCC-Rewrite-Engine-Command-Line'); > group: 'Tools' > with: > #('SmaCC-Development-UI' 'Examples' 'Rewrite' > 'SmaCC-Parse-Tree-Comparison'); > group: 'Debugging' with: #('SmaCC-Debugging-Support'); > group: 'Examples' > with: > #('SmaCC-Smalltalk-Parser' 'SmaCC-C-Parser' 'SmaCC-Java' > 'SmaCC-CSV-Parser' 'SmaCC-Line-Parser'); > group: 'Examples-Extra' > with: > #('SmaCC-IDL' 'SmaCC-CSharp' 'SmaCC-Cucumber' 'SmaCC-Swift' 'SmaCC-Delphi' > 'SmaCC-DelphiForms' 'SmaCC-Python' 'SmaCC-Javascript-Parser'); > group: 'Tests' > with: #('SmaCC-Tests' 'SmaCC-Rewrite-Engine-Tests' 'SmaCC-Python-Tests') ] > > > Should I add a new group, something like > > spec group: 'Reification' > > with: #('SmaCC-Reification') > > > But then I must also specify the dependencies of the SmaCC-Reification > package, so I need to add > > spec package: 'SmaCC-Reification' with: [ spec requires: > #('SmaCC-Smalltalk-Parser' 'SmaCC-Runtime' 'SmaCC-Java') ] > > > (I assumed that this would go earlier in the method, with the other > package specs. So I put it right after package: 'SmaCC-IDL') > Yep. You must do both :). Also, I think the order is not important, they are just declarations, the engine takes care of calculating the order later. > > Once I've done that, I tried to load the BaselineOfSmaCC again, and I find > that I've broken it. I get a walkback with the message > "Could not resolve: SmaCC-Reification [SmaCC-Reification] in > /Users/black/Development/Pharo/images/Pharo 7.0 SmallGrace > 0.34/pharo-local/package-cache git@github.com:apblack/SmaCC.git[fglr]" > > Why is it trying to load SmaCC-Reficiation? Did my changes to the > baseline somehow change the default configuration too? > By default, if you don't specify anything, a baseline will load **all described packages**. If you want to override that behaviour, AFAIR you need to override the #default group spec group: 'default' with: #( .... ) Actually, I've cloned your project and see that default is defined as download tools. So, how are you loading your project. Moreover, I've just tried it and it worked, so there is something else to it: - I've cloned SmaCC - I've checked out the flgr branch - I've loaded the baseline and added spec package: 'SmaCC-Reification' with: [ spec requires: #('SmaCC-Smalltalk-Parser' 'SmaCC-Runtime' 'SmaCC-Java') ] - then, I've done right click on the iceberg project and selected Metacello -> load baseline... => then inserted SmaCC-Reification and I got that package + dependencies loaded... > Moreover, my original problem is still there â it's looking in a > nonexistent package cache, rather than on github, or in my > ~/iceberg/apblack/SmaCC clone of github. > I don't think this is quite like that... Metacello will try to lookup the package in several places. And it will check at last the package cache. So it fails because it was not able to found that package in any of your repositories, but the last it checked was the package cache. > - If SmaCC-Reification is in a non-default group, you probably want to add > > spec > baseline: 'SmaCC-Reification' > with: [ spec repository: 'github://apblack/SmaCC:working'; loads: #( > 'NAME-OF-YOUR-REIFICATION-GROUP' ) ]. > > > This would go in the BaselineOfGrace package, right? Not in > BaselineOfSmaCC > yep. > > And then your packages can depend on it. > > - IF SmaCC-Reification is not in the SmaCC baseline, then, there is > nothing you can do, but to add it :) > > > Thanks for the help so far > > Andrew > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

July 16, 2018

Re: [Pharo-users] Changing a BaselineOf... to include one more package

by Andrew P. Black

Any more ideas o how to get this working? Andrew > On 11 Jul 2018, at 7:30, Andrew P. Black <apblack(a)pdx.edu> wrote: > > Hi Guillermo, > > Thanks for the explanation. I guess that I really don't have much idea how this baseline stuff is supposed to work, so when it fails, I don't know where to look. > > My initial question was about why iceberg (or Metacello?) was looking in the wrong directory, but that seems to have been the wrong question. > > So, you are right; the BaselineOfSmaCC has not been updated to include the SmaCC-Reification package, which is new (and experimental). So it seems that I have to add it. Here is the current baseline: > >> BaselineOfSmaCC >> baseline: spec >> <baseline> >> spec >> for: #common >> do: [ spec blessing: #baseline. >> spec >> package: 'SmaCC-Source-Editing'; >> package: 'SmaCC-Runtime'; >> package: 'SmaCC-GLR-Runtime' >> with: [ spec requires: 'SmaCC-Runtime' ]; >> package: 'SmaCC-Debugging-Support' >> with: [ spec requires: 'SmaCC-Development' ]. >> spec >> package: 'SmaCC-Development' >> with: [ spec requires: 'SmaCC-GLR-Runtime' ]. >> spec >> for: #Alt >> do: [ spec >> package: 'SmaCC-Alt' with: [ spec requires: 'SmaCC-Runtime' ]; >> package: 'SmaCC-Development-UI' >> with: [ spec >> requires: #('SmaCC-Development' 'SmaCC-Alt' 'SmaCC-Debugging-Support') ] ]. >> spec >> for: #NoAlt >> do: [ spec >> package: 'SmaCC-Development-UI' >> with: [ spec requires: #('SmaCC-Development' 'SmaCC-Debugging-Support') ] ]. >> spec >> package: 'SmaCC-Tests' >> with: [ spec requires: 'SmaCC-Development' ]; >> package: 'SmaCC-Browser' with: [ spec requires: 'SmaCC-Runtime' ]; >> package: 'SmaCC-Parse-Tree-Comparison' >> with: [ spec requires: 'SmaCC-Runtime' ]; >> package: 'SmaCC-Rewrite-Engine' >> with: [ spec >> requires: #('SmaCC-GLR-Runtime' 'SmaCC-Source-Editing' 'SmaCC-CSV-Parser') ]; >> package: 'SmaCC-Rewrite-Engine-Tests' >> with: [ spec requires: 'SmaCC-Rewrite-Engine' ]; >> package: 'SmaCC-Rewrite-Engine-Command-Line' >> with: [ spec requires: 'SmaCC-Rewrite-Engine' ]; >> package: 'SmaCC-Rewrite-Server'; >> package: 'SmaCC-Rewrite-Server-Worker' >> with: [ spec requires: 'SmaCC-Rewrite-Engine' ]; >> package: 'SmaCC-Swift' >> with: [ spec requires: 'SmaCC-GLR-Runtime' ]; >> package: 'SmaCC-Smalltalk-Parser' >> with: [ spec requires: 'SmaCC-Runtime' ]; >> package: 'SmaCC-Generic-Smalltalk-Parser' >> with: [ spec requires: 'SmaCC-GLR-Runtime' ]; >> package: 'SmaCC-C-Parser' >> with: [ spec requires: 'SmaCC-Runtime' ]; >> package: 'SmaCC-CSV-Parser' >> with: [ spec requires: 'SmaCC-Runtime' ]; >> package: 'SmaCC-CSharp' >> with: [ spec requires: 'SmaCC-GLR-Runtime' ]; >> package: 'SmaCC-Cucumber' >> with: [ spec requires: 'SmaCC-GLR-Runtime' ]; >> package: 'SmaCC-Javascript-Parser' >> with: [ spec requires: 'SmaCC-GLR-Runtime' ]; >> package: 'SmaCC-Java' >> with: [ spec requires: 'SmaCC-GLR-Runtime' ]; >> package: 'SmaCC-Python' with: [ spec requires: 'SmaCC-Runtime' ]; >> package: 'SmaCC-Python-Tests' >> with: [ spec requires: 'SmaCC-Python' ]; >> package: 'SmaCC-Line-Parser' >> with: [ spec requires: 'SmaCC-Runtime' ]; >> package: 'SmaCC-Delphi' >> with: [ spec requires: 'SmaCC-GLR-Runtime' ]; >> package: 'SmaCC-DelphiForms' >> with: [ spec requires: 'SmaCC-GLR-Runtime' ]; >> package: 'SmaCC-IDL' with: [ spec requires: 'SmaCC-Runtime' ]. >> spec >> group: 'default' with: #('Tools'); >> group: 'Runtime' with: #('SmaCC-GLR-Runtime'); >> group: 'Rewrite' with: #('SmaCC-Rewrite-Engine'); >> group: 'Rewrite-Server' >> with: >> #('SmaCC-Rewrite-Server-Worker' 'SmaCC-Rewrite-Server' 'Rewrite' 'SmaCC-Rewrite-Engine-Command-Line'); >> group: 'Tools' >> with: >> #('SmaCC-Development-UI' 'Examples' 'Rewrite' 'SmaCC-Parse-Tree-Comparison'); >> group: 'Debugging' with: #('SmaCC-Debugging-Support'); >> group: 'Examples' >> with: >> #('SmaCC-Smalltalk-Parser' 'SmaCC-C-Parser' 'SmaCC-Java' 'SmaCC-CSV-Parser' 'SmaCC-Line-Parser'); >> group: 'Examples-Extra' >> with: >> #('SmaCC-IDL' 'SmaCC-CSharp' 'SmaCC-Cucumber' 'SmaCC-Swift' 'SmaCC-Delphi' 'SmaCC-DelphiForms' 'SmaCC-Python' 'SmaCC-Javascript-Parser'); >> group: 'Tests' >> with: #('SmaCC-Tests' 'SmaCC-Rewrite-Engine-Tests' 'SmaCC-Python-Tests') ] > > > Should I add a new group, something like > >> spec group: 'Reification' >> with: #('SmaCC-Reification') > > But then I must also specify the dependencies of the SmaCC-Reification package, so I need to add > >> spec package: 'SmaCC-Reification' with: [ spec requires: #('SmaCC-Smalltalk-Parser' 'SmaCC-Runtime' 'SmaCC-Java') ] > > (I assumed that this would go earlier in the method, with the other package specs. So I put it right after package: 'SmaCC-IDL') > > Once I've done that, I tried to load the BaselineOfSmaCC again, and I find that I've broken it. I get a walkback with the message > "Could not resolve: SmaCC-Reification [SmaCC-Reification] in /Users/black/Development/Pharo/images/Pharo 7.0 SmallGrace 0.34/pharo-local/package-cache git@github.com:apblack/SmaCC.git[fglr]" > > Why is it trying to load SmaCC-Reficiation? Did my changes to the baseline somehow change the default configuration too? > Moreover, my original problem is still there â it's looking in a nonexistent package cache, rather than on github, or in my ~/iceberg/apblack/SmaCC clone of github. > >> - If SmaCC-Reification is in a non-default group, you probably want to add >> >> spec >> baseline: 'SmaCC-Reification' >> with: [ spec repository: 'github://apblack/SmaCC:working'; loads: #( 'NAME-OF-YOUR-REIFICATION-GROUP' ) <> ]. >> > > This would go in the BaselineOfGrace package, right? Not in BaselineOfSmaCC > >> And then your packages can depend on it. >> >> - IF SmaCC-Reification is not in the SmaCC baseline, then, there is nothing you can do, but to add it :) >> > > Thanks for the help so far > > Andrew >

July 16, 2018

Ecstatic features in Pillar

by Ben Coman

I just saw a comment in the Ecstatic issue tracker that most of its features have been pushed to Pillar, which sounds really interesting. Could someone describe this and how to generate a static site? Also, anyone know of templates suitable for a small engineering consultancy? Just in the last couple of days a need has arisen for me to do this. cheers -ben

July 16, 2018

Re: [Pharo-users] Smalltalk Programming Competition

by horrido

Actually, my math is wrong: 800 people x C$20 will make this happen! We're so close, I can smell it! horrido wrote > It's been one full month since the GoFundMe campaign began. We've raised > C$3,080 from 25 generous contributors. It's a good start, but we're still > a > long way off. In order to make the goal more attainable, I've lowered the > funding goal again, this time, to C$20,000. And for the last time. You > see, > C$20,000 is necessary for the MVC (not Model-View-Controller, but Minimum > Viable Competition). Anything less and we don't have an impactful > marketing > event. > > Please spread the word on social media. Please make use of your email > contacts. Let's reach as many people as we can. I will bet dollars to > doughnuts that not every Smalltalk fan in the world is aware of this > campaign and programming competition. It only takes about 1,000 people > giving a paltry $20 each to make this happen. How hard can it be? > > > > horrido wrote >> So far, we've raised CA$2,400 from 18 generous contributors. Not bad for >> the >> first two weeks of the GoFundMe campaign: >> https://www.gofundme.com/smalltalk-programming-competition >> >> I've lowered the funding goal to $25,000. So we're now about 10% of the >> way >> to the target. >> >> Meanwhile, I've been busy preparing for the competition. Here is the >> competition website, currently rigged as a demo: >> http://smalltalkrenaissance.pythonanywhere.com/JRMPC/default/index >> >> When it goes live, the proper sponsors will be displayed, and the >> database >> will be scrubbed clean. >> >> I've also design T-shirts (swag) for the competition. Here's the main >> design: <http://forum.world.st/file/t128560/T-shirt-x.png> >> >> Here's the alternate design: >> <http://forum.world.st/file/t128560/Hot-Air-Balloon-x.png> >> >> Everything is lining up, ready to go. >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 16, 2018

Re: [Pharo-users] XML support for pharo

by oswall arguedas

Hello Peter I proceed to install them in the project. I will feed it back. Thanks Oswall ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org> en nombre de Peter UhnÃ¡k <i.uhnak(a)gmail.com> Enviado: sÃ¡bado, 14 de julio de 2018 15:29 Para: Any question about pharo is welcome Asunto: Re: [Pharo-users] XML support for pharo Hi Oswall, for processing, take a look also at these three projects. They work on top of XML libraries, but provide some automation/simplification/inference. https://github.com/peteruhnak/xml-dom-visitor https://github.com/peteruhnak/xml-magritte-generator https://github.com/peteruhnak/xmi-analyzer Peter On Thu, Jul 12, 2018 at 10:00 PM, oswall arguedas <oswallcr(a)hotmail.com<mailto:oswallcr@hotmail.com>> wrote: Solved To access the values of the nodes is as follows: yearmem: = (tree xpath: '// year') first contentString asNumber. I also edit the other methods of the XMLNode class. Thanks Oswall ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> en nombre de PBKResearch <peter(a)pbkresearch.co.uk<mailto:peter@pbkresearch.co.uk>> Enviado: jueves, 12 de julio de 2018 12:09:20 Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] XML support for pharo Hi Oswall Well, you have located the correct node, which is some kind of XMLNode, so all you need is to access its content. If you browse the class and look at its âaccessingâ protocol, you see the method XMLNode>>#contentString, which will give you, in your test case, â2014â as a string. If you want to enter it in the database as a number, asNumber will do thatâ HTH Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> On Behalf Of oswall arguedas Sent: 12 July 2018 18:35 To: 'Any question about pharo is welcome' <pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org>> Subject: Re: [Pharo-users] XML support for pharo Hello Peter, Thanks for your help. The value I get is: <year> 2014 </ year> What I need is to extract the atomic value of the node, which is: 2014 To assign it to variables and create objects. I can not find how to obtain that punctual value 2014. The main purpose is to read many xml files and create smalltak objects with that data, then save them in DB and process the data. ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> en nombre de PBKResearch <peter(a)pbkresearch.co.uk<mailto:peter@pbkresearch.co.uk>> Enviado: jueves, 12 de julio de 2018 11:17:41 Para: 'Any question about pharo is welcome' Asunto: Re: [Pharo-users] XML support for pharo Hi Oswall What sort of failure did you get? It helps with this sort of thing to execute the code in a playground and inspect the result. One thing you need to know is that the result of xpath is almost always some sort of XMLCollection, even when there is only one element. I would expect the result you want if you write yearmem := (tree xpath: âcardset/card/yearâ) first. Note that you should not need a slash at the start; xpath starts searching in the children of the top node. Also you do not need to give every step of the hierarchy; you can always skip levels provided the result specifies a unique route to the node you want. So in this case you can write: yearmem := (tree xpath: â//yearâ) first. Hope this helps Peter Kenny From: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> On Behalf Of oswall arguedas Sent: 12 July 2018 17:09 To: pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org> Subject: Re: [Pharo-users] XML support for pharo Regards, I practice with the example of the book. I can not read the atomic values of the nodes. For example, with this piece of the example: <cardset> <card> <cardname lang = "en"> Arcane Lighthouse </ cardname> <types> Land </ types> <year> 2014 </ year> To get the atomic value of the node year and assign it to the variable yearmem, I do it like this: yearmem: = tree xpath: '/ cardset / card / year'. But it fails. How do I get the 2014 value? Thank you Oswall ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> en nombre de oswall arguedas <oswallcr(a)hotmail.com<mailto:oswallcr@hotmail.com>> Enviado: miÃ©rcoles, 11 de julio de 2018 20:17:55 Para: pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org> Asunto: Re: [Pharo-users] XML support for pharo Thanks Franz and Monty. I'm working on it, everything is going very well. The feedback when I master it. Oswall ________________________________ De: Pharo-users <pharo-users-bounces(a)lists.pharo.org<mailto:pharo-users-bounces@lists.pharo.org>> en nombre de monty <monty2(a)programmer.net<mailto:monty2@programmer.net>> Enviado: miÃ©rcoles, 11 de julio de 2018 03:32 Para: pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org> Asunto: Re: [Pharo-users] XML support for pharo This is the latest version of the XML/XPath Scraping Booklet: <https://files.pharo.org/books-pdfs/booklet-Scraping/2018-01-07-scrapingbook…> Scraping HTML with XPath - files.pharo.org<https://files.pharo.org/books-pdfs/booklet-Scraping/2018-01-07-scrapingbook…> files.pharo.org<http://files.pharo.org> 1.6 Alargeexample â¢ Siblings.Siblingsarechildnodesthathavethesameparent.Thecard-name,types,year,rarity,expansionandcardtextelementsareallsib- ___ montyos.wordpress.com<http://montyos.wordpress.com>

July 16, 2018

Re: [Pharo-users] Request for Windows test

by Jan BlizniÄenko

Hello No, I have only default world menu there (same as with empty image). Note that some of those errors in info messages I receive even for the empty Pharo 7 image, so it's probably just me having issues with current Pharo 7, not with your app itself. Jan HilaireFernandes wrote > Thanks for your feedbacks. > > Jan, when you click in the background do you have the Dr. Geo world > menu? If so can you open a sketchwhen selecting "Open a Sketch" ? > > Thanks > > Hilaire > > > Le 12/07/2018 Ã 11:25, Jan BlizniÄenko a Ã©critÂ : >> Hi >> >> Windows 10 1803 64bit: >> Running via DrGeo.bat, Pharo itself starts (I have SmartScreen disabled), >> but when opened I receive multiple errors in (gray) info messages and I >> do >> not see a way to use you app (if there should be any opened GUI or world >> menu items). >> >> 2018-07-12.png <http://forum.world.st/file/t369698/2018-07-12.png> >> >> Jan > > -- > Dr. Geo > http://drgeo.eu -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 15, 2018

Re: [Pharo-users] Pharo 6 Freetype plugin stopped working after Windows update

by Jan BlizniÄenko

Agreed, it's not just FT. And it happens to me very often. Rebooting PC works every time (well, since it seems random-ish, MOST of the times), but to close all my work just to reboot PC for Pharo is quite annoying. Jan Peter UhnÃ¡k wrote > This is not FT plugin problem. This is Windows failing to load a proper > dll > for Pharo. Happens regularly at least with FT and Cairo. > > Peter > > On Fri, Jul 13, 2018 at 10:00 AM, webwarrior < > reg@ > > wrote: > >> Peter Kenny wrote >> > Hello >> > >> > This seems exactly like a problem I reported almost exactly a year ago >> - >> > 15 July 2017. Peter Uhnak reported then that he saw it regularly. The >> only >> > sure remedy we found is to reboot the machine - occasionally reboot >> twice. >> > I am using Pharo 6.1 on Windows 10. Since that report, I have seen it >> very >> > rarely. Most recently I found that the Pharo window appearance was >> > distorted - wrong font size etc - but I did not see the debug console >> > error message. >> > >> > Advice to Webwarrior - reboot machine and see if it goes away. >> > >> > HTH >> > >> > Peter Kenny >> >> Rebooted, and the problem did go away. >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 15, 2018

Re: [Pharo-users] XML support for pharo

by Sean P. DeNigris

Peter UhnÃ¡k wrote > Did you read the README? If I had read you're wonderful readme, I wouldn't have asked ;) All clear now. Thanks. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 15, 2018