31 May
2010
31 May
'10
12:36 p.m.
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.
31 May
31 May
1:07 p.m.
New subject: about Rationalizing EntityState and DefaultEntityState (issue 195)
On 31 mai 2010, at 12:36, Cyrille Delaunay wrote:
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
2:16 p.m.
New subject: about Rationalizing EntityState and DefaultEntityState (issue 195)
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 ?
2010/5/31 Simon Denier <Simon.Denier(a)inria.fr>
On 31 mai 2010, at 12:36, Cyrille Delaunay wrote:
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
4:20 p.m.
New subject: about Rationalizing EntityState and DefaultEntityState (issue 195)
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 
7:55 p.m.
New subject: about Rationalizing EntityState and DefaultEntityState (issue 195)
Hi Cyrille,
Thanks for the effort. This cleaning was needed since a long time :).
And, yes, please add a deprecated entityGroups for the moment.
Cheers,
Doru
On 31 May 2010, at 16:20, Simon Denier wrote:
On 31 mai 2010, at 14:16, Cyrille Delaunay wrote:
--
www.tudorgirba.com
"Don't give to get. Just give."
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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev 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
5072
days inactive
5072
days old
4 comments
3 participants
participants (3)
-
Cyrille Delaunay -
Simon Denier -
Tudor Girba