Replace setattr with codegen for better intellisense

[mkundu1]

In vscode:

Similar auto-completion list also appears in spyder. But it is very slow, I was not able to capture a screenshot.

[dnwillia-work]

I'm a little bit confused as to why you would call them main_menu when the user documentation is referring to them as commands:

https://ansyshelp.ansys.com/account/secured?returnurl=/Views/Secured/corp/v221/en/flu_tcl/flu_tcl.html

Would commands be better then?

[mkundu1]

I'm following the terminology in scheme source code. The helpstrings within the source code are also calling file, define etc. as menus. These source code helpstrings are exposed in PyFluent. The documentation helpstrings are generated outside of Fluent source.

[dnwillia-work]

OK, I see. My concern then would be that this is not the customer visible terminology. If I click on the link you provided it's an internal Ansys link but the link I shared is the user documentation that all customers can see. I don't mind which direction this goes but both need to be consistent I think.

I understand the help strings come from Fluent currently, I'll pass you the content that Stephen provided. We should look at a way to get this published here as well.

[mkundu1]

Thanks, will accommodate the user doc help-content in the current PR.

[mkundu1]

I have added the helpstrings from the XML file.

[mkundu1]

The doc build is currently failing with the following error message:

make: *** [Makefile:19: html] Error 1
make: Leaving directory '/home/runner/work/pyfluent/pyfluent/doc'
Error: Process completed with exit code 2.

@smf2001 @dnwillia-work Any idea whether the doc side changes are incompatible with the current python code changes? The tui.py files now contain a top-level class main_menu (which would be renamed) holding the global functions (like print_license_usage, switch_to_meshing_mode) and the top-level menu classes (like file, define, solve).

[mkundu1]

Most of the missing menus here are dynamically generated menus which cannot be captured in static queries during codegen (relevant bug #90).

[mkundu1]

Due to item 1 of #38, original Fluent TUI paths aren't available across the API. The Fluent strings are converted before sending through the API. The above code will do similar conversion for the XML strings (which are exact Fluent strings), but few cases are missed (e.g. Fluent string 1D_coupling is converted to one_D_coupling during the API call, which is not converted in the above code). In a separate PR, I'll enhance the above code to match with the Fluent side conversion logic (we need to bring that logic in client side to fix #38).