March 2016 - Pharo-users - lists.pharo.org

BaselineOf's and Loose Dependencies
by Sean P. DeNigris March 30, 2016

March 30, 2016

I know this is not technically a Pharo question, but I'm in China on my honeymoon and can't access the Metacello Google group! There was a pattern in pre-BaselineOf Metacello where one would define dependencies loosely in the #baselineXyz:, and then pin them to a specific version in the #versionAbc:. For example: baseline100: spec ... project: 'BabyMock' with: [ spec className: #ConfigurationOfBabyMock; versionString: #'stable'; repository: 'http://smalltalkhub.com/mc/zeroflag/BabyMock/main/' ] ... and then: version10: spec ... spec project: 'BabyMock' with: '1.2' ... How does one handle this sort of thing with #baseline:import:? This is what I came up with: version10: spec ... baseline: 'BabyPhexample' with: [ spec repository: 'github://seandenigris/Baby-Phexample:INSERT-SHA-HERE/repository' ]; import: 'BabyPhexample'. spec project: 'BabyMock' with: '1.2' ... But I got this error from the last line: MessageNotUnderstood: receiver of "fetchUsing:" is nil Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/BaselineOf-s-and-Loose-Dependencies-tp4885749.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

2 5

GTSpotter fuzzy search
by Peter UhnÃ¡k March 30, 2016

March 30, 2016

Would be possible to have fuzzy-search? Or rather Pascal-based search? RTAE -> *RTA*bstract*E*xample BCF -> *B*l*C*onfigurable*F*ormatter etc.

4 5

NBSQLite on Moose 5.1 connection problems
by Torsten Bergmann March 29, 2016

March 29, 2016

Offray wrote: >We have been dealing with a pretty strange and awkward problem in our >workshops regarding the NBSQlite package and Moose 5.1 interaction I checked in a recent Moose 5.1 image from CI (which is based on latest Pharo 4 #40626) and anything looks good (see screenshot attached). I tested on Windows, the sqlite3.dll is placed in the VM executable directory (folder of Pharo.exe). Unfortunately you just posted the stack trace - but not the error message that was displayed in the debugger. But as it failed already in the first API call (opening sqlite) I can only guess it is again the issue that the module was not found on your local machine. But you also said sometimes it workes and sometimes not. Mmmmhh. In case you have Sqlite cipher support already loaded you might have an issue after running the tests. I found the reason: The NBSQLCipher3ConnectionTest switches to sqlcipher support in #setUp but does not reset the class variable #Library in NBSQLite3FFI which is holding the module name back to 'sqlite' module in #tearDown). This was experimental stuff from Pierce anyway but it might have been in the config loaded already. I fixed this now in general by providing a #tearDown and updated the config with a new version 1.3 having also all latest packages. Fix is not optimal as when one is using sqlciper module the NBSQLCipher3ConnectionTest test switches back to sqlite then. But should be OK as most people use sqlite instead of sqlcipher and we discontinue NBQLite3 package starting with Pharo 5 anyway. (NBSqlite is not working with Pharo 5 because NB was dropped in favour of UFFI). So anything green here in the tests with latest config when I try in fresh images (Pharo 4/Moose 5.1). Also your example script works and outputs to the Transcript in both images. So please: ========== 1. load updated NBSqlite3 from config browser again in a fresh Mosse 5.1 image and try to provoke the error again 2. In case you still have trouble check what the expression: NBSQLite3FFI classVarNamed: 'Library' returns. It should give #sqlite3 on Mac and 'sqlite3' on Linux/Windows 3. If broken or the system still laments about the module you can even try to give the module with an absolute path: NBSQLite3FFI classVarNamed: 'Library' put: '/mypath/sqlite3.so' HTH Bye T.

2 1

condensing a changes file
by Johannes Brauer March 29, 2016

March 29, 2016

Hi, in VisualWorks there is the feature to condense a changes (.cha) file. Is it possible in Pharo, too? Johannes

3 3

NBSQLite on Moose 5.1 connection problems
by Offray Vladimir Luna CÃ¡rdenas March 29, 2016

March 29, 2016

Hi, We have been dealing with a pretty strange and awkward problem in our workshops regarding the NBSQlite package and Moose 5.1 interaction. Some times it works, most times it doesn't, specially when I'm in the workshop. My solution was to unzip the sqlite package for the platform, copy sqlite3 as libsqlite3.so in the "bin/" directory of the platform and it worked (last week). Yesterday I tried the same in our workshop and if failed again even in my local installation. I tried copying and renaming (as "sqlite3.so", "libsqlite3.so") and put it where the moose image lives ("shared/") without any success. Is the biggest frustration in our workshops and we need to export as csv and read manually each useful query result in SQLite... and I can made sense of the error trace or why this error is happening. Monticello reports NBSQLite3-TorstenBergmann.26. Any pointer on how to solve it in a reliable way is welcomed. Here is the error log, while executing http://ws.stfx.eu/POQCW0NVKZJN: NBFFICallout(Object)>>error: NBFFICallout>>generateCall:module: [ :gen | gen callType: conv; sender: context; parseOptions: options; generateCall: functionSignature module: moduleNameOrHandle ] in NBFFICalloutAPI>>function:module: in Block: [ :gen | ... [ bytes := aBlock value: (self newForMethod: method) ] in NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry: in Block: [ bytes := aBlock value: (self newForMethod: metho...etc... BlockClosure>>on:do: NBRecursionDetect class>>in:during: NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry: NBFFICallout class(NBNativeCodeGen class)>>handleFailureIn:nativeCode: NBFFICalloutAPI>>function:module: NBSQLite3FFI(Object)>>nbCall:module: NBSQLite3FFI>>apiOpen:via: NBSQLite3FFI>>open:via: NBSQLite3Connection(NBSQLite3BaseConnection)>>open NBSQLite3Connection class(NBSQLite3BaseConnection class)>>openOn: UndefinedObject>>DoIt OpalCompiler>>evaluate RubSmalltalkEditor>>evaluate:andDo: RubSmalltalkEditor>>highlightEvaluateAndDo: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] in [ textMorph textArea handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] ] in GLMMorphicPharoPlaygroundRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: in Block: [ ... RubEditingArea(RubAbstractTextArea)>>handleEdit: [ textMorph textArea handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] ] in GLMMorphicPharoPlaygroundRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: in Block: [ ... WorldState>>runStepMethodsIn: WorldMorph>>runStepMethods WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: WorldMorph>>doOneCycle [ [ World doOneCycle. Processor yield. false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in Block: [ ... [ self value. Processor terminateActive ] in BlockClosure>>newProcess in Block: [ ... Cheers, Offray

1 0

Roassal2 on Ubuntu 64
by Evan Donahue March 29, 2016

March 29, 2016

Hello, I'm trying to learn Roassal, but I can't seem to get the first visualization from https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/QuickStart/… working on any combination of image and vm. I've tried the vm+40 and vm+50 from get.pharo and the moose 6.0 image from the moose site. The issue seems to be that CairoLibrary>>unixModuleName does not contain the /usr/lib/x86_64-linux-gnu/libcairo.so.2 path where 64-bit Ubuntu installs cairo. If I symlink that library, I get an Error: External module not found from AthensCairoSurface. I don't really know enough about the external module system to know what this is telling me. Any ideas would be much appreciated. Thanks, Evan

9 20

Additional Pomodoro features
by Torsten Bergmann March 29, 2016

March 29, 2016

Stephan Eggermont wrote: >Couldn't write to the repo, Added you as contributor >and not everything is as clean as it should be then clean it up ;) Bye T.

1 0

[Metacello] about required list
by stepharo March 29, 2016

March 29, 2016

Hi using the dependency analyser I see that may packages have the following dependencies for example package: 'Math-DistributionGamma' with: [ spec requires: #('Math-Core' 'Math-DHB-Numerical' 'Math-Series' 'Math-Core-Distribution') ]; package: 'Math-DistributionBeta' with: [ spec requires: #('Math-DistributionGamma' 'Math-Core' 'Math-Core-Distribution' 'Math-DHB-Numerical' 'Math-Series') ]; so I wrote the requirement this way Now does it have an impact on Metacello and should I keep only the direct depend. package: 'Math-DistributionBeta' with: [ spec requires: #('Math-DistributionGamma' ) ]; This is annoying because I have 50 packages and doing that manually is a pain. Stef

4 3

[Metacello] Apparent loop in before / after ....
by stepharo March 28, 2016

March 28, 2016

hi dale I'm working a pretty large configuration and I got the following error messsage (and I do not understand I cannot debug). Do you have any suggestion because I did not even know that this error exist before. I disabled the validation of the config because it validates packages that I cannot modify such as XML or SMark. Stef

3 2

Call for action for Roassal
by Alexandre Bergel March 28, 2016

March 28, 2016

Dear community, As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: What are the 3 aspects you would like to see improved in Roassal? You can answer publicly or by sending private messages. Kind regards, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

8 26