Dark theme - contribution

[georger_br]

I really like C::B and have always wanted it to have a nice dark theme, so I pieced one together from Monokai (Sublime Text 2, Eclipse) and Resesif (Xcode). I really like the end result. I use it along with these settings:
1) General Settings/Editor settings/Font is Consolas 12;
2) General Settings/Editor settings/Other options/Highlight line under caret is enabled;
3) Margins and caret/Caret/Style is Line, Width is 3, and Colour is red (255 0 0).

Those interested may import this with CB Share Config (rename from .txt to .conf). It goes without saying that you should first back up your current configuration file!

Georger

[golgepapaz]

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.

[georger_br]

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 just changed the keywords to blue, and I think it looks better now. I have attached the updated color theme. To those that have already downloaded, here goes the changelog:

1) Keyword
From 249 38 114
to 38 249 173

2) User keyword
From 166 226 46
to 249 38 114

3) Preprocessor
From 166 226 46
to 249 38 114

4) Operator
From 38 249 173
to 166 226 46

I don't think Scintilla's lexer is limited, rather it seems that ST2's lexer is really sophisticated - it can parse variable and function names, constants, classes, and a number of other tokens.

Enjoy!

[georger_br]

I've attached a new, final (?) version with updated colours for comment lines, strings, and numbers.

[oBFusCATed]

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?

[georger_br]

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?

Hi oBFusCATed,
Sure. Problem is, upon trying to log in with my username and password (same as the forum), I get the following error:

"Login error
You have not specified a valid user name."

Could it be the underscore?

[oBFusCATed]

Don't know... Probably Morten and Jens could answer this question.

[Jenna]

If I remember correctly the underscore is in fact the problem.
As far as I know you can not change the login-name yourself (just the shown username), it can be done by an admin, but would reset your passord and generate a new one, which will be sent to your mail-address, so it must be valid.
So changing the name might not work without the "help" of an admin.

If you want me to do that, please post it here or sent me a pm with the new name.

[georger]

It's on the wiki.
As the wiki does not allow uploading files with the .conf extension (neither does the forum, but it will accept a .txt), I'll upload the colour theme file here and point the wiki back to this thread so that registered forum users may download it.

To those coming from the wiki: log in to the forum, download the .txt file attached to this reply, change its extension to .conf and you'll be able to import it into Code::Blocks with CB Share Config.

[Jenna]

Unfortunately the attachements get deleted from time to time, so the theme will be lost.
If there is no other way to store it in the wiki or on pastebin or something like that, I can upload it to my server and post the download link here.

[oBFusCATed]

We need some kind of system, where users can upload themes

[georger]

We need some kind of system, where users can upload themes

For the time being, I pasted the theme right into the wiki page.

[georger]

We need some kind of system, where users can upload themes

For the time being, I pasted the theme right into the wiki page.

Now the config file at the wiki page has the following colour themes:
- Bright Yellow (by hongwenjun)
- Dark Gray (by hongwenjun)
- Idel (by hongwenjun)
- Modnokai (my modified version of Wimer Hazenberg's Monokai)
- Oblivion (by hongwenjun)
- Solarized Dark (by Ethan Schoonover)
- Solarized Light (by Ethan Schoonover)
- Son of Obsidian (by Eric Millin)
- Sublime (by hongwenjun)
- Vim (by hongwenjun)

Only Modnokai has a screenshot.

[georger]

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

[BlueHazzard]

thank you for the work!

[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.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

[Biplab]

Thanks Jens for clearing this.

I request you to restore it for the benefit of other users. An empty page is creating confusion and a poor impression of us all.

[Jenna]

Thanks Jens for clearing this.

I request you to restore it for the benefit of other users. An empty page is creating confusion and a poor impression of us all.

It's there again, with a note, that the themes are only usable with the C/C++-lexer.

[georger]

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.

"the user himself" here. I removed the content because I was discouraged by oBFusCATed's (not Alpha's), a developer, statement.

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

Unfortunately for me, MediaWiki only allows admins to delete a page once and for all - so I couldn't purge the page forever, which I would have done if I could. All I could do was overwrite the old content.

I politely request that the page be purged. Even though I had to answer "C++" to the question "What language Code::Blocks is designed for? (letter,2x sign):" while registering to write this reply, I don't really feel that contributions that only apply to C++ are welcomed by the developers.

To make myself perfectly clear: please, PLEASE purge the page once and for all, beyond recovery, like it never existed in the first place. I left Code::Blocks after this event, and I am sincerely annoyed that the content that I created and was dismissed was brought back.

[...] is creating [...] a poor impression of us all.

That I can agree with.

Now off to delete the forum membership.

[oBFusCATed]

"the user himself" here. I removed the content because I was discouraged by oBFusCATed's (not Alpha's), a developer, statement.

I guess, I've been misunderstood here, probably because English is not my native language.
What I've said is that we can't include the themes in the official C::B source code until they are finished or at least have themes for the more popular languages.
I have nothing against the page on the wiki.
Sorry if you've felt offended, but this was not the intend...

[Jenna]

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.

"the user himself" here. I removed the content because I was discouraged by oBFusCATed's (not Alpha's), a developer, statement.

Both are developers, but you are right, it was oBFusCATed's commment I meant.
Why are you discouraged, if one developer of the whole team says, it does not make sense to add it to trunk ?
If there are two different opinions, people should start a discussion, not run away.

It would be a good point to start seriously thinking about a theming engine for C::B.
Because theming is not only interestant for users who just don't like the default look, but also for user with handicaps or for systems that are to be used in places with problematic light conditions.

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

Unfortunately for me, MediaWiki only allows admins to delete a page once and for all - so I couldn't purge the page forever, which I would have done if I could. All I could do was overwrite the old content.

I politely request that the page be purged. Even though I had to answer "C++" to the question "What language Code::Blocks is designed for? (letter,2x sign):" while registering to write this reply, I don't really feel that contributions that only apply to C++ are welcomed by the developers.

To make myself perfectly clear: please, PLEASE purge the page once and for all, beyond recovery, like it never existed in the first place. I left Code::Blocks after this event, and I am sincerely annoyed that the content that I created and was dismissed was brought back.

I'm not sure if any of the forum admins can do that (except from our project leader and server owner, who has only been very, very rarely here in the last years).
I would be happy, if you would decide to leave it there for the benefit of other users.

[...] is creating [...] a poor impression of us all.

That I can agree with.

Why do you think lowly of a whole project, if you do not agree with the opinion of one developer.

Now off to delete the forum membership.

[georger]

Why are you discouraged, if one developer of the whole team says, it does not make sense to add it to trunk ?
If there are two different opinions, people should start a discussion, not run away.

I am fine with one developer stating that it does not make sense to add something to trunk. It is well within a developer's right and duty to do so.
I am also fine with one developer stating that a piece of work is useless. Even if I think the wording could be improved, it still means that the developer assessed the contribution and found it inadequate.
I am not fine, however, with bringing back someone else's work that was deemed useless.

The "one developer of the whole team" was the only one that expressed his opinion. There was no discussion after my reply to the developer's statement. No other developer commented on it after the work was considered useless. In my view, he spoke for the whole team.

I'm not sure if any of the forum admins can do that (except from our project leader and server owner, who has only been very, very rarely here in the last years).
I would be happy, if you would decide to leave it there for the benefit of other users.

It's not up to me to decide. I don't know what license covers the content published in your project's wiki. What I do know is that, if at all possible, I would like that the content that I wrote be removed, and that the removal be irreversible.

Why do you think lowly of a whole project, if you do not agree with the opinion of one developer.

Again, one sole developer expressed his views on my "contribution". You might think otherwise, but as far as I'm concerned, he spoke for the project.

Now off to delete the forum membership again, and for good this time.

[Biplab]

To make myself perfectly clear: please, PLEASE purge the page once and for all, beyond recovery, like it never existed in the first place. I left Code::Blocks after this event, and I am sincerely annoyed that the content that I created and was dismissed was brought back.

I disagree. I appreciate your effort in working on and compiling a list of themes. A particular developer may have said it cant be included in the trunk. But there is a reason behind that. Probably it was a miscommunication. I'm sure a lot of users and developers find your work interesting & useful.

If there are two different opinions, people should start a discussion, not run away.

Unfortunately Jens we do discourage both users and developers. I, personally, have faced several strong objections from admins several times. I even wrote a long rant to post 5 months ago (which I didn't post) due to a "silly" comment on one of my commit from one of the admins. That rant summarized my frustrations I faced in past 7 years. I do not wish to elaborate here, but I'm ok to discuss it separately.

Likewise we do discourage a number of users who wish to contribute. We also discourage a number of newbie users by asking them to shut-up and stop asking newbie questions. I know there is a reason behind that. But if admins wishes, we can overcome that difficulty.

It would be a good point to start seriously thinking about a theming engine for C::B.

I think a better question to ask is do we have a roadmap? Code::Blocks project is presently moving like a ship without any steering wheel.

• Features are decided randomly and then implemented.
• Release dates are often decided as - "we'll release when we deem necessary" or "lets package next nightly and rename as stable release"
• Plugins are often included without deciding a maintainer.
• We have plugins that describes itself as "For the anal but lazy." Sound cool but no one knows who maintains it.
• We drop platform support randomly. Just to avoid #ifdef statements we bump wxwidgets version requirement.
• SDK version is changed at will.

The list goes on and on. Seriously we should pause and think about it.


P.S.: Just to clear myself I'm not accusing Jens of the above. Rather it is to the entire project team including myself.

[dmoore]

@georger: if it isn't abundantly clear by now, WE like your contribution and want to keep it on the wiki. Eventually someone will take your work and figure out a way to make those themes work for other languages, and when that happens it will make it into trunk. So please stop requesting that we remove it over a misunderstanding. It was oBFusCATed who recommended you puts these on the wiki in the first place, so he clearly likes what you've done too.

[Ansem]

thanks for the wiki!
I have only one big problem: where i must import the file? i have ubuntu 12.04, and i don't find the path

[oBFusCATed]

cb_share_config should automatically detect, where your default.conf is located (~/.codeblocks/default.conf usually).
But theme importing is better supported with a night build. 12.11 is rather limited in this regard, so I advise you to try a night build.

[Ansem]

thanks! now all works perfectly!
in any case, i think that a native black theme will be perfect.
For example i love ninja ide for his layoults (black theme and all setting to the left,and not on the top).

[SegmentationFault]

Just transferred over from Orwell Dev C++ to CodeBlock and stumbled upon this thread on themes and I gotta say they are awesome! One thing that did get me confused was that when I was doing the transfer process of themes the program would not detect where my default.conf was. I ended up have to manually go to it, but no big issue.