- Pharo-dev - lists.pharo.org

Re: [Pharo-project] SqueakSource 3

by Tobias Pape

Am 2011-04-20 um 15:49 schrieb Torsten Bergmann: >> How shall I specify 'I want a working Seaside of version X' >> in my metacello Config? > > Have a look at ConfigurationOfExternalWebbrowser in > squeaksource/MetacelloRepository for an example. > > This one requires the FFI project. > > You add the project in the baseline > > > spec > project: 'FFI' with: [ > spec > className: 'ConfigurationOfFFI'; > file: 'ConfigurationOfFFI'; > repository: 'http://www.squeaksource.com/MetacelloRepository']. > > and set the version in your version method: > > spec > project: 'FFI' with: '1.3'. There is not much difference to the spec I used but a) I put the version into the project spec in the basline b) I put the groups to load into the project spec, too. Shall I omit the groups spec? So Long, -Tobias

April 20, 2011

Re: [Pharo-project] SqueakSource 3

by Tobias Pape

Am 2011-04-20 um 15:44 schrieb GermÃ¡n Arduino: > 2011/4/20 Tobias Pape <Das.Linux(a)gmx.de>: >> >> Am 2011-04-20 um 14:19 schrieb Torsten Bergmann: >> >>> Hi Tobias, >>> >>> looks like it is basically working. I used a clean Pharo 1.2.1, then loaded Seaside >>> >>> Gofer new >>> squeaksource: 'MetacelloRepository'; >>> package: 'ConfigurationOfSeaside30'; >>> load. >>> >>> ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load. >>> >>> >>> then loaded you script: >>> >>> >>> Gofer new >>> squeaksource: 'MetacelloRepository'; >>> package: 'ConfigurationOfSqueakSource'; >>> load. >>> ((Smalltalk at: #ConfigurationOfSqueakSource) project version: #development) load. >>> >>> After that I started Seaside using the seaside control panel >>> and went to http://localhost:9094/installSS >>> >>> I got two errors, but after proceeding I was able to run >>> an instance of SS3. Cool. >> >> I would be certainly interested in the errors. > > In a Squeak 4.2 image with seaside preloaded, trying to install > SqueakSource3, the first error coming is: > MessageNotUnderstood: MethodContext>>tempScopedNames (seems to be in > WAPharoWalkback). Ah, that oneâ¦, -.-' One of the differences between Squeak and Pharo. The method is called tempNames in Squeak and was in earlier Pharos. Now the Pharo one changed and is used henceforth in WAPharoWalkback. That is a Seasdie problem, after all. Possible solutions: 1) hack the imaged and add MethodContext>>tempScopedNames to return self tempNames 2) persuade the Squeak community to rename tempNames to tempScopedNames (just kidding) 3) persuade the Pharo community to re-rename tempScopedNames to tempNames (well, just kidding, too) 4) persuade the Seaside-developers to a) Create a WASqueakWalkback that is like the WAPharoWalkback but uses the indicated message or b) make the tempScopedNames-message âgreasyâ, ie, marked as platform-dependent. BTW: when a Walkback is popping up, there must be a root cause, would you like to seek for that? So Long, -Tobias

April 20, 2011

Re: [Pharo-project] input for pending items to integrate

by Marcus Denker

On Wed, Apr 20, 2011 at 1:01 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > Take three minutes and reply to this mail. I would like to get a list of pending fixes I should focus on to help you. > Because I can take the tagged items but this is a bit like ok that one > but I want to make sure that I'm spending time to making you making progress. > So just tell me. > It would be nice to have more people looking at reducing the number of bugs in the tracker. http://code.google.com/p/pharo/issues/list 435 to go... -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

April 20, 2011

Re: [Pharo-project] SqueakSource 3

by Tobias Pape

Am 2011-04-20 um 15:33 schrieb GermÃ¡n Arduino: > 2011/4/20 Tobias Pape <Das.Linux(a)gmx.de>: >> >> >> oO the Seaside3-dependency should be there. >> But it is a basic dependency not dictating any adaptor. >> >> To Dale or whoever is capable of this: >> >> How shall I specify 'I want a working Seaside of version X' >> in my metacello Config? >> >> Aparently, doing >> >> spec >> package: 'SqueakSource-Core' with: [ >> spec requires: #( "â¦" 'Seaside Extras' "â¦" )]; >> project: 'Seaside Extras' with: [ >> spec >> className: 'ConfigurationOfSeaside30'; >> loads: #('Seaside-Email' 'RSS-Core'); >> file: 'ConfigurationOfSeaside30'; >> versionString: '3.0.4'; >> repository: 'http://www.squeaksource.com/MetacelloRepository']; >> >> does not suffice. >> >> > > Yes, a dependency is missing. Why not load the complete Seaside? > I don't understand. As an âapplication developerâ I cannot tell the one who will install that what installtion configuration of seaside to use. Eg, I cannot say 'use this adaptor' because I do not have this dependency. Is there a 'default group' for Seaside that brings me 'Seaside-Email', but a runnable Seaside installation, too? So Long, -Tobias

April 20, 2011

[Pharo-project] SqueakSource 3

by Torsten Bergmann

>How shall I specify 'I want a working Seaside of version X' >in my metacello Config? Have a look at ConfigurationOfExternalWebbrowser in squeaksource/MetacelloRepository for an example. This one requires the FFI project. You add the project in the baseline spec project: 'FFI' with: [ spec className: 'ConfigurationOfFFI'; file: 'ConfigurationOfFFI'; repository: 'http://www.squeaksource.com/MetacelloRepository']. and set the version in your version method: spec project: 'FFI' with: '1.3'. Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

April 20, 2011

Re: [Pharo-project] SqueakSource 3

by GermÃ¡n Arduino

2011/4/20 Tobias Pape <Das.Linux(a)gmx.de>: > > Am 2011-04-20 um 14:19 schrieb Torsten Bergmann: > >> Hi Tobias, >> >> looks like it is basically working. I used a clean Pharo 1.2.1, then loaded Seaside >> >> Gofer new >> Â Â Â Â Â Â Â squeaksource: 'MetacelloRepository'; >> Â Â Â Â Â Â Â package: 'ConfigurationOfSeaside30'; >> Â Â Â load. >> >> Â Â Â ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load. >> >> >> then loaded you script: >> >> >> Gofer new >> Â Â Â squeaksource: 'MetacelloRepository'; >> Â Â Â package: 'ConfigurationOfSqueakSource'; >> Â Â Â load. >> ((Smalltalk at: #ConfigurationOfSqueakSource) project version: #development) load. >> >> After that I started Seaside using the seaside control panel >> and went to http://localhost:9094/installSS >> >> I got two errors, but after proceeding I was able to run >> an instance of SS3. Cool. > > I would be certainly interested in the errors. In a Squeak 4.2 image with seaside preloaded, trying to install SqueakSource3, the first error coming is: MessageNotUnderstood: MethodContext>>tempScopedNames (seems to be in WAPharoWalkback).

April 20, 2011

Re: [Pharo-project] SqueakSource AND SmalltalkHub down ;)

by Geert Claes

Janko MivÅ¡ek wrote: > > Guys, be patient please, this is alpha release only! I think StHub is > worth waiting a bit more to stabilize and I'm sure Nico and Seb will > manage to do the job. > > And you already see how big step forward not to mention all yet to be > explored potential has this hub, isn't that so? > Absolutely, at least we have been able to lift the lid and have a peak at what's coming :) -- View this message in context: http://forum.world.st/SqueakSource-AND-SmalltalkHub-down-tp3462530p3463021.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 20, 2011

Re: [Pharo-project] SqueakSource 3

by GermÃ¡n Arduino

2011/4/20 Tobias Pape <Das.Linux(a)gmx.de>: > > > oO the Seaside3-dependency should be there. > But it is a basic dependency not dictating any adaptor. > > To Dale or whoever is capable of this: > > Â Â Â Â How shall I specify 'I want a working Seaside of version X' > Â Â Â Â in my metacello Config? > > Â Â Â Â Aparently, doing > > Â Â Â Â spec > Â Â Â Â Â package: 'SqueakSource-Core' with: [ > Â Â Â Â Â Â spec requires: #( "â¦" 'Seaside Extras' "â¦" )]; > Â Â Â Â Â project: 'Seaside Extras' with: [ > Â Â Â Â Â Â spec > Â Â Â Â Â Â Â className: 'ConfigurationOfSeaside30'; > Â Â Â Â Â Â Â loads: #('Seaside-Email' 'RSS-Core'); > Â Â Â Â Â Â Â file: 'ConfigurationOfSeaside30'; > Â Â Â Â Â Â Â versionString: '3.0.4'; > Â Â Â Â Â Â Â repository: 'http://www.squeaksource.com/MetacelloRepository']; > > Â Â Â Â does not suffice. > > Yes, a dependency is missing. Why not load the complete Seaside?

April 20, 2011

Re: [Pharo-project] SqueakSource 3

by Tobias Pape

Am 2011-04-20 um 14:19 schrieb Torsten Bergmann: > Hi Tobias, > > looks like it is basically working. I used a clean Pharo 1.2.1, then loaded Seaside > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside30'; > load. > > ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load. > > > then loaded you script: > > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSqueakSource'; > load. > ((Smalltalk at: #ConfigurationOfSqueakSource) project version: #development) load. > > After that I started Seaside using the seaside control panel > and went to http://localhost:9094/installSS > > I got two errors, but after proceeding I was able to run > an instance of SS3. Cool. I would be certainly interested in the errors. > > Would be nice if the config for Squeaksource 3 could be > extended for Pharo (together with a dependency on Seaside 3 config) oO the Seaside3-dependency should be there. But it is a basic dependency not dictating any adaptor. To Dale or whoever is capable of this: How shall I specify 'I want a working Seaside of version X' in my metacello Config? Aparently, doing spec package: 'SqueakSource-Core' with: [ spec requires: #( "â¦" 'Seaside Extras' "â¦" )]; project: 'Seaside Extras' with: [ spec className: 'ConfigurationOfSeaside30'; loads: #('Seaside-Email' 'RSS-Core'); file: 'ConfigurationOfSeaside30'; versionString: '3.0.4'; repository: 'http://www.squeaksource.com/MetacelloRepository']; does not suffice. > so that one could easily load anything using your simple > script right from a Pharo 1.2 image. > > It could then be added to http://ci.pharo-project.org by Marcus > as one of the projects to build and everybody is able to download > his own private squeaksource server ... Probably; I'm thinking of similar things :) So Long, -Tobias

April 20, 2011

Re: [Pharo-project] input for pending items to integrate

by Alexandre Bergel

RPackage and Nautilus :-) Alexandre On 20 Apr 2011, at 07:01, StÃ©phane Ducasse wrote: > Hi guys > > Take three minutes and reply to this mail. I would like to get a list of pending fixes I should focus on to help you. > Because I can take the tagged items but this is a bit like ok that one > but I want to make sure that I'm spending time to making you making progress. > So just tell me. > > I will try to integrate some fixes regularly now. > My own list is > Transcript :) > Zinc > and fixxxxing RPackage :( > Stef -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 20, 2011