category handling needs updating for sasmodels (Trac #524)

[butlerpd]

For release 4.0 we are moving to sasmodels which changes all the model names. Eventually having a list of default categories as part of the model is probably the right answer but will require changes to category manager logic which does not seem a priority for this release.

In the meantime we will need to edit the default_category.json file to refer to the correct names.

Also need to use a different name for serialzed_categories.json so that we don't have problems with users having 3.1.2 and 4.0 alongside each other.

Migrated from http://trac.sasview.org/ticket/524

{
    "status": "closed",
    "changetime": "2016-04-16T22:06:11",
    "_ts": "2016-04-16 22:06:11.154519+00:00",
    "description": "For release 4.0 we are moving to sasmodels which changes all the model names.  Eventually having a list of default categories as part of the model is probably the right answer but will require changes to category manager logic which does not seem a priority for this release.\n\nIn the meantime we will need to edit the default_category.json file to refer to the correct names.\n\nAlso need to use a different name for serialzed_categories.json so that we don't have problems with users having 3.1.2 and 4.0 alongside each other.",
    "reporter": "butler",
    "cc": "",
    "resolution": "fixed",
    "workpackage": "SasModels Redesign",
    "time": "2016-03-16T20:26:47",
    "component": "SasView",
    "summary": "category handling needs updating for sasmodels",
    "priority": "blocker",
    "keywords": "",
    "milestone": "SasView 4.0.0",
    "owner": "butler",
    "type": "task"
}

[ajj]

Trac update at 2016/03/18 15:58:45: ajj commented:

Partially done. Waiting on all models to be converted to close.

[ajj]

Trac update at 2016/03/20 12:05:59:

• ajj changed description from:

For release 4.0 we are moving to sasmodels which changes all the model names. Eventually having a list of default categories as part of the model is probably the right answer but will require changes to category manager logic which does not seem a priority for this release.

In the meantime we will need to edit the default_category.json file to refer to the correct names.

to:

For release 4.0 we are moving to sasmodels which changes all the model names. Eventually having a list of default categories as part of the model is probably the right answer but will require changes to category manager logic which does not seem a priority for this release.

In the meantime we will need to edit the default_category.json file to refer to the correct names.

Also need to use a different name for serialzed_categories.json so that we don't have problems with users having 3.1.2 and 4.0 alongside each other.

• ajj changed owner from "" to "butler"
• ajj changed status from "new" to "assigned"
• ajj changed summary from "default_category.json needs updating for sasmodels" to "category handling needs updating for sasmodels"

[butlerpd]

Trac update at 2016/03/21 12:23:31: butler commented:

new user categories file is called categories.json. changes pushed but forgot to link commit to this ticket. once models are in we can finalize default_categories.json and close the ticket.

[sasview-bot]

Trac update at 2016/04/16 22:01:26: paul butler butlerpd@udel.edu commented:

In [42585bf]:

#!CommitTicketReference repository="" revision="42585bf5a1366b2c27e83e0b966687142fa2abd6"
oops ..renabled by default.  should now be ready for alpha release.
closes #657

[butlerpd]

Trac update at 2016/04/16 22:06:11:

• butler commented:

apparently #xxx is recognized as a ticket link but closes did not close the ticket. Doing it manually now.

• butler changed resolution from "" to "fixed"
• butler changed status from "assigned" to "closed"