lp:~syslock/tomdroid/note-editing

Description:
~~~~~~~
This is a modification to trunk that replaces the static TextView widget for note display with an EditText widget and allows to edit notes in a WYSIWYG manner and store changed note contents to the internal content provider. Currently all changes are lost during synchronization and some notes are not stored correctly.

Requirements:
~~~~~~~~~
- native Android/IME editing capabilities in notes
- no the need to enter a specific editing mode, just place cursor and type
- changes are stored automatically in Tomdroid (not necessarily synced automatically to Web or file system)
    - no need to hit a save button ever
- do not show on-screen keyboard without cursor placement/selection
- maybe hide on-screen keyboard on timeout/dragging events

Functional Analysis of Code in Trunk:
~~~~~~~~~~~~~~~~~~~~~~~
- Web and SDCard sync services store XML source in Note instances
- XML source is cached/stored by Androids content provider using managed queries, but currently cannot be synced back to SDCard or Snowy (see lp:~trappe/tomdroid/two-way-sync)
- note selection from the list triggers creation of a SpannableStringBuilder instance from the notes XML source, that can be used by a TextView (or EditText) to display formatted text, but is not cached/stored at all

TODO:
~~~~
- A first step would be to find a way to update XML content of a note with changes done to its Spannable object through an EditText instance, which can be done in at least two variants:
    - a) design a reverse converter that compiles XML content from a Spannable object
        - might be hard to reproduce 1:1 copy of original XML content with unchanged Spannable, but not sure if this is a problem
        - we already have partially working code utilizing this method
    - b) create hooks on each possible update to the Spannable object that trigger identical updates to the notes existing XML content
        - might be hard to hook and translate every possible Spannable update to a corresponding XML update
        - probably harder to get something working
- bidirectional sync services are needed capable of uploading/writing changed XML content to the Web/file system (see lp:~trappe/tomdroid/two-way-sync)
- formatting tools and editing rules equivalent to those of desktop tomboy have to be implemented, that enable the user to not only change text but also change text formatting properties