Multi-level hard coded / binaryformatter serialized path...?

[PascalSoftwares]

I downloaded and looked around package, but only realizing 'Getting started' is full of fixed-pathy autogenerations.
Delight editor plugin finds default paths from config file in specific path (asset root), and the path in config is fixed to specific structure (assets/Config/[subdirectories]), and its fallback paths is hardcoded in constant, and autogeneration tries to access template files from hardcoded fixed paths (assets/Delight/Content/Assets/[cs files], etc etc....

I thought I could modify a little to rearrange asset structure into comparted subdirectory, but it turned out like extremely hard.
It is disappointing If this structure is inevitable.

[patrik-u]

That is a limitation of the framework currently. You can specify the root folder of content (views, models, etc) but the name of the subdirectories are fixed. And there might be issues with hardcoded fixed paths (those should be relative to the Delight folder which is configurable but I haven't haven't tested this).

If you want to specify specific folders for specific content types (views, models, etc) then the framework need to be extended, with new configuration options to specify which directories to parse specific content from. If you want to take a crack at this I can help answer questions you have, I'm around at the discord chat as well for feedback.

Otherwise this is a feature I'll put in my TODO.

[amelkor]

It would be really nice to get Delight working under Plugins folder, that's where all 3rd party stuff usually end up in my case. Much more convenient rather then having a mess of folders in the Assets directory.

And the Content folder should remain under /Assets and be configurable

[patrik-u]

Getting it to work inside a Plugins folder is a bit trickier, it might work but a limitation could be that all the user content (views, models, assets, etc.) then also needs to reside within the Plugins folder just because partial classes need to reside within the same assembly. This applies to classes such as Assets and Models through which you access all the assets and models used by the framework, and used by the framework when doing data-binding, managing assets, etc.