- Pharo-dev - lists.pharo.org

[Pharo-project] Export Pier to Latex

by Guillermo Polito

Does Pier support that? Do I need a plugin? Has someone tried to do something like that? :) Thanks! Guille

Feb. 4, 2011

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

by Guillermo Polito

Yeap, building groups :). On Thu, Feb 3, 2011 at 9:03 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 3 February 2011 22:08, Dale Henrichs <dhenrich(a)vmware.com> wrote: > > 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... > > > > I don't know much details, but i think it is possible with metacello > to say 'load config which not using OB' . Right? > > > 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 > >>> > >>> > >> > >> > > > > > > > > > > -- > Best regards, > Igor Stasenko AKA sig. > >

Feb. 4, 2011

[Pharo-project] Where is OB Was: [what do we do for OmniBrowser?]

by Guillermo Polito

Today's ConfigurationOfOmniBrowser relies on lukas repo and PharoTaskForces (in SS). When there is an 1.2 specific fix, I'm commiting it to PharoTaskForces. When there is a fix on Lukas repo, I merge it and commit it to PharoTaskForces. BTW, If we push everything in PharoOB, we'll have everything there (OB code and metacello configurations). PharoOB has global read and write access (I recreated it a few hours ago since it got lost :P ), so everyone may contribute :). Guille On Thu, Feb 3, 2011 at 8:57 PM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > Guillermo please tell us which code base you are using otherwise OB > will continue to be one-man show. > > 2011/2/3 Guillermo Polito <guillermopolito(a)gmail.com>: > > > > I'm integrating already the fixes into PharoTaskForces. If I have some > tome > > tomorrow I'll push OB from Lukas repo to PharoOB and merge. > > > > Guille :) > > > >> > >> Stef > >> > >

Feb. 4, 2011

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

by Igor Stasenko

On 3 February 2011 22:08, Dale Henrichs <dhenrich(a)vmware.com> wrote: > 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... > I don't know much details, but i think it is possible with metacello to say 'load config which not using OB' . Right? > 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 >>> >>> >> >> > > > -- Best regards, Igor Stasenko AKA sig.

Feb. 4, 2011

Re: [Pharo-project] what do we do for OmniBrowser?

by HernÃ¡n Morales Durand

Guillermo please tell us which code base you are using otherwise OB will continue to be one-man show. 2011/2/3 Guillermo Polito <guillermopolito(a)gmail.com>: > > I'm integrating already the fixes into PharoTaskForces.Â If I have some tome > tomorrow I'll push OB from Lukas repo to PharoOB and merge. > > Guille :) > >> >> Stef >>

Feb. 3, 2011

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

by Sven Van Caekenberghe

Hi Torsten, Thanks for the quick reply. On 03 Feb 2011, at 22:02, Torsten Bergmann wrote: > 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]). I did take a fresh image. > Make sure you start in a new directory (or at least rename > the package-cache folder). Then run the following expressions: I did not, why is this necessary (loading all these packages is slow enough already) ? But that seems the only variable, a specific, named package should always be the same no matter what, right ? > DEVImageWorkspaces openExternalProjectWorkspace > > In this workspace run the first script > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside30'; > load. > > ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load. That is the expression that I tried. > Tell me if this works for you. I will try again tomorrow, I will let you know. It is good to know that it works for you. Sven

Feb. 3, 2011

Re: [Pharo-project] Move packages in monticello w/o losing history

by Dale Henrichs

If I'm not mistaken, Gofer will copy all versions of a package for you ... I think that the 'push' command will do the trick, but reading the method comments makes me think you might have to 'fetch' the versions to your cache, then 'push' them to your destination repository. Dale On Feb 3, 2011, at 2:34 PM, Guillermo Polito wrote: > Hi! > > I want to move some packages from a Squeaksource repository to another, but I don't want to lose all the history of the package, so copying the last version does not solve it at all. > > Is there nice way to do this? > > thanks! > Guille

Feb. 3, 2011

[Pharo-project] Move packages in monticello w/o losing history

by Guillermo Polito

Hi! I want to move some packages from a Squeaksource repository to another, but I don't want to lose all the history of the package, so copying the last version does not solve it at all. Is there nice way to do this? thanks! Guille

Feb. 3, 2011

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

by Adrian Lienhard

Hi Sean and Dmitri, Thanks for offering your help. Indeed, it would be cool if we could set up a small team of two or three people who would help building the community through regular blogging, twittering, improving the website, etc. Cheers, Adrian On Feb 3, 2011, at 21:45 , StÃ©phane Ducasse wrote: > 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] 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