This file is a short term todo list I  update very regularly ... almost each time a write a piece of code.
It is not supposed to plan the development on a long or even medium term.
It is just a pragmatic way for me to keep a track of what i want to code during the next weeks.

TODO:


**********************************************************
=>
Test the function mlview_editor_close_all_documents_interactive
to fix the bug 723.
***********************************************************

**********************************************************
=>Start to write the mlview internals doc to test
the new "automatic-subtree-adding" feature.
***********************************************************


********************************************************
*All the interactive methods of MlViewEditor should be suffixed "_interactive".
*That would be great for the overall program legibility.
*********************************************************


**************************************
When creating a node, make sure the tree is expanded, selected and that the focus is transfered to the appropriate edition area.
***************************************

*******************************************
*Enable selection of a set of nodes.
*******************************************

******************************************
*add facilities to detect when MlView is going to overwrite a file and display a dialog box to warn the user.
******************************************

*==================
When user attempts to exit MlView, ask him to save if needed !!!!
*==================

*========================
*improve the support of the other types of node/instructions (comments, processing instruction, xml prolog, doctype ... etc). Focus on completeness of
*the types of node that can be edited. (Very important): => in mlview-node-editor.c: started to add a XMLPINodeView structure. Edition works.
*Now, code the mlview_node_editor_clear_xml_pi_node_view() etc methods.
*========================================


*======================================
*Do some code cleaning: Provide static getters/setters for all the private data and avoid accessing private data (for code inside an object) directly
*for non accessor methods. Document the code. For the MlViewXMLDocument class: provide all the used methods of MlViewXMLDocTreeView to avoid users
*of MlViewXMLDocument to access the doc tree view. These users should not know anything about the views a document. A document should provides
*methods to edit itself. (node creation, cut/copy/paste etc ...). That should make addition of other views less painfull.
*=========================================

*===================================
*add a method  mlview_xml_document_set_doc_path_info() to MlViewXMLDocument. That method changes the tree part title of the doc tree view.
*Changes the code of the function build_ctree_from_xml_doc and build_ctree_from_xml_tree so that they do not set their column title to
*the name of the xml doc given in argument.
*=======================================


*=================================
*finish the emission of the appropriate signal when a node is cut/added/inserted. A default behaviour when the tree changes should be at least, set the last
*modif date to the current document.
*=================================