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

A question about dependencies and configurations
by Sergi Reyner March 21, 2014

March 21, 2014

I am creating a web interface for chromia using Seaside. I would like to have it as a separate package, so chromia can be loaded without pulling Seaside in. Would I have ConfigurationOfChromia and ConfigurationOfChromiaWeb, the latter depending on the former? Cheers, Sergi

3 2

Tiling Window Manager in 3.0: working but still issues with WorldMorph
by phil＠highoctane.be March 20, 2014

March 20, 2014

TWM works in 3.0 after some work on icons and updating menus. Gofer new smalltalkhubUser: 'LaurentLaffont' project: 'TilingWindowManager'; configuration; load. ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: '3.0') load You can also use ((Smalltalk at:#ConfigurationOfTilingWindowManager) project version: #development) load but this will for sure change over time. There is the World management icon which is still there and it looks like it can create worlds but switching between them just breaks havoc. Maybe should we just remove that feature from TWM as 3.0 doesn't seem to be multiworld friendly. Nothing done on tests nor themeing (which appears to be not that working well in 3.0 either due to theming changes); At least the thing is back :-) [I missed it...] Phil

2 5

[ANN] Pharo and ST books page (as another Seaside demo on PharoCloud)
by Torsten Bergmann March 20, 2014

March 20, 2014

There are some free Smalltalk books collected by Stef in the past. http://stephane.ducasse.free.fr/FreeBooks.html Yet this page is often unknown to people. I therefore converted them to a more Seaside like demo using the Bootstrap project at: http://pharo.pharocloud.com/pharobooks as part of the Pharo/Seaside/Bootstrap demos at http://pharo.pharocloud.com Code for this is on http://smalltalkhub.com/#!/~TorstenBergmann/PharoCloud. I would suggest that we create a shortlink "books.pharo.org" for http://pharo.pharocloud.com/pharobooks to it - any takers? This way we can tell people: "Ahh you want to get Pharo, just use get.pharo.org" "Ahh you want to download Pharo, just use files.pharo.org" "Ahh you want to enhance Pharo, just use bugs.pharo.org" "Ahh you want to control Pharo, just use ci.pharo.org" and now "Ahh you want to learn Pharo, just use books.pharo.org" to be continued ... Kudos to Stef for the collection and to Mike for being able to host a demo on pharocloud. Have fun T.

3 4

What's wrong whith this code?
by Friedrich Dominicus March 20, 2014

March 20, 2014

elements := #('eins' 'zwei' 'drei' 'vier'). elements do: [ :element | Delay forSeconds: 2. ] displayingProgress: [ :element | 'Working on', element asString ]. Shouldn't it just open a progress bar and iterate through the elements printing 'Working on...? Regards Friedrich

6 9

Phratch Website + version 3.0 in dev
by jannik laval March 20, 2014

March 20, 2014

Dear all, I am pleased to announce Phratch website: www.phratch.com Thanks to the support of ESUG, it is possible to make visible this wonderful project. For now, what is available on the site: - a presentation of Phratch (you can refer to it now) - installation files, there is a portable version for Windows, Linux, MacOS. - tutorials - block documentation: generated from a Phratch image ! - Some elements for Jetstorm (a lot of new articles will come soon) - a category with news Now about the versions, I am developing the version 3.0 Why this number ? Why a third version in one year of work ? It is clear that a lot of work is already done. Each version represents strong changes in the architecture. - version 1.0 is the port of Scratch + BYOB + Panther in Pharo. It is working but not extendable. - version 2.0 makes Phratch really extendable. We can develop our own block for everything in Pharo. I also make Phratch more modular with the use of Pragmas for some menus, declaration of blocks... It is available only in Pharo 3.0. There are some languages available, I hope more people can translate in other languages (http://www.phratch.com/archives/612) - version 3.0 is the version in development. What is new here: Before this version Phratch was really slow. I am cleaning the code, and now it begins to be fast, really fast ! We also begun to write tests. I am really happy to have the support of ESUG and Pharo. Thanks to the community to make Pharo as usable as it it, it makes our dreams possible. Cheers, -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

3 3

Calculate angle between two vectors (probably @Igor :)
by MartinW March 19, 2014

March 19, 2014

Hello, i probably made some embarassing mistake, but as i cannot find it, i ask you to have a look at this method. It should calculate the angle between two vectors. And vectors are instances of Point (perhaps here is already a misconception?). It is used in my flocking simulation PharoBoids (http://smalltalkhub.com/#!/~MartinWalk/Boids) Here is my version of the method: angleBetween: vector1 and: vector2 onError: aBlock | cosinusOfAngle innerProductOfVectors productOfVectorsLengths| innerProductOfVectors := (vector1 dotProduct: vector2). productOfVectorsLengths := (vector1 r) * (vector2 r). productOfVectorsLengths = 0 ifTrue: [ ^ aBlock value ]. cosinusOfAngle := innerProductOfVectors / productOfVectorsLengths. ^ cosinusOfAngle arcCos But my Boids behave wrong when i use it. I found another implementation of the same problem by Igor Stasenko which works and looks like this: angleBetween: p1 and: p2 ifDegenerate: aBlock " Calculate an angle (in radians) between two vectors. Evaluate a block, in case if calculation not possible because one of the vectors has zero length " | x1 y1 x2 y2 dot2 n2 | x1 := p1 x. y1 := p1 y. x2 := p2 x. y2 := p2 y. dot2 := x1 * x2 + (y1 * y2). dot2 := dot2 * dot2. n2 := (x1*x1 + (y1*y1)) * (x2*x2 + (y2*y2)). n2 = 0 ifTrue: [ ^ aBlock value ]. ^ (dot2 / n2) arcCos Can anybody explain the problem of my method? M. -- View this message in context: http://forum.world.st/Calculate-angle-between-two-vectors-probably-Igor-tp4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

5 9

[ANN] Rickshaw.js charting library for Seaside
by Esteban A. Maringolo March 19, 2014

March 19, 2014

I just uploaded to SmalltalkHub an initial wrapper for the Rickshaw.js charting library (http://code.shutterstock.com/rickshaw/) As usual, you can load it with the following expression: Gofer it smalltalkhubUser: 'emaringolo' project: 'rickshaw'; package: 'ConfigurationOfRickshaw'; load. (Smalltalk at: #ConfigurationOfRickshaw) project development load: 'All' This will load all the packages, including a Seaside component installed at '/rickshaw' containing various examples. It is an initial version and my first package uploaded to SmalltalkHub, so bugs and and mistakes are expected :) Questions are welcome too. Regards, Esteban A. Maringolo

2 2

[ANN] Rickshaw.js charting library for Seaside
by Torsten Bergmann March 19, 2014

March 19, 2014

Esteban A. Maringolo wrote: >I just uploaded to SmalltalkHub an initial wrapper for the Rickshaw.js >charting library (http://code.shutterstock.com/rickshaw/) Nice. I added a browsable demo of "Rickshaw" to http://pharo.pharocloud.com which is also directly accessible at http://pharo.pharocloud.com/rickshaw Thx T.

2 1

Re: [Pharo-users] What's wrong whith this code?
by PBK Research March 19, 2014

March 19, 2014

Well I did some experiments, and I seem to have a solution. In the method Collection>>do:displayingProgress:every:, you will find (three lines from the end) the line: ifFalse: [ProgressNotification signal: '' extra: (oldLabel := newLabel)]. If you replace that with: ifFalse: [bar label: (oldLabel := newLabel)]. you will find that the examples of changing labels will work. I haven't tested this as thoroughly as I should, so there may be other consequences, but clearly this is where the problem lies. Peter Kenny _____ From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of PBK Research Sent: 19 March 2014 09:09 To: nicolaihess(a)web.de; 'Any question about pharo is welcome' Subject: Re: [Pharo-users] What's wrong whith this code? Note however that the first example used in the method comment, which displays a static label, does work. There is something wrong in the method of computing the changing label in the second example. I can't follow the code here, so I can't see the error, but it should be clear where to look. Peter Kenny _____ From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Nicolai Hess Sent: 19 March 2014 08:56 To: Any question about pharo is welcome Subject: Re: [Pharo-users] What's wrong whith this code? 2014-03-19 8:17 GMT+01:00 Friedrich Dominicus <frido(a)q-software-solutions.de>: Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> writes: > ouch, I added a . in the middle, sorry! > > elements := #('eins' 'zwei' 'drei' 'vier'). > elements > do: [ :element | (Delay forSeconds: 2) wait ] > displayingProgress: [ :element | 'Working on', element asString ]. > > 2014-03-18 9:55 GMT+01:00 Bernat Romagosa > <tibabenfortlapalanca(a)gmail.com>: > > Without having tried it, I think you're missing a #wait message in > there: > > > > elements := #('eins' 'zwei' 'drei' 'vier'). > elements do: [ :element | (Delay forSeconds: 2) wait ]. > > displayingProgress: [ :element | 'Working on', element asString ]. Sorry even with that I do not see the 'Working on ' message. It's just a progress bar with nothing else. No "Working on" anywhere. Regards Friedrich It doesn't work anymore. (This worked in Pharo 1.4) In the comment of Collection>>do:displayingProgress: is a example, that doesn't work: Smalltalk allClasses do:[:aClass| (Delay forMilliseconds: 1) wait] displayingProgress:[:aClass| 'Processing ', aClass name]. This should show the class names but it shows only a single progressbar.

1 0

Pharo3 release delayed!
by Esteban Lorenzano March 19, 2014

March 19, 2014

Ladies and gentlemen, For achieving a great 3.0 release we still have some tasks that we still need to prepare. They are not many, but we (Pharo Board) think it deserves some more effort: 1) Technically, there are still some minor bugs to tackle around RPackage and Nautilus. We do not miss much and that could be done in a couple of days work (in fact, I'm working on them and trying to have it before going to Argentina next week), but in order to be sure, we better wait a bit :). It would be great to see more eyeballs focused on these issues. 2) We want to create a real marketing strategy this time, and that requires preparation time. "Marketing strategy" sounds probably really bombastic, but in our case it means to create pages, send mails, construct the progress log, etc. We we need some time to prepare it properly. So... Pharo3 release date has been moved to April 22. Cheers, Esteban

1 0