lyfflyff / veles Goto Github PK

Hello, I'd like to ask if there's any chance you could publish the source of the native parts of this? The VelesNative repo just seems to be the Godot module example.

Importing and opening the project in Godot 3.5 gives an error right off the bat:
res://src/Classes/Normal/SongLoader.gd:8 - Parse Error: Can't preload resource at path: res://src/Scenes/song/SongSpace.tscn

This can be easily fixed however, by changing the code in SongLoader.gd from:
const songspace_scene : PackedScene = preload("res://src/Scenes/song/SongSpace.tscn")
to:
const songspace_scene : PackedScene = preload("res://src/Scenes/Song/SongSpace.tscn")

This, however only solves one error, I still have around 12 errors all for different files saying:
E 0:00:00.649 _load: Failed loading resource: res://src/Scenes/SubOptions/PlaylistGrid/Creators/NormalPlaylistCreator.tscn. Make sure resources have been imported by opening the project in the editor at least once. <C++ Error> Condition "found" is true. Returned: RES() <C++ Source> core/io/resource_loader.cpp:270 @ _load()

The files do exist on this path but the code refuses to run, any idea why?

I'd be glad if I could get this project up and running as I'd like to try my skills at writing a D-bus implementation in GDnative and this project seems like the place to do it.

So, I'm not quite sure where to start with this, cause this isn't so much of a bug issue and more of just a general inquiry...

I am a developer that has made and worked on several projects in Godot, and I would like to contribute to this project, but some of the contributions I would like to make involve considerable changes to the codebase.

Some of the more minor ones I would like:

• Tweaking the folder system, so that it also scans subfolders of a chosen folder, and then subfolders of those and etc., until it finds music files. This would create a lot less manual work for the users, because they can just choose their base folder and be done with it, and Veles will do the rest.
• Change the ID3 reader to an in-house GDscript script that I made, main benefit being more universal platform support out of the box (my repo for that is here)

Now, some of the more extreme changes:

• I would like to do a major overhaul of the codebase. I noticed when working with Veles for personal forks (more on that in a bit) that the codebase is very spread out, and I would like to simplify it. Of course, this would be a very major change to get used to, but my hope is that it will be a lot simpler for other programmers to follow, so that it is less difficult for more people to contribute to the project in the future.
• Update to Godot 4. I have personally been working on this in my own personal (private, unreleased) fork of Veles, because I work in Godot 4, and I think it could bring benefits in the extra GDscript performance, for low end devices. This would be less of an extreme change compared to the above, however I think it would still be "extreme" because it is moving to an entire different version of Godot.

Thanks for reading. Also, if you happen to have Discord, I would prefer to talk there