Editor Restart
Posted: 25 Nov 2012, 17:44
As you all probably have recognized by now the development of our editor does not progress a lot. While we also do have a few larger issue to solve with OpenMW, the engine should be finished not too far into the future. That unfortunately means that the editor won't have the head start I was hoping for, which in turn means we will be stuck after 1.0 in regards to adding new features to OpenMW.
Our current approach (editor branch) has several problems. Some of them are structural (the data model not being entirely correct and the Ui design having significant usability problems), but there are also organizational problems (one developer working mostly by himself on whatever he fancies without communicating much or using the issue tracker).
It seems I need to take a stronger lead for the required progress to be made. Which I herewith do.
During the last few days I started to read up on Qt and I have already build a new framework for the editor (editor2 branch, just pushed to github). Hopefully we will probably be able to reuse a lot of the code for the editor branch, but from now on editor2 is the main branch for the new CS.
I have left lots of todo comments in the code and I will start to add tasks for it to the tracker (for 0.21.0). These are small to medium tasks of easy to medium difficulty. I hope this will make it easer for other developers to pick them up.
The new editor already provides the following features:
- multiple documents with only one editor process
- multiple top level views per document
- a sub-window system (blender-like)
- an undo/redo-system
- edit-locking
- the UI for multi-threaded operations (saving, searching and a few more; the actual multi-threading still needs to be implemented).
We can't do ESX loading yet. Still need to implement a data model. And we also need the refactored ESX selector from the launcher. But if everything goes well, I hope we are ready to release a partially functional preview of the editor along with 0.22.0 or maybe 0.23.0.
Our current approach (editor branch) has several problems. Some of them are structural (the data model not being entirely correct and the Ui design having significant usability problems), but there are also organizational problems (one developer working mostly by himself on whatever he fancies without communicating much or using the issue tracker).
It seems I need to take a stronger lead for the required progress to be made. Which I herewith do.
During the last few days I started to read up on Qt and I have already build a new framework for the editor (editor2 branch, just pushed to github). Hopefully we will probably be able to reuse a lot of the code for the editor branch, but from now on editor2 is the main branch for the new CS.
I have left lots of todo comments in the code and I will start to add tasks for it to the tracker (for 0.21.0). These are small to medium tasks of easy to medium difficulty. I hope this will make it easer for other developers to pick them up.
The new editor already provides the following features:
- multiple documents with only one editor process
- multiple top level views per document
- a sub-window system (blender-like)
- an undo/redo-system
- edit-locking
- the UI for multi-threaded operations (saving, searching and a few more; the actual multi-threading still needs to be implemented).
We can't do ESX loading yet. Still need to implement a data model. And we also need the refactored ESX selector from the launcher. But if everything goes well, I hope we are ready to release a partially functional preview of the editor along with 0.22.0 or maybe 0.23.0.