Dark theme - contribution

[golgepapaz]

Yeah . Good work

[Alpha]

Now all 11 colour themes at the wiki page have screenshots.

@devs: The embedded .conf file makes this page rather large.  Should we upload it to SourceForge and/or SVN, and put a link on the wiki instead?

[oBFusCATed]

We need some way to make it user controlled. Someone could start a separate project on github or sf.net where all these themes could be stored.

[georger]

We need some way to make it user controlled. Someone could start a separate project on github or sf.net where all these themes could be stored.

While that doesn't happen, I've uploaded a new theme to the wiki page.
I am satisfied that now there 14 themes available, and I am content with the theme I chose for my own use (Modnokai Night Shift v2). I do not have plans for adding more themes in the foreseeable future.

[georger]

We need some way to make it user controlled. Someone could start a separate project on github or sf.net where all these themes could be stored.

While that doesn't happen, I've uploaded a new theme to the wiki page.
I am satisfied that now there 14 themes available, and I am content with the theme I chose for my own use (Modnokai Night Shift v2). I do not have plans for adding more themes in the foreseeable future.

Shame on me, I've added yet another theme to the wiki page...
@devs, any chance of this making it to trunk?

[oBFusCATed]

A theme can make it in trunk, only if it has been implemented for most of the languages we support.
A C/C++ only theme is useless most of the times.

[Alpha]

A future idea someone could consider, if they have the programming time, is to change lexers so instead of (or maybe in addition to) taking color parameters for each item, they take a variable name ex. "MainKeyword", "LightComment", "Operator",...
Then creating a new theme could be done for all languages by creating a new color set of definitions for the variables.

[georger]

A theme can make it in trunk, only if it has been implemented for most of the languages we support.
A C/C++ only theme is useless most of the times.

Ouch. I see Code::Blocks as a C/C++ IDE. How come "A C/C++ only theme is useless most of the times"?

There are 45 languages listed in Settings/Editor.../Syntax highlighting. It's a daunting task to create a new theme that supports "only", say, 15 of those. If by "most" you mean at least half, it becomes discouraging.

How about the dev team runs a poll to find out what languages people use most in Code::Blocks?

[oBFusCATed]

How come "A C/C++ only theme is useless most of the times"?

Let it say another way: we cannot ship it in the installation, because it will be incomplete.

There have been a user that have done a perl script that does a theme conversion.
See here for details: http://forums.next.codeblocks.org/index.php/topic,17896.0.html

[Ansem]

Looks very good. I had my own monokai theme but I've overwrote it after
installing another theme from here so the OPs advice about backing it up is
sound.

Here is a comparison between SublimeText's monokai theme and
this one. Scintilla's lexer seems indeed limited.

That light blue (or is it teal? I am colour blind.   ) colour for keywords
seem better suited but that's up to one's own taste I guess.

Hi, i like a lot the right theme! How can I do for install it on my codeblocks on linux?

[oBFusCATed]

You can't, because the parser/lexer/highlighter in SublimeEdit is different than the one we're using. Sorry.
You'll have to bug the Scintilla developers to improve their C++ lexers, until then we could do nothing.

[Ansem]

You can't, because the parser/lexer/highlighter in SublimeEdit is different than the one we're using. Sorry.
You'll have to bug the Scintilla developers to improve their C++ lexers, until then we could do nothing.

i can at least use the left theme? there is some script for it?

[oBFusCATed]

You can import it with the cb_share_config available in the CB's installation.

[Biplab]

First this

georger_br: Can you start a page on the wiki with your theme, so we can start collecting users supplied themes and to store them in a single place?

And then after the user painstakingly creates a wiki page it is deleted saying

A theme can make it in trunk, only if it has been implemented for most of the languages we support.
A C/C++ only theme is useless most of the times.

What is wrong with us? Can't the original page content be kept with a warning that it us a C/C++ only theme?

Seriously I don't get the rationale behind wiping that page clean. We are simply discouraging users to contribute to C::B improvement.

[Jenna]

First this

georger_br: Can you start a page on the wiki with your theme, so we can start collecting users supplied themes and to store them in a single place?

And then after the user painstakingly creates a wiki page it is deleted saying

A theme can make it in trunk, only if it has been implemented for most of the languages we support.
A C/C++ only theme is useless most of the times.

What is wrong with us? Can't the original page content be kept with a warning that it us a C/C++ only theme?

Seriously I don't get the rationale behind wiping that page clean. We are simply discouraging users to contribute to C::B improvement.

It was the user himself, who cleaned the wiki-page (see: http://wiki.codeblocks.org/index.php?title=Syntax_highlighting_custom_colour_themes&action=history).
I guess he was discouraged, because of Alpha's comment about c++-only themes.

But it's still in the wiki's history: http://wiki.codeblocks.org/index.php?title=Syntax_highlighting_custom_colour_themes&oldid=7656