Hi Martin,

This should work. This is partly what I do already but within one one single layout file.

However, my concern with this solution is that I should reorganize user-symbols definitions into one single (or just a few) layout definitions which need to be copied at the last level of layouts. I have to think more about such an organization. It does not seem very natural a-priori but it might be more efficient than redefining to null the user-symbols.

Xavier

Le 13/09/2013 10:22, Martin Sluka a écrit :

My idea was to divide your layout into small parts, each one with one metapost definition of user symbol and use the command in thconfig file:

input - works like input command in data files - includes other files.

copy <source layout id> . set properties here that are not modied based on the given source layout. - in your layout.

file: layout_foo:

layout u_foo

code metapost

definition of u:foo

endcode

endlayout

thconfig file:

input layout_foo

layout my_layout

#copy u_foo #this is the line which could be commented

endlayout

export foo_off

it was not tested prior post!

m.

Sep 13, 2013 v 8:27 AM, Xavier Pennec <Xavier.Pennec@inria.fr>:

Well, I gathered my layout definitions in a single file to avoid repeating and duplicating everything in my 50 thconfig files. This allows me to modify only one layout file to modify consistently all the layouts of all caves. I think heritage + redefinition is a more structured
_______________________________________________
Therion mailing list
Therion@speleo.sk
http://mailman.speleo.sk/mailman/listinfo/therion

-- 
> -------------------------
> Xavier Pennec
> Senior Research Scientist / Directeur de recherche
> Asclepios project-team, INRIA Sophia-Antipolis
> 2004 Route des Lucioles, BP93
> F-06902 Sophia-Antipolis Cedex, France
> +33 4 92 38 76 64
> +33 6 78 35 16 90
> http://www-sop.inria.fr/asclepios/
> -------------------------------