[Kommander-devel] KTextEditor in Kommander

[Eric Laffoon]

On Tuesday 05 September 2006 1:48 am, Andras Mantia wrote:
> On Tuesday 05 September 2006 11:09, Eric Laffoon wrote:
> > Thanks Andras, this is a big improvement. Unfortunately a few things
> > are not handled well yet. At least one may be a real headache but
> > most should be easy. I'm sure you're way faster at this than me...
>
> Well, it's only about writing the correct rules. ;-)
>
> > 1) functions that don't use method definitions lock highlighting
> > until something else comes along...
> > @dcop()
> > @global()
> > @setGlobal()
> > @exec()
> > @readSetting()...
> > These continue highlighting into the parenthesis and beyond.
>
> Should be fixed, but for some reason here the parenthesis are not bold,
> while for the rest are. I have no idea why, as the rule for them is
> exactly the same...

I could be missing something,  but this does not look fixed. Here's what 
works...
@functiongroup.function
The period ends the function group highlighting and everything is fine. Here's 
what doesn't work...
@global(counter)
Since it doesn't see a period it continues. Check out how this line is 
highlighted...
@Array.setValue(orientation, @global(counter), "landscape")
The entire line from the global on is green.

Here is my question. Can we write it with conditional logic so that it will 
end if there is a period, or if it encounters a left parenthesis or a space? 
Otherwise we could write the non modified functions as a separate list so 
they can have a different rule. This is actually pretty easy because the only 
group written this way is the Kommander group. Everything else uses the 
function group in the name with a dot syntax.
>
[...]

-- 
Eric Laffoon
Project Lead - kdewebdev module