You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lets have a look at this:
Deve...User... erhm.. scientists, have to be able to create interfaces to launch specific tasks.
So the interfaces must be able to interact with plugins and core easily.
And what about being able to launch the jobs? Would be nice, I've seen it like:
Interface provided by http server (or whatever)
Passed to core as a configurable module with classes, enable some special class that contains information like the plugin that's going to be used (there's a default plugin for default behaviour! so that we don't have to repeat code nor make special cases) and so on
So the core can instanciate the view and instanciate the job with a new initialized plugin objectas arguments foreach view requiring it.
That way, a view can initiate a job usign plugin features, or even (as the way it's done right now) provide a plugin in a view's module!
Hmm yes, a scientist could want to be able to send a new view (akin to a new AppVersion in BOINC parlance)
Actually, "As scientist, I would like to be able to test easily my new interfaces or/and views"
As developer, I want to be able to create easily create interfaces using the framework
The text was updated successfully, but these errors were encountered: