Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SofaKernel] Set BaseData to non-persistant by default #1191

Merged
merged 2 commits into from
Oct 23, 2019

Conversation

damienmarchal
Copy link
Contributor

@damienmarchal damienmarchal commented Oct 18, 2019

This is a long standing issue in Sofa about not being able to save 'usable' scene in runSofa.

This is the result of multiple problems combined together among which:

  • there is keywords that are not Data field but parsing hook (eg: src, compatbility hook) and they needs to be converted into Data.
  • the Data have a persistant field. But it is let to the component to specify which are or not depending on some object property but depend on their context of "use".
    Eg:
    *) a data changed in the GUI should be saved
    *) a data filled with a script shouldn't
    etc...

To allow to control fine grain the state of a data is now set to non persitant
by default and should only be activated specifically (by the GUI, or the script)
if it is needed to save it.

This is what this PR do, and despiste this is a behavior change...it is on a totally broken feature.


This PR:

  • builds with SUCCESS for all platforms on the CI.
  • does not generate new warnings.
  • does not generate new unit test failures.
  • does not generate new scene test failures.
  • does not break API compatibility.
  • is more than 1 week old (or has fast-merge label).

Reviewers will merge only if all these checks are true.

This is a long standing issue in Sofa about not being able to save 'usable' scene in runSofa. Several PR had been made a long time ago.

There is multiple problems among which:
- keywords that are not Data field but parsing hook (eg: src, compatbility hook) needs to be converted into Data
- the Data are not persistant or not depending on some object property but depend on their context of "use".
Eg:
   *) a data changed in the GUI should be saved
   *) a data filled with a script shouldn't
etc...

To allow to control fine grain the state of a data is now set to non persitant
by default and should only be activated specifically (by the GUI, or the script)
if it is needed to save it.

This is a behavior change...but it is on a totally broken feature :)
@damienmarchal damienmarchal added the pr: status to review To notify reviewers to review this pull-request label Oct 18, 2019
@guparan guparan added the enhancement About a possible enhancement label Oct 23, 2019
@guparan guparan changed the title [SofaKernel] BaseData are set to non persistant by default. [SofaKernel] Set BaseData to non-persistant by default Oct 23, 2019
@guparan guparan added pr: breaking Change possibly inducing a compilation error pr: status wip Development in the pull-request is still in progress and removed pr: status to review To notify reviewers to review this pull-request labels Oct 23, 2019
@damienmarchal damienmarchal added pr: status to review To notify reviewers to review this pull-request and removed pr: status wip Development in the pull-request is still in progress labels Oct 23, 2019
@guparan guparan added pr: status ready Approved a pull-request, ready to be squashed and removed pr: status to review To notify reviewers to review this pull-request labels Oct 23, 2019
@epernod epernod merged commit e30595d into sofa-framework:master Oct 23, 2019
@guparan guparan added this to the v19.12 milestone Jan 14, 2020
@damienmarchal damienmarchal deleted the setDataPersistantcyToFalse branch August 25, 2020 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement About a possible enhancement pr: breaking Change possibly inducing a compilation error pr: status ready Approved a pull-request, ready to be squashed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants