Restructure the repository and handle addon files

[marcinn]

Solves #59

[JezSonic]

I still don't really like the idea of having dependencies in the root folder and copying them over instead of just having them in a demo/.

There's a high chance to overwrite files by mistake and having copy of that just makes kinda no sense to me.

I haven't look through everything yet and checked it all, will get to that in a few hours

[marcinn]

Demo is just a project which can disappear from this repo. All sources must be outside the project, because this is an addon. Just imagine that there is no demo folder.

The same issue will be with the Game and MSED repositories, because libmaszyna will not be stored under project's addons dir.

There's a high chance to overwrite files by mistake and having copy of that just makes kinda no sense to me.

Yes. This is the case for all dependencies, which will be under your development, especially when you switch to the target project (Game or Editor). To solve this case you can use symlinks (the easiest and straightforward way). You can use them on Windows by enabling developer mode.
You can also create tools you like, i.e. a script which will copy back files from demo/addons/libmaszyna (or other project you will work with) to the addon sources dir, maybe automatically based on inotify.
Or maybe you will develop with the source files, and there will be a script based on inotify, which will automatically run scons after detecting changes.

It is up to you. Personally I would stick with symlinks, but they will not be committed to the repository.

[marcinn]

Switching to draft.

For easier development will be possible to use symlink

It works for existing files, however Scons is DELETING your new files during next build. This is unacceptable. After a texting on the Scons Discord, they asked me to report a bug. Looks like we're stuck for a while. I'll try to workaround this by manually checking for the existence of the symlink.

[marcinn]

applied workaround

[JezSonic]

Demo is just a project which can disappear from this repo. All sources must be outside the project, because this is an addon. Just imagine that there is no demo folder.

The same issue will be with the Game and MSED repositories, because libmaszyna will not be stored under project's addons dir.

There's a high chance to overwrite files by mistake and having copy of that just makes kinda no sense to me.

Yes. This is the case for all dependencies, which will be under your development, especially when you switch to the target project (Game or Editor). To solve this case you can use symlinks (the easiest and straightforward way). You can use them on Windows by enabling developer mode. You can also create tools you like, i.e. a script which will copy back files from demo/addons/libmaszyna (or other project you will work with) to the addon sources dir, maybe automatically based on inotify. Or maybe you will develop with the source files, and there will be a script based on inotify, which will automatically run scons after detecting changes.

It is up to you. Personally I would stick with symlinks, but they will not be committed to the repository.

K, thx for clarification

[JezSonic]

Seems good to me

[carmel4a]

As I've told on discord. I'm not sure if .gitigore and few commits from main merged successfully, but it seems to be ok.