On 24 juin 08, at 11:53, Venkatesh Nandakumar wrote:
Hi Fabio, Malaka,
After my discussion with Stephane, we've decided that Malaka should continue with improving the core editor as such.. That is, better syntax highlighting and stuff..
What do you refer to when you say "stuff"?
I've implemented a bit of ContentOutline Page, (that shows the overall view of the page, like titles, paragraphs overview etc), as a TreeViewer implementation.
For now, I'll try to integrate the present editor with xeclipse extension. Then, I'd try to introduce wikimodel support, that is, conversion of one syntax to another syntax. For this, I think we'll have to code editors for all other syntaxes too, since after conversion, we'll have to support editing in that syntax.. right??
Actually this is exactly what the GSoc project is about (not just plain syntax highlighting). So this might be an issue because this is exactly what Malaka is supposed to do. Currently he is investigating the integration of the new rendering infrastructure into the Eclipse framework so that the output XDOM will be the base for all the syntax highlighting, suggestions etc. Malaka, could you please report the status of your investigation and the problems you encountered? I still have the feeling that you are both working on the very same project, with a big overlap (i.e., the "stuff" you mentioned before that should be done by Malaka is exactly what you are working on). I propose that Malaka continues to work on the integration of the rendering infrastructure as the source of structural information, exchanging as much as possible on the list. If he succeeds this means that your code will need to be refactored to conform to the new architecture. If he doesn't then he will improve what you have been doing. I don't see any other solution to reconcile your work with the GSoC. WDYT? Cheers, Fabio