June 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Pharo-2.0-Tests Â» 32,linux - Build # 131 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

June 20, 2012

[Pharo-project] SmalltalkHub

by Torsten Bergmann

Nico wrote: >BTW: I'm very open to any form of comment/idea/contribution to SmalltalkHub. Hi Nico, SmalltalkHub is nicely done and I like the idea of combining Amber on the client side with Smalltalk on the server side. I think one of the main problem before contributing to a project is accessibility and visibility of the project: I know that your project is not only running on smalltalkhub.com but also the code for the implementation lives there. Its good that you eat your own dog food - but maybe a hurdle to contribute. So I dont know: - if others know that the code is there (a list of projects hosted on SmalltalkHub is as you know still missing) - on which Pharo version it is running - how to easily load it into a recent Pharo image - what other things one needs to run it locally (Mongo?) and fix or modify it Also the page found by Google: http://www.objectfusion.fr/en/smalltalkhub.html tells me nothing where to get the code, how to start. It only says "work in progress". After more googling I can find a link www.smalltalkhub.com/user/NicolasPetton/SmalltalkHub which is NOT working! After more and more googling I found out from a twitter link that the code is there: http://smalltalkhub.com/#!/~NicolasPetton/SmalltalkHub I know it is a chicken and egg problem since all these infos will be on SmalltalkHub when implemented. But these days it is very hard to find and get startet. My proposal: ============ Since Metacello is standard these days I would really welcome a "ConfigurationOfSmalltalkHub" in MetacelloRepository which would: - allow the code to load - allow to see which Pharo version is used - allow to run it locally to do modifications - allow to follow stable releases and development progress just by looking into the configuration and in then end allow to contribute to the project. GruÃ T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

June 20, 2012

Re: [Pharo-project] FileSystem and file extensions

by Camillo Bruni

On 2012-06-20, at 06:45, Sean P. DeNigris wrote: > > Eliot Miranda-2 wrote >> >> Why not >> #('foo' 'foo.tar' 'foo.tar.gz' 'foo.1.tar' 'foo.1.tar.gz') collect: >> [:thing| thing extension] => #('' 'tar' 'gz' 'tar' 'gz') >> and >> #('foo' 'foo.tar' 'foo.tar.gz' 'foo.1.tar' 'foo.1.tar.gz') collect: >> [:thing| thing extensions] => #(#() #('tar') #('gz' 'tar') #('tar' '1') >> #('gz' 'tar' '1')) >> or >> #('foo' 'foo.tar' 'foo.tar.gz' 'foo.1.tar' 'foo.1.tar.gz') collect: >> [:thing| thing extensions] => #(#() #('tar') #('tar' 'gz') #('1' 'tar') >> #('1' 'tar' 'gz')) >> ? >> > > I opened an issue (http://code.google.com/p/pharo/issues/detail?id=6091) > which order do we like for extensions? I'd say in the order they appear in the full basename, that will avoid confusion :)

June 20, 2012

[Pharo-project] [update 2.0] #20143

by Esteban Lorenzano

20143 ----- Issue 6095: jenkins build failing because basicEntryAt: answers nil http://code.google.com/p/pharo/issues/detail?id=6095 Issue 6094: Configurations browser should be smarter http://code.google.com/p/pharo/issues/detail?id=6094

June 20, 2012

[Pharo-project] Integrated interactive tutorial?

by Malcolm Macgregor

At the top right of http://www.pharo-project.org/home is the heading "Get started now" Underneath is "Download Pharo ... Follow the integrated, interactive tutorial" Where is the "integrated interactive tutorial"?

June 20, 2012

Re: [Pharo-project] ScriptManager config in 1.4

by petton.nicolas＠gmail.com

> Pharo 2.0 is neither stable nor released thats why the repo is still > empty. Also the 2.0 repo is on SmalltalkHub (http://smalltalkhub.com/mc/Pharo/Packages20/main) and I dont > know whats planned here. Hi! My very short term goal is to add UI support for project contributors and project search to SmalltalkHub. The next step is to finish the scripting API and make SmalltalkHub search engine friendly. BTW: I'm very open to any form of comment/idea/contribution to SmalltalkHub. Cheers, Nico -- Nicolas Petton http://nicolas-petton.fr

June 20, 2012

Re: [Pharo-project] ScriptManager config in 1.4

by Torsten Bergmann

> IMO, what we need is to add a tab "Untrusted" to configurations browser (pointing to MetacelloRepository) and let people choose from there. > done: http://code.google.com/p/pharo/issues/detail?id=6094 OK - but now it does not open in 2.0 since SqS is down and "MetacelloRepository" is not available :( What about closing "MetacelloRepository" on squeaksource and moving it to SS3 as well? Any takers? Thanks T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

June 20, 2012

[Pharo-project] Worskpace question

by Hilaire Fernandes

DHello, I have a question regarding the Workspace when you execute code from there. Let me show with an example: I want to execute code instantiating an empty DrGeo sketch (a morph) then create programmatically content: |canvas| canvas := DrGeoCanvas new. canvas segment: 5@4 to: 10@20. canvas vector: 0@0 to: 2@2. ... The line with DrGeoCanavas creates and opens a new morph of a DrGeo sketch. My problem is: the morph only shows up on screen when the whole Workspace code is executed. I would like the canvas morph to show up when instantiated then get the construction code done step by step in the screen. Is the workspace code executed with higher priority than the user interface thread? Thanks Hilaire -- Dr. Geo -- http://www.drgeo.eu

June 20, 2012

Re: [Pharo-project] ScriptManager config in 1.4

by Torsten Bergmann

Sven wrote > Let's use that then: it is important that during 2.0 development, you can > easily load (validated) metacello configs; many of us are using 2.0 daily, > as in eating our own dogfood, if metacello configs + browser are the way > forward, we should start using that now. > > Sven Ok, then use SS3 meanwhile and maybe switch to smalltalkhub later. So: 1. I created http://ss3.gemstone.com/ss/MetaRepoForPharo20 2. made Scriptmanager working in Pharo 2.0 by switching from ReferenceStream to FLSerializer and FLMaterializer and using SmalltalkEditor instead of ParagraphEditor in "ScriptManager-Core-tbn.17.mcz" Code is cleaner and transition was very easy. Fuel rocks! Since ReferenceStream is not anymore in Pharo 2.0 and old script manager exports can not be used I changed the file extension from *.obj to *.fuel 3. changed the ConfiguratonOfScriptManager to have a new version 1.5. using the new mcz-version 4. added a line stable spec in the config spec for: #'pharo2.0.x' version: '1.5' 5. made a copy of the new ConfiguratonOfScriptManager available in "MetaRepoForPharo20" also 6. opened issue http://code.google.com/p/pharo/issues/detail?id=6093 to point Pharo 2.0 to the new config repo In the issue and attached you will find a small changeset that switches the config browser from smalltalk hub to the new SS3 repo So ScriptManager (using Fuel) is now the first package loadable from the config browser in Pharo 2.0. (maybe we should switch topic to "ScriptManager config in 2.0" now ;) Feel free to upload other configs known to work for 2.0 to http://ss3.gemstone.com/ss/MetaRepoForPharo20 Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

June 20, 2012

Re: [Pharo-project] ScriptManager config in 1.4

by Esteban Lorenzano

done: http://code.google.com/p/pharo/issues/detail?id=6094 On Jun 20, 2012, at 10:38 AM, Esteban Lorenzano wrote: > -1 > > IMO, what we need is to add a tab "Untrusted" to configurations browser (pointing to MetacelloRepository) and let people choose from there. > > Esteban > > On Jun 20, 2012, at 10:19 AM, StÃ©phane Ducasse wrote: > >> + 1 >> >>>>> and wonder why we dont use a >>>>> http://ss3.gemstone.com/ss/MetaRepoForPharo20.: >>>> >>>> We can use it too for now. >>>> What is missing is the process behind >>> >>> Let's use that then: it is important that during 2.0 development, you can easily load (validated) metacello configs; many of us are using 2.0 daily, as in eating our own dogfood, if metacello configs + browser are the way forward, we should start using that now. >>> >>> Sven >> >> >

June 20, 2012