Is your Qt-related suggested approach still valid?
Have new features been developed in ADAMS 2018?
Or where are we now wrt. Python implementation?
Is there a set of propotype Python code (Alpha, beta, whatever) stuff we can nibble at?
At this point, my main hurdle is how to get data or input from ADAMS to Python in a structured approach.
What I do now is mayor clunky:
get the user input in a AView dialog,
Store them in global vars in AView and
Spoon them out in a Python module.
But being able to directly build Python scripts with automated AView dialog box generation (in Qt?) would be an enormous step to get me going further, and motivate me to invest more in Python in ADAMS !!!!!,
Is your Qt-related suggested approach still valid?
Have new features been developed in ADAMS 2018?
Or where are we now wrt. Python implementation?
Is there a set of propotype Python code (Alpha, beta, whatever) stuff we can nibble at?
At this point, my main hurdle is how to get data or input from ADAMS to Python in a structured approach.
What I do now is mayor clunky:
get the user input in a AView dialog,
Store them in global vars in AView and
Spoon them out in a Python module.
But being able to directly build Python scripts with automated AView dialog box generation (in Qt?) would be an enormous step to get me going further, and motivate me to invest more in Python in ADAMS !!!!!,