- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Image's size in pillar

by Natalia Tymchuk

Thank you. Best regards On Mar 17, 2014, at 9:08 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi Natalia, > > On Sun, Mar 16, 2014 at 2:23 PM, Natalia Tymchuk > <natalia.tymchuk(a)unikernel.net> wrote: >> but with changing the value width I didn't get changes of my images sizes. How can I make my images take half of the page's width? > > I fixed this a month ago in the development version of Pillar but > didn't release a stable version yet. > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

March 19, 2014

Pharo3 release delayed!

by Esteban Lorenzano

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

March 19, 2014

Re: [Pharo-dev] Just found, i can compile this:

by Christophe Demarey

Le 18 mars 2014 Ã 19:50, Eliot Miranda a Ã©crit : > On Tue, Mar 18, 2014 at 10:10 AM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > Why arguments should be read only? > They are just temporary variables with an initial value. > > Read the blue book. It was a decision of the language designers to forbid assignment to arguments to allow debugging. The assignment to block arguments is a side-effect of the old BlockContext implementation of blocks where block arguments were mapped onto temporary variables of the home context. It is an anachronism and should be forbidden also. Thank you for the explanation. I'm just curious why it is so difficult to implement a debugger if arguments are assignable? If you need to restart the execution of a method, and so you need to get the initial value of the argument, I understand you cannot find the value anymore in the method context but it is available in the caller context, no? As I never implemented a debugger, I cannot figure out the difficulties.

March 19, 2014

Re: [Pharo-dev] SmalltalkHub troubles

by Nicolas Petton

Hi Philippe, Can you send me the mcz privately so I can take a look? Cheers, Nico -- Nicolas Petton http://nicolas-petton.fr

March 19, 2014

Re: [Pharo-dev] FileSystem-Git status update 2

by Pharo4Stef

+1 On 19 Mar 2014, at 08:53, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Good to see this progress! Thanks for your effort. > > Uko > > On 19 Mar 2014, at 08:46, Max Leske <maxleske(a)gmail.com> wrote: > >> - I moved all the code to the FileSystemGitDev team on Smalltalkhub >> - we now have a working LibGit2 build (tests fail but that will be fixed in the coming days) >> - we got simple fetch working yesterday (yay!) >> - we (which means Stefan) started rewriting our tests with SUnit, moving away from Phexample (for several reasons) >> >> Todayâs program: >> - migrate more tests >> - fix initialization and setup issues >> - try to perform a complete fetch + merge (without conflicts) >> - implement clone >> - try to get push working >> >> Have a great day! >> >> Cheers, >> Max > >

March 19, 2014

Re: [Pharo-dev] FileSystem-Git status update 2

by Goubier Thierry

Le 19/03/2014 08:46, Max Leske a Ã©crit : > - I moved all the code to the FileSystemGitDev team on Smalltalkhub > - we now have a working LibGit2 build (tests fail but that will be fixed in the coming days) > - we got simple fetch working yesterday (yay!) > - we (which means Stefan) started rewriting our tests with SUnit, moving away from Phexample (for several reasons) > > Todayâs program: > - migrate more tests > - fix initialization and setup issues > - try to perform a complete fetch + merge (without conflicts) > - implement clone > - try to get push working > > Have a great day! With such news, it is a great day :) Thanks for the effort, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

March 19, 2014

Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31

by Tudor Girba

On Wed, Mar 19, 2014 at 8:35 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > ### Here's what I've been up to since the last WhatsUp: > > - reported a couple bugs for Pharo 3.0 > - got one commercial deal signed with Pharo as the underlying technology > Great! We are looking forward for a new success story. > - learning Roassal > :) Doru ### What's next, until 2014-03-31 (*): > > - another deal coming - proposal in the intertubes > > Phil > > -- www.tudorgirba.com "Every thing has its own flow"

March 19, 2014

Re: [Pharo-dev] Removing tools

by Pavel Krivanek

Hi Torsten, we plan to do that in Pharo/SystemConfigurations(/Unreloader). That mail was something like a late night backup of very experimental stuff :-) Cheers, -- Pavel 2014-03-19 9:08 GMT+01:00 Torsten Bergmann <astares(a)gmx.de>: > Hi Pavel, > > dont know if this is a good idea but why not: > - put this into a ConfigurationOfNoTools with a > spec postLoadDoIt: #postloadToShrinkWithLoader:package:. > - put the script into a #postloadToShrinkWithLoader:package > - store the project on STHub > - create a CI job for loading the Config > > This way one can: > - browse the changes to the script in Monticello as it progresses > - have the CI built the image automagically > - the final image can be downloaded from CI or using Pharo launcher easily > > If some simply unit tests will be applied (like checking for Undeclared, > etc) one can control > if the image will get/be/stay red or green. > > Bye > T. > > > *Gesendet:* Dienstag, 18. MÃ¤rz 2014 um 23:00 Uhr > *Von:* "Pavel Krivanek" <pavel.krivanek(a)gmail.com> > *An:* "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> > *Betreff:* [Pharo-dev] Removing tools > Hi, > > this is an initial attempt to produce an image without development tools. > Currently it leaves Workspace and Transcript in the image, has no obsolete > classes and six Undeclared. The image size is still quite big, 16.1 MB. > Tested on #30798. Do not forget to share your improvements ;-) > > Cheers, > -- Pavel >

March 19, 2014

Re: [Pharo-dev] Removing tools

by Torsten Bergmann

March 19, 2014

SmalltalkHub troubles

by Philippe Marschall

Hi I'm having trouble committing to SmalltalkHub and I don't know where to go for support. When trying to commit to Seaside31 I get the following error: HTTP/1.1 403 Forbidden Date: Tue, 18 Mar 2014 20:16:45 GMT Content-Length: 512 Vary: Accept-Encoding Server: Zinc HTTP Components 1.0 Connection: close Content-Type: text/plain Unknown token type I double checked and my username and password are correct. Cheers Philippe

March 19, 2014