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

Re: [Pharo-dev] how to Initialize class layouts

by Pavel Krivanek

Hmm, it was removed in 30618. I'll look at it. Thanks -- Pavel 2014-02-16 16:19 GMT+01:00 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com>: > There was (is?) a Slot virus that, if I remember correctly, was in charge > of propagating the slot layout instantiation. > > Ben > > On 16 Feb 2014, at 16:13, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi, > > the classes in bootstrapped image have no layouts set. We must initialize > them somehow because than class builder fails. Is there the code that did > this task during Slot integration somewhere? Or can someone erudite tell us > how to do that? > > Cheers, > -- Pavel > > >

Feb. 16, 2014

Re: [Pharo-dev] how to Initialize class layouts

by Benjamin

There was (is?) a Slot virus that, if I remember correctly, was in charge of propagating the slot layout instantiation. Ben On 16 Feb 2014, at 16:13, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi, > > the classes in bootstrapped image have no layouts set. We must initialize them somehow because than class builder fails. Is there the code that did this task during Slot integration somewhere? Or can someone erudite tell us how to do that? > > Cheers, > -- Pavel

Feb. 16, 2014

how to Initialize class layouts

by Pavel Krivanek

Hi, the classes in bootstrapped image have no layouts set. We must initialize them somehow because than class builder fails. Is there the code that did this task during Slot integration somewhere? Or can someone erudite tell us how to do that? Cheers, -- Pavel

Feb. 16, 2014

Re: [Pharo-dev] Fosdem Videos and Pharo. 4 presentation

by Marcus Denker

Hi, the video now is fixed. I added it to youtube for slightly easier viewing, too: http://www.youtube.com/watch?v=mUV9E03u52g On 12 Feb 2014, at 00:22, Bernardo Ezequiel Contreras <vonbecmann(a)gmail.com> wrote: > Hi, > They already know it, but they are busy. be patient > > On Sun, Feb 09, 2014 at 08:06:03PM -0200, Bernardo Ezequiel Contreras wrote: > > Hi, > > the following video > > http://video.fosdem.org/2014/K4401/Saturday/Pharo4_Plans_and_Dreams.webm > > doesn't contain the presentation by marcus denker, instead it contains the > > "Objective Smalltalk" presentation by Marcel Weiher. > > Could someone fix this, please? > > Thanks for letting us know. > > The video team will take a look as soon as they can, but please > understand if it takes a while as they are still busy! > >

Feb. 16, 2014

Re: [Pharo-dev] Dirty Seaside-pharo-core and Seaside-pharo-core-backtracking

by Max Leske

Hmâ¦ donât really know but I guess they could come fromt the configuration. If you look for the string âseaside-pharoâ in the image then youâll see that those packages are specified in the configuration. But if you really want to know youâll probably have to step through a loading cycle with Metacelloâ¦ good luck with that :) On 16.02.2014, at 14:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > As far as I can see, there is no such package, at all, that is why I am puzzled ;-) > > On 16 Feb 2014, at 14:50, Max Leske <maxleske(a)gmail.com> wrote: > >> If youâve loaded Seaside-Pharo then those extensions would be in the Seaside-Pharo package, wouldnât they? >> >> >> On 16.02.2014, at 14:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> When using the latest Seaside on Pharo 3 (either loading ConfigurationOfBootstrap or the Seaside image, 3.0 bleedingEdge, built on the pharo-contribution CI server), I have two mysterious dirty packages without a repository: >>> >>> - Seaside-pharo-core >>> - Seaside-pharo-core-backtracking >>> >>> These only contain extensions. There are no such Seaside package as far as I can see. >>> >>> What puzzles me is how the code got in the image in the first place: I can understand that these are possible wrong extension protocol names, but since they must be loaded by an MC package, how did they get into that package in the first place ? >>> >>> Sven >>> >>> -- >>> Sven Van Caekenberghe >>> http://stfx.eu >>> Smalltalk is the Red Pill >>> >>> >> >> > >

Feb. 16, 2014

Re: [Pharo-dev] Dirty Seaside-pharo-core and Seaside-pharo-core-backtracking

by Sven Van Caekenberghe

As far as I can see, there is no such package, at all, that is why I am puzzled ;-) On 16 Feb 2014, at 14:50, Max Leske <maxleske(a)gmail.com> wrote: > If youâve loaded Seaside-Pharo then those extensions would be in the Seaside-Pharo package, wouldnât they? > > > On 16.02.2014, at 14:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> When using the latest Seaside on Pharo 3 (either loading ConfigurationOfBootstrap or the Seaside image, 3.0 bleedingEdge, built on the pharo-contribution CI server), I have two mysterious dirty packages without a repository: >> >> - Seaside-pharo-core >> - Seaside-pharo-core-backtracking >> >> These only contain extensions. There are no such Seaside package as far as I can see. >> >> What puzzles me is how the code got in the image in the first place: I can understand that these are possible wrong extension protocol names, but since they must be loaded by an MC package, how did they get into that package in the first place ? >> >> Sven >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> > >

Feb. 16, 2014

Re: [Pharo-dev] Dirty Seaside-pharo-core and Seaside-pharo-core-backtracking

by Max Leske

If youâve loaded Seaside-Pharo then those extensions would be in the Seaside-Pharo package, wouldnât they? On 16.02.2014, at 14:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > When using the latest Seaside on Pharo 3 (either loading ConfigurationOfBootstrap or the Seaside image, 3.0 bleedingEdge, built on the pharo-contribution CI server), I have two mysterious dirty packages without a repository: > > - Seaside-pharo-core > - Seaside-pharo-core-backtracking > > These only contain extensions. There are no such Seaside package as far as I can see. > > What puzzles me is how the code got in the image in the first place: I can understand that these are possible wrong extension protocol names, but since they must be loaded by an MC package, how did they get into that package in the first place ? > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > >

Feb. 16, 2014

List methods with problematic source

by Sebastian Sastre

Hi guys, How can I collect a list of methods with undefined classes in its source? Example: Iâve recently saw that Comanche http server had a package that wonât load in Pharo 3 because is using FileDirectory. Comanche now loads alright after a patch but.. Instead of iterating lazily this kind of problem in other packages, I would like to make a script that lists all this kind of cases in a given package. BTW a script like this would help to anticipate potential problems to other developers porting a product to Pharo When inspecting one of this methods Iâve sent #recompile to see if it raises an exception but it isnât. How can I perceive, using code, that a compiled method has this kind of problem? sebastian o/

Feb. 16, 2014

Dirty Seaside-pharo-core and Seaside-pharo-core-backtracking

by Sven Van Caekenberghe

When using the latest Seaside on Pharo 3 (either loading ConfigurationOfBootstrap or the Seaside image, 3.0 bleedingEdge, built on the pharo-contribution CI server), I have two mysterious dirty packages without a repository: - Seaside-pharo-core - Seaside-pharo-core-backtracking These only contain extensions. There are no such Seaside package as far as I can see. What puzzles me is how the code got in the image in the first place: I can understand that these are possible wrong extension protocol names, but since they must be loaded by an MC package, how did they get into that package in the first place ? Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Feb. 16, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30764 Home: https://github.com/pharo-project/pharo-core

Feb. 16, 2014