search

paulwinex / pw_MultiScriptEditor

Python Editor for CG Applications
138 stars 40 forks source link

Qt.py support and RV integration #3

Open nebukadhezer opened 6 years ago

nebukadhezer commented 6 years ago

Hello, first thanks for this editor. Have been using it for some time now. I changed the code to be compatible with Qt.py. I also went for the explicit declaration of methods from modules. All imports from submodules are now relative and the main path does not need to be appended to sys.path to make the editor work. I needed to remove the if main if clause at the end cause it is not working with relative imports... It is a lot of changes but I hope you like them. If you dont want the code to be merged I am fine with keeping the fork and keeping it uptodate.. I also would like to add a setup.py and put the code in pypi, so it is easier to install and jedi could be marked as a dependency.

All the best Johannes

nebukadhezer commented 6 years ago

Here is a screengrab of the RV integration: rvscripteditor

paulwinex commented 6 years ago

Very nice! But i think my editor is first prototype with lot of mistakes. I planing to develop version 3 with totally new engine and structure. Also with Qt.py, py2 and py3 support. But your RV integration will be good stuff for me in future. Also i want to create integration for Blender, Fusion and other common softwares.

Im not sure about pypip. If you use pip modules will be installed to default system python, but we need to install to some pipeline repository. Ofc you can install pip on houdini or maya python but most of users can't) Alternative will be realised in my current project FenxPipeline, where exits special module manager and you can install MSE in one clisk for all softwares. Also i hope i will have time to update my VEX Editor with same principels. So, keep and update your branch, i will add link to readme and wait for the new version. Pls, update Readme in your branch, add information about RV supporting.

nebukadhezer commented 6 years ago

hi Paul, ok shell we close the PR then ? Or is this a good way to keep you in the loop ?