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

nuke #10

Merged
merged 11 commits into from
Sep 4, 2017
Merged

nuke #10

merged 11 commits into from
Sep 4, 2017

Conversation

loonghao
Copy link
Contributor

support nuke

loonghao added 6 commits June 26, 2017 00:57
- launchfornuke.py support in nuke
- README.md add create nuke menu description
…d if it does not exist, the menu will be created
…to nuke

# fix Conflicts:
#	python/scriptsmenu/action.py
#	python/scriptsmenu/launchformaya.py
#	python/scriptsmenu/scriptsmenu.py
@BigRoy BigRoy requested a review from aardschok June 26, 2017 09:46
README.md Outdated
@@ -33,10 +33,12 @@ menu = ScriptsMenu(title="Scripts",
menu.add_script(parent=menu,
title="Script A",
command="print('A')",
sourcetype='',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well spotted, this should've been fixed in the README. Though I don't believe an empty string is the fix we're looking for. This should be sourcetype="python"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. I get it, Thank you.

@@ -112,7 +112,7 @@ def run_command(self):
callback(self)
return

exec(self.process_command())
exec (self.process_command())
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any particular reason you strayed away from PEP08 and added the space?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, later I can check my settings, maybe is fix conflicts lost something

@BigRoy
Copy link
Member

BigRoy commented Jun 26, 2017

@loonghao Great! :) I made two line comments regarding changes, aside from that this is looking great.

Thanks for this!


Will you be using this in production?

@loonghao
Copy link
Contributor Author

@BigRoy Not yet, just for myself.

@BigRoy
Copy link
Member

BigRoy commented Jun 26, 2017

Not yet, just for myself.

Feel free to create any issues if you're looking for specific features.

@loonghao
Copy link
Contributor Author

Ok, cool

@loonghao
Copy link
Contributor Author

@BigRoy can you help me, merger this PR?

@BigRoy
Copy link
Member

BigRoy commented Jun 27, 2017

Sure can, will have a look first thing tomorrow.

@BigRoy
Copy link
Member

BigRoy commented Jul 3, 2017

Some minor notes still:

  • With the readme fix, can you also patch the top example there by adding "python" as the argument for sourcetype.
  • Could you version up to 1.2.0 by increasing the minor version in version.py?

loonghao added 2 commits July 3, 2017 22:54
update version.py  version:1.2.0
@loonghao
Copy link
Contributor Author

loonghao commented Jul 3, 2017

@BigRoy already fix

@aardschok aardschok merged commit f82c905 into Colorbleed:master Sep 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants