Skip to content
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

0.7.0 #204

Merged
merged 28 commits into from Jun 24, 2016
Merged

0.7.0 #204

merged 28 commits into from Jun 24, 2016

Conversation

mottosso
Copy link
Member

@mottosso mottosso commented Jun 19, 2016

Stripped 2 out of 3 dependencies, only pyblish-base is required now!

Also added installation instructions to README. More to come.

Before

  1. Install pyblish-rpc
  2. Install pyblish-integration
  3. Install pyblish-maya, or something like it.
  4. Install pyblish-qml
  5. Launch Pyblish QML in terminal
  6. Start server within your host
  7. Emit a show signal to Pyblish QML
  8. Done.

After

  1. Install pyblish-qml
  2. Launch Pyblish QML in terminal
  3. pyblish_qml.show()

@tokejepsen
Copy link
Member

Guessing this will the standalone as well?

@mottosso
Copy link
Member Author

Guessing this will the standalone as well?

You mean replace pyblish-standalone? The roles haven't changed, just that you no longer will need to install RPC or Integration separately. Standalone should still be relevant in the same way.

@tokejepsen
Copy link
Member

You mean replace pyblish-standalone?

Yeah, since we are getting rid on pyblish-maya etc., was thinking that pyblish-standalone would be merged as well?

@mottosso
Copy link
Member Author

pyblish-maya remains, it still contains plug-ins and helper functionality related to Maya. It's just the QML part being stripped, to make room for alternative GUIs, such as Lite.

@tokejepsen
Copy link
Member

Ahh, I see. Got confused from your Before/After :)

@mottosso
Copy link
Member Author

Cool. :) Does it make sense though? I'm looking for ways to make QML simpler, while at the same time open up for other GUIs. At the moment, pyblish-maya and other integrations are quite heavily dependent on QML.

@tokejepsen
Copy link
Member

It does make sense, and I think the simplicity is going to serve new people very well.

At the moment, pyblish-maya and other integrations are quite heavily dependent on QML.

Guessing ideally you would just have some plugins for each integration?

@mottosso
Copy link
Member Author

Plug-ins that are common across integrations, and specific things like the menu item, yes. Anything specific to a particular host, basically.

The next challenge is how to get the menu item to come from something like pyblish-maya, but trigger pyblish-qml, pyblish-lite or any other GUI. Still thinking about that..

@BigRoy
Copy link
Member

BigRoy commented Jun 19, 2016

How about something similar to register_host () but for GUI. register_gui ("QML", gui_method)
Possibly passing it the method to instantiate it directly or passing it the command to run. "import pyblish_qml; pyblish_qml.show ()"
The latest registered gui could be the active one. Similarly one can list the available gui and enable another one again.

@mottosso
Copy link
Member Author

Thanks Roy, I'll give that a try.

@mottosso
Copy link
Member Author

+6,400 −13,010

Nothing better than reducing the size of a project. <3

@mottosso
Copy link
Member Author

mottosso commented Jun 19, 2016

Ok, guys. It would be great if you could give these changes a try.

Have a look at the README for how it's meant to be used.

@mottosso
Copy link
Member Author

@BigRoy done. Let me know what you think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants