Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global Asset Library #28142

Closed
user865 opened this issue Apr 17, 2019 · 10 comments
Closed

Global Asset Library #28142

user865 opened this issue Apr 17, 2019 · 10 comments

Comments

@user865
Copy link

user865 commented Apr 17, 2019

Been learning about Godot for about a week, and what seems like somewhat of a glaring issue to me is having to recreate basic assets for every new project. Or having to navigate to other projects, search through, pick out what you need (along with dependencies), and drag into the editor or copy and paste to your current project. Either way it's a hassle.

The first solution that comes to my mind is to have a global asset library you could drop all your materials, shaders, meshlibs, textures, etc into, and make them accessible from any project.

I think it's also important that, if something in the editor appears to be a single object, we have the ability to treat it like a single object everywhere, without having to worry about its parts or dependencies.

@groud groud changed the title Feature: "Global Asset Library" Global Asset Library Apr 18, 2019
@LikeLakers2
Copy link
Contributor

LikeLakers2 commented Apr 18, 2019

I believe you can achieve basically the same result by making your own folder (say, on your desktop), which you copy those sorts of things to. Then when you want to add them to a project, you just copy them to that project. I don't think this isn't a bad idea, mind you, it's just not something I think you'd need the editor to be able to do.

@isaacremnant
Copy link
Contributor

isaacremnant commented Apr 18, 2019

How about just a way to link to folders outside of res:// ? I definitely see an advantage in not propagating copies of the same stuff.

edit (had the wrong folder) : You can use symlinks to link to folders outside of res://. I didn't test with exports, but if it works, then just manually creating a link to your global asset folder should be enough for this feature proposal.

@fire
Copy link
Member

fire commented Apr 18, 2019

Symlinks don't work on windows very well.

Linking folders outside of res.. There was a brief design to rewrite the plugin system to include an entire project as an addon. The addon will include the entire library. This will avoid symlinks. Not sure if the entire design was completed.

@willnationsdev
Copy link
Contributor

willnationsdev commented Apr 18, 2019

A lot of this discussion has been going on in #19486 (that one is a hotpot of several different related discussions, so it's not quite as focused as the discussion going on here). Also relevant is this comment from #19506 (apparently there are plans to make the Asset Library host more individual classes in the future, when the API and plugin tooling is more flexible/powerful).

@KoBeWi
Copy link
Member

KoBeWi commented Apr 18, 2019

@willnationsdev Looks like you referenced wrong issue.

@willnationsdev
Copy link
Contributor

@KoBeWi Fixed, thanks.

@silkentrance
Copy link
Contributor

Some info about git and handling symlinks on windows using a post checkout hook:

https://stackoverflow.com/questions/5917249/git-symlinks-in-windows

@menip
Copy link
Contributor

menip commented Jun 3, 2019

If you mean locally, then a folder does the trick. You can even host/setup a local assetlib.
If you mean being able to use other people assets, how is this different from AssetLib? Sure it's in need of serious TLC, but still.

@paulhocker
Copy link

try this -- its still a WIP but I use it for all my projects

https://gitlab.com/godot-stuff/gs-project-manager/wikis/home

@mhilbrunner
Copy link
Member

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.

The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.

If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!

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

No branches or pull requests