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

Re: [Pharo-project] Oh, great.. SqS is down

by Marcus Denker

On Feb 3, 2011, at 5:47 PM, Igor Stasenko wrote: > so i can do home... (grrrrrrr) > up again. I will give you the needed info to restart it yourself tomorrow. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 3, 2011

Re: [Pharo-project] documentation for "blessed" pharo repositories?

by Dale Henrichs

Igor, I am willing to add new features to Metacello to make the development process run smoother. The MetacelloToolBox has a number of methods for programmatically building configurations and creating new versions and I have Metacello support for copying configurations files to different repositories and automatically saving dirty mcz files, so many of the features that you are talking about may already be there. The MetacelloToolBox is documented here: http://gemstonesoup.wordpress.com/2011/01/17/metacello-1-0-beta-28-unearthe… The current toolbox api pretty much reflects my working style, but I am willing to extend/expand the api to support a broader range of requirements. Dale On Feb 3, 2011, at 6:54 AM, Igor Stasenko wrote: > On 3 February 2011 14:02, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> There is new repositories for pre-existing packages like PharoOB, Filesystem, PharoSound. >> As in the future this repositories can grow, and people like me can be confused... I wonder if we can add a page somewhere with this information? >> > > I think best would be to put it close to code. > I mean In some class comment: > - my official location is _here_ use it , or get out of my sight :) > > And of course we having metacello configs. > > I think for builds, we could create something which generating the > configurations > by extracting the official locations from some package class.. > > So, by implementing tools which can do: > MyPackageInfo officialLocation > MyPackageInfo createMetacelloConfiguration: ConfigurationOfMyPackage > > we can avoid manual steps, which lead to mistakes. > > What i tried to do is to directly extract package information form > current image and compose a script > which loads exactly same package you are using in your image. > So, then such script could be used to reproduce your configuration. > > Actually i wonder, if this feature could be added to Metacello.. > > So you could tell something like: > > ConfigurationOfMyPackage createSnapshotForNewVersion > > so, it will capture the state of packages in current image and generate > new #versionXYZ: > at instance side, which reflects it. > >> Cheers, >> Esteban >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Feb. 3, 2011

Re: [Pharo-project] Oh, great.. SqS is down

by Marcus Denker

On Feb 3, 2011, at 5:47 PM, Igor Stasenko wrote: > so i can do home... (grrrrrrr) > I will check. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 3, 2011

Re: [Pharo-project] 1.2: class var #Instance not allowed

by Marcus Denker

On Feb 3, 2011, at 6:01 PM, Sean P. DeNigris wrote: > >>>>>> One more problem: if some class have a class variable named #Instance, >>>>>> it is not loadable anymore. > > > Janko MivÅ¡ek wrote: >> >> Proceeding on this exception actually continue and successfully load Aida. >> > > So the class can be loaded, and that solves the original problem, right? > > The current behavior seemed right to me. I think it's good to know that you > will be hiding a global by using a certain class variable name. Maybe the > issue is that the message isn't clear enough, like it could be "There is > global defined with this name, click proceed to add anyway"? Or something to > make it more clear that this is a warning and you have to make your own > decision. Hmm... normally these warnings should be suppressed when loading code automatically in non-interactive mode (that is, monticello loads code vs. accepting in the browser). In the browser, we want lots of warnings. When we compile code, we just want Transcript notifications. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 3, 2011

Re: [Pharo-project] 1.2: class var #Instance not allowed

by Sean P. DeNigris

>>>>> One more problem: if some class have a class variable named #Instance, >>>>> it is not loadable anymore. Janko MivÅ¡ek wrote: > > Proceeding on this exception actually continue and successfully load Aida. > So the class can be loaded, and that solves the original problem, right? The current behavior seemed right to me. I think it's good to know that you will be hiding a global by using a certain class variable name. Maybe the issue is that the message isn't clear enough, like it could be "There is global defined with this name, click proceed to add anyway"? Or something to make it more clear that this is a warning and you have to make your own decision. Sean -- View this message in context: http://forum.world.st/1-2-class-var-Instance-not-allowed-tp3253817p3258499.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 3, 2011

[Pharo-project] Issue 3650 in pharo: PluggableShoutMorph not present in latest build of Pharo1.2

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3650 by tulipe.m...(a)gmail.com: PluggableShoutMorph not present in latest build of Pharo1.2 http://code.google.com/p/pharo/issues/detail?id=3650 Pharo image: Pharo1.2rc2 Pharo core version: #12330 Virtual machine used: Cog3.0.0 mac Steps to reproduce: 1. Download latest build from Hudson 2. Open the image 3. Do it on "ProfStef go" in the welcom workspace 4. DNU It seems that the PluggableShoutMorph is not there.

Feb. 3, 2011

[Pharo-project] Oh, great.. SqS is down

by Igor Stasenko

so i can do home... (grrrrrrr) -- Best regards, Igor Stasenko AKA sig.

Feb. 3, 2011

Re: [Pharo-project] Hudson build for Seaside too?

by Igor Stasenko

On 3 February 2011 17:04, Torsten Bergmann <astares(a)gmx.de> wrote: > OK - we have the hudson build for Pharo Core, Pharo, Moose, ... > > Since Pharo is the reference platform for Seaside > wouldnt it make sense to run a hudson build for > Seaside too: > > > Â Â Â Gofer new > Â Â Â Â Â Â Â Â squeaksource: 'MetacelloRepository'; > Â Â Â Â Â Â Â Â package: 'ConfigurationOfSeaside30'; > Â Â Â Â load. > > Â Â Â Â ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load. > > I know that http://hudson.lukas-renggli.ch/ builds a seaside > one click ... but still on the old Pharo 1.1. > > Wouldnt it make sense to have one for Pharo1.2 with Seaside3.0 > already. So we can see early when we break things for Seaside ... > +1 > Bye > T. > > > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > -- Best regards, Igor Stasenko AKA sig.

Feb. 3, 2011

Re: [Pharo-project] [squeak-dev] Accessing external resources in a cross-platform way

by Igor Stasenko

On 3 February 2011 17:14, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Ok, saved FSExtensions package in > > http://www.squeaksource.com/fs.html > > I would not integrate into main package because it depends of > ProcessWrapper and Grease. Notice the ConfigurationOfFilesystem in > MetacelloRepository now is using the release at > http://source.wiresong.ca/mc Then somebody have to release a new version of it? :) > > 2011/2/3 Igor Stasenko <siguctua(a)gmail.com>: >> On 3 February 2011 10:45, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> Ok I published everything to Filesystem which BTW was dead since 2004! >>> >>> Let us see what it will change. >>> >> >> Good. >> So let encourage people to use it as an OFFICIAL repository for >> Filesystem package. >> >> >>> Stef >>> >>>>> Hernan >>>>> >>>>> I'm documenting and reorganizing and writing more tests for FS. >>>>> I contacted colin several times but got no feedback. The version that we will integrate in Pharo is >>>>> available at: >>>>> Â Â Â Â PharoTaskForces >>>>> Â Â Â Â if you want to integrate/publish your code there, then you are welcomed. >>>>> We will do several rounds, probably integrate dale gemstone fixes, deprecate and change some api >>>>> like workingDirectory returning a path and calling it workingDirectoryPath >>>>> and push FS in Pharo. Of course, people may probably complain but we will do it. >>>>> >>>> >>>> >>>> How about using open repo.. not pharo-specific? >>>> >>>> MCHttpRepository >>>> Â Â location: 'http://www.squeaksource.com/fs' >>>> Â Â user: '' >>>> Â Â password: '' >>>> >>>> I see that FS is quite easy to port over forks/dialects. >>>> So, with some effort we can make it easily available across many >>>> smalltalk platforms. >>>> It will benefit not only Pharo (yes, Pharo could be a testbed for new >>>> filesystem), >>>> but then if people will want to port it on another platform, they will >>>> have to just get in and start hacking there, >>>> without using controversial repository (PharoTaskForces) , because it >>>> means that this stuff is only for Pharo. >>>> >>>>> Stef >>>>> >>>>> On Feb 3, 2011, at 1:01 AM, HernÃ¡n Morales Durand wrote: >>>>> >>>>>> I've just implemented an initial release on top of FileSystem and >>>>>> ProcessWrapper (it uses some bit of Grease too). This is how it works >>>>>> in Windows: >>>>>> >>>>>> ( FSLocator sysEnvBinaries / 'notepad.exe' ) resolve Â " >>>>>> C:\WINDOWS\system32\notepad.exe " >>>>>> ( FSLocator sysEnvBinaries / 'X264VFW.DLL' ) resolve Â " >>>>>> C:\WINDOWS\system32\X264VFW.DLL " >>>>>> ( FSLocator userBinaries / 'excel.exe' ) resolve Â Â Â Â Â Â Â " C:\Archivos de >>>>>> programa\Microsoft Office\OFFICE11\EXCEL.EXE " >>>>>> ( FSLocator userBinaries / 'firefox.exe' ) resolve Â Â Â Â Â Â " C:\Archivos de >>>>>> programa\Mozilla Firefox\firefox.exe" >>>>>> >>>>>> So #sysEnvBinaries search in the OS PATH environment variable >>>>>> locations (which is usually pretty fast) and #userBinaries in the >>>>>> "program files" locations (it could be slow depending the amount of >>>>>> entries). It's only tested under Windows, IIRC user binaries in Unix >>>>>> are inside "/usr/local/bin" but you may tweak it to other locations, I >>>>>> have no access to a Unix or MacOS. Feel free to suggest or add any >>>>>> enhacements you like. >>>>>> Cheers, >>>>>> >>>>>> HernÃ¡n >>>>>> >>>>>> 2011/1/28 Colin Putney <colin(a)wiresong.com>: >>>>>>> On Fri, Jan 28, 2011 at 9:17 AM, HernÃ¡n Morales Durand >>>>>>> <hernan.morales(a)gmail.com> wrote: >>>>>>>> Thanks David, >>>>>>>> >>>>>>>> I've seen FileSystem package http://www.wiresong.ca/filesystem/ >>>>>>>> it seems related in some way too >>>>>>> >>>>>>> Yes, FileSystem does attempt to provide a cross-platform way to >>>>>>> resolve paths that are system-dependent. It doesn't include a way to >>>>>>> search for executables, although that's a good feature idea. As David, >>>>>>> mentioned you probably want to get the value of the PATH environment >>>>>>> variable, and use that for your search. That will handle cross-host >>>>>>> differences as well as cross-platform issues. >>>>>>> >>>>>>> Colin >>>>>>> >>>>>>> >>>>>> <Fsextensions-hfm.2.mcz> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko AKA sig. >>>> >>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> > > -- Best regards, Igor Stasenko AKA sig.

Feb. 3, 2011

[Pharo-project] Alien-Prerequisites is now not required

by Igor Stasenko

Just found that evil overrides which contains this package are completely same as in existing Parser. The Alien-Prereqs-KenTreis.5 contains only two of them: Parser>>pragmaLiteral: selectorSoFar Parser>>pragmaStatement both are the same as in image. So, i conclude that we don't need this guy anymore for loading Alien -- Best regards, Igor Stasenko AKA sig.

Feb. 3, 2011