Metamodeling: Functions browser

[odeimaiz]

I would like to see a section next to the Templates and Public Projects, where I can browse and handle the Functions I have access to.

I want to be able to rename, share, delete and even edit the function, the usual thing I can do with a Template.

Ideally, this section will be shown only if I can see at least one Function.

[JGO] Functionality to be included:

• Listing of all functions accesible by the user (paginated)
• List of inputs and outputs
• delete button
• info button to display the pipeline (as Project Card)

All these are already available in the mmux-vite repo - would just need to be implemented in the osparc-frontend.

Additionally, we would need the option to rename a function and edit the description (these are only visual changes, does not modify the underlying uid). @wvangeit probably knows which endpoint to do for that.

[JavierGOrdonnez]

This would be a great feature - but, as users won't be able to create their own functions under the current release plan, I would say it is not critical for the release. @esraneufeld might disagree, however.

[pcrespov]

@odeimaiz all these operations above would be for the framework front-end (i.e. qooxdoo app) or the user service's front-end ? or both?

[odeimaiz]

@odeimaiz all these operations above would be for the framework front-end (i.e. qooxdoo app) or the user service's front-end ? or both?

@pcrespov not sure I follow, here how I would solve it

[pcrespov]

@odeimaiz all these operations above would be for the framework front-end (i.e. qooxdoo app) or the user service's front-end ? or both?

@pcrespov not sure I follow, here how I would solve it

@odeimaiz understood

[pcrespov]

@JavierGOrdonnez @wvangeit I assigned this issue to you so you can lead it throughout the sprint.
@odeimaiz already split the work to be done in the framework's front-end.

Please make sure to enrich the description above before the PMs

[wvangeit]

I discussed this with @esraneufeld to be sure I understood correctly. We will allow, even in this release, a limited set of users to create/run functions, based on requests. This would become much easier if we had the frontend to list the created functions. So if @odeimaiz has time to work on this, it would be great.

[wvangeit]

One thing to keep in mind, the only endpoints that are released in the REST api to be used by the front end, are 'register', 'get' and 'delete' functions. Listing etc is not there yet, since not needed for now.
Since I'm handling many other issues atm, I doubt I will have time myself to extend this list, of course I'm ok if somebody jumps in to implement these.

[matusdrobuliak66]

A few comments for discussion:

• The metamodelling service is using the public API, which primarily relies on functions functionality.
• Our frontend client is using the webserver API, which primarily relies on projects functionality (for listing, patching, creating, and copying).

The naming/description of projects/functions is not consistent - how will they be represented in the osparc frontend versus the metamodelling service?

[wvangeit]

@matusdrobuliak66 can you explain maybe what you would consider inconsistent between the two? You mean like 'register' vs 'create'?
In a sense the public API and webserver API are all calling the same service layer for functions. So I guess we could keep them as synchronized as possible?
Or is it more a pure frontend/naming issue you're talking about?