stippi
commented
9 years ago Hi again,
I have begun implementing. My thoughts were that it is best to design a builder pattern. The core builder implementation would only work with interfaces, and there would be a default implementation which constructs a document model. As such, it would be possible to connect a completely different document model directly to the builder, parsing an RTF straight into an unknown document model. This would be achieved by writing thin wrappers implementing the interfaces defined by RTF Parser Kit in terms of the foreign document model. At the same time, the default RTF Parser Kit document model implementation could be used to transfer a foreign model and then write an RTF. But maybe there is an even better way, I have not yet started on that part. For now, I have text landing in the right destinations and will start looking into styling next.
Regards, -Stephan
joniles
Hi Jon,
thanks for making this nice piece of code. I am trying to use it in my project, but the StandardRtfParser is still too low level for my purposes. I am pondering whether to contribute to your project and start on an RTF document model, especially, since it would allow to create an RTF writer as well. I have some ideas how to approach this, but I would love to discuss with you first and find out what you had in mind. Do you think the issue tracker is the ideal place for discussion? If so we could use this issue, otherwise we could switch to other means of communication. For example, I think chatting in IRC could be beneficial, then noting the result back here. My nick on Freenode is stippi.