Feature description

Thanks for the hard work! The newest version actually solve this problem by showing the key-value pairs in the right side. Thus we could put some context in the right side as key-value pair. For example, when we annotate one wikipadia page, the key-value will contain "wikipadia title" ,"url" and something like this.

But if the context is large text, it won't work...

For example, here is my annotation task, we annotate each sentence in a document into one type. And we used document classification. User annotate one sentence at a time. Actually, when you annotate one sentence you need to see the context sentence of the annoted sentence and even the whole document. Thus we have to parse the data like this.

Here is one sentence when user see the annoated sentence, we connect the annoated sentence and the context string directly, separated by some delimiters("----------"):

However, using the same path, I was able to load the file when I did getResourceAsStream().
-------------------------------------------------------------------------------------------------
question body:
I was trying to load a file in a webapp, and I was getting a FileNotFound exception when I used FileInputStream. However, using the same path, I was able to load the file when I did getResourceAsStream(). What is the difference between the two methods, and why does one work while the other doesn't?

Is it possible to add an area below the area where the text need to be annoated to show the context? The content of this context area is determined by the "context" field in the data set for each annotated data point. It can be empty, so this area is hidden.

I think this context is useful for other annotation. For example, when I annoatate the type of Stack Overflow answer post, the question post should be shown to make the annotator understand the answer context.