Does MANullAccessor have to be so so... erm unusable?
If you happen to use it nothing seems to work with it.
i.e. accessor selector doesnt work, one should argue that it shouldnt,
but is it doing a good job of being a null?
Most users of read: dont test canRead: first.
I am thinking of implementing a subclass MADummyAccessor which does
implement read: just so as it can play with the other accessors in
mementos etc.
I just wondered if there was a case for making MANullAccessor more
friendly, i.e. swap its behaviour from pessimistic to optimistic, rather
than expecting all users to test canRead: first, expect those users that
really care to test cantRead:
just an idea
Keith
hi -
How does one make a widget appear only if a certain user is logged in?
How would one for instance make the 'views' box appear only if the
admin user is logged in?
(Is there a place I could have found the answer? I read the docs I
found and browsed the archives, but didn't find anything. I'm working
my way to the relevant place in the code, but a nudge would be
useful.)
thanks,
ts
In magritte MAUnlimited is a subclass of Magnitude, since MAUnlimited is
either a Unlimited Positive, or Unlimited negative and since it overrides
#adaptToNumber: andSend:, is there a reason why it shouldnt be a subclass of
Number rather than a subclass of Magnitude. it might make it easier for me
if i made MAUnlimited subclass of number instead of Magnitude in the
GemStone/s version.
thanks
Isaiah
--
View this message in context: http://www.nabble.com/Magritte-MAUnlimited-tf4606754.html#a13154302
Sent from the SmallWiki mailing list archive at Nabble.com.
Thanks Philippe
yeh i undestand how the meta-descriptions for an object are built.
it makes sense to use the solution you propose, however i dont want to get rid of the cache, i like the idea of keeping a cache of built descriptions for an object and each time new code is deployed the cache has to be manually flushed, by calling #flush on the default instance of MADescriptionBuilder.
Dale is going implement SystemChangeNotifier soon for, so we can always allow MADescriptionBuilder to subcribe to systemEvents later.
Does that sound reasonable ?
PS: looking at the squeak implementation it seems that MADescriptionBuilder flushes its cache of description if any method is changed or modified or added in the entire System, not necessrily an object in the MADescriptionBuilder cache > Date: Wed, 10 Oct 2007 06:48:18 +0200> From: philippe.marschall(a)gmail.com> To: cappadonza(a)hotmail.com> Subject: Re: [GS/SS Beta] [betaG/S] SystemChangeNotifier> CC: beta(a)seaside.gemstone.com> > 2007/10/9, isaiah perumalla <cappadonza(a)hotmail.com>:> >> > in squeak there is a class ystemChangeNotifier, what is the equivalent of> > that in Gemstone/S> > I don't think you necessarily need one. Some background:> To build a metadescription of an object Magritte per default only> looks a the class side. It collects all the selectors the class of the> object contains that begin with 'description' and performs them. This> can take a moment on Squeak so a cache was added that maps classes to> metadescriptions. This cache will have to be invalidated if a class is> changed (a method added or removed).> > A solution for this would be to make a MADescriptionBuilder for use in> production, this one would not be invalidated automatically. You would> have to invalidate it whenever you deploy code. It might be that> building metadescriptions of GemStone in fast enough and you don't> need any cache.> > Cheers> Philippe> > > ________________________________> > Sell your car for just $30 at CarPoint.com.au. It's simple!
_________________________________________________________________
It's simple! Sell your car for just $30 at CarPoint.com.au
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%…
hey guys
In Magritte in MAObjectTest class there is a method #testReferenceStream
which basically ensures every object is serializable and after the object is
deserialized, the original and serialized object are equal but have
different references. (ie serialized object is a copy of the original
object).
In Magritte what and where is object serialization used for ? so i can get a
better understanding on how to test this in GemStone/s
thanks
Isaiah
--
View this message in context: http://www.nabble.com/Magritte-object-serialization--testReferenceStream-tf…
Sent from the SmallWiki mailing list archive at Nabble.com.
Hello,
I have a settings model which initializes from description defaults and
keeps its values as a properties dictionary. If when coding I happen to
change or remove a description, when I edit and save the settings the
stale description still remains in the properties dictionary.
I am looking for a hook with which I can tell the Memento, to clear the
old settings and write the new ones. Is there such a thing?
For example if the model knew it was about to be saved to it could clear
out/reset its values in anticipation.
best regards
Keith
I have attempted to use the MAFileUploadComponent slightly more manually
than usual.
e.g.
getComponent
^ widget childrenCache at: {item. field} ifAbsentPut: [
(field componentClass
memento: (MAStraitMemento model: item description:
field)
description: field
parent: widget).
].
However, the value returned to the callback is the filename string,
rather than the file itself. I feel I am missing something somewhere,
any ideas what it might be?
Keith