You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
b779f358d0
* moving files in refactor/re-org Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * dev env refactor/re-org Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * moving/re-org so we can deprate the SDK nomiclature Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * moving/re-org so we can deprate the SDK nomiclature Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * Refactoring env so I can replace SDK with Tools folder Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * re-org and prune, from SKD to Tools Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * Removing old .bat files from SDK Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * updated how to retreive PYTHONHOME Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * Can't use/set PYTHONHOME with DCC Tools Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * small refactor Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * repaired a missed typo (causes error) Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * Added missing EntityId.h include to FocusModeInterface.h Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * refactor additional LY to O3DE tags Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * Some design scaffold file stubs Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * stubbing in scaffold file pattern Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * Removal of corrupted prefabs Signed-off-by: Benjamin Black <benblac@amazon.com> * refactored config_utils to maintain py2.7 support for maya 2020 Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * refactored config_utils to maintain py2.7 support for maya 2020 Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * pruning and cleanup Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * .env is for local dev overrides Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * .env is for local dev overrides Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * clean up init and logging patterns Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * Core refactoring, config.py functional standalone Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * cleaned up some bad logging, fixed up boostrap Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * fixed validation errors Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * fix logging issue, tiddy up Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * tiddy up maya for .bat bootstraping and launch Signed-off-by: Jonny Gallowy <gallowj@amazon.com> * name stub, fix validation Signed-off-by: Jonny Gallowy <gallowj@amazon.com> Co-authored-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> Co-authored-by: Benjamin Black <benblac@amazon.com> |
4 years ago | |
|---|---|---|
| .. | ||
| .p4ignore | 5 years ago | |
| __init__.py | 5 years ago | |
| hot_keys.py | 4 years ago | |
| readme.txt | 5 years ago | |
| test.py | 4 years ago | |
readme.txt
This particular sub-package is devoted to WingIDE It is mainly wingide specific extensions Some notes ... There are a couple of projects set up for Lumberyard python development with WingIDE The FIRST is the DCCsi: dev\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\Solutions\.wing\DCCsi_7x.wpr This provides devs a project to directly work on the DCCsi itself You can launch wing and directly load this project via the following .bat file: dev\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\Launchers\Windows\Launch_WingIDE-7-1.bat Note: the data-driven env hooks for the DCCsi are in the Env.bat: dev\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\Launchers\Windows\Env.bat ^ when you launch wing via the .bat file it bootstraps that env first Additionally, that same env is being transitioned to a python implementation using dynaconf (WIP): dev\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\.env dev\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\settings.json dev\Gems\AtomLyIntegration\TechnicalArt\DccScriptingInterface\config.py ^ this last file is the root dynaconf config for the DCCsi This will also allow us to have per-tool, per-project, per-dcc app env extensions and settings in a more nested way The SECOND is the AtomTechArt Lumberyard project: dev\AtomTechArt dev\AtomTechArt\DCCsi\envs\AtomTechArt\AtomTechArt.wpr Note: this is set up as a venv based on the lumberyard python intstall and thus provides a sandbox silo to develop outside of the lumberyard python, and outside of the DCCsi This .bat will launch wing and directly load this project: dev\AtomTechArt\DCCsi\Launch_AtomTechArt_WingIDE-7-1.bat WingIDE auto-complete with Lumberyard: Lumberyard when built will generate .pyi files for source analysis, inspection and auto-complete On a per-project basis they are generated in the cache like: dev\Cache\AtomTechArt\pc\user\python_symbols\azlmbr Note: to get this to work unfortunatley each user must configure the wingide prefs to include this path (there is no shared project / data-driven way that I know of to set this up otherwise) Note: lumberyard is not currently generating __init__.pyi files in that package structure: SPEC-3315 The workaround is to create them yourself (they can be empty) and needs to be in the root of each package folder, like this: dev\Cache\AtomTechArt\pc\user\python_symbols\azlmbr\__init__.pyi dev\Cache\AtomTechArt\pc\user\python_symbols\azlmbr\materialeditor\__init__.pyi ETC... Then to enable do the following in WingIDE 1. (Dialog) WingIDE > Edit > Peferences 2. (Section) Category > Source Analysis > Advanced 3. (Add Path) In the area labeled "Interface File Path", insert a new path and point it to your cache: Example (mine): g:\depot\JG_PC1_spectrAtom\dev\Cache\AtomTechArt\pc\user\python_symbols You might need to reboot wing. Then you should have auto-complete for the lumberyard api > import azlmbr Note: the entirety of azlmbr api does not generate .pyi files currently, all of the "Behaviour Context" based classes do non-BC modules such as azlmbr.paths currently do not SPEC-3316