Eeeeh… let’s try to summarize:
@@PLyczkowski I indeed intend to use filebrowser as a regular asset manager, from which one should be able to drag’n drop into other editors as well. However, I think that kind of ‘local lib’ you describe should rather be handled by separated addons - want to keep core funcs as generic as possible, to then allow defining any custom workflow one may imagine - this is also (remotely) connected to the 101 project (you know, ‘easy’ blender for beginners, schools, etc.).
re fonts: yes, of course they are also assets, and yes, we’ll need to work on them. Afraid to say they are not on the top of my priority list currently, though.
I could say that my goal currently is not to add a ‘fluid’-like tool to Blender, it’s to make it much much easier to do things like that!
Note this project is a rather long term one, for at least two reasons:
- It is simply a quite big one - core feature should hopefully be done soon(ish), but potential ramifications are huge.
- It’s gonna need many cycles of dev + testing, because it will affect all users’ workflow, from casual/beginners to full professional studios. Needs to be done in the right way!