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

Re: [Pharo-project] [Pharo-users] Pharo By Example 2 Book - Assembled Files in PDF form.

by Damien Cassou

On Tue, Feb 19, 2013 at 9:45 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > This should be made into a Jenkins job I think so that we can have the > PBE2 and other books in PDF form for easier dissemination. you are right. Here is one: https://ci.inria.fr/pharo-contribution/job/DeepIntoPharo/ the only missing piece is the automated upload to GForge (http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/) I'm working on it. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Feb. 19, 2013

Re: [Pharo-project] Pharo 2.0 and iOS

by Esteban Lorenzano

already answered: you are just scared :) 1) NB does not need to be used in 2.0... is just there, as any other package... it just will not work in iOS, but the image will be ok 2) Athens will replace old graphics infrastructure, but not in 2.0 and certainly, that should not be a problem for use it in iOS in the future (since athens is a framework that uses cairo, but can use other backends, like the old balllon3d) Esteban On Feb 19, 2013, at 3:08 PM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > There is a potential problem for me with 2.0: > > It includes NativeBoost/Athens.... > > As I am targeting iOS running on a StackVM, am I stuck to 1.4? > Is there anything to do to ensure that Pharo 2.0 is not a dead end for > such developments? > > Maybe this is just me scaring myself... There is value in an all > software Pharo stack. Which is why I went that way in the first place. > > Phil >

Feb. 19, 2013

[Pharo-project] Pharo 2.0 and iOS

by phil＠highoctane.be

There is a potential problem for me with 2.0: It includes NativeBoost/Athens.... As I am targeting iOS running on a StackVM, am I stuck to 1.4? Is there anything to do to ensure that Pharo 2.0 is not a dead end for such developments? Maybe this is just me scaring myself... There is value in an all software Pharo stack. Which is why I went that way in the first place. Phil

Feb. 19, 2013

Re: [Pharo-project] Magritte and Spec

by Benjamin

Cool :) I will have a look asap ^^ Ben On Feb 19, 2013, at 12:53 AM, DeNigris Sean <sean(a)clipperadams.com> wrote: > Since I'm using Spec for all my Pharo UIs, I'm interested in having Spec as the backend to Magritte. If anyone is interested, I started an experiment at http://ss3.gemstone.com/ss/SpdPlayground/ . Look for the Magritte-Spec package. > > Cheers, > Sean

Feb. 19, 2013

[Pharo-project] Slices and monticello - add to package... or add package to ... ? + procedure

by phil＠highoctane.be

I was educating myself on slices. Maybe I'll be able to contribute a bit properly one of these days. Reading from http://code.google.com/p/pharo/wiki/HowToContribute. Creating a slice in my own package-cache is all fine. Now, to add it to the PharoInbox, I watched the screencast: http://www.pharocasts.com/2010/03/how-to-contribute-to-pharo.html There is this thing were we need to go to the PharoInbox repo in the right pane on monticello. The right click and select the Add to package.. option and then select the slice. All right, I can understand but this feels like unnatural to be on a repository and ask to "Add to package..." where what I want to do is to add the package to the repository. I understand that this is required to have the repository associated with the package so that I can save the package to one of its associated repositories. Maybe "Associate with package..." may be more helpful. Also the procedure on HowToContribute is not right anymore. As the UI changed. There is my version: # How to make a slice Slice: Your modification affect more than one package: you have to create a SLICE package in your package cache A SLICE is just a package with dependents ones, so you have to indicate the dependent packages. ## Procedure Open the Monticello browser. You should see one or more packages marked as modified (they have an asterisk before their name). Select your package-cache repository on the right hand pane. Create the new SLICE (click on the ''+SLICE'' button) and follow the instructions. ### Old way _Mark all_ the modified packages (the ones with asterisks before their names) required by your SLICE package. To do this, right click on the SLICE package in the left pane and select ''add required package'', then select the package from the next menu. Repeat for all modified packages. (Yeah, boring) ### New way (Pharo 2.0 at least) Put the issue tracker number in the Issue Number box and hit "Grab" to get the title of the issue. The (un)select in the list of "Dirty Packages to be included in the slice" ### Back to regular programming... Select your package-cache repository, this will enable the save button. Save the SLICE package (click on the ''Save'' button). An mcz package will be saved in your cache for the SLICE package and all the modified packages. (Name: something along the lines of SLICE-Issue-XXXX-YYYY-ZZZZ-Comment-Initials.1) You will be prompted for a log message (for each one of them ?), type a useful comment for the first package, (copy it and paste it on the others - sure?). Make sure to give the number of the issue your SLICE addresses in the comment. Publish the package to PharoInbox repository. # Hwo to publish to the PharoInbox repository Open monticello. Select the PharoInbox repository on the right pane. Right click the repository and select "Add to package..." (this will associate the package to the repository). You'll be presented with a list of possible packages. Pick up your slice. Then, go back to Monticello Browser with a list of packages on the left and a list of repositories on the right. Select on your slice on the left. Select the PharoInbox repository on the right. Click the Save button on the top bar. That's it, slice now in PharoInbox. Phil

Feb. 19, 2013

Re: [Pharo-project] Fuel out stack... other error

by Esteban Lorenzano

patience, my friend... I'm on it :) just give me time to make another integration :) On Feb 19, 2013, at 12:09 PM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > I put a new istead of newFull and continued. > > No, I get some FuelMetalevel thing... > <PharoScreenshot.1.png>

Feb. 19, 2013

[Pharo-project] Fuel out stack... other error

by phil＠highoctane.be

I put a new istead of newFull and continued. No, I get some FuelMetalevel thing...

Feb. 19, 2013

Re: [Pharo-project] Fuel Out Stack: MNU in 20555

by Esteban Lorenzano

yes I know. will be fixed this afternoon On Feb 19, 2013, at 12:02 PM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Tried to FileOut stack from a debugger. > > FLSerializer class>>newFull - MNU > > ? > > Phil > <PharoScreenshot.png>

Feb. 19, 2013

[Pharo-project] Fuel Out Stack: MNU in 20555

by phil＠highoctane.be

Tried to FileOut stack from a debugger. FLSerializer class>>newFull - MNU ? Phil

Feb. 19, 2013

Re: [Pharo-project] Phexample should methods

by Sean P. DeNigris

Great post... a lot to think about :) Adrian Kuhn wrote > Classes and methods are not the best model to structure tests. Alas in > Smalltalk it's all we can work with.... we cannot break free from classes > and methods (imposed by the Smalltalk IDE rather than the language) so its > what we must work with. I consider classes and methods to be the assembler of specifications (I prefer to "testing"). Because we have our amazing IDE, with Smalltalk turtles all the way down, all there is to do is create a GUI that works the way our minds do. Just like Spec will eventually have a painter covering the raw spec methods, so too can we have a Specification Painter. I started work on this several times, but there was so much cleaning to do in Pharo... But with all the progress made for 2.0, I feel that we are getting closer and closer and have been wanting to resume my work on that this week. It seems that a Morphic overhaul is the only thing left to make that easier, and at least a new text model (one of the more infuriating parts of Morphic) is already underway. Cheers, Sean -- View this message in context: http://forum.world.st/Re-Phexample-should-methods-tp4670589p4670629.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 19, 2013