Lorenzo Angeli

Administrators
  • Content Count

    77
  • Joined

  • Last visited

  • Days Won

    5

Reputation Activity

  1. Like
    Lorenzo Angeli got a reaction from cjarv in Py3K early access   
    Please note, the current development status is in Beta stage and is not suitable for production.
    Welcome to the ftrack-python-api tech preview for python 3.x compatibilty.
    Here are some brief instructions on how to start testing the upcoming release of the new API.
    We strongly recommend sandboxing the testing environment using virtualenv.

    Prepare your sandbox
    Create a virtualenv with the Python 3 interpreter:
    $ virtualenv -p `which python3.6` ~/ftrack_python_api_py3k Activate virtualenv:
    $ source ~/ftrack_python_api_py3k/bin/activate Install
    Install from the development branch:
    $ pip install git+https://bitbucket.org/ftrack/ftrack-python-api.git@backlog/ftrack-python-api-compatibility-with-python-3 Test
    Run python from virtualenv and check that everything is in place:
    (ftrack_python_api_py3k) $ python -V (ftrack_python_api_py3k) $ Python 3.6.5
    You can now start the Python interpreter and start using the API as usual.
    >>> from ftrack_api import Session >>> session = Session() >>> projects = session.query('Project').all() >>> print(projects) If you need to use the Python3 and the ftrack module just run Python directly from the virtualenv using:
    $ ~/ftrack_python_api_py3k/bin/python3 -c "import ftrack_api;print(ftrack_api.__version__)"

    Bug reporting
    Please use this thread to report issues and bugs.
    When reporting bugs, please remember to include:
    * Operating system in use.
    * Python version in use (use: python -V).
    * Full stack trace or error.
  2. Like
    Lorenzo Angeli got a reaction from Justin Porter in 2D/3D Asset Library   
    Although not web based, one option I can think of would be :
    1) have a project to act as library,
    2) one action which allows to re migrate the assets to/from a given project .
    (could be a reworked version of this example: https://bitbucket.org/ftrack/ftrack-recipes/pull-requests/4)
    This could be extended to keep reference (as metadata or custom attribute) on where the asset originally comes from (as project when publishing back).
    3) a pyside based browser (so can be used as widget in maya, nuke and any other qt based application) to act as library browser.

    Although requires some work, seems doable.
    L.
  3. Like
    Lorenzo Angeli reacted to Martin Pengelly-Phillips in Component/Version/Asset from path   
    We wrote a convenience method for this in our extension of the ftrack API. Might be something we can contribute via pull request.
  4. Like
    Lorenzo Angeli got a reaction from Fredrik Limsater in ftrack connect version 1.1.0   
    Download ftrack-connect-package 1.1.0
    Windows Linux Osx
    What's new ? 
    With this minor release, we have started a long journey for a complete revamp of connect and connector plugins.
    This release mostly focuses on moving the hard-coded connector plugins to standalone connect plugins, so these can be customized and extended by the users as they see fit.
    This release also includes an improvement for the Nuke Studio integration.
     
    Changes:
    ftrack-connect-nuke-studio 2.1.0  Tokens to compose assets names as well as components. Support for multi-track export. Fix Hiero template parser.
      ftrack-connect-maya 1.2.0 converted to connect plugin
      ftrack-connect-nuke 1.2.0  converted to plugin
      ftrack-connect-3dsmax 0.4.0 converted to plugin
      ftrack-connect-hieroplayer 1.3.0 converted to plugin
      ftrack-connect-foundry 1.2.0 remove ftrack-connect from dependency links Known issue
    None reported atm
  5. Like
    Lorenzo Angeli got a reaction from Milad Entezami in 2D/3D Asset Library   
    Although not web based, one option I can think of would be :
    1) have a project to act as library,
    2) one action which allows to re migrate the assets to/from a given project .
    (could be a reworked version of this example: https://bitbucket.org/ftrack/ftrack-recipes/pull-requests/4)
    This could be extended to keep reference (as metadata or custom attribute) on where the asset originally comes from (as project when publishing back).
    3) a pyside based browser (so can be used as widget in maya, nuke and any other qt based application) to act as library browser.

    Although requires some work, seems doable.
    L.
  6. Like
    Lorenzo Angeli got a reaction from Remus Avram in CentOS 7 Connect No Qt Binding Were Found   
    Hi @hulmanen & @AnthonyM this is a good point.
    I'll make sure is going to be added somewhere sensible in the docs.
    Cheers.
    L.
    p.s
    Cheers @Remus Avram