December 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Which tests should be run in CI?
by Stephan Eggermont Dec. 12, 2013

Dec. 12, 2013

Torsten, For unit tests building on green builds might be enough, but what about integration/smoke tests? Concrete case: I added a test to check that no class implements >>packages That is a test that should be run by all builds, but is not. The consequence is that Moose and Pharo3 based builds using seaside or magritte can not reliably use "senders of" I assume there are more tests like this. Stephan

4 9

MessageNotUnderstood: SmallInteger>>isEmpty
by Dario Trussardi Dec. 12, 2013

Dec. 12, 2013

Ciao, i work with a new Pharo 2.0 20628 image. I do first : A) Gofer new url: 'http://smalltalkhub.com/mc/DiegoLont/QCMagritte/main'; package: 'ConfigurationOfQCMagritte'; load. and: B) ((Smalltalk at: #ConfigurationOfQCMagritte) project version: '0.2') load: #( 'Demo' ). After some works the system when Fetching 1.0.2.1 of ConfigurationOfTwitteBootstrap erase the error: SmallInteger(Object)>>doesNotUnderstand: #isEmpty MetacelloMCVersionSpec>>resolveToLoadableSpecs:map: MetacelloMCVersionSpec>>resolveToLoadableSpecs: MetacelloMCVersionSpec>>expandToLoadableSpecNames: in Block: [:cache | ... MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:at:doing: MetacelloMCVersionSpec>>expandToLoadableSpecNames: MetacelloMCVersion>>expandToLoadableSpecNames: MetacelloMCProjectSpec>>relativeCurrentVersion in Block: [vrsn expandToLoadableSpecNames: (loadList := self...etc... BlockClosure>>on:do: MetacelloMCProjectSpec>>relativeCurrentVersion MetacelloProjectReferenceSpec>>relativeCurrentVersion MetacelloMCVersionSpec>>isPartiallyCurrentAgainst: in Block: [:prj | ... MetacelloProjectReferenceSpec>>projectDo:packageDo:groupDo: MetacelloMCVersionSpec>>specsNamed:projectDo:packageDo:groupDo: in Block: [:name | | pkgSpec | (pkgSpec := map... Array(SequenceableCollection)>>do: MetacelloMCVersionSpec>>specsNamed:projectDo:packageDo:groupDo: MetacelloMCVersionSpec>>isPartiallyCurrentAgainst: MetacelloMCVersionSpec>>isPartiallyCurrent MetacelloMCProject(MetacelloProject)>>currentVersionAgainst: in Block: [:version | ... Array(SequenceableCollection)>>do: MetacelloMCProject(MetacelloProject)>>currentVersionAgainst: in Block: [:cache | ... MetacelloPharoPlatform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [:dict | ... MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: Any idea? Thanks, Dario

4 7

[Pharo Trick: #0006] - Run code from a button window
by Torsten Bergmann Dec. 12, 2013

Dec. 12, 2013

----------------------------------------------------------------------------------- [Pharo Trick: #0006] - Run code from a standalone button window ----------------------------------------------------------------------------------- Works in: Pharo 2.0, 3.0, ... ----------------------------------------------------------------------------------- In Pharo there is a class called ButtonModel - it is a model used for buttons when building UI's with the Spec framework. But it can be used also standalone to open a button window with an action block: |b| b := ButtonModel new. b openWithSpec; label: 'Run my code'; action: [ Transcript open ] So you just have to click to run some code.

2 1

[Pharo Trick: #0005] - Pick up morphs that do not want to be picked up"
by phil＠highoctane.be Dec. 12, 2013

Dec. 12, 2013

Usually one can deal with morphs by doing the alt-shift-click on them, so that we get the halos and do whatever. Now, some morphs do not want to let you do this (like the Pharo image on the desktop background) - or you just don't see them as they are leftovers from experiments. A shift click (on Windows) brings a "find window" popup where you can select what you want, no matter what. Try to pick the ImageMorph in there for the Pharo Logo. Phil

1 0

[pharo-project/pharo-core]
by GitHub Dec. 12, 2013

Dec. 12, 2013

Branch: refs/tags/30638 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 3f85b9: 30638
by GitHub Dec. 12, 2013

Dec. 12, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 3f85b941eaab5b182b2139d9d3f889ad2f059cfa https://github.com/pharo-project/pharo-core/commit/3f85b941eaab5b182b2139d9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-12-12 (Thu, 12 Dec 2013) Changed paths: M Graphics-Display Objects.package/DisplayMedium.class/instance/private/highLightBitmaps.st M Graphics-Display Objects.package/DisplayMedium.class/instance/private/initializeHighLights.st M Keymapping-Tools-Spec.package/KMDescription.class/class/specs/defaultSpec.st M Keymapping-Tools-Spec.package/KMDescription.class/definition.st A Keymapping-Tools-Spec.package/KMDescription.class/instance/accessing/categoryList.st R Keymapping-Tools-Spec.package/KMDescription.class/instance/accessing/displayList.st R Keymapping-Tools-Spec.package/KMDescription.class/instance/accessing/dropList.st R Keymapping-Tools-Spec.package/KMDescription.class/instance/accessing/list.st A Keymapping-Tools-Spec.package/KMDescription.class/instance/accessing/orderingList.st A Keymapping-Tools-Spec.package/KMDescription.class/instance/accessing/shortcutList.st A Keymapping-Tools-Spec.package/KMDescription.class/instance/initialization/collectDescriptionShortcut.st A Keymapping-Tools-Spec.package/KMDescription.class/instance/initialization/collectShortcutDescription.st A Keymapping-Tools-Spec.package/KMDescription.class/instance/initialization/initCategoryList_.st M Keymapping-Tools-Spec.package/KMDescription.class/instance/initialization/initialize.st M Keymapping-Tools-Spec.package/KMDescription.class/instance/initialization/initializePresenter.st M Keymapping-Tools-Spec.package/KMDescription.class/instance/initialization/initializeWidgets.st A Keymapping-Tools-Spec.package/KMDescription.class/instance/initialization/updateShortcutList.st M Keymapping-Tools-Spec.package/KMDescription.class/instance/protocol/categories_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/package filter/buildPackageSearch.st A Nautilus.package/PackageTreeNautilusUI.class/instance/package/fileOutPackages_.st M Nautilus.package/extension/RPackage/instance/fileOut.st A Nautilus.package/extension/RPackageTag/instance/fileOut.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script293.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30638.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Settings.package/SettingBrowser.class/README.md Log Message: ----------- 30638 12409 DNU RPackage>>#item when FileOut https://pharo.fogbugz.com/f/cases/12409 12402 Display reverse: leads to error https://pharo.fogbugz.com/f/cases/12402 12384 Package filter dialog: Make the feature more apparent https://pharo.fogbugz.com/f/cases/12384 12396 SystemNavigation class comment uses deprecated message https://pharo.fogbugz.com/f/cases/12396 12094 Drop down does show the items wrongly https://pharo.fogbugz.com/f/cases/12094 http://files.pharo.org/image/30/30638.zip

1 0

Voronoi diagram
by Natalia Tymchuk Dec. 11, 2013

Dec. 11, 2013

Hello. I started implementing visualization of Voronoi diagrams and I need to do a lot of operations on the lines and polygons. I have some questions: Is it implemented somewhere? Did somebody do something with the Voronoi diagrams? Best regards, Natalia

8 12

Which tests should be run in CI?
by Stephan Eggermont Dec. 11, 2013

Dec. 11, 2013

I notice that several builds are green, though I added a breaking test to Pharo 3. That probably means that those builds don't run all of the Pharo tests. Most builds probably don't need to run all tests (all the time), but it might be useful to be able to mark tests as integration tests, that are expected to be run by all downstream builds. Concrete, every Pharo 3 build that loads Grease should currently be red. Stephan

2 1

Workaround for File Out Package
by Alfredo Sanzo Dec. 11, 2013

Dec. 11, 2013

Hi! I am having a problem when trying to export a Package to .st using Right Click -> Fileout. Here is the case: https://pharo.fogbugz.com/f/cases/7519 Do anyone know a workaround? A way to do it via code? This is a feature we use at several universities in order to provide fast and simple code exporting, without the need to explain code sharing principles. Thanks in advance for any response, and sorry if this is not the right list. :) Cordially, Alf

3 3

[ANN] Neo-Caching
by Sven Van Caekenberghe Dec. 11, 2013

Dec. 11, 2013

Hi, Caching is an important technique to trade time (speed of execution) for space (memory consumption) in computation. Used correctly, caching can significantly improve an applicationâs performance. Given the key/value nature of a cache, a Dictionary is often the first data structure used for implementing it. This is however not a good idea since a simple Dictionary is unbounded by definition and can/will lead to explosive cache growth. Quick and dirty hacks to turn a Dictionary into a least-recently-used (LRU) and/or time-to-live (TTL) based limited cache are often incorrect and inefficient. The LRUCache implementation currently in Pharo is too simple and not efficient, being O(n) on its main operation. Pharo deserves and needs a good LRU/TTL cache implementation that can/should be used uniformly in various places of the system and in code built on top of it. That is why I implemented a proposal. Neo-Caching is an implementation of both a good LRU cache as well as a TTL extension of it. The caches are easy to use, yet have a number of interesting features. The implementation is properly O(1) on its main operations and is 2 to 3 times faster than LRUCache. The package also contains a double linked list implementation. The code comes with a full set of unit tests. There are class and method comments and the code is easy to read. The code (which has no dependencies) can be found here http://mc.stfx.eu/Neo http://www.smalltalkhub.com/mc/SvenVanCaekenberghe/Neo/main There is only one package to load. The code has been written in Pharo 3.0 but it should run on older versions as well. Code Letâs create a 16K ordered collection of keys that have some repetitions in them with a reasonable distribution: data := Array streamContents: [ :out | 1 to: 4096 do: [ :each | each primeFactorsOn: out. out nextPut: each ] ]. data := data collect: [ :each | each asWords ]. By using #asWords the keys have better hash properties. Now, we put all this in a cache: cache := NeoLRUCache new. cache maximumWeight: 512. cache factory: [ :key | key ]. data do: [ :each | cache at: each ]. cache. ==> a NeoLRUCache(#512 512/512 [ 1 ] [ :key | key ] 72%) We had a 72% hit ratio, which is good. The cache is of course full, 512/512 with 512 entries (not necessarily the same thing, see further). We can now benchmark this: [ data do: [ :each | cache at: each ] ] bench. ==> '35.8 per second.â And compare it to LRUCache: cache := LRUCache size: 512 factory: [ :key | key ]. [ data do: [ :each | cache at: each ] ] bench. ==> '12.6 per second.â Features Instead of just counting the number of entries, which is the default behaviour, the concept of weight is used to determine when a cache is full. For each cached value, a block or selector is used to compute its weight. When adding a new entry causes the weight to exceed a maximum, eviction of the least recently used item(s) takes place, until the weight is again below the maximum. cache computeWeight: #sizeInMemory; maximumWeight: 16*1024. Will keep the cache below 16Kb in real memory usage. This can be very useful when caching various sized images or MC packages, for example. By default, no concurrent access protection takes place, but optionally a semaphore for mutual exclusion can be used. This slows down access. cache useSemaphore. NeoTTLCache extends NeoLRUCache by maintaining a timestamp for each cached value. Upon cache hit, there is a check to see if this timestamp is not older than the allowed time to live. If so, the value is stale and will be recomputed. (cache := NeoTTLCache new) timeToLive: 10 minutes; factory: [ :key | ZnEasy get: key ]; maximumWeight: 32*1024; computeWeight: #contentLength. cache at: âhttp://zn.stfx.eu/zn/numbers.txt'. ==> a ZnResponse(200 OK text/plain;charset=utf-8 71B) cache ==> a NeoTTLCache(#1 71/32768 #contentLength [ :key | ZnEasy get: key ] 0% 0:00:10:00) Would be a simple HTTP cache, keeping resolved URLs in memory for 10 minutes maximum before refreshing them. It uses #contentLength on ZnResponse to compute the weight. You can see from the print string that there is now 1 entry, while the weight is 17 bytes out of 32768. These are the main points, please have a look at the code. Feedback is welcome. Regards, Sven

8 17