The recreator is fully integrated with the program model such that program lines can be converted back into text. When lines are entered into the program, the lines need to be recreated back to text and put into the edit box (the GUI), specifically into the text document of the edit box. Like the temporary program view (being used for debugging) is the viewer of the data held by the program model, the edit box is the viewer of the data contained in the document. The edit box also allows editing, so it is more than just a viewer.
The document of the edit box is really just the text representation of the program. The program model holds the actual data of the program. Ideally, the program model would be the document of the edit box and it would convert text to program code and back while editing. However, Qt does not have an abstract text document class from which a document sub-class could be built that would hold its data in another form like program code. The QTextDocument class is meant for text.
Alternatively, a new viewer could be designed that would allow all the text editing features (cut, copy, paste, undo, redo, etc.) like the QPlainTextEdit class that the edit box class is based on. Designing one would be quite an effort. Therefore, the edit box will the viewer for two data models at the same time, the text document (to allow text editing) and the program model (for holding the program code). The program model will be the master of the data, with the text document being updated as the program changes.
This implies that the edit box either own the program model with the program code or at least have easy access to it like via a pointer. The later approach will be used since the main window class will ultimately be the owner of the program. Eventually there will be a list of program models, one for the main routine and several for the subroutines and functions of the program. There will only be associated edit box instances when the main routine, subroutines or functions are open for editing.
Since the edit box will now have access to the program model, signals from the program model (for program changes) do not need to contain actual data. For instance, when a program line has changed, its recreated text is needed to update the text document. The signal could contain both the line number and text (already recreated). Looking at the edit box to document interface, when the document changes, only the position, number of characters removed and inserted are contained in the signal. The edit box must obtain the actual text changes by querying the document. So, when the program changes, only the line number will be sent and the edit box will request the recreated text from the program model.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
All comments and feedback welcomed, whether positive or negative.
(Anonymous comments are allowed, but comments with URL links or unrelated comments will be removed.)