Plan 1 (Based on Text content).
Serialized or not will be no difference to the User “inside of the editor”
So just don’t serialize content to Binary, keep it’s original state (Plan Text) (when open / editing / save, not after compile / cook / run),
And Let the Coders decide what they will do “outside of the eiditor”
Plan 2 (Based on Binary / Text content).
That’s require open a new topic
at least need to write BluePrint Plugin / Independent Unreal Tool For IDE (Visual Studio, KDevelop, QTCreator …) and Source Control (Git / SVN …)
Basically it’s all about let code to know about what inside binary
And we need talk about all the functions of this plugin / independent tool and it’s different version compatibility
I don’t want consider details of Plan 2, Because almost everything is ready for Plan 1
If Plan 1 done, may be we begin to think text based is hard to use, then we will want Plan 2 plugin for IDE, But at least we have Plan 1 can use
If we push Plan 2 now, we can only use Plan 2 (Based on Binary), and limited by more tool, more things need to change to text based content
But If we push Plan 1 now, we can use Plan 1 / Plan 1 + Plan 2 (Based on Text) latter if we want