We need to add some way of tagging MRL objects to identify which sub-model
they belong to (Task, Presentation, Application, etc).
I think this will be useful in general in the development tools, but I have a
use for it right now. In the HTML documentation generator I would like to
distinguish between different sub-models to be able to generate indices for
the objects organized in different ways: one of them which is by category.
So, there would be something like a list of categories, and if the user
clicks, they get all the objects in that category (ie, al task related
objects).
I am not quite sure what the best way to do this is.
One possibility is to extend the _Def classes with another field which is the
model category. The model category would be a symbol that identifies the
category. The question still remains whether the category field should hold a
single symbol, or multiple, for objects that belong to multiple categories.
We can also have a "common" category for elements such as Expressions that can
belong in multiple sub-models.
To do this we need to figure out a way to indicate in the MRL files to which
category a set of definitions belong. I suggest imposing the restriction that
all elements in one MRL file must belong to the same category, so we can have
a line at the beginning of the file that indicates the category. For example
in_model Task;
Object Task .....
Comments?
I would like to come to a closure on this soon, so we can proceed quickly with
the generation of all the documentation, which we need to deliver to NRaD asap.
Pedro Szekely
USC/ISI, 4676 Admiralty Way, Marina del Rey, CA 90292
Phone: 310/822-1511, Fax: 310/823-6714
URL: http://www.isi.edu/isd/szekely.html