... | ... | @@ -57,7 +57,8 @@ The way project files are handled currently is that the serialised form (XML) is |
|
|
|
|
|
![image](uploads/deca45c6ccf29dc4ae1c61f92f29916e/image.png)
|
|
|
|
|
|
A standard way to load saved projects is to parse it (from whatever format it is) and then create an in-memory representation of it which is very easy to work with for developers. This approach has several advantage besides usability for developers. One is that de-serialisation (loading the project file) is happening in a single place and all issues (like decimal separator, document version updates, validations) are done in that step. Afterwards, the developer does not need to worry about reading XML DOM nodes in order to get a property, but simply access the data model in memory.
|
|
|
A standard way to load saved projects is to parse it (from whatever format it is) and then create an in-memory representation of it which is very easy to work with for developers. Comment from Alcinos: This is essentially what happens today already, in our model files. See https://invent.kde.org/multimedia/kdenlive/-/blob/master/src/timeline2/model/builders/meltBuilder.cpp
|
|
|
This approach has several advantage besides usability for developers. One is that de-serialisation (loading the project file) is happening in a single place and all issues (like decimal separator, document version updates, validations) are done in that step. Afterwards, the developer does not need to worry about reading XML DOM nodes in order to get a property, but simply access the data model in memory.
|
|
|
|
|
|
![image](uploads/fca9607dd572a66c3dfd90304662ed5f/image.png)
|
|
|
|
... | ... | |