3 Jan
2012
3 Jan
'12
6:17 p.m.
El 03/01/2012, a las 2:11p.m., Lukas Renggli escribió:
he... no, but I will start think on that now :)
k, I will look... it shouldn't, but you never know :)
ok, I will, after I review some small issues.
Esteban
Hi Esteban,
Great news!
well... right now I just marked #description as deprecated, not that I removed it
In fact... I wasn't talk about this because I wanted to test it in a real-life
environment before.
I made some minor changes to magritte2, to
accomplish a
few things you pointed as desirable:
Please send such mails to the list.
1) replace #description with #magritteDescription
Right, but that will break a lot of code. Especially with Pier, that
does a lot of fancy reflection on its structure and that is very hard
to fix (at least the last time I tried). What about doing that in a
second step? 2) Create a pragma-based builder, using
<magritteDescription> and <magritteContainer> pragmas
Great.
- Did you consider moving the descriptions to the instance-side, so
that we have the descriptions together with the accessors and that we
can have instance- and class-side descriptions?
- Did you think about descriptions that get dynamically injected from the model?
- Did you consider getting rid of the description cache and replacing
it with a description selector cache? So that we can get the
descriptions quickly but they are built dynamically in the context of
the object?
- Did you think about the extensibility properties, i.e. with method
extensions: #descriptionFoo, #descriptionFooBarExt:,
#descriptionFooZorkExt:, ... 3) a small fix to make Magritte-Morphic work on
Pharo 1.4 (a change on multiselect lists)
Just commit it, if it doesn't break Pharo 1.3. this is still not well tested (although all tests
are green), but Nick wanted to start using it, so I wonder if there should be a new
repository (magritte3, maybe, or "magritte2.1", whatever) to start working?
what do you think, should I create it (in your repository)?
Feel free to commit it to the current repository, if it doesn't break
any builds. Otherwise we might want to submit it somewhere else before
merging into the head.