Suggestions to improve customization

[maten21]

1. Option to add a custom startup (and maybe also shut down) script.
2. Options to edit and generate file adapters based on template similarly to session methods.
3. I am not sure if it is actually necessary, but a defined location to safely store custom codes in the project folder could be good. (e.g. some function that would be used in multiple session methods or table variables). Actually a startup script would kind of solve the problem by adding whatever external folder to the Matlab path.

[ehennestad]

1. Could you explain more, and perhaps provide an example? Would this be like a startup script for a project? This is a great idea, I think the easiest would be to add a startup.m and a finish.m file to the project, and make sure they are executed when a project is activated/deactivated
2. This is something I am working on at the moment, so I'll try to speed up adding it:)
3. Also working on this. I am restructuring the project folder and the idea is to have a code folder where all the session method/ table variables/file adapters will live, but it could also be a place to add other custom code which these rely on. I would definitely aim towards adding dependent functions into the project itself, as another thing I hope to see is projects being shared in GitHub repositories.

[maten21]

1. For example in ScanImage there is a GUI input line to link an optional script that runs sometime during the starting or the closing process. It could in theory run a custom GUI window or check the available HDD space and give warning etc. something that the developer didn't implement but could be useful in certain circumstances. I use a script at ScanImage during the closing process to automatically copy and rename the imaging files from a temporary location in a similar structure as SciScan does.

2. Not urgent for me. :)

3. (3?) About sharing, I started to think about making a simple Session Method or plug in manager GUI window where one can list the installed Session Methods as well as those that are shared the on a remote location. The idea is that with the simple check box one could install/uninstall them, maybe also leaving the option to edit the menu location.

[ehennestad]

For point 1, it seems like then adding a startup.m and a finish.m in the project folder that can be executed when a project is selected/unselected would fit your idea

For point 3, that looks very nice. I am also in the process of creating something called modules. A module is a folder that contains a set of session methods, table variable and file adapters. There will of course be a two-photon module which contains all the session methods that are two photon related. The user will be able to select/unselect modules, and this will then update which session methods are available.

But I also like the idea of being able to control it on an individual level, and also being able to edit menu location in a gui!