2018/05/22
Major update:
- No more pip install, useless for this project. Also too exposed for non full open source.
- There is now an install script that will generate the flame_trigger.py scripts meant to expose just what we want to Flame (to dl_python_path)
The idea is that the flame tools package might contain files that we don't want Flame to even bother looking at, like yaml or txt files. It comes from the fact that Flame seems to look at every single file under it's DL_PYTHON_PATH (recursively). Then modules like yaml might return error messages (even if things work anyway) ... and we don't want that.
So instead of Flame looking at the whole package, we only expose the trigger scrips, which then import appropriate top level hooks like CustomUIactions (CUA), export hooks. ...
It doesn't matter where we put the original flamepy_sg package, as long as we run flamepy_install.py giving the right path for flame hooks.
Running flamepy_install.py from a terminal/shell (giving the DL_PYTHON_PATH filepath as an argument) will create the flamepy_triggers folder and all needed flame_trigger_... scripts.
How to install:
- Do NOT put the package where Flame hooks are, that would again expose files we don't want to expose. Save it anywhere else and run the install script.
- You can either use the location set as a pre-existing entry in the ~/.bash_profile, or temporary source a file containing your desired $PATH.
- Once you've set that match, run flamepy_install.py in the terminal, giving your path to the 'dl_python_path' target folder as an argument: python /path/to/flamepy_install.py /path/to/dl_python_path_folder
That's it, you should be able to start Flame from a terminal within this env.
Todo:
-
Somehow extract the DL_PYTHON_PATH from sys and use that as an argument to run the install script.
-
Modify the installer as needed.
2018/05/20
Can now be installed using pip: pip install flamepy_sg
force version update with: pip install --upgrade --force-reinstall flamepy_sg
Once the package is intalled, source the appropriate bash_profile_... file (found in /for_install) and start Flame from the same terminal. But first, once the file located, modify the path to be sourced according to your system and where you installed the package. The target folder/module is 'flame_start' which should be right next to the 'flamepy_sg' folder/module.
2018/05/18
How to install and add to the env.
The 'flame_start' folder should be copied or moved next to the 'flamepy_sg' module. Then source the OS appropriate env lines from the '...bash_profile' file. You'll need to edit this file for your specific path. The filepath to add is to the 'flame_start', and the 'flamepy_sg' folder must be next to it, inside the same folder.
updates:
-
Removed the 'lib' folder and put its content into the 'script' folder
-
Started to look at how to make this an installable module. (added the begining of a setup.py ...)
2018/05/15
About this new Flame python rep: The FlamePy_sg folder can be placed anywhere on your computer (i.e. your working folder or /opt/... or /var/temp/ ...) You need the DL_PYTHON_PATH to be added to your environment, by either:
-
Sourcing the text file named Paths_to_source.txt (in /lib) in the terminal/shell from which you will start Flame.
-
Add the path to your .bash_profile (on mac) and then source it in the terminal from which you will start Flame.
2018/05/14
Stripped down from previous version (Flame python dev). This is also an attempt to work in a more common/pythonic way, mostly regarding the structure (folders, modules, packages...) and how things are imported/linked ... Work in progress, first step.