This will:
kill the TextRenderer inheritance chain
incorporate the functionality of the base TextRenderer in the base TextFormatter
rename TextFormatter to TextRenderer and appropriate references
That is because both essentially do the same job; encompass the style (or "how") information about how to render text, but using two slightly different interfaces. While that could allow for more flexibility, it is a faux choice that needlessly complicates the pipeline. By having a single interface to comply with, we still allow for custom renders while at the same time making all the code downstream simpler to use and understand.
Widget test for DragCallbacks and TapCallbacks
Added some common function in separate file for common use case
Minor test case description changed for MultiTouchTapDetector
DebugTextFormatter is a text formatter for use in tests, correspondingly, it is defined in flame_test.
Compared to DebugTextPainterTextElement it has several advantages:
Does not depend on a TextPainter, and thus it is truly platform-independent;
Supports font-weight, font-style, and color.
DebugTextPainterTextElement and the debugMode in TextPainterTextFormatter are deprecated.
* Independent test helpers
* Relative test helper path
* Fix imports
* Fix pubspec description
* Less tested lines, since the moved lines were in tests
* Move to canvas_test
