…mmunication and completes functions in photoshop js reference

Signed-off-by: TsXor <[email protected]>

I may have to correct something about Action Manager and its classes: ActionDescriptor, ActionList, ActionReference. Action Manager is NOT something to describe your action palette. Action Manager actually enables low-level access into photoshop, and all things in this repo can actually be rewritten in Action Manager. You can consider an ActionDescriptor as dict, ActionList as array, ActionReference as filters for searching. So we should NOT set an INSTANCE of ActionDescriptor as an attribute of a Session and instead we should set the ActionDescriptor CLASS (the same for ActionList, ActionReference).

Signed-off-by: TsXor <[email protected]>

desc_value_types and ref_form_types defines classes which describes AM things and utils contains a shortcut for id conversion.

Nothing breaking. All AM functions are still available.

My submodule uses relative importing because absolute importing causes bigger possibility in path typos.

Signed-off-by: TsXor <[email protected]>

For example, I advice to do 'import photoshop.api.action_manager as am'. Then jprint(prefix='am') should be helpful.

Signed-off-by: TsXor <[email protected]>

… use of my submodule

In fact, why use those ****s born by ScriptListener Plug-in which is totally unreadable?

Signed-off-by: TsXor <[email protected]>

Signed-off-by: TsXor <[email protected]>

change patching to (try eval + except), and now run black -l 80 to avoid hound warning

There will be lots of violations in hound's eye which I cannot find out locally because hound's linter is not up to date. I will have to do some shattered commits, and for these commits, I will name them hop (hound oriented programming).

Signed-off-by: TsXor <[email protected]>

… import picture example

Signed-off-by: TsXor <[email protected]>

…ded instead of do it on import to pass import test. 2. Warns user when typeID collision happens. (And id2str will try to avoid giving user string that will cause collision.)

typeID collision happens when a stringID and a charID share the same name. For example, charID 'From' -> stringID 'from' and charID 'from' -> stringID 'originalAddressAttr', so 'from' is a string that will cause collision. After scanning the cpp header "PITerminology.h" and "PIStringTerminology.h", I found 3 such strings and hardcoded them into utils.py. str2id() will not automatically correct user when user gives a collision string (because no one knows what he want it to be a stringID or an charID!), but will regard that string as stringID and throw a warning. Users can follow that warning's guide to fix error and suppress that warning.

Signed-off-by: TsXor <[email protected]>

Signed-off-by: TsXor <[email protected]>

Signed-off-by: longhao <[email protected]>

Signed-off-by: TsXor <[email protected]>

…le_integration

Signed-off-by: 23Xor <[email protected]>