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

Re: [Pharo-project] About FileSystem

by Dale Henrichs

On Feb 3, 2011, at 1:08 PM, StÃ©phane Ducasse wrote: > I tried to publish a new configurationOfFilesystem > but after 15 min I stopped because I could not make it load. > For me there is something wrong with the interface of metacello because I can never remember it > version: '1.0.2' did not load it while it defined as version: #'1.0.2' > and of course I tried string and symobols.... Stef, I recommend that you try to use the validator: (MetacelloToolBox validateConfiguration: ConfigurationOfFilesystem) inspect The validator should complain about using #'1.0.2' or '1.0.2' incorrectly. If the issue printString isn't enough you should be able to get more info from the #reasonCode: MetacelloToolBox descriptionForValidationReasonCode: <reasonCode from validation issue> If the validator doesn't provide a good enough explanation, I'm interested in improving it. If you run into a problem when you reconstruct the configuration and the validator doesn't give you good information, then please feel free to ship me a copy of the configuration so I can be the human validator - which in turn will spur me on to improve the validator:) I extend this invitation to anyone having trouble with Metacello. Dale

Feb. 3, 2011

[Pharo-project] Pharo fondation: administration and real people

by Torsten Bergmann

>We need to replace squeaksource soon, this is really sucking too much energy >like that. Maybe it is that squeaksource.com is getting on its LIMITS now and then. There are other squeaksource servers http://source.lukas-renggli.ch http://source.squeak.org and I havent heard that they face the same problems as the one from squeaksource.com. Maybe we should set up a NEW AND EMPTY squeaksource server instance for Pharo in parallel. And pharosource.com is still available ;) This new server instance can then be used to host the pharo/pharo inbox projects and other directly related Pharo stuff like the eventually forked OB. Anyone able to donate a webserver with good backup or is it possible to run this on our existing infrastructure? Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

Feb. 3, 2011

[Pharo-project] Hudson build for Seaside too?

by Torsten Bergmann

>I find strange that seaside relies on OB. >We should remove this dependency (of course making sure that OB loads is >important) but this is another issue.? No, dont judge too early. Seaside itself is not dependent on OB. But there are same tools that get loaded when you load the full config for Pharo. These tools use OB to provide a browser for registered applications for instance, ... and it is OK that these are based on OB. So no architectural problem - Seaside is really good layered/modularized. Thanks to Lukas, Phillipe and a whiteboard I think ... Bye T. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

Feb. 3, 2011

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

by Dale Henrichs

Stef, The Seaside control panel is built on top of OB. It is entirely possible to deploy a Seaside application without including the Seaside control panel, but you need to know how to manually configure/start/stop the adaptors. As a result it was decided to include the control panel as part of the default install. For the purposes of testing Seaside, one could arrange to load everything but the control panel - I could provide you with a load expression that excluded the control panel. As I think about this it probably is a _good_ to test Seaside against Pharo with and without OB on top of a core image, since Seaside is expected to work in both cases... Dale On Feb 3, 2011, at 12:40 PM, StÃ©phane Ducasse wrote: > I find strange that seaside relies on OB. > We should remove this dependency (of course making sure that OB loads is important) but this is another issue. > > Stef >>> Gofer new >>> squeaksource: 'MetacelloRepository'; >>> package: 'ConfigurationOfSeaside30'; >>> load. >>> >>> ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load. >> >> For the last couple of weeks, and again this evening I wanted to start using 1.2 as my main image, but that requires Seaside 3, the above still does not work for me: >> >> Pharo1.2rc2 >> Latest update: #12330 >> >> ConfigurationOfOmnibrowser>>postLoadOBStandard >> >> Preferences DNU #enable >> >> As long as Seaside does not load, I will have to stick with 1.1.1, even if I really would like to switch... >> And I am pretty sure I am not the only one >> >> Sven >> >> > >

Feb. 3, 2011

Re: [Pharo-project] About FileSystem

by StÃ©phane Ducasse

I tried to publish a new configurationOfFilesystem but after 15 min I stopped because I could not make it load. For me there is something wrong with the interface of metacello because I can never remember it version: '1.0.2' did not load it while it defined as version: #'1.0.2' and of course I tried string and symobols.... And I got a bug in the decompiler that crashed my image probably here [tempVector remoteTemps size = maybeTVTag value size]]] assert] and so I lost everything... popIntoTemporaryVariable: offset | maybeTVTag tempVector start | maybeTVTag := stack last. ((maybeTVTag isMemberOf: Association) and: [maybeTVTag key == #pushNewArray]) ifTrue: [blockStartsToTempVars notNil "implies we were intialized with temp names." ifTrue: "Use the provided temps" [[(tempVector := tempVars at: offset + 1 ifAbsent: [ParseNode basicNew]) isTemp and: [tempVector isIndirectTempVector and: [tempVector remoteTemps size = maybeTVTag value size]]] assert] ifFalse: "Synthesize some remote temps" [tempVector := maybeTVTag value. offset + 1 <= tempVars size ifTrue: [start := 2. tempVector at: 1 put: (tempVars at: offset + 1)] ifFalse: [tempVars := (Array new: offset + 1) replaceFrom: 1 to: tempVars size with: tempVars. start := 1]. start to: tempVector size do: [:i| tempVector at: i put: (constructor codeTemp: numLocalTemps + offset + i - 1 named: 't', (tempVarCount + i) printString)]. tempVars at: offset + 1 put: (constructor codeRemoteTemp: offset + 1 remoteTemps: tempVector)]. tempVarCount := tempVarCount + maybeTVTag value size. stack removeLast. ^self]. self pushTemporaryVariable: offset; doStore: statements On Feb 3, 2011, at 10:43 AM, StÃ©phane Ducasse wrote: > Hi guys > > Igor convinced me to publish filesystem into the squeaksource Filesystem so that others people can not feel > that we are stealing it from colin. Now since we want it as a fondation for the our system, we should invest on it. > and this is what I'm doing. > > So here is what I did > - fetched all the versions from colin, lukas, pharotaskforces > - pushed all the versions to squeaksource/Filesystem > - pushed all the versions to pharoTaskForces > > Now I will publish to squeaksource/Filesystem. > > If people want to join this is open and free. > > Stef

Feb. 3, 2011

[Pharo-project] Hudson build for Seaside too?

by Torsten Bergmann

Sven wrote: >For the last couple of weeks, and again this evening I wanted to start using >1.2 as my main image, but that requires Seaside 3, the above still does not >work for me: Hi Sven, works for me without a problem. I work in latest pharo-dev 1.2 with Seaside 3.0.3 loaded. Can run JqueryWidgetBox and MetaSource for example without any problem, just bootstrapped today using the configs. There are some red tests due to the fact that Seaside uses Preferences in some packages and these are thrown out in Pharo 1.2. Maybe your image is outdated. Did you try one of the prebuilt clean pharo 1.2 images from the hudson server http://ci.pharo-project.org ? Try the one from the latest working build from today (see [1]) and download the image (direct url to the ZIP is [2]). Make sure you start in a new directory (or at least rename the package-cache folder). Then run the following expressions: DEVImageWorkspaces openExternalProjectWorkspace In this workspace run the first script Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load. Tell me if this works for you. Bye T. [1] https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/116/ [2] https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/116/artif… -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl

Feb. 3, 2011

Re: [Pharo-project] Pharo fondation: administration and real people

by StÃ©phane Ducasse

Cool and thanks. Sean you know we try to pay attention to your fixes and we appreciate them/ Just not enough time to do all the work that should be done but we will do it. I think that it would be good for native english speakers to help bloging :) Since the mailing is quite dense, a digest every week for the outside world would be a huge promotion. I know some people that cannot cope with the amount of mails but would love to be aware of what we are doing. Stef On Feb 3, 2011, at 9:32 PM, Sean P. DeNigris wrote: > > I would be happy to participate if I can be of service. I am aligned with and > excited about the Pharo vision and am very interested in building on the > North American (and especially New York) community. > > Sean > -- > View this message in context: http://forum.world.st/Pharo-fondation-administration-and-real-people-tp3257… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Feb. 3, 2011

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

by StÃ©phane Ducasse

+1 >> > We need to replace squeaksource soon, this is really sucking too much energy like that.

Feb. 3, 2011

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

by StÃ©phane Ducasse

I find strange that seaside relies on OB. We should remove this dependency (of course making sure that OB loads is important) but this is another issue. Stef >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfSeaside30'; >> load. >> >> ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load. > > For the last couple of weeks, and again this evening I wanted to start using 1.2 as my main image, but that requires Seaside 3, the above still does not work for me: > > Pharo1.2rc2 > Latest update: #12330 > > ConfigurationOfOmnibrowser>>postLoadOBStandard > > Preferences DNU #enable > > As long as Seaside does not load, I will have to stick with 1.1.1, even if I really would like to switch... > And I am pretty sure I am not the only one > > Sven > >

Feb. 3, 2011

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

by StÃ©phane Ducasse

good idea! Stef On Feb 3, 2011, at 7:19 PM, Nicolas Cellier wrote: > Also, if there is a deprecated repositoriy: > - put a comment clearly stating that the directory is intended to be > closed and read only > - indicate where further work should take place. > You have the main web tab, the wiki. > I also suggest to publish a last MC version for the main packages > with no change, and a commit comment indicating new location. > > Nicolas > > 2011/2/3 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> thanks dale >> I should finish the chapter. But I got two projects to write for the 18th, so after :) >> >> On Feb 3, 2011, at 6:16 PM, Dale Henrichs wrote: >> >>> 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