Open siglocpp opened 2 years ago
Hi, these are some cool features you are mentioning here!
I just have a little remark on the "Pathing Support" feature you are describing. I believe the UI script should remain in the same folder along the uxml
file, just like the traditional WinForm/WPF code-behind approach. But when we think about the binding script, we don't really need to have it along with them and we could just put all generated scripts in the same folder. Maybe a Rosalina/Generated
folder at the root of the Assets
folder.
This Rosalina
folder could also be the place where we store its configuration file for namespace and disabled documents.
I think the idea with the Rosalina folder for configurations and binding scripts is a good idea.
I understand your point with UI script/uxml file. I just happen to have a background where I prefere to seperate code and declaring visuals. Fortunately it's currently possible to just move the UI script where ever you want, since it does not get regenerated on uxml save. So our different approaches are a non issue and this part of the pathing idea can be scrapt. If we move the generated bindings to the suggested rosalina folder, we can just skip the whole pathing request, since it's fully resolved with this change.
Thumbs up to this idea. My suggestion would be to handle the generation using a scriptable object. There, you could drag the uxml files that you want to generate from, the file generation path (absolute or relative to the scriptable object location) and whatever generation setting you want to add there (like the namespace of the generated script files).
Update: The generated binding files are now located in Assets/Rosalina/AutoGenerated
.
I have some references on this topic:
Partially shipped in version 2.0.0
:
Assets/Rosalina/AutoGenerated
.I've added some very basic support for being able to change the default namespace and also added some simple settings support that could be a help for some of the other features mentioned here. See: https://github.com/Eastrall/Rosalina/compare/main...markcastle:Rosalina:main
I'll happily create some basic docs and a PR if this is of any interest?
The settings...
Sorry for the late reply @markcastle, feel free to open a PR if you want to contribute to the project! We are always looking for contributors in order to improve the tool!
I quite like, what this plugin does, but I'm missing some key features to make it better usable in bigger/structured projects:
Namespace-Support
Pathing Support
Disabling Rosalino for some VTAs