Opened 2 years ago

Last modified 17 months ago

#589 new defect

Need to provide at least one custom model in plugins directory

Reported by: butler Owned by:
Priority: major Milestone: SasView Next Release +1
Component: SasView Keywords:
Cc: Work Package: SasView Framework Enhancements

Description

Users would like to see a default example so they can understand the structure. Creating an easy model gives some basics but probably should include a full model from sasmodels including one python only and one python+C. Could take some of the original plugins and convert? should include documentation at beginning and test suite at end so users can start to get used to what will be required to submit as full model.

Change History (4)

comment:1 Changed 2 years ago by butler

  • Milestone changed from SasView 4.0.0 to SasView 4.1.0

Looks like this will require more "infrastructure" work than just dropping a model into a directory of the repo — at this stage of release best not to muck with it specially since we are documenting how to get there and have the marketplace as well as github to download from. Moving to 4.1

comment:2 Changed 2 years ago by pkienzle

Can point users to builtin models for examples.

It would be nice to disable the Advanced Edit/Delete/Load plugin models menu if there are no items in the submenu.

Last edited 2 years ago by smk78 (previous) (diff)

comment:3 Changed 2 years ago by ajj

  • Milestone changed from SasView 4.1.0 to SasView 4.2.0

comment:4 Changed 17 months ago by butler

  • Milestone changed from SasView 4.2.0 to SasView Next Release +1

We should consider whether this is still necessary - probably more useful to spend time uploading models to the marketplace? Not necessary for 4.2 and not likely to happen so moving

Note: See TracTickets for help on using tickets.