Linking projects

[LeXXik]

The copy/paste feature is a god sent! Thank you all who made it happen :)

With the new feature in place, a new behavior patterns emerged. One such is to develop a common framework or an SDK, that holds scripts with convenience methods and a template scene layout with screens and all. When a new project starts, we copy/paste a framework to the new project, so there is a boilerplate, and as we develop the project, we add to the original boilerplate additional common methods.

When a new project starts, we grab the framework from the latest project, since it has new methods and stuff, remove the pieces not needed and use it in the new project. The cycle goes on.

This creates diffferent versions of potentially the same framework. It would be super nice, if there was an option to link a project. Like you link libraries and projects in Microsoft Visual Studio. This would allow to always point to the latest version of the framework which would be maintained in its own project.

[LeXXik]

This is still a very much wanted feature ;) A single source framework or sdk, shared across multiple projects would be a life saver.

[yaustar]

+1 as another client has mentioned the need for this on larger/multiple projects on a call

[yaustar]

I was thinking about 'symlink' folders where you could create a folder that is a read only symlink to another folder in other projects by asset id. And/Or have it as a manual sync where it would still be read only, but you would have an option to copy all the assets from the other project.

[Maksims]

Technically, assets have a "scope", and there is a clone between scopes feature already, which is used when downloading an asset from a store.

Additional scope could have been introduced, like "org scope", where assets would be shared between org projects.
Also "user scope", where a user could store assets that can be shared between projects.

The only thing to be figured out: how to manage those assets, as it is very like a project, but without hierarchy, but still should allow editing/creating templates.

This would help a lot for the case where studios create templates of projects, or have to update multiple project clones, and process is not an easy right now.

[yohami]

Bump

[leonidaspir]

This is becoming more and more relevant for our company projects and for clients we support.

Being able to reuse assets from one project to the other, without copy/pasting and having multiple copies to maintain around.

Multiple scenes and branches are all good, but eventually the projects become too big to maintain and in some situations too slow to launch. Also the Scripts Loading Order panel becomes quickly non usable. In one case the team had to resort to a custom scripts tagging system to only load and order the required scene scripts instead of all project scripts (script tags like sceneName-02, script sceneName-02).

[yaustar]

Related comment in #654 (comment)

[yaustar]

Another user needing this feature https://forum.playcanvas.com/t/project-organization-question/26068/

[querielo]

I also upvote it. It would be great to have the feature, especially for big projects.