I may be less responsive than usual - I'm traveling on business for the rest of the week...
-Marshall On 4/11/2011 4:30 AM, Jörn Kottmann wrote: > On 4/9/11 5:32 AM, Marshall Schor wrote: >> >> On 4/8/2011 8:53 AM, Jörn Kottmann wrote: >>> On 4/8/11 2:20 PM, Marshall Schor wrote: >>>> (You might be able to tell I haven't really used this in a long while ... >>>> :-) - >>>> so this feedback might be typical of a new-ish user). >>>> >>>> 1) In the outline view - I expected to be able to click on instances of >>>> RoomNumber and see the features, covered text etc., and maybe even edit the >>>> features. But apparently you have to open another viewer - the "edit view" >>>> for >>>> this. Maybe these two views could be combined? >>>> >>> The covered text is displayed to some degree, because space is limited, >>> didn't >>> you notice it? >> I did notice it - nice :-). > Maybe you can have a second look here, I believe it should be ok. > >>> Sure it would be possible to combine these two views. >>> When I made it I put it into an extra view because then it can easily be >>> reused by some other >>> maybe even non-text kind Cas Editor implementation. >> maybe there's a way to have the best of both approaches? not sure... > > I am also not sure, it would of course be possible to somehow refactor the > edit > view in a way it could be embedded into the outline view. Maybe that would be > nice, > because it makes viewing a CAS document outside the Cas Editor Perspective > easier. >>>> 2) In the menu pick: Windows -> Show View -> Other -> there's a pick >>>> for "Cas >>>> Editor". It might be good to prefix all our menus with UIMA - to avoid >>>> name >>>> collisions in the future. >>> +1 to do that, is it an eclipse convention? >> I don't know if it's an eclipse convention, but I think it's in general a >> good >> approach for systems like eclipse where many "vendors" can each contribute to >> menus > I created a jira issue for this: > https://issues.apache.org/jira/browse/UIMA-2119 > >>>> 3) I see (on my system) in the pick list from Windows -> Show View -> >>>> Other -> >>>> Cas Editor : two entries for "Edit viewer" ? >>> It really exists two times, because otherwise dragging feature structures >>> around is not possible. >>> Lets say FS a has a field which references FS b. Now you want to create FS a >>> and FS b, and then link >>> the field of FS a to b. For this you can now select FS a, lock it in one of >>> the two FS views and select FS b, >>> now you can simply drag b on the field of a. >>> >>> Any ideas to make linking between FSes easier are very welcome. >> OK, let's think more about this. >>> In my opinion we should switch one day from the swing based tooling to >>> eclipse >>> tooling, >>> I believe we have now most of the features we would need to make such a >>> switch. >>> As a first step we could deprecate the swing tooling and update our >>> tutorials >>> to the eclipse tooling. >> Well, not everyone likes / uses Eclipse. And some people find command-line >> tooling to be best in certain situations. So I would be wary of doing this. > > Most of the tooling we have is swing tooling, and not command line based > tooling, right? > In my opinon we should have a command like tools also for tools like the pear > installer > or some AE runner. > > What do you think of the Feature Structure View? Should it be extended in some > way > to support Index Repositories? Would be nice to have your opinion here. > > Jörn > > >
