- Pharo-dev - lists.pharo.org

the athens tutorial is not working in latest 30.
by StÃ©phane Ducasse Dec. 12, 2013

Dec. 12, 2013

2 1

Image frozen on Socket>>waitForConnectionFor: timeout ifTimedOut: timeoutBlock
by Sebastian Sastre Dec. 12, 2013

Dec. 12, 2013

Hi guys, I'm having an issue.. What happens? The image UI gets frozen when terminating a thread that's waiting on that method What I've discovered so far? seaside /config responds (but nothing else) restarting the UI process results to no avail terminating the process (selected in that screenshot) freezes everything but.. debugging works and.. when I debug and close the debugger freezes everything, but.. if instead I evaluate with an inspector the block [(status = WaitingForConnection) and: [(msecsEllapsed := Time millisecondsSince: startTime) < msecsDelta]] it answers false and closing the dbugger after that leaves the system normal (meaning that if I terminate the process after that, it doesn't freeze and all go as expected) Still working on it.. Help and ideas appreciated

1 1

[Pharo Trick: #0008] - If appropriate use the memory file system
by Torsten Bergmann Dec. 12, 2013

Dec. 12, 2013

----------------------------------------------------------------------------------- [Pharo Trick: #0008] - If appropriate use the memory file system ----------------------------------------------------------------------------------- Works in: Pharo 2.0, 3.0, ... ----------------------------------------------------------------------------------- It may be possible that your application has to export some data into an external file in a specific format. Pharo allows writing into a file using Streams as any other Smalltalk. But sometimes you want to check the result right from the Pharo image without having to look into the external file using external tools. So the trick here is to use the memory file system instead of the real disk file system during development since also no cleanup on the hard disk is required afterwards: |fs| fs := FileSystem memory. (fs / 'hello.txt') writeStreamDo: [:s| s nextPutAll: 'Exported data' ]. (fs / 'hello.txt') readStream contents. The memory filesystem is also nice if you need to work with files within a unit test. So when the test runs nothing remains left on the hard disk. If you need a real copy of the file on the hard disk you can also copy from the memory file system to the disk file system using #copyTo: |fs| fs := FileSystem memory. (fs / 'hello.txt') writeStreamDo: [:s| s nextPutAll: 'Memory first and then disk' ]. (fs / 'hello.txt') copyTo: (FileSystem disk / 'exactCopy.txt')

4 5

[Pharo Trick: #0001] - Simple TODO list
by Torsten Bergmann Dec. 12, 2013

Dec. 12, 2013

Hi, the mailinglist, stackoverflow and other Pharo related medias are typically used in the "here is a question to problem" followed by an "answer from community" style. But lets also think the other way around: if we already have a solution for a problem that others may have too or may have in the future we should share the answer/solution as well. I'm sure many of you have some tricks that make developing with Pharo much easier and others can profit from these tricks if we share them here on the list. Be it - a simple and useful script - a simple key combination other may not yet know of - a package one can use or how you use it - a link to a nice description on the web related on how to use Pharo - a custom tool that makes development easier - an algorithm or something that you think was solved very elegant - a way you solved a common problem easily in your app - ... Then just describe it in a few lines and post it. Also write in which Pharo version you tried it - this makes it easier for others to see in which version the trick/solution is known to work. The idea goes like this: if you have a trick to share then send a mail with subject "Pharo Trick: #xxxx] - Short Description" to the Pharo dev AND Pharo user list (see http://lists.pharo.org) Make sure to increase the trick counter xxxx. Using this special subject one can later easily get the tricks from the mailinglist archive. Also others can refer to the trick if it solves a common problem other may ask for on the list. Lets see if we are able to reach the goals of 100, 1000 or more Pharo tricks ;) Bye T. I will start with something easy but useful: ----------------------------------------------------------------------------------- [Pharo Trick: #0001] - Simple TODO ----------------------------------------------------------------------------------- Works in: Pharo3.0 Latest update: #30635 but should work in other versions too ----------------------------------------------------------------------------------- If you develop an app with Pharo you may not yet fully implement all features. Some kind of marker for future "ToDo's" is often needed. Using a pragma on a method is the easiest solution here: foo <todo: 'Add world later'> "That method is not yet fully implemented" Transcript show: 'Hello' Using a simple expression in the workspace you can browse all the TODOs for your project afterwards in a window: SystemNavigation default browseAllSendersOf: #todo: You can even query the system for the todo descriptions if you need the full list of things to work on: (PragmaCollector filter: [:prg | prg keyword = 'todo:']) reset; collect: [:each| each arguments first ] As the pragma keyword #todo: is very common and may be used by others too it may be wise to use a custom one like "myappplicationTodo:" or similar. -----------------------------------------------------------------------------------

6 7

[Pharo Trick: #0004] - Run code using a key command to speedup development
by Torsten Bergmann Dec. 12, 2013

Dec. 12, 2013

----------------------------------------------------------------------------------- [Pharo Trick: #0004] - Run code using a key command to speedup development ----------------------------------------------------------------------------------- Works in: Pharo3.0 Latest update: #30637 but should work in other 2.0/3.0 versions ----------------------------------------------------------------------------------- If you have to run some code very often you typically have to evaluate it from a workspace over and over again. But to speed up you can assign a global keymapping which allows to run it with a simple keyboard shortcut: World on: $a shift command do: [ Object browse ]. Evaluate this once in a workspace. After that anytime you press SHIFT, the command button (on Windows this is ALT) and A together the block gets evaluated and your code runs easily. Background: =========== In Pharo there is a global morph called "World" representing the desktop. One can assign a key combination to any morph including this world. If you are interested on the Keymappings then read http://playingwithobjects.wordpress.com/2013/03/19/keymappings-101-for-phar… for more

7 10

Fwd: Categories, packages, and tags [cont'd]
by Roberto Minelli Dec. 12, 2013

Dec. 12, 2013

Hi guys, I have a question about the new âPackageTreeModelââ¦ In a previous discussion (https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg09271.html) we discussed about the new package model. Now I understood it but I am wondering one thing. Since Stef said that categories will be removed, i.e., the ByteSymbol representation of what I used to call packages, I am wondering how one could ask the system which are the installed packages, tags, etc. In short I want to know which is the best method to ask what used to be âSystemOrganization categoriesâ. Thanks in advance, R

3 5

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

Dec. 12, 2013

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

1 0

[pharo-project/pharo-core] 01f4ef: 30639
by GitHub Dec. 12, 2013

Dec. 12, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 01f4ef1faba4b076c0d655bb2db238bb8556f597 https://github.com/pharo-project/pharo-core/commit/01f4ef1faba4b076c0d655bb… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-12-12 (Thu, 12 Dec 2013) Changed paths: M Compression.package/extension/ReadWriteStream/instance/asUnZippedStream.st M MenuRegistration.package/PragmaMenuBuilder.class/class/private/orderAssignBlock.st M NECompletion.package/NECOverrideModel.class/instance/initialize-release/initializeSelectors.st M RecentSubmissions.package/MessageListNonInspectableNode.class/instance/testing/includes_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script294.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30639.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/SlotClassBuilder.class/instance/private validating/validateClassName.st M System-CommandLine.package/BasicCommandLineHandler.class/instance/private/selectHandlers.st A System-CommandLine.package/BasicCommandLineHandler.class/instance/private/subCommandsRoot.st A System-CommandLine.package/CommandLineArguments.class/instance/accessing/optionAt_ifPresent_ifAbsent_.st M System-CommandLine.package/CommandLineArguments.class/instance/testing/longOptionAt_ifAbsent_.st A System-CommandLine.package/CommandLineHandler.class/instance/accessing arguments/optionAt_ifPresent_ifAbsent_.st M System-Hashing.package/DigitalSignatureAlgorithm.class/instance/large integer arithmetic/isProbablyPrime_.st M System-Settings.package/SettingTree.class/instance/querying/childrenOf_.st M System-Support.package/SystemNavigation.class/instance/query/allReferencesToPool_.st M System-Support.package/SystemNavigation.class/instance/query/allReferencesToPool_from_.st M Tools.package/SyntaxErrorDebugger.class/instance/initialization/checkForUnprintableCharacters_.st A Tools.package/TimeStampMethodConverter.class/instance/private/formattedModificationTextFor_atStamp_.st M Tools.package/TimeStampMethodConverter.class/instance/private/internalGetText.st Log Message: ----------- 30639 12391 Error on MessageBrowser when selecting TimeStamp display https://pharo.fogbugz.com/f/cases/12391 12340 Cleanup on more Tools methods https://pharo.fogbugz.com/f/cases/12340 12411 Small missing methods https://pharo.fogbugz.com/f/cases/12411 http://files.pharo.org/image/30/30639.zip

1 0

Using TreeModel>>selectAll
by Martin Dias Dec. 12, 2013

Dec. 12, 2013

Hi, I'm not sure how this method should be used. I tried in different ways, for example: TreeModel new roots: #(1 2 3); selectAll; openWithSpec But always the items are unselected. Is it a bug? or I didn't find the way to use it? Thanks, MartÃn

4 12

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