Introduce a "persistence" module which will encapsulate all
persistence-related functionality.
Ideally, the following should happen:
- the only module depending on persistence/ is sources/
- the following files move under persistence/:
- FileManager
- FileSystemMapping
- IsolatedFileSystem
- IsolatedFileSystemManager
- FileSystemWorkspaceBinding
- NetworkMapping is purged (yay!)
- UISourceCode gets freed from persistent-related methods:
- hasUnsavedCommittedChanges
- forceLoadOnCheckContent
- saveAs
- checkContentUpdated
- ResourceScriptMapping/StylesSourceMapping are in charge of creating UISourceCodes for the Script/StyleSheet
A document, explaining the motivation and design goals:
https://docs.google.com/document/d/12EU7HgFNWBsP_3syPCviHEOmU-Yn-q4kiF6RT_kBmO0/edit#
Introduce a "persistence" module which will encapsulate all
persistence-related functionality.
Ideally, the following should happen:
- the only module depending on persistence/ is sources/
- the following files move under persistence/:
- FileManager
- FileSystemMapping
- IsolatedFileSystem
- IsolatedFileSystemManager
- FileSystemWorkspaceBinding
- NetworkMapping is purged (yay!)
- UISourceCode gets freed from persistent-related methods:
- hasUnsavedCommittedChanges
- forceLoadOnCheckContent
- saveAs
- checkContentUpdated
- ResourceScriptMapping/StylesSourceMapping are in charge of creating UISourceCodes for the Script/StyleSheet. Design doc for this last change: https://goo.gl/rt9RAS
A document, explaining the motivation and design goals:
https://docs.google.com/document/d/12EU7HgFNWBsP_3syPCviHEOmU-Yn-q4kiF6RT_kBmO0/edit#
Comment 1 by bugdroid1@chromium.org
, Sep 26 2016