- Pharo-dev - lists.pharo.org

Re: [Pharo-project] XML package is barking at load time
by StÃ©phane Ducasse Oct. 31, 2010

Oct. 31, 2010

in seaside3.0 On Oct 31, 2010, at 10:55 AM, stephane ducasse wrote: > Gofer new > squeaksource: 'XMLSupport'; > package: 'XML-Parser'; load. > > raise error because of tests not present. > > Did I do something wrong? > > > Then why the configuration load pastell? > > why this is squeakCommon? Does it work if this is in pharo? > > Why do we load SIXX in gemstone? > > This configuration looks like a mess. Can somebody fix that. > core should load the parser > sixx may be sixx > pastell should load core and pastell > > Stef > > > version105: spec > <version: '1.0.5' imports: #('1.0.5-baseline' )> > > spec for: #'common' do: [ > spec blessing: #stable. > spec author: 'Alexandre Bergel'. > spec timestamp: '10/5/2010 14:06'. > ]. > > spec for: #'squeakCommon' do: [ > spec > package: 'XML-Parser' with: 'XML-Parser-AlexandreBergel.93'; > package: 'Pastell' with: 'Pastell-Alexandre_Bergel.18'.]. > > spec for: #'gemstone' do: [ > spec project: 'Grease Core' with: '1.0-rc'. > spec > package: 'XML-Parser' with: 'XML-Parser.g-DaleHenrichs.93'; > package: 'SIXX' with: 'SIXX-NorbertHartl.171'.]. > > > > Stef >

1 0

Re: [Pharo-project] how to load magritte in seaside 3.0?
by StÃ©phane Ducasse Oct. 31, 2010

Oct. 31, 2010

Ok I will use magritte2. should I load grease too? Stef On Oct 31, 2010, at 10:41 AM, Lukas Renggli wrote: > Magritte 2 uses Grease as a portability layer and works well on Seaside 3. > > Magritte 1 has its own portability layer, works well on Seaside 2.8, > but also 3 (I think). > > You should use Magritte 2 on Seaside 3. > > Lukas > > > > On 31 October 2010 10:36, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> thanks lukas >> >> what is magritte2 vs magritte? >> Because I 'm trying to rebuild an old image of mine that use an old version of magritte >> >> Stef >> >> On Oct 31, 2010, at 10:11 AM, Lukas Renggli wrote: >> >>> Until somebody figures out why the configuration does not work you >>> could use the following script from >>> http://github.com/renggli/builder/blob/master/scripts/magritte2.st. Of >>> course this assumes that Seaside 3 is already loaded. >>> >>> Gofer new >>> renggli: 'magritte2'; >>> package: 'Magritte-Model'; >>> package: 'Magritte-Pharo-Model'; >>> package: 'Magritte-Seaside'; >>> package: 'Magritte-Pharo-Seaside'; >>> package: 'Magritte-Morph'; >>> package: 'Magritte-Tests-Model'; >>> package: 'Magritte-Tests-Pharo-Model'; >>> load. >>> >>> Lukas >>> >>> On 31 October 2010 09:38, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>> Hi >>>> >>>> I want to load magritte with Seaside 3.0 and I followed >>>> >>>> http://book.pharo-project.org/book/PharoTools/Magritte/ >>>> >>>> Magritte2 For Pharo With Seaside 3 >>>> >>>> Gofer it >>>> squeaksource: 'MetacelloRepository'; >>>> package: 'ConfigurationOfMagritte'; >>>> load. >>>> (ConfigurationOfMagritte2 project version: '2.0.5') load >>>> >>>> but I does not load. >>>> >>>> Stef >>>> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch >

2 1

[Pharo-project] how to load magritte in seaside 3.0?
by stephane ducasse Oct. 31, 2010

Oct. 31, 2010

Hi I want to load magritte with Seaside 3.0 and I followed http://book.pharo-project.org/book/PharoTools/Magritte/ Magritte2 For Pharo With Seaside 3 Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagritte'; load. (ConfigurationOfMagritte2 project version: '2.0.5') load but I does not load. Stef

2 1

Re: [Pharo-project] Issues Tagged 1.2 on the BugTracker
by Marcus Denker Oct. 31, 2010

Oct. 31, 2010

On Oct 31, 2010, at 9:45 AM, StÃ©phane Ducasse wrote: > Thanks marcus. > So what is the process do we declare 1.2 beta? > -> Declare it. -> Change the version number with an update. We should do that soon. Of course, after that only "show stopper" bug fixes are allowed. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] [OffTopoc] Symbol understands value: nice hehehehehhe
by StÃ©phane Ducasse Oct. 31, 2010

Oct. 31, 2010

+1 especially when this is specific to a given system > I like the idea of using fooValue: instead of value:. > > On 10/30/10 14:15 , Tudor Girba wrote: >> We use this pattern in Mondrian scripts, Glamour scripts, and in Moose scripts for navigating models. >> >> However, we are most of the times doing it with other Symbol selectors. For example: >> - in Mondrian, we use moValue: >> - in Glamour, we use glamourValue: >> >> Using dedicated extensions enable us to control the kinds of semantics we want in the scripting. For example, the glamourValue: is different from moValue:. >> >> Cheers, >> Doru >> >> >> On 30 Oct 2010, at 22:56, Andres Valloud wrote: >> >>> Mariano, >>> >>> On 10/30/10 13:14 , Mariano Martinez Peck wrote: >>> >>>> 100% agree. It was just funny for me, how could I do that, just >>>> implementing Synbol>> value: >>>> Just something curious and funny. Not to really use it. >>> >>> I agree with this, polymorphism is awesome. For instance, something I did with Assessments was to make objects polymorphic with classes. This device allows Assessments to run SUnit tests without needing to touch any of the test case classes (you can just create pseudo-classes that pretend to be the classes you need but can't have). And you get to implement #new on the instance side :). >>> >>> Andres. >>> >> >> -- >> www.tudorgirba.com >> >> "Be rather willing to give than demanding to get." >> >> >> >> . >> >

2 1

[Pharo-project] [update 1.2] #12221
by Marcus Denker Oct. 31, 2010

Oct. 31, 2010

12221 ----- Issue 2815: Must kick me to provide TEasilyThemed helpers for all widgets (first part) Issue 3186: UndoManagerTest needs to be moved to a test package Issue 3176: Move Debugger tests from Tools to ToolsTest Issue 3175: Remove strange Packages -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Changes not working since update
by StÃ©phane Ducasse Oct. 31, 2010

Oct. 31, 2010

may be this is related to the strange registration to smalltalk that caused the recentMessages to not contain changes too. On Oct 31, 2010, at 9:22 AM, Marcus Denker wrote: > > On Oct 31, 2010, at 9:21 AM, Marcus Denker wrote: >> >> >> I checked: yes, one needs to open the changesorter once to get any >> changes recorded. >> >> This is a bug... maybe some #initialize call is missing in the cleanup code? > > > > http://code.google.com/p/pharo/issues/detail?id=3189 > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

1 0

Oct. 31, 2010

Thanks marcus. So what is the process do we declare 1.2 beta? Stef On Oct 31, 2010, at 9:17 AM, Marcus Denker wrote: > 37 out of 387: > > http://code.google.com/p/pharo/issues/list?cursor=2858 > > ... not all are showstoppers. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

1 0

Re: [Pharo-project] Changes not working since update
by Marcus Denker Oct. 31, 2010

Oct. 31, 2010

On Oct 31, 2010, at 9:21 AM, Marcus Denker wrote: > > > I checked: yes, one needs to open the changesorter once to get any > changes recorded. > > This is a bug... maybe some #initialize call is missing in the cleanup code? http://code.google.com/p/pharo/issues/detail?id=3189 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Changes not working since update
by Marcus Denker Oct. 31, 2010

Oct. 31, 2010

On Oct 31, 2010, at 2:47 AM, Igor Stasenko wrote: > after updating pharo core image (Update #12220), > the list of changes is just one: 'Unnamed', Yes, that comes from the #releaseCleanup cleaning the changesets. > also, it was empty once i tried to check what changes i did to image, > after some coding. > Once i created a new changeset, and changed few things, these changes > recorded properly in new changeset I checked: yes, one needs to open the changesorter once to get any changes recorded. This is a bug... maybe some #initialize call is missing in the cleanup code? -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0