-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CGWire to Avalon launch #28
Comments
It could be the launcher's responsibility to have a requests server to receive calls. |
Finally got around to testing this again, and got something working: There are a lot of stuff todo before it works, but its promising now. The server is running with bottle which will be integrated with Avalon with getavalon/core#524.
Getting the Kitsu selection id and having metadata (cgwire/kitsu#100), we should be able to find the asset in Avalon. After that its matter of passing this asset id to the launcher so users just need to choose their application to open. |
Thought about this some more, and the launcher itself being present in the tray might be a good candidate to listen to a local port. |
Avalon Launcher can be launched multiple times which will have multiple running instances in tray, will that be a problem ? |
Good point. Didn't think of that. What are the use cases that? Is it used anywhere? Thinking they all could change context. |
Hmmm, I didn't concider it as a feature, haha. But I do find artists here, often accidentally launching multiple Launcher instances. Should concider as a bug, since you may have multiple listeners if implementing this into Launcher ? |
Yeah, certainly a case that needs testing against. I would imagine that all the launcher will pop up in the right context, so either the user realises or doesn't care :) |
Goal
Minimize the amount of navigation when using CGWire and Avalon.
Motivation
Currently you might be spending your time in CGWire when commenting and updating statuses on tasks, but when you want to launch the same task in Avalon, you have to navigate from the project level and find it.
Implementation
CGWire currently have custom actions, which we might be able to use to start the Avalon launcher in the correct context.
The text was updated successfully, but these errors were encountered: