okay, yep I see your logic, and it is probably better than mine, but I have historic features like no suffix on my plan files, because I started the project without them.
I think I can reasonably easily implement what you are doing, and will try to quickly, as it is exemplar. Maps: I did not realise you could create outside of a survey, as I thought this was how it inherited its name, map at survey and have had no reason to try. I tend just to have a map in the main th file to just just that part of the data set, this then allows people to check it works. (yes I know that if you do not put a map in everything is exported) Then people who are new to therion can run just the bit that they have produced, and all they need to do is add an include, the map and equates to the parent file and they have added there bit. I am not sure where you would write a map in an automatic system if it was not there? I do not want to use this program to edit files that already exist automatically that leads to madness. Anyway if you have a place that you consistently put maps and it is a new file every time I will try to add it, if you send me an example. Documentation: so that explanation worked I will do an update or maybe Graham will, I noticed that the documentation predates the ability to change the surveyors and explorers. Andrew On 29/07/13 08:48, Bruce wrote: > > > The approach I am trying to enforce is that each object inherits the > name of itâs parent, and any suffixes that might have been appended to > the parent (or grandparent). Also that each object name describes quite > explicitly and unambiguously what it contains (but not overly verbose). > Pretty close to what Topparser encourages already. > > >
