And do not forget that we got rtf package contribution. It just uses JavaCC grammar with not acceptable license. So I would say that we need to create JavaCC grammar from scratch.
SY, Alexey 2008/3/31, Alexei Zakharov <[EMAIL PROTECTED]>: > Just a few words in addition to that Alexei has already said. > > > Implementation will fully cover functionality of Sun implementation of RTF > > parser, and, if possible, supersede it adding support of latest versions of > > RTF specification. > > Sun implementation most likely supports (or is a subset of) RTF v1.7 > or below. So it probably make sense to set this spec. version as an > intermediate goal. Of course it depends on differences between 1.7 and > 1.9 (222 pages of text vs. 283 pages). If differences are minimal then > we may probably avoid this step. > > I also support Alexei's point 5: it would be nice if you can find some > RTFEditorKit demo somewhere. I heard that one of the Sun's standard > demos uses it but I was unable to find anything like this in JDK 1.5 > demos. May be you'll be more lucky. > > As for the rest of your proposal - IMO it looks good. So I'm +1 for submit. > > Regards, > Alexei > > > 2008/3/30, Aleksey Lagoshin <[EMAIL PROTECTED]>: > > Thanks for comments. I've taken them into account. > > > > 2008/3/30, Alexei Fedotov <[EMAIL PROTECTED]>: > > > > > > > > Aleksey, > > > Great job. Here are few comments: > > > > > > 1. > > > > at worst, cover the functionality of Sun's RTF parser, the first goal > > > will be to conduct black-box tests on Sun's implementation of > > RTFEditorKit. > > > I believe "worst" is not good for application, let's be positive. I > > > suggest we set a goal "to conduct black box testing of Sun > > > implementation, create a grammar under Apache license for one of the > > > popular parser generators, and create RTFEditorKit toolkit > > > implementation based on that grammar. The side goal of exposing such > > > grammar under open source license would help any java program to > > > conduct RTF parsing." > > > > > > 2. > > > > Test cases for all created Java classes and documentation. > > > I believe testing classes is enough. > > > > > > 3. > > > Please, add the parser from Eclipse team to you list. While we may not > > > want the third parser in Harmony, but this consideration might be weak > > > compared to the advantages of that parser advantages. BTW I believe we > > > are using ecj already for hdk. > > > > > > 4. > > > It seems that "" around URLs are not needed to get them work on Apache > > > Wiki. > > > > > > 5. May be replace "mid-term evaluation" with "enabling <some test> > > > with RTF editor"? I've heard Sun has some RTF demo. > > > > > > Thank you for your effort! > > > > > > > > > On Sun, Mar 30, 2008 at 3:28 PM, Aleksey Lagoshin <[EMAIL PROTECTED]> > > > wrote: > > > > Here is my application for harmony-swing-rtf project. It would be great > > > if > > > > someone read it and gave advice on how to improve it. > > > > > > > > > > > http://wiki.apache.org/general/AlekseyLagoshin/GSoC2008/harmony-swing-rtf > > > > > > > > Many thanks. :) > > > > -- > > > > Thanks, > > > > Aleksey > > > > > > > > > > > > > > > > > > > -- > > > With best regards, > > > > > > Alexei > > > > > > > > > > > > > -- > > Thanks, > > > > Aleksey > > >
