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

Re: [Pharo-project] Monticello gives me new version numbers when I just want to publish a fix to PharoInbox

by Simon Denier

On 12 janv. 2010, at 18:52, Matthias Berth wrote: > Hi, > > > I was following > > http://code.google.com/p/pharo/wiki/HowToContribute > > I have saved the patched package into my package-cache, giving > Network-Protocols-MatthiasBerth.17.mcz. Then I restarted the image > (pharo core 1.0rc 10505). > > Then I wanted to save to PharoInbox, by selecting PharoInbox in > Monticello browser and clicking "save". Monticello asked for my > initials (no problem) and then it gave the package a new version > number Network-Protocols-MatthiasBerth.18.mcz. Is that expected > behavior? I cancelled that because I did not want to increase the > version number. > > I tried again, now by following the instructions to the letter and > pressing the +Repository button. Same problem, even worse: now I got > version 19 (Network-Protocols-MatthiasBerth.19.mcz). > > Do others see the same problem? Am I doing something stupid here? Yes it's the expected behavior for Monticello, which always increases the version number if you save the package. Instead, one you can do from the MC browser is to *copy* your version 17 to the PharoInbox (provided that PharoInbox is registered as a repository for the package) -- Simon

Jan. 12, 2010

Re: [Pharo-project] Where is BytecodeGenerator class?

by Miguel Enrique CobÃ¡ Martinez

El mar, 12-01-2010 a las 11:58 -0600, Miguel Enrique CobÃ¡ Martinez escribiÃ³: > Does somebody knows what package the class BytecodeGenerator is part of? > > I am loading WriteBarrier-pmm.26 from > > squeaksource.com/WriteBarrier.html and > squeaksource.com/Magma.html > > and has references to BytecodeGenerator > > Thanks Responding to myself, google says that is part of NewCompiler. -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 12, 2010

Re: [Pharo-project] Pharo core and Seaside 3.0

by Dale Henrichs

Since I'm maintaining the Seaside3.0 config, I am probably at fault on this one although I haven't run into a problem with underscore assignment ... How do I run a pharo image that _does not_ allow underscore assignment? Specifically, the Seaside3.0 config is not using the Swazoo code that Lukas modified (I assume this is what Lukas is referring to), because it departs from the naming convention used by the Swazoo folks and as a result causes problems when one tries to load the latest version of the package....I've got write permission on the Swazoo repository, but I'm still in the process of negotiating a proper name for the package (on very low back burner), so if this is popping to the surface as an issue, I'll "raise the heat". Dale ----- "Torsten Bergmann" <astares(a)gmx.de> wrote: | Hi, | | "ScriptLoader loadSeaside30" | | does not work in latest image due to Gofer changes. Should we remove | it | or replace it with Metacello configs? | | It is now easy to build a dev image with seaside 3.0 right from the | core | (see script below). | | Still underscore assignment has to be enabled due to OB. Any chance | this | is cleaned up? | | Bye | T. | | | ---------------------------------------------------------------------------- | | |font codeFont titleFont installWebTools| | installWebTools := false. | "HTTPSocket useProxyServerNamed: '111.111.111.111' port: 8080." | | Scanner allowUnderscoreAsAssignment: true. | | Gofer new | squeaksource: 'MetacelloRepository'; | package: 'ConfigurationOfPharo'; | load. | ((Smalltalk at: #ConfigurationOfPharo) project version: | '1.0-rc2.10505') load. | | Gofer new | squeaksource: 'MetacelloRepository'; | package: 'ConfigurationOfSeaside30'; | load. | | (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion. | | | SmalltalkImage current snapshot: true andQuit: true. | | | -- | Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox | 3.5 - | sicherer, schneller und einfacher! | http://portal.gmx.net/de/go/atbrowser | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 12, 2010

Re: [Pharo-project] Monticello gives me new version numbers when I just want to publish a fix to PharoInbox

by Gary Chambers

You should open your package cache repository and, for the required version, choose "copy" then select the PharoInbox repository as destination. Might be nice if MC effectively did this for saving working copies of saved versions that have no changes. Regards, Gary ----- Original Message ----- From: "Miguel Enrique CobÃ¡ Martinez" <miguel.coba(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, January 12, 2010 6:03 PM Subject: Re: [Pharo-project] Monticello gives me new version numbers when I just want to publish a fix to PharoInbox > El mar, 12-01-2010 a las 18:52 +0100, Matthias Berth escribiÃ³: >> Hi, >> >> >> I was following >> >> http://code.google.com/p/pharo/wiki/HowToContribute >> >> I have saved the patched package into my package-cache, giving >> Network-Protocols-MatthiasBerth.17.mcz. Then I restarted the image >> (pharo core 1.0rc 10505). >> >> Then I wanted to save to PharoInbox, by selecting PharoInbox in >> Monticello browser and clicking "save". Monticello asked for my >> initials (no problem) and then it gave the package a new version >> number Network-Protocols-MatthiasBerth.18.mcz. Is that expected >> behavior? I cancelled that because I did not want to increase the >> version number. >> >> I tried again, now by following the instructions to the letter and >> pressing the +Repository button. Same problem, even worse: now I got >> version 19 (Network-Protocols-MatthiasBerth.19.mcz). >> >> Do others see the same problem? Am I doing something stupid here? > > Same happens to me. I don't care for the numbers :) > >> >> >> Cheers >> >> Matthias >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 12, 2010

Re: [Pharo-project] [Feature Request] Better integration with OSX Window Management

by John Toohey

In cases like this, I have used http://www.heliumfoot.com/mercurymover/ to recover windows that are positioned off the current screen. Use the task selector to get the focus on the app, and then the arrow keys to move it back to your laptop. On Mon, Jan 11, 2010 at 07:34, Stefan Marr <pharo(a)stefan-marr.de> wrote: > Hello: > > I just had a very annoying experience with the lake of sufficient window > management tools on Mac OS X. (Annoying enough to write this mail...) > > > The following happened: > > At home I have a external screen attached to my mac book, it is configured > to be a secondary screen positioned above the main (internal) screen. > > The Pharo window was moved to that screen. > > In the office, I have another configuration, and there was no way to get > hold of the Pharo window anymore. > > It remembered its positioning and was just of screen. Expose allows me to > see it, and shows even a beautiful animation moving it out of reach after > clicking on it. > > Obviously the menu SqueakVM > Quit is not really helpful, since the > question whether to save or not is displayed unreachable off screen, too. > > > > I am not sure whether the standard OS X window menu functionality with > "minimize" and "zoom" would help here, but might be a start. On the other > hand, I would guess, that the OSX windowing systems sends some events which > could be handled like all other windows do. > > > The only workaround for the moment, is to have a external screen and fiddle > with the screen configuration and positioning until I can get hold of the > window... Not exactly convenient. > > > Best regards > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 3956 > Fax: +32 2 629 3525 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- -JT

Jan. 12, 2010

Re: [Pharo-project] Monticello gives me new version numbers when I just want to publish a fix to PharoInbox

by Miguel Enrique CobÃ¡ Martinez

El mar, 12-01-2010 a las 18:52 +0100, Matthias Berth escribiÃ³: > Hi, > > > I was following > > http://code.google.com/p/pharo/wiki/HowToContribute > > I have saved the patched package into my package-cache, giving > Network-Protocols-MatthiasBerth.17.mcz. Then I restarted the image > (pharo core 1.0rc 10505). > > Then I wanted to save to PharoInbox, by selecting PharoInbox in > Monticello browser and clicking "save". Monticello asked for my > initials (no problem) and then it gave the package a new version > number Network-Protocols-MatthiasBerth.18.mcz. Is that expected > behavior? I cancelled that because I did not want to increase the > version number. > > I tried again, now by following the instructions to the letter and > pressing the +Repository button. Same problem, even worse: now I got > version 19 (Network-Protocols-MatthiasBerth.19.mcz). > > Do others see the same problem? Am I doing something stupid here? Same happens to me. I don't care for the numbers :) > > > Cheers > > Matthias > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 12, 2010

[Pharo-project] Where is BytecodeGenerator class?

by Miguel Enrique CobÃ¡ Martinez

Does somebody knows what package the class BytecodeGenerator is part of? I am loading WriteBarrier-pmm.26 from squeaksource.com/WriteBarrier.html and squeaksource.com/Magma.html and has references to BytecodeGenerator Thanks -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 12, 2010

[Pharo-project] Monticello gives me new version numbers when I just want to publish a fix to PharoInbox

by Matthias Berth

Hi, I was following http://code.google.com/p/pharo/wiki/HowToContribute I have saved the patched package into my package-cache, giving Network-Protocols-MatthiasBerth.17.mcz. Then I restarted the image (pharo core 1.0rc 10505). Then I wanted to save to PharoInbox, by selecting PharoInbox in Monticello browser and clicking "save". Monticello asked for my initials (no problem) and then it gave the package a new version number Network-Protocols-MatthiasBerth.18.mcz. Is that expected behavior? I cancelled that because I did not want to increase the version number. I tried again, now by following the instructions to the letter and pressing the +Repository button. Same problem, even worse: now I got version 19 (Network-Protocols-MatthiasBerth.19.mcz). Do others see the same problem? Am I doing something stupid here? Cheers Matthias

Jan. 12, 2010

[Pharo-project] Issue 1788: SMTPClient does not send HELO or EHLO, session is not initiated

by Matthias Berth

Hi, I fixed a regression with sending email when using SMTPClient without login. Can someone have a look please? http://code.google.com/p/pharo/issues/detail?id=1788 Cheers Matthias

Jan. 12, 2010

[Pharo-project] [ANN] pre-buit Core#10506

by Marcus Denker

http://gforge.inria.fr/frs/download.php/25177/PharoCore-1.0-10506rc1.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 12, 2010