Skip to content

Journal #1

Open
Open

Description

@mottosso

Allzpark (a.k.a. LaunchApp2) started as a 4-month commission for the Japanese Studio Anima. Time was divided into roughly these parts.

  1. Week 0-0 Tour of physical building, infrastructure and crew
  2. Week 1-2 Requirements gathering, an evaluation if current system
  3. Week 3-4 Evaluation of off-the-shelf options, e.g. Rez
  4. Week 5-6 Evaluation of studio, system and personnel resources
  5. Week 7-8 Integration and testing of fundamental infrastucture software, Ansible
  6. Week 9-10 Research and development of Rez to fit the criteria and initial prototype
  7. Week 11-12 Conversion of existing package repository
  8. Week 13-14 Implementation of graphical user interface, LaunchApp2
  9. Week 15-16 Refinement of features, including localisation
  10. Week 17-18 Final integration and training of staff

Journal

Allzpark was initially an internal project, never intended to be open sourced. As a result, the first 2 months of development are locked away behind an internal journal for the company (due to disclosure of sensitive information).

Luckily, it was around this time that Allzpark got approved for open source and when I was able to start sharing its development publicly, so that you are able to take part in the design decisions made, the why and how. This way, you're able to accurately determine whether a solution to a new problem takes the original requirements into consideration; something all too often lost in software projects.

Find below the daily journal from this development since then.

Activity

  1. mottosso commented on Jul 10, 2019

    @mottosso
    OwnerAuthor

    This time having a look at project cosmetics, and project package metadata.

  2. Repository owner locked and limited conversation to collaborators on Jul 10, 2019
  3. mottosso commented on Jul 12, 2019

    @mottosso
    OwnerAuthor

    Artists and developers can now localise packages visually, alongside the command-line.

  4. mottosso commented on Jul 12, 2019

    @mottosso
    OwnerAuthor

    Had a look at excluding localised and development packages, along with maintaining and restoring default values of parameters, both for package options and settings overall.

  5. mottosso commented on Jul 16, 2019

    @mottosso
    OwnerAuthor

    Had a look at rez env --patch today, to enable arbitrary package additions, or changes to resolved versions, via the GUI. This could also be used to select asset and shot combinations, albeit a bit rudimentary. The entry is currently stored alongside the GUI on open/close, across applications and projects.

  6. mottosso commented on Jul 16, 2019

    @mottosso
    OwnerAuthor

    Today I had a look at theming and user-editable environment variables.

  7. mottosso commented on Jul 17, 2019

    @mottosso
    OwnerAuthor

    Today was general bug-fixing and testing in production, filling in missing bits of documentation and generally increasing the robustness of the system.

  8. mottosso commented on Jul 18, 2019

    @mottosso
    OwnerAuthor

    Finding more edge cases and implementing a few new features, in particular the ability to have a range of versions for a given application, and an accurate preview of the final command used in the shell to reproduce the environment coming out of Allzpark.

  9. mottosso commented on Jul 19, 2019

    @mottosso
    OwnerAuthor

    Today was about visualising "latest" and "beta" status of packages, having a look at graphing a resolve, along with a number of bug fixes.

    Latest Graph
  10. mottosso commented on Jul 22, 2019

    @mottosso
    OwnerAuthor

    Having a look at more intuitive patching, by double-clicking on the version in the Packages tab. Now it translates that action into what you would otherwise have to type manually into the Patch field.

  11. mottosso commented on Jul 23, 2019

    @mottosso
    OwnerAuthor

    Had a look at error handling and visualisation, using GraphViz.

  12. mottosso commented on Jul 29, 2019

    @mottosso
    OwnerAuthor

    If I had more time, I would have written shorter documentation.

    image

  13. mottosso commented on Jul 30, 2019

    @mottosso
    OwnerAuthor

    General maintenance today, sifting through and making sure everything works, also adding a right-click menu to the profile.

  14. mottosso commented on Jul 31, 2019

    @mottosso
    OwnerAuthor

    Had a request to facilitate use of pythonw on Windows, in order to allow for the Allzpark window to appear without an associated console window, which I then went ahead and implemented!

    pythonw -m allzpark
  15. mottosso commented on Jul 31, 2019

    @mottosso
    OwnerAuthor

    Finishing up at Anima, to be continued in the open source realm!

    image

  16. mottosso commented on Aug 1, 2019

    @mottosso
    OwnerAuthor

    1st August 2019

    Rounded off some documentation and fixed a critical bug related to changing profiles in Allzpark. Expecting to make an announcement of a version 1 beta on Tech-Artists, Python-Inside-Maya and 3DPRO early next week.

  17. mottosso commented on Aug 5, 2019

    @mottosso
    OwnerAuthor

    5th August 2019

    Working with the Avalon community to get Allzpark into the mix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions