Hi,
Also, with regards to heirarchy, you can look at it visually. An reference to an object might have the form:
element1 of element 2 of … of elementn of application appidentifier
where elementn has the form:
elementclass elementidentifier
some elementidentifiers might be numeric index, name, id, range, filter, etc.
On the other hand, if each of the elements above were say folders, then you can apply a property of class folder to each of those elements. eg. if name is a property of an element, then y ou can apply the name property to aeach of those elements:
name of element1 of element2 of … of elementn of application appidentifier
name of element2 of … of elementn of application appidentifier
name of elementn of application appidentifier
All these words may not mean much. You might want to just do AppleScript and then one day reading dictionaries might come like a bolt of lightning and you’ll slap your head and say “I got it!”. One of the main things are inheritance.
With Inheritance, you need to experiment because all properties of the parent might not apply.
The main difference is this. If you look above, the objects have identifiers. On the other hand, properties don’t have identifiers because they apply to all objects of a certain class. For instance, you don’t see such things as:
name 1 of folder “a” of folder “b” of app “Finder”
Properties don’t need the “1”, while if name where a class, then the “1” would be required.
gl,