31 May
2010
31 May
'10
4:20 p.m.
On 31 mai 2010, at 14:16, Cyrille Delaunay wrote:
Yes also, and I just see that I didn't do it in a
very safe way ...
I changed MooseEntity >> entityGroups by MooseEntity >> entityCache.
So this change can be the origin of some errors.
should I reimplement MooseEntity >> entityGroups as deprecated ?
yes please
2010/5/31 Simon Denier <Simon.Denier(a)inria.fr>
On 31 mai 2010, at 12:36, Cyrille Delaunay wrote:
--
Simon
Hello,
What I did for the moment:
renamed all the methods from EntityState with the convention of a dictionary (propertyAt:
, cacheAt: ,
attributesAt: ). We kept the old ones as deprecated.
I kept all previous methods as 'deprecated'. So normally, If I did that well, if
your code is still using the old entityState API, you should have a 'deprecated'
message re-directing you to the new API.
thanks!
Isn't there some changes in the MooseEntity API also?
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev