Script Repository

[capitanevs]

We had talked a lot about that, but we never opened an issue.

I do not remember this point: ultimately, this has nothing to do with the info widget, true?

[aljosahafner]

Correct, it has nothing to do with the widget...

[aljosahafner]

This is GUI v1

I am reusing the repository (index and files) from the previous project where I had an OWS repository.

[capitanevs]

I have elaborated a little bit what we discussed yesterday.

It's just a summary, nothing really new.

There are two main topics: 1) usage/repository and 2) code/abstraction layer.

Topic 1): I see two possible cases

a) the user uses functions/scripts that are in the repository
b) the user uses function/scripts that she created (example for doing some plot, or quick analysis), but which are not yet on the repository.

In case b) enter also the case where the users loaded a script from the repository and they heavily modify the content (not just by changing the settings).

Considerations

-We could start focus on a), as I am the mantainer of the repository and I can quickly add anything I (and my close cooperator) need.
-b) is still interesting, as it is of general order. The Python Script widget has a "library" listbox in it, which seem to address the same problem, but I have never understood how to use it.
-b) Thinking of it if I had b), I would not mess up with a) :-) I would have my local folder of scripts and I would locally maintain it. Then I would manually push them on GIT. Of course, this does not mean that a) is not important, but I just wanted to recall where everything was born from :-)
-b) for b we could think about a "custom" local folder, which can be maintained either via external IDE (e.g. spyder) or just by means of "Save to..." command, added in the editor window.

Topic 2) More philosophical.

There is the question of "how the code should look like". This is more subtle. I see many different behaviors that one might wish

• The same as the Python Script widget: you execute all the code in the editor.
• A widget which is "automatically connected" to a function and let the users specify only the input parameters (either via GUI or just as python text)
• A widget that let the users choose among the functions within a module
• A wdiget which just run an external python script,
• etc...

Considerations

As we said yesterday, we should focus on the first one for the moment. Improvements are always possible in the future, once we have really understood our needs.

Topic 3): About metadata etc.

Still to be discussed. In addition to author name, editing date etc, the relevant information is the description of the script.

Possible places where to store it are:

• the script file
• the function that is called by the script file (if the script file calls a function)
• the json file
• ...else...?

We need to figure out what to do

[capitanevs]

Just as personal notice: I put a screenshot of Python Script widget.

How about making a widget where the users can choose between the local and the remote library, and see where this is taking us?