Search Unity

  1. Unity 2018.1 has arrived! Read about it here
    Dismiss Notice
  2. Scriptable Render Pipeline improvements, Texture Mipmap Streaming, and more! Check out what we have in store for you in the 2018.2 Beta.
    Dismiss Notice
  3. If you couldn't join the live stream, take a peek at what you missed.
    Dismiss Notice
  4. Improve your Unity skills with a certified instructor in a private, interactive classroom. Learn more.
    Dismiss Notice
  5. ARCore is out of developer preview! Read about it here.
    Dismiss Notice
  6. Magic Leap’s Lumin SDK Technical Preview for Unity lets you get started creating content for Magic Leap One™. Find more information on our blog!
    Dismiss Notice
  7. Want to see the most recent patch releases? Take a peek at the patch release page.
    Dismiss Notice

Feature Request - Different Colours for Local Packages in Project View

Discussion in 'Package Manager' started by equalsequals, Jun 8, 2018.

  1. equalsequals

    equalsequals

    Joined:
    Sep 27, 2010
    Posts:
    56
    Hey there,

    First off, I'm loving the direction of Packages in 2018.2, specifically how they are organized in the Project Window. One thing that came up while giving another Engineer at our studio a run-down of the Packages feature was that it's not easy to tell which Packages are Local and which ones are not.

    A simple change to the Folder colour was their suggestion. In this case, I have pulled SRP from GitHub and installed them as Local Packages:



    Cheers
     
  2. DanielTG

    DanielTG

    Unity Technologies

    Joined:
    Feb 15, 2018
    Posts:
    33
    Hi @equalsequals,

    Thanks for the feedback, it's noted. We're actively brainstorming & working on the UX for packages installed within your project. To clarify, when you say local, are modifying the source package in any way? (we're starting to use the term "embedded" package in that case, where it's no longer linked back to back Unity hosted repository)

    Thanks again,
    Daniel
     
  3. equalsequals

    equalsequals

    Joined:
    Sep 27, 2010
    Posts:
    56
    Hey @DanielTG thanks for responding.

    When I say Local, I mean that I have pulled from your Git repo into a folder outside of my Assets directory and modified the manifest.json to point to the package (as mentioned by izym) We may or may not modify the package, but if we do the changes would be tracked as local Branch of that Git repo, so we can Fetch and Merge things appropriately as needed.

    Cheers
     
  4. equalsequals

    equalsequals

    Joined:
    Sep 27, 2010
    Posts:
    56
    @DanielTG I forgot to mention that we are also beginning to experiment with the new Packages as a means of distributing our internal Framework to our various Projects in the studio. This would be done through version control, and the workflow would be similar to branching from Unity's Git repositories.