I wrote this because I want my data model classes to have one set of
#description's to model their data structure and another set of
#settings to model the view/filter settings that are available for each
class.
I dont know what the best way to achieve this with magritte would be,
but I figured being able to have multiple sets of descriptions for
different unrelated purposes could be very useful.
As an implementation detail, it might be useful if the
MADescriptionBuilder 'Cache' was a class instance var rather than a
classVar.
best regards
Keith
p.s. Lukas, I want to thank you for all of the great help you have
provided, especially in the past few days.
In
http://mc.lukas-renggli.ch/pieraddons
Name: Magritte-CustomBuilder-kph.1
Author: kph
Time: 18 August 2007, 2:53:47 am
UUID: dc2d465c-4d2d-11dc-b626-000a95edb42a
Ancestors:
- Variant of MADescriptionBuilder that is not tied to #description as a
prefix.
usage: (MCCustomDescriptionBuilder prefix: #settings) for: anObject
Notes: Includes a performance enhancement to double speed of description
building. (selectors of Object are ignored)
before:
[ 1000 timesRepeat: [MADescriptionBuilder default build: (ProductData) ]
] timeToRun. 21622
after:
[ 1000 timesRepeat: [(MACustomDescriptionBuilder prefix: #description)
build: (ProductData) ] ] timeToRun. 11075