🚀 go-pugleaf

Carl-- 

We had a thread going on label conventions earlier, but now--thanks in part to the forum's truly miserable Search feature--I can't find it. Anyway, yes, planning is good.<g> 

One thing that we talked about earlier was using some kind of a field separator in labels--that way, multiple scripts could make use of the label feature.  

Why would we need conventions for label delimiters? If script A expects to find the name of the object in the lable, and script B expects to find an array containing the object's ideal coordinates, and script C expects to find an executable script snippet...you can see that it gets complicated pretty fast. Next, scripts should not erase the label information left by other scripts. 

I've taken to structuring labels something like an AppleScript record: 

<property>:<value>| <property>:<value>|, etc.  

Then, when I'm testing for a given value, I use containment comparison operators rather than equality operators. This way, I can store multiple property/value pairs in a label. 

Thanks, 

Ole