Needed Files and folder location (templates, modules and span_settings)

[reno-]

On loadbang, SPAN will get his own path to determine where is the library folder, the template folder and the span_settings.json file. The span_settings.json is the first file that span loads (on loadbang), we use an explicit path to access it. If we move span_settings.json, or if we move span.maxpat patch, the system will be broken. I mean it's not a very elegant solution.

Maybe we could : *span_settings file* : Load it from the search path (without path, considering there is only one span_settings.json file in Max Search Paths). Or maybe put in ~/Library/Preferences folder. This is a way to are sure that there is only one file. Maybe his preferences folder could contains temp-folder too (temp-project). modules folder** : No better solution - it has to be in the span root path. It hasn't to be in Max Search Path because span_builder makes a dynamic allocation of Max Search Path to load the abstraction (module). We know the path of the module because we do an exploration of Modules folder to list available modules (described by json folder) *templates folder : No better solution - it has to be in the span root path? it hasn't to be in the search path too.

[reno-]

i put settings file in library folder, like span.maxpat. So now it still the same, if you move span.maxpat, span_settings or modules and templates folder, all paths will be broken

[tmays]

I think it's ok that the internal organization of the span folder can't be messed with or it might break something. The modules folder, however, can be anywhere. It's path will be a part of the project. I would like to be able to define along with the templates folder, a default project folder, where one could place one's media files or other data in sub folders if one wanted to. It would be scanned and copied as is, so one could modify it easily to customize.

There could be a templates folder, a modules folder and a defaultproject folder in the span folder. These would be saved in the new "system" key of span dict. If one wanted to, they could define other templates, modules or defaultproject folders in the "paths" section. When needed, span would first look to see if there is a path (project), and if not, would go to the system path for the default.

[reno-]

My message had one month when you answer it, so it was out-of-date. Modules folder doesn't exist in span, maybe you will implement one in tapemovie, but there is no modules in span ;-)