Hi Adam,
Please see my in-line comments.
The point of the discussions was not primarily about UI but about
> integration with the CAS Editor (UI just got dragged into it since
> there are UI implications for how the integration is done).
Yes, you are right. We are still talking at the "abstract"
On Fri, Aug 22, 2008 at 1:27 PM, Tong Fin <[EMAIL PROTECTED]> wrote:
> Hi,
> It is almost 7 weeks now since I submitted the CAS Viewer. There are some
> discussions about various issues related to GUI, sharing code, etc. Some are
> related to CAS Viewer itself and some are general issues related to
Hi,
It is almost 7 weeks now since I submitted the CAS Viewer. There are some
discussions about various issues related to GUI, sharing code, etc. Some are
related to CAS Viewer itself and some are general issues related to Eclipse
UI.
If the CAS Viewer is accepted by Apache UIMA, my original plan
Unless I missed it, an important area of discussion are the various scenarios
using CAS Edit/View functionality. In my own experiences, switching back
and forth between looking at a CAS and looking at annotator code,
descriptors and type systems is the most common.
The CAS viewer, fitting into a s
On Aug 15, 2008, at 6:07 PM, Tong Fin wrote:
Here an example:
The student Marco Nehmeier told us that he has written a tool to
view and
annotate html with eclipse his task would have been easier if he
could
have just reused our views for cas specific things other than
displaying
the html
>
> In addition, I tend to rearrange the views in a perspective to suit
> my needs. I like some views stacked, others get their own area.
> My workspace will remember those changes for me.
I do the some way as you. This is the way that Eclipse User Guideline
recommends.
I don't think you
> can d
On Fri, Aug 15, 2008 at 3:25 AM, Jörn Kottmann <[EMAIL PROTECTED]> wrote:
> I don't mean that.
>> From the end-user's point of view, it is a good idea for users to "see"
>> only
>> one tool (like the way users edit the UIMA-AS Deployment Descriptor).
>> Under
>> the cover, it may switch to View mo
Jörn Kottmann wrote:
>> I don't mean that.
>> From the end-user's point of view, it is a good idea for users to
>> "see" only
>> one tool (like the way users edit the UIMA-AS Deployment Descriptor).
>> Under
>> the cover, it may switch to View mode or Edit mode according to some
>> preference or se
I don't mean that.
From the end-user's point of view, it is a good idea for users to
"see" only
one tool (like the way users edit the UIMA-AS Deployment
Descriptor). Under
the cover, it may switch to View mode or Edit mode according to some
preference or setting (or dynamically switch).
The q
On Thu, Aug 7, 2008 at 6:01 PM, Adam Lally <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 7, 2008 at 5:16 PM, Tong Fin <[EMAIL PROTECTED]> wrote:
> > For the CAS Editor, editing a CAS is a tedious operation that can take
> long
> > time, for example, when users try to create "gold standard" CAS files. I
On Thu, Aug 7, 2008 at 5:16 PM, Tong Fin <[EMAIL PROTECTED]> wrote:
> For the CAS Editor, editing a CAS is a tedious operation that can take long
> time, for example, when users try to create "gold standard" CAS files. It
> may make sense to have it own perspective for the CAS Editor.
>
Are you su
On Thu, Aug 7, 2008 at 4:24 PM, Adam Lally <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 7, 2008 at 12:05 PM, Tong Fin <[EMAIL PROTECTED]> wrote:
> > The approach taken by the CAS Viewer is not new. The GUI design of the
> CAS
> > Viewer is based on "multiple-page form editor" like plug-in/manifest
> e
On Thu, Aug 7, 2008 at 12:05 PM, Tong Fin <[EMAIL PROTECTED]> wrote:
> The approach taken by the CAS Viewer is not new. The GUI design of the CAS
> Viewer is based on "multiple-page form editor" like plug-in/manifest editor.
> In CAS Viewer, each page corresponds to each CAS view (sofa). In each pa
On Fri, Aug 1, 2008 at 2:40 PM, Adam Lally <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 1, 2008 at 2:33 PM, Jörn Kottmann <[EMAIL PROTECTED]> wrote:
> > I still think that the huge benefit of doing it the Cas Editor way with
> > multiple views:
> >
> > + Its easier to explore a CAS file because there
On Fri, Aug 1, 2008 at 2:33 PM, Jörn Kottmann <[EMAIL PROTECTED]> wrote:
> I still think that the huge benefit of doing it the Cas Editor way with
> multiple views:
>
> + Its easier to explore a CAS file because there is more screen space to see
> things.
>
I agree with that. I've used the CAS Ed
Good suggestion to have a new plugin to switch the underline tools
(CAS
Editor or CAS Viewer). We just provide some customization (through
Eclipse
preference ?) for users to select what is the "default" mode they
would like
to have since different users may have different usage pattern.
Act
On Thu, Jul 31, 2008 at 9:55 AM, Jörn Kottmann <[EMAIL PROTECTED]> wrote:
> I definitely think the CAS Editor and CAS Viewer should be merged, and
>> I think the merged tool could become the primary tool for viewing and
>> editing CASes. We could refer to it in our documentation and
>> tutorials,
I definitely think the CAS Editor and CAS Viewer should be merged, and
I think the merged tool could become the primary tool for viewing and
editing CASes. We could refer to it in our documentation and
tutorials, and it would become more popular than both the Document
Analyzer and CAS Visual Debu
The thinking so far is to provide a CAS API to access a CAS journal
object and use that to query for the CAS operations that have been
logged. The CAS journal object will provide APIs to access the following:
1) get the list of component AEs that have processed this CAS in the order
they were ca
On Tue, Jul 15, 2008 at 5:15 PM, Marshall Schor <[EMAIL PROTECTED]> wrote:
> I'm starting this thread to discuss the Cas Viewer submission. The initial
> code is attached to this Jira issue:
> https://issues.apache.org/jira/browse/UIMA-1102.
>
> An initial comparison of features of this Viewer, th
Hi Thilo,
Yes, I expect that we will have APIs independent from how we visualize the
information so that tools in different environments (e.g., based on Swing
like CVD or on Eclipse like CAS Viewer) will benefit from that.
We need a discussion on that.
-- Tong
On Thu, Jul 24, 2008 at 2:20 PM, Th
Are you planning to make a general API available so that
the CVD, for example, could also benefit from this information?
--Thilo
Tong Fin wrote:
According to the previous note on the history of the work here, there is
some desire to take advantage of the Eclipse plugin packaging of this
compone
> According to the previous note on the history of the work here, there is
> some desire to take advantage of the Eclipse plugin packaging of this
> component and reuse it in further Eclipse-based tooling being considered,
> such as debugging tools.
>
>
One of the debugging tools is "Provenance Tra
I'm starting this thread to discuss the Cas Viewer submission. The
initial code is attached to this Jira issue:
https://issues.apache.org/jira/browse/UIMA-1102.
An initial comparison of features of this Viewer, the Annotation Viewer,
and the CAS Visual Debugger (but not the Cas Editor) was do
24 matches
Mail list logo
