July 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] 1.4 update is broken do not use it

by StÃ©phane Ducasse

Hi guys apparently (I suspect some changes we did with Sven I will check), the updates mechanism only download the latest of the issues and skips all the ones in between. So if you want to use 1.4 use for now https://gforge.inria.fr/frs/download.php/28827/Pharo-1.4-14065.zip stef

July 29, 2011

Re: [Pharo-project] CameraPlugin for VM

by Bernat Romagosa

Sure, I attach it here. It looks like a standard MIT license with just these extra conditions added. 2011/7/29 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Yet another license syndrom. > > The Scratch source code license allows you to distribute derivative works > based on the Scratch source code for non-commercial uses subject to the > following restrictions: > â¢ you cannot use the word "Scratch" to refer to derivative works > (except in the phrase "Based on Scratch from the MIT Media Laboratory"), > â¢ you cannot use the Scratch logo or the official (copyrighted) > Scratch cat in derivative works, > â¢ you cannot implement the ability to upload projects to any MIT > Scratch website (currently, http://scratch.mit.edu) > â¢ copies or derivative works must retain the Scratch copyright > notice and license, and > â¢ you must make the source code for derivative works available. > This is just a summary; the full license is in the file "license.txt" > included in the source code download package. > The purpose of these restrictions is to avoid confusion in the Scratch user > community between the official version of Scratch (supported by the Lifelong > Kindergarten group) and experimental variations. We are happy the share our > source code, but we want to protect the Scratch brand and our user > community. > We hope you will appreciate the reasons for these restrictions. > > > > I do not want to see code from scratch in Pharo. Bernat do you have the > license.txt somewhere? > > Stef > > > > On Jul 29, 2011, at 12:12 PM, Bernat Romagosa wrote: > > > Oops sorry, I accidentally sent it twice. > > > > The license should be MIT, check out the "The Scratch Source Code > License" section: http://info.scratch.mit.edu/Source_Code > > > > Although they don't specifically state what's the license for the Camera > Plugin, I guess it just applies by extension since it belongs to the project > and the whole project is MIT. > > > > If we are to include it in Pharo I suppose we should check it > thoroughly... > > > > Cheers, > > > > 2011/7/29 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > > Hi Torsten, > > > > The plugin works out of the box for me in a Cog machine with no problems, > just follow these instructions: > > > > * Get Scratch's CameraPlugin (you can get them here > http://code.google.com/p/scat/downloads/list) > > * Depending on your OS, place it in: > > GNU/Linux and Win32 â The Pharo root directory. That is, where the > .sh and .lnk files are. > > MacOSX â The image path. > > * FileIn the three .st files I attach (they originally came from the > Scratch source, but were modified by us to get them working in Pharo) > > * DoIt: ScratchCameraDialog new openCamera; openInWorld > > > > Of course, you don't need the ScratchCameraDialog class, but it's nice to > have it as it's a pretty simple working example. I'm not sure whether you > need CameraMedia either, didn't have time to check... > > > > Hope it helps! > > > > Cheers, > > > > 2011/7/29 Torsten Bergmann <astares(a)gmx.de> > > Bernat Romagosa wrote: > > > In Scat we've managed, maybe after lunch i can give you some directions > > > to get it running. > > > > Yes, I managed to make it work last year, just with the > > *.cs and the Win32 DLL from scratch. > > > > However feel free to post a short guide for the recent Pharo > > image to the list so others can profit from it. > > > > > > My post was more oriented towards the VM developers > > since AFAIK there was a discussion of integrating > > the plugin back into Squeak VM sources so it is > > available in general to Squeak/Etoys/forks. > > > > As Bert wrote: > > > > "but the Scratch folks are interested in having their > > plugins in the main Squeak VM, so they do not have to > > package and maintain them themselves for ever." > > > > Would be nice if one would be able to use the cam > > out of the box with a recent VM (standard and cog) and Pharo. > > > > Thx > > Torsten > > -- > > NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! > > Jetzt informieren: http://www.gmx.net/de/go/freephone > > > > > > > > > > -- > > Bernat Romagosa. > > > > > > > > -- > > Bernat Romagosa. > > > -- Bernat Romagosa.

July 29, 2011

Re: [Pharo-project] CameraPlugin for VM

by StÃ©phane Ducasse

Yet another license syndrom. The Scratch source code license allows you to distribute derivative works based on the Scratch source code for non-commercial uses subject to the following restrictions: â¢ you cannot use the word "Scratch" to refer to derivative works (except in the phrase "Based on Scratch from the MIT Media Laboratory"), â¢ you cannot use the Scratch logo or the official (copyrighted) Scratch cat in derivative works, â¢ you cannot implement the ability to upload projects to any MIT Scratch website (currently, http://scratch.mit.edu) â¢ copies or derivative works must retain the Scratch copyright notice and license, and â¢ you must make the source code for derivative works available. This is just a summary; the full license is in the file "license.txt" included in the source code download package. The purpose of these restrictions is to avoid confusion in the Scratch user community between the official version of Scratch (supported by the Lifelong Kindergarten group) and experimental variations. We are happy the share our source code, but we want to protect the Scratch brand and our user community. We hope you will appreciate the reasons for these restrictions. I do not want to see code from scratch in Pharo. Bernat do you have the license.txt somewhere? Stef On Jul 29, 2011, at 12:12 PM, Bernat Romagosa wrote: > Oops sorry, I accidentally sent it twice. > > The license should be MIT, check out the "The Scratch Source Code License" section: http://info.scratch.mit.edu/Source_Code > > Although they don't specifically state what's the license for the Camera Plugin, I guess it just applies by extension since it belongs to the project and the whole project is MIT. > > If we are to include it in Pharo I suppose we should check it thoroughly... > > Cheers, > > 2011/7/29 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > Hi Torsten, > > The plugin works out of the box for me in a Cog machine with no problems, just follow these instructions: > > * Get Scratch's CameraPlugin (you can get them here http://code.google.com/p/scat/downloads/list) > * Depending on your OS, place it in: > GNU/Linux and Win32 â The Pharo root directory. That is, where the .sh and .lnk files are. > MacOSX â The image path. > * FileIn the three .st files I attach (they originally came from the Scratch source, but were modified by us to get them working in Pharo) > * DoIt: ScratchCameraDialog new openCamera; openInWorld > > Of course, you don't need the ScratchCameraDialog class, but it's nice to have it as it's a pretty simple working example. I'm not sure whether you need CameraMedia either, didn't have time to check... > > Hope it helps! > > Cheers, > > 2011/7/29 Torsten Bergmann <astares(a)gmx.de> > Bernat Romagosa wrote: > > In Scat we've managed, maybe after lunch i can give you some directions > > to get it running. > > Yes, I managed to make it work last year, just with the > *.cs and the Win32 DLL from scratch. > > However feel free to post a short guide for the recent Pharo > image to the list so others can profit from it. > > > My post was more oriented towards the VM developers > since AFAIK there was a discussion of integrating > the plugin back into Squeak VM sources so it is > available in general to Squeak/Etoys/forks. > > As Bert wrote: > > "but the Scratch folks are interested in having their > plugins in the main Squeak VM, so they do not have to > package and maintain them themselves for ever." > > Would be nice if one would be able to use the cam > out of the box with a recent VM (standard and cog) and Pharo. > > Thx > Torsten > -- > NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! > Jetzt informieren: http://www.gmx.net/de/go/freephone > > > > > -- > Bernat Romagosa. > > > > -- > Bernat Romagosa.

July 29, 2011

Re: [Pharo-project] [ANN] pre-build 1.4#14065

by StÃ©phane Ducasse

ARGH! I checked and indeed we only get the last update....I will spend the afternoon looking at that. There is probably something related to the changes we did with sven. Stef On Jul 29, 2011, at 2:53 PM, Marcus Denker wrote: > > https://gforge.inria.fr/frs/download.php/28827/Pharo-1.4-14065.zip > > PLEASE NOTE > > To me it looks like there is a problem that 1.4 just loads the *last* update from the stream... > http://code.google.com/p/pharo/issues/detail?id=4569 > > this needs to be checked / fixed before we can move on... > (I build this by updating from 14025, which worked. 14044 it seems to just load the last > update). > > Marcus > > > -- > Marcus Denker -- http://marcusdenker.de > >

July 29, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by StÃ©phane Ducasse

Us too :) On Jul 29, 2011, at 12:03 PM, Sven Van Caekenberghe wrote: > > On 29 Jul 2011, at 11:06, Lukas Renggli wrote: > >> Ok, problem solved. All server adaptors work now. >> >> A little benchmark for 500 requests (concurrency level 10): >> >> 1. Zinc -- 2073.80 [Kbytes/sec] received >> 2. Kom -- 1857.66 [Kbytes/sec] received >> 3. Swzoo -- 1662.48 [Kbytes/sec] received >> >> Zinc can nicely play out the keep-alive. Kom doesn't support >> keep-alive. With Swazoo a lot of requests fail if keep-alive is >> enabled (so I disabled it). Details in the attachment. >> >> Glad that we have Zinc as the default server now :-) > > I am happy and smiling now! > > Sven > >

July 29, 2011

Re: [Pharo-project] cool to see pier, and other running on 1.3

by StÃ©phane Ducasse

No idea Probably the same I will ask olivier when he is back from holidays On Jul 29, 2011, at 11:56 AM, Mariano Martinez Peck wrote: > > > On Fri, Jul 29, 2011 at 11:51 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > >> Zinc can nicely play out the keep-alive. Kom doesn't support > >> keep-alive. With Swazoo a lot of requests fail if keep-alive is > >> enabled (so I disabled it). Details in the attachment. > > > > what is keep-alive? > > The server keeps the socket open after a request-response cycle and > allows clients (browsers) to reuse the same socket for multiple > requests. This is typically faster than to open a new socket for each > request. > > > What is the difference between that and a database connection pool ? > > > > -- > Mariano > http://marianopeck.wordpress.com >

July 29, 2011

[Pharo-project] [ANN] pre-build 1.4#14065

by Marcus Denker

https://gforge.inria.fr/frs/download.php/28827/Pharo-1.4-14065.zip PLEASE NOTE To me it looks like there is a problem that 1.4 just loads the *last* update from the stream... http://code.google.com/p/pharo/issues/detail?id=4569 this needs to be checked / fixed before we can move on... (I build this by updating from 14025, which worked. 14044 it seems to just load the last update). Marcus -- Marcus Denker -- http://marcusdenker.de

July 29, 2011

[Pharo-project] new pre-build Core1.3#13291

by Marcus Denker

... with the build servers not working, one done by hand: https://gforge.inria.fr/frs/download.php/28826/PharoCore-1.3-13291.zip Marcus -- Marcus Denker -- http://marcusdenker.de

July 29, 2011

[Pharo-project] [update 1.3] #13291

by Marcus Denker

13291 ----- Issue 4561: Monticello GUI is broken -- Marcus Denker -- http://marcusdenker.de

July 29, 2011

[Pharo-project] Build failed in Hudson: Pharo Core 1.3 #391

by marcus.denker＠inria.fr

See <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/391/> ------------------------------------------ Started due to content change in http://pharo.gforge.inria.fr/updates/pharo1.3/updates13.list Construction ? distance sur pharo-build.lille.inria.fr FATAL: Impossible de produire un fichier de script hudson.util.IOException2: Failed to create a temp file on <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/ws/> at hudson.FilePath.createTextTempFile(FilePath.java:964) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601) at hudson.model.Build$RunnerImpl.build(Build.java:174) at hudson.model.Build$RunnerImpl.doRun(Build.java:138) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416) at hudson.model.Run.run(Run.java:1241) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:122) Caused by: hudson.util.IOException2: remote file operation failed: <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/ws/> at hudson.remoting.Channel@fb6bad6:pharo-build.lille.inria.fr at hudson.FilePath.act(FilePath.java:752) at hudson.FilePath.act(FilePath.java:738) at hudson.FilePath.createTextTempFile(FilePath.java:942) ... 11 more Caused by: hudson.util.IOException2: Failed to create a temporary directory in /tmp at hudson.FilePath$12.invoke(FilePath.java:953) at hudson.FilePath$12.invoke(FilePath.java:942) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2028) at hudson.remoting.UserRequest.perform(UserRequest.java:114) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:270) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Read-only file system at java.io.UnixFileSystem.createFileExclusively(Native Method) at java.io.File.checkAndCreate(File.java:1704) at java.io.File.createTempFile(File.java:1792) at hudson.FilePath$12.invoke(FilePath.java:951) ... 11 more Archiving artifacts Enregistrement des r?sultats des tests Description set:

July 29, 2011