Magma January 2008

magma@lists.squeakfoundation.org

11 participants
8 discussions

Start a nNew thread

[Fwd: Re: [ANN] Magma seasideHelper and Tutorial]
by Keith Hodges 30 Jan '08

30 Jan '08

1 0

[ANN] Magma seasideHelper and Tutorial
by Robert Schwarz 30 Jan '08

30 Jan '08

Hi Keith, I have tried out your Magma seasideHelper and the ToDo application. Everything looks good but I have one problem. The data inputs in the ToDO application are not stored in the magma database (used the default configuration WAMagmaSoloAuto). When I call "self session db addUser: 'aUser' in a renderContentOn method, the new user was added to the STMagmaDatabase dictionary but these changes are not stored persistent in the magma database. Do I anything wrong or how can I find out what was going wrong? Robert

4 4

FW: Re: Nil in an index
by brent＠zamail.co.za 16 Jan '08

16 Jan '08

Hi, Actually the MaDateIndex was used in some real work. It mught be prudent to accept a tested patch to the MaDateIndex that, conditionally, allows null date values. Since this null feature will probably crop up in a lot of index classes, it might be prudent to agree on a naming convention. E.g. index := MaDateIndex new acceptNulls; yourself. Chris should have the final word on the naming IMHO. Cheers Brent From: asqueaker(a)gmail.com To: nmanzanos(a)gmail.com, Subject: FW: Re: Nil in an index Date: Sat, 12 Jan 2008 22:48:11 -0500 The indexes provided with Magma are really just simple examples. Robust applications will almost certainly want to define their own custom indexes. That is your path to a clean solution. Make your own DateIndex that accepts a nil. Just override #canIndex: in addition to #indexHashForIndexObject:, et al... On Jan 11, 2008 9:43 AM, Norberto Manzanos <nmanzanos(a)gmail.com> wrote: > Hi! > > Is it a good idea avoid nil in magma indexes? > This question rised when I tried MaDateIndex. Until this moment, I used > String or Integer indexes having care to answer allways a String (an empty > string if the object is nil) and an Integer (a zero if nil). But with dates > there is a conceptual problem: there is not a null date. In some > applications, business stuff, for example, you can think in an ovbiously > unused date (01-01-1500, for example) that acts as a null date. It's a > little dirty, but it would work. But in other applications every possible > date has a meaning. And if the object could be inexistent in some cases, you > have no choice: it's nil. > That's my case, and I'm forced to use a StringIndex, converting the dates to > Strings, answering an empty string if the object is nil. That's really > dirty. > Would'nt be better if magma indexes just ignore nil objects? Is it a > requirement for magma that every object from a MagmaCollection must be > present in all indexes? > I hope there is something I misunderstood and there is a more elegant > solution. > > Regards > Norberto > > > _______________________________________________ > Magma mailing list > Magma(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma > > _______________________________________________ Magma mailing list Magma(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma

2 1

Magma on Seaside 2.8 mini-image
by Chad Nantais 14 Jan '08

14 Jan '08

http://seaside.st/download/squeak?13 Has anyone been able to install Magma on the Seaside 2.8 mini-image on the page above? I can't because it wants me to install eToys and a bunch of other stuff. Thanks, Chad

5 7

FW: Re: Nil in an index
by brent＠zamail.co.za 14 Jan '08

14 Jan '08

Hi, Actually the MaDateIndex was used in some real work. It mught be prudent to accept a tested patch to the MaDateIndex that conditionally, allows null date values. Since this null feature will probably crop up in a lot of index classes, it might be prudent to agree on a naming convention. E.g From: asqueaker(a)gmail.com To: nmanzanos(a)gmail.com, Subject: FW: Re: Nil in an index Date: Sat, 12 Jan 2008 22:48:11 -0500 The indexes provided with Magma are really just simple examples. Robust applications will almost certainly want to define their own custom indexes. That is your path to a clean solution. Make your own DateIndex that accepts a nil. Just override #canIndex: in addition to #indexHashForIndexObject:, et al... On Jan 11, 2008 9:43 AM, Norberto Manzanos <nmanzanos(a)gmail.com> wrote: > Hi! > > Is it a good idea avoid nil in magma indexes? > This question rised when I tried MaDateIndex. Until this moment, I used > String or Integer indexes having care to answer allways a String (an empty > string if the object is nil) and an Integer (a zero if nil). But with dates > there is a conceptual problem: there is not a null date. In some > applications, business stuff, for example, you can think in an ovbiously > unused date (01-01-1500, for example) that acts as a null date. It's a > little dirty, but it would work. But in other applications every possible > date has a meaning. And if the object could be inexistent in some cases, you > have no choice: it's nil. > That's my case, and I'm forced to use a StringIndex, converting the dates to > Strings, answering an empty string if the object is nil. That's really > dirty. > Would'nt be better if magma indexes just ignore nil objects? Is it a > requirement for magma that every object from a MagmaCollection must be > present in all indexes? > I hope there is something I misunderstood and there is a more elegant > solution. > > Regards > Norberto > > > _______________________________________________ > Magma mailing list > Magma(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma > > _______________________________________________ Magma mailing list Magma(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma

1 0

r41Alpha4
by Chris Muller 13 Jan '08

13 Jan '08

A new alpha release has just been posted to the MagmaTester project of squeaksource. There are several fixes and improvements. Recommended for to use in your development environments.

1 0

Nil in an index
by Norberto Manzanos 13 Jan '08

13 Jan '08

Hi! Is it a good idea avoid nil in magma indexes? This question rised when I tried MaDateIndex. Until this moment, I used String or Integer indexes having care to answer allways a String (an empty string if the object is nil) and an Integer (a zero if nil). But with dates there is a conceptual problem: there is not a null date. In some applications, business stuff, for example, you can think in an ovbiously unused date (01-01-1500, for example) that acts as a null date. It's a little dirty, but it would work. But in other applications every possible date has a meaning. And if the object could be inexistent in some cases, you have no choice: it's nil. That's my case, and I'm forced to use a StringIndex, converting the dates to Strings, answering an empty string if the object is nil. That's really dirty. Would'nt be better if magma indexes just ignore nil objects? Is it a requirement for magma that every object from a MagmaCollection must be present in all indexes? I hope there is something I misunderstood and there is a more elegant solution. Regards Norberto

2 1

Hang while commiting objects with attribute as MagmaCollection+index
by Hilaire Fernandes 10 Jan '08

10 Jan '08

While writing test I met the following problem: I want to add hundred of (learner) object in a users MagmaCollection (it is located in a branch of the DB and it has index too) While looping, the commit becomes slower and slower until Squeak stall at the 90th iteration. I know I can move the commit: in the outer block, it is faster but still hang at the final commit time. The mouse icon is then stuck to the write icon and the Squeak has to be brutally stopped. In the Learner initialization if I remove the addIndex:, the process run at a constant speed and finish. It looks like a problem related to index creation. testAddLearner | user | 100 timesRepeat: [user := IFILearner new. IFIDbSession commit: [IFIModels users add: user "IFIMagmaResource current school addPerson: user"]] self assert: IFIMagmaResource current school learners size = 100 IFILearner>>initialize super initialize. schoolYear := #CE2. learningStates := MagmaCollection new. learningStates "addIndex: (MaCompetencyIndex attribute: #competency);" addIndex: (MaFloatIndex attribute: #acquisitionLevel)

2 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma January 2008