12 Jun
2008
12 Jun
'08
10:48 a.m.
Hi Venkatesh,
On Jun 12, 2008, at 10:40 AM, Venkatesh Nandakumar wrote:
[snip]
1. Syntax Highlighting, to a large extent, though
there have been
problems, as pointed out by Malaka, *bold~~combined~~bold* doesn't
give
the required effect, and secondly, the complex use of '*' in the wiki
syntax makes it a bit difficult to differentiate between actual *bold*
usage versus listing uses, maybe we would have to create own custom
regex-based rules for it later. For other tags, its been simple and
straightforward.
Do you really need to parse it yourself? We have a parser in charge of
doing this so you don't have to care at all about these problems.
That's unless the system you use for syntax highlighting uses regexs
(in which case I think it should be changed).
Thanks
-Vincent
2. Content Proposal, type <the first character of syntax> and drop-
down
of possible syntaxes, when selected, moves cursor to correct
position of
entry of text. Key-combination also brings down the menu. Also valid
for
applying styles to selected text.
3. As a minor addition, context information. ( though very partially)
4. Indentation strategies (very partial implementation till now)
5. minor - Hyperlink detection and linking within {quote} and a
hyperlinks
I've also divided the document into partitions,(as of now,
pre,code,table,<dl> and default) for possibility of different content
proposal/content assist/syntax highlighting.
I have not integrated any of the code with the xeclipse plugin's code.
What I have created as of now, is just another eclipse-plug-in.
Venkatesh