Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [Dltk-dev] Re: script editor syntax coloring..

For Ruby (for TCL there are similar classes) the TODO tasks are processes by the following classes:

- page in preferences to configure keywords
org.eclipse.dltk.ruby.internal.ui.preferences.RubyTodoTaskPreferencePage

- parse the sources and create task markers (it is called from the ValidatorBuilder)
org.eclipse.dltk.ruby.internal.parser.RubyTodoTaskAstParser

- highlighting is done via
org.eclipse.dltk.ui.text.ScriptCommentScanner

Regards,
Alex

----- Original Message -----
From: "Johan Compagner" <jcompagner@xxxxxxxxx>
To: "DLTK Developer Discussions" <dltk-dev@xxxxxxxxxxx>
Sent: Thursday, August 7, 2008 10:12:27 PM GMT +06:00 Almaty, Novosibirsk
Subject: Re: [Dltk-dev] Re: script editor syntax coloring..



thx. 

i just implemented an extention point so that plugins can contribute keywords/tokens or rules 
I use that extention point for our own keywords are rules and it works perfectly 

Except 1 and that is that i like to color this better: 

// FIXME: xxxx 
// TASK: xxx 

that kind of stuff.. but those are now taken by the EndLineRule on // 

i would like that those kind of things would auto go into the task list that would also be very nice to have. 

johan 


johan 



On Fri, Jul 11, 2008 at 7:06 PM, Alexey Panchenko < alex@xxxxxxxxx > wrote: 


Hi, 

TCL collects keywords from several plugins using TCL-specific extension points. 
tcl + xotcl + itcl 

IMHO it is better to be kept language specific. In the future this should be solved by introducing language dialects/versions. 

Alex 




----- Original Message ----- 
From: "Johan Compagner" < jcompagner@xxxxxxxxx > 
To: "DLTK Developer Discussions" < dltk-dev@xxxxxxxxxxx > 
Sent: Friday, July 11, 2008 10:54:54 PM GMT +06:00 Almaty, Novosibirsk 
Subject: [Dltk-dev] Re: script editor syntax coloring.. 

They are not really common those are specific to our ide (servoy) this 
could be solved if we could contribute through an extention keywords 
with defaul colors that users then could override if needed. 

Or the end users can just create a list of keywords and there colors 
on there own (but then it will also be nice that a plugin can 
contribute, set a preference) 

On 7/11/08, Jae Gangemi < jgangemi@xxxxxxxxx > wrote: 
> it can be done, take a look at the JavascriptCodeScanner. if these are 
> 'common' keywords that everyone would want colored, you can add the keywords 
> to the JavaScriptKeywords class and things should just work. 
> 
> On Fri, Jul 11, 2008 at 3:54 AM, Johan Compagner < jcompagner@xxxxxxxxx > 
> wrote: 
> 
>> Hi, 
>> 
>> how easy would it be to define your own keywords in the syntax coloring 
>> preference panel with there own color? 
>> Now we have 3 types and some sub types. But they are all fixed.. 
>> We have a lot of common prefixes like "plugins." or "elements" that kind 
>> of 
>> stuff and we also would like to color those 
>> 
>> i havent looked at the code yet but would this be a nice addition to the 
>> core? 
>> 
>> johan 
>> 
>> 
>> _______________________________________________ 
>> dltk-dev mailing list 
>> dltk-dev@xxxxxxxxxxx 
>> https://dev.eclipse.org/mailman/listinfo/dltk-dev 
>> 
>> 
> 
> 
> -- 
> -jae 
> 
_______________________________________________ 
dltk-dev mailing list 
dltk-dev@xxxxxxxxxxx 
https://dev.eclipse.org/mailman/listinfo/dltk-dev 
_______________________________________________ 
dltk-dev mailing list 
dltk-dev@xxxxxxxxxxx 
https://dev.eclipse.org/mailman/listinfo/dltk-dev 


_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev


Back to the top