Conversation
- Also add project manager.
- Creator - maintained_selection
- The Dispatch object cannot be stored if it needs to be called from a different thread. - Exposed `get_all_layers` and `read` for publish plugin development.
- "get_all_layers" to "get_layers_in_document" - added "get_layers_layers"
- "maintained_visibility" - "get_layers_in_document" - "get_layers_in_layers" - "com_objects"
- import_as_smart_object - containerise
- imprint - import_smart_object - replace_smart_object
This reverts commit f58268c.
|
Sorry for all the commit spamming, but got the test to pass now. |
What do you mean with
Yeah, currently a container is a single layer, but you could essentially containerise multiple layers with the same metadata.
When using smart objects, the layers from a PSD gets flattened. Unless I'm missing a workflow? |
Ah ! Did not know that, thought they were different things. Thanks !
If that's the case, could
So the
No no, I was just imaging what would I have to do to referencing another PSD file or other kind of subsets that may have multiple images or layers. |
But if publishing or loading that kind of subset in Photoshop would make things too complicated from actual production needs, then I can ignore that. :) |
Sure, that is possible. Though I thought for the sake of simplicity of the function, have a single layer as argument would be better? Can always containerise multiple times.
Yeah, could be any layer or |
After a good thought, I think it's not necessary for Photoshop. Plus, artist can only find stuff from that layer stack UI, so yeah, it's a good idea to keep things as simple as possible. 👍
Nice ! |
|
This PR is waiting on #523 to be merged. |
|
The problem with #523 is still this particular comment. That should need to be tested and made sure that Blender will continue to work. |
|
With 98503a6, this PR is ready to be merged. |
|
The #527 actually has a generic server which we could use for all Adobe products. Lets leave this PR open for now, and I might rework this PR. |
|
@tokejepsen You mentioned potentially reworking this PR. Should we merge this as is and open an issue? Should we close this? I noticed Pype merged something like this. So this is usable? If so, is there any documentation? :) |
|
The Pype team have been using this in production, so there may be a couple of bugs from them. Otherwise, yeah, we could merge this. The Pype team is also working on a second iteration using websocket and native javascript in PS for cross platform compatibility, so the question is whether we wanna wait for that. @mkolar and @iLLiCiTiT can update about the production testing and second iteration. |
|
This PR has been superseded by the Pype, so it better for the code to come from there. |
What's changed?
This is the Photoshop integration which fixes #516
The best introduction to the integration is with the README