Support Jump Indicators on OAT View

[alonalbert]

Notes:

• DexTextArea & OatTextArea are trivial, but I think it results in a cleaner project.
• The oat package currently contains only OatTextArea, but it would make sense to move the oat parsing there too.

[romainguy]

Thanks. I didn't add support for jumps in the OAT text area initially because a lot of jumps need to be computed, which is a pita, but I guess this is better than not having them at all.

Another thing I wanted to do was what you started doing: parsing should produce a list of class/methods/instructions. This way computing the jumps in the text area wouldn't require to re-parse the document line by line every time, instead we could just lookup the instruction directly in a data structure and get its matching line in the text area document. O(n) to O(1) effectively.

[alonalbert]

Yeah, we should have something like:

sealed CodetextViewContent {
    class CodeContent(classes: List<CodeClass>): CodetextViewContent
    class ErrorContent(error: String) : CodetextViewContent
}

[alonalbert]

Can you share an example of a OAT jump that needs to be computed?

I'm not sure I understand.