I’ve updated the Eclipse Maya Editor plugin. You can find it at CreativeCrash.com
The icons are updated. The default documentation paths now use Maya 2015 and the update PySide and Qt versions.
I’ve added a new feature. You can now import/reload a script using its file location. The original “Send Selection” and “Send All” commands save the editor to temp files. So if you have imports that rely on relative paths in the script, these would never work properly. With the new Import To Maya command, the script location is added to Maya’s sys.path and imported/reloaded from the actual file location.
I’m looking into a couple of other new features. Currently, PyDev syntax highlighting does not offer the option to highlight custom keywords (ie. the Maya Python commands or the Maya API keywords). PyDev would have to be modified internally to provide this functionality.
Also, there’s been some interesting discussions about “semantic highlighting”. This is giving each variable it’s own unique colour so that it is very easy to follow where it is used through the script. In order to not make the editor look like a horrendous mess of colours, choices are constrained to a user definable range of hue and saturation.
Any thoughts as to how helpful these options would be?
Custom syntax highlighting would be handy, and sematic highlighting does sound very appealing. A simple little colour palette with a few predefined colours sounds handy to highlight particular variables. Although would depend on if there’s any performance hit?
And thanks, been waiting for the relative import!
For those that have already downloaded the latest version, I made a couple of slight enhancements yesterday. I added an automatic save of the current editor when using the new import script to Maya function. Also, if you want to remap the hot keys, I’ve exposed the commands in the preferences/General/Keys area. Use a filter of ‘*Maya’ to see the commands to remap.
Thanks for the feedback. But it’s interesting that both of the replies mention you were waiting for this relative import feature. Some one at work came by just a few days ago and asked if it was possible and I figured, sure, it’s probably easy, so I added it. So if you guys have been waiting for it, how come you haven’t asked for it? What else are you “waiting for”?
Ive been thinking about that feature, but always seemed to just replace the relative imports with absolutes or testing the modules from an outside script. And then forgetting to feedback on it:) So saying waiting for it, should probably be thinking about it instead.
Same as Toke. I suppose ‘waiting for’ was more of a ‘something I wanted but worked around’. As I’d just gotten used to working around it, never though to request it.
I probably have a list of things somewhere, will dig up and rationalise
I finally added this plugin to be available using the Eclipse Marketplace. You no longer have to install manually. Search for “Maya” when in the Marketplace to find the plugin.
Just testing out the update, and using the Eclipse Marketplace is super easy. Nice going. I’m having problem with the relative import, it still says; "Attempted relative import in non-package # "
Sorry I dont quite get what to do. If I test the script in IDLE, I’ll need to import the package for it to work. Where I thought that the relative feature in the plugin would allow code like; “from .resources import dialog” to be executed without having to go outside the package, and import the package?
Hi cgjedi thanks for update and thanks for the cool feature
I have problem here, auto completion is not going well:
exam:
“import maya.open” cant be done “import maya.OpenMaya”
when it just “import maya.” then auto completion show view oiption like “import maya._OpenMaya”
and please explain detail about this:
“Import the script being edited (add the script location to sys.path and import/reload it)”
this can’t work for me. How to add the script location to sys.path, that You mean append ??
please give some example, thanks
