January 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Package names
by Torsten Bergmann Jan. 11, 2010

Jan. 11, 2010

>We adopted the same naming rule as for tests. >We have NetworkSystemSettings as we have NetworkTests If you want to write a script that throws things out it would be easier to have "-" as a seperator: Without "-" you would have two options: "Network" "SystemSettings" "NetworkSystem" "Settings" So "Network-SystemSettings" is more explicit compared to a "NetworkSystem-Settings". Bye T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

2 1

[Pharo-project] Monticello repository edit works but doesn't update UI
by Mariano Martinez Peck Jan. 11, 2010

Jan. 11, 2010

Pharo image: Any Pharo core version: Any 1. Open a Monticello Browser and select any repository 2. Right button over the repository and then "edit repository info" 3. Change the URl to something different and press OK 4. The change has effect, but the UI still shows the precious URL, not the modified. If I close and open Monticello Browser again, it shows Ok. However, I think it should be updated after pressing OK. Issue: http://code.google.com/p/pharo/issues/detail?id=1774 Cheers Mariano

1 0

[Pharo-project] Package names
by Torsten Bergmann Jan. 11, 2010

Jan. 11, 2010

Shouldnt we rename some packages/class categories: "PolymorphSystemSettings" -> "Polymorph-SystemSettings" "CompilerSystemSettings" -> "Compiler-SystemSettings" ... so they would align with existing ones? Bye T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

4 3

[Pharo-project] Alien & (using Gofer and Flair)
by John M McIntosh Jan. 11, 2010

Jan. 11, 2010

Whoever is looking after the Alien Gofer & Flair loader needs to revisit the logic since Flair fights and loses against the current Gofer. Which then prevents Alien from loading as per the instructions supplied on: http://www.squeaksource.com/Alien.html -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

5 9

[Pharo-project] Interim build server
by Michael Roberts Jan. 11, 2010

Jan. 11, 2010

Hi, following on from the timely Hudson post ;-) I too have been working on continuous integration. I am more interested in identifying & integrating the various bits of plumbing first rather than the build solution itself. I figured the infrastructure needed to be understood first, and there could be value in such an interim solution To this end I have: -written a simple image builder that updates the image in place. -running remotely on a Linux host I have borrowed access -building PharoCore 1.1 from #11110 onwards -started to publish images at http://pharo.gforge.inria.fr/experimental/ remaining is to rename the core images to unstable and then look at running some tests. This has exposed various issues, mainly image timeout caused by the various dialogs that can popup when filing in code. so 1) if anyone would like to test the integrity of these experimental auto-build images, please do 2) discuss if something in this namespace http://pharo.gforge.inria.fr/<> is suitable for automatic publishing - i am not sure how you automatically create gforge "releases" but for core images perhaps this is not needed 3) find a real server we can run this on, (if this is considered worthwhile). My requirements are Linux + daemontools + vnc server - i can host my solution for a while, we need something strategic then once we have a server I'm happy to look at Hudson or whatever we consider the right tool for doing this. I have also been playing with Mason and sent some feedback to Colin. Like i say, for me the real issues are running a Pharo image completely automated. Cheers, Mike

5 9

[Pharo-project] Alien plugin? Status of VMMaker
by Schwab,Wilhelm K Jan. 11, 2010

Jan. 11, 2010

Do any of you know of an alien plugin for linux? Is VMMaker alive and well on Pharo? I am getting close to (perhaps) being able to move some number crunching onto Pharo, but it will depend on external libraries and callbacks. My reading suggests that the existing FFI is unable to handle callbacks, and that plugins are required. Alien looks a lot closer to what I have working on Dolphin. Unless Alien is pre-built, it appears that I am stuck with setting up VMMaker?? That might not be all bad, because I am suspicious I might want to use a plugin for OpenSSL, but that is (so far) a little further away. I would be happy to bypass that learning curve for a while longer :) Bill

6 8

[Pharo-project] [ANN 1.1] pre-built core#11151
by Marcus Denker Jan. 11, 2010

Jan. 11, 2010

... to not have a completely broken prebuilt, I made a new one: http://gforge.inria.fr/frs/download.php/25163/PharoCore-1.1-11151-UNSTABLE.…

1 0

[Pharo-project] inspector and auto-update
by John M McIntosh Jan. 11, 2010

Jan. 11, 2010

Hi I noticed that in the past (likely some current squeak image) When you brought up an inspector on an object it would auto-update the instance variables shown. However this behaviour is lacking in a PharoCore1.0rc1 Latest update: #10502 So is that what is expected? -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

5 4

[Pharo-project] [ANN] ClaseUseDiscovery tool
by Mariano Martinez Peck Jan. 11, 2010

Jan. 11, 2010

Hi folks: As part of my PhD I started to work with ImageSegment. This week I clean up all the stuff related to class discovery from there. I then wanted to put that extracted code in a separate class. I didn't like that code at all, so at the end I finished rewriting completely this stuff. The cool thing is that: - I remove all that stuff from ImageSegment (which has nothing to do with that) - I remove that stuff from classes like Behavior and ClassDescription - I put all these as an external package that can be perfectly loaded in core - I rewrote that in style that I like much more. At least for me, it is much more easy to understand and to use now - I wrote test cases - I wrote good class comment. The repository is: http://www.squeaksource.com/ClaseUseDiscovery and the license is MIT. It is a little project, but maybe someone find it useful. This project only works with Pharo images newer than 1.1 version 11142 I paste here the class comment of CUDClassesUseDiscoverer: Cheers Mariano A CUDClassesUseDiscoverer is a little class which can be used to discovering used and unused classes during a period of time. If you want to build minimal images, it is useful also to detect for example, the amount of classes that are used just to do a simple message invokating. It helps also when some classes are being used and you don't know why. Little examples of how to use it: | aDiscoverer | aDiscoverer := CUDClassesUseDiscoverer startDiscovery. ......DO SOMETHING HERE...... aDiscoverer stopDiscovery. After that, you can: aDiscoverer activeClassesDuringDiscovery. aDiscoverer inactiveClassesDuringDiscovery. aDiscoverer activeClassesByCategoryDuringDiscovery. aDiscoverer swapOutInactiveClassesDuringDiscovery. For more details, see the tests in class CUDClassesUseDiscovererTest. Explanation: The Virtual Machine pays attention not to crash totally when you put a nil in a Method Category. In addition, there is a possibility to force a MethodDictionary fault (message induceMDFault) with the message. This method copies the methodDict in the organization slot. Actually, it creates an Array with the methodDict and the organization and set it in the organization slot. Finally, it sets a nil to the methodDict instance variable. After this is done, when that class is used and the methodDict is asked (it is very important to acces the methodDict using the accessor) it checks whether it is nil or not. If it is nil, it will search for that methodDict in the Array of the organizaction it will then copy it to the methodDict instance variable and will log in Smalltalk at: #MDFaultDict. Sometimes you will see that you have classes that were used but you do not know why or who used it. To solve this question, we can have that log. But in order to have that trace, you have to use the message startDiscoveryWithTrace instead of startDiscovery. The log will be then put in that dictionary and you can inspect it after the discovery. Taking that explanation in mind, you can follow these steps: 1) Send the message CUDClassesUseDiscoverer startDiscovery or startDiscoveryWithTrace which forces a MethodDictionary fault in all classes. Yes! It sends the message induceMDFault to all classes except classes like Array, Object, Class, Message and MethodDictionary. After this, all classes but those ones, will have the methodDict with nil. 2) Do a few things, use the system for a while. Maybe even save and resume the image. 3) Stop the discovery. This will stop everything and restore all remaining MethodDictionary faults. It will also process which classes were active and which ones were not. 4) Now, it is easy. All classes that still have a nil in the mehodDict is because they were not used, and those who have something different from nil is because they were. With the message activeClassesDuringDiscovery or inactiveClassesDuringDiscovery you can and return the active or unactive classes respectively. There is also the message swapOutInactiveClassesDuringDiscovery which makes up segments by grouping unused classes by system category and write them to disk. There are some categories that are excluded because they have problems, like System and Kernel. If you started the discovery with the message startDiscoveryWithTrace, after doing all those steps you can then inspect Smalltalk at: #MDFaultDict and you will see that in the dictionary you will have an element per class. That element is a ByteString that contains all the stack trace. This shows you all the messages and why that class was used. This approach of swapping out inactive classes have two big problems: - The granularity is too high: the class. As soon as only one method is invoked, the whole class is recovered. - It is very common to recover all classes doing a simple action. For example, searching for implementors or senders of a certain method. Because of this, when you are developing in your Smalltalk image is very likely that all classes are recovered in less than 5 minutes of work. It is not useful. Browsing or editing code seems not to be a problem, thus. Maybe this approach has more sense in production images rather than development.

4 4

[Pharo-project] [update 1.1] #11151
by Marcus Denker Jan. 11, 2010

Jan. 11, 2010

11150 ----- Issue 1593 : Packages: strange MC packages in need of cleanup (again) MC lost lots of classes... so this loads all affected packages (the settings ones).

4 3