|Re: text editor sample - status [message #237843 is a reply to message #237809]
||Sun, 12 August 2007 12:31
| Nils Kaiser
Registered: July 2009
Well I get more and more the impression than this issue is just not
getting any attention... I remember having read someone complained about
too less help from the community. On the other hand, I do find it very
difficult to get into code of the example. This is due to
in-developmnent code as example and lack of documentation (very few
explanations in bugzilla or in code itself).
I made a first step on collecting the information around bugzilla and
the code base.
What I am asking for? Is it possible for someone who has understanding
of the code base to comment on bug 74784, adding the status of the text
support/example and sorting the different issues (bugzilla, code todos)
I provided here?
I believe that providing more information on the example could generate
more returns from the community.
TODO : cleanup any pending styles? TextTool.java
TODO : during a swipe, the viewer should not be firing selection changes
the whole time. SelectionRangeDragTracker.java
TODO : optimize by ensuring that runs in the same container don't cause
TODO : Pratik you should expose the text location first (it might not
be visible) GraphicalTextViewer.java
TODO : should this be all pending styles or just the recently set?
TODO : should this be reflexive? Container.java
TODO : uncomment this when this class moves to the same package as
TODO :Pratik change all these setSelection() methods so that they
don't affect GraphicalTextViewer.java
TODO :Pratik Hack. This shouldn't be here. CommandStack should be
doing this automatically. GraphicalTextViewer.java
TODO :Pratik remove getSelectionRange and all references to it. Use
TODO :Pratik remove setSelectionRange and all references to it. Use
TODO :Pratik StyleService cannot be final TextTool.java
TODO :Pratik this should never happen TextFlowPart.java
I also collected the info from the bugtracker:
Graphical Text support - https://bugs.eclipse.org/bugs/show_bug.cgi?id=74784
Caret not revealed when typing in text example -
Navigation problems with the text package -
insert key doesn't work properly in the text example -
GraphicalTextviewer needs API to show SelectionRange -
GraphicalTextviewer needs API to show SelectionRange
TextEditParts need to communicate additional caret information -
Need to introduce post-selection delay in the text example -
[text] support prev/next paragraph PAGE_UP, PAGE_DOWN -
Refactor code in TextEditPart#getTextLocation() -
[text] Add support to copy/cut/paste text -
[text] Need to introduce concept of SelectionProcessor -
[text] Create TextSelectionModel and related ISelection subclass -
Text Editing status displayed in status bar -
Selecting text in WSIWIG example makes text disappear -
Some of the bugs (106416: insert key doesn't work properly in the text
example) seem to be partly fixed but no comment was made on the bug
Some other bugs contain code (135345: Selecting text in WSIWIG example
makes text disappear), can it be used?
Nils Kaiser schrieb:
> I am thinking about building an application that requires me structured
> text input (drag and drop of paragraphs, nestable groups of paragraphs,
> citations ). I discovered the text sample from GEF to be very useful input.
> However I am curious if somebody is still working on the sample. There
> seem to be some bugs (disappearing caret, loosing ability of changing
> font size), and a lot of the methods used are deprecated. I had a look
> at CVS and many of the files were not touched since a long time... I
> also know I am not the first one asking this.
> 1) can the errors be fixed by someone not knowing the internals ;)
> 2) is the architecture of the sample good as base for the stated project
> (unsure due to the deprecated methods)
> 3) will the sample be updated someday?
Powered by FUDForum
. Page generated in 0.04519 seconds