hey ana originally i planned on exposing blur's pyqt implementation and simplify it but its proved a lot harder (not impossible). then jo came along and showed us a much easier way to host a pyqt app inside softimage. so pyqtforsoftimage is a lot lighter than blur's implementation. the python key stroke rerouting is very similar, in fact is a near copy of it.
as jo points out, blur's implementation has a lot of wrappers to provide cross platform (3dsmax, softimage, motionbuilder) functionality but that comes at a cost. outside that, they provide very similar functionality because they really just expose pyqt. with all that said, pyqtforsoftimage needs to be tested more and pushed harder. i would love to hear more about how people are using pyqt and provide example code and tutorials. there is one issue someone logged last week... https://github.com/caron/PyQtForSoftimage/issues/2 please test to see if this is an issue for you and if it is provide feedback on the github issues page. s On Mon, May 7, 2012 at 12:38 PM, jo benayoun <jobenay...@gmail.com> wrote: > Hi Ana, > > Qt on windows relies on the win32 api as well as Softimage (MFC). As they > share a common base, both are "hackable". > So, whatever the strategy that is used, it still remains the same ... > hooking a widget into the main softimage app by going thru the win32 api. > The only main difference I would say by using pyQtSoftimage (except the > source codes) is to not have to deal with all the overhead and extra layers > Blur developers put over their modules/wrappers ... > Those packages are both first steps considering more should be done by > spending time on it and make things working better. > I had lot of feedback around me saying studios are using this > implementation ... so it should be solid enough to go with it. > So feel free to make your own additions and come back here to share them > with us ... > > :) > -jo > > > > > > > > 2012/5/7 Ana Gomez <agomezalca...@gmail.com> > >> Hello everybody! >> >> I'm trying PyQtForSoftimage and I'm wondering some questions. >> As far as I know, this plugin is based on Blur tools. So, which are the >> differences between them? Do they have the same features? (of course, from >> the point of view of PyQt) >> >> Thanks in advance and thanks to Steven Caron and Jo Benayoun for sharing >> it. >> >> >> >
