Developer volunteers sign up here

[280Z28]

Hey I'm Sam. Just found this project and I'm very impressed with it. My primary text editor is ConTEXT and my primary development environment is Visual Studio 2005. Both of these have advantages and disadvantages and are closed source. I would love to help with this project in the hopes of finally having an editor that solves my greatest annoyances.

----------------
Basic note:

CodeBlocks is fast to start. This is so important to me that if it wasn't the case, I would have immediately uninstalled it and never thought to look at CB again. (Think JEdit)

----------------
Editor specific:

CB uses a powerful lexer engine, but (for right now at least) it is "hard to extend." There are not many lexer modules available for CB yet. I am interested in creating a Scintilla lexer and plugin that reads and uses ConTEXT highlighter files. They have several known limitations due to a fixed format and varying syntax between languages (Matlab single quotes for strings and for matrix inversion confuses it), but there are an enormous number of highlighter files readily available and it will ease transition for new users who expect highlighting in lots of different kinds of files.

Keyboard shortcuts are now configurable. This is another huge plus for me. Unfortunately mouse actions are still fixed. I have a patch for wxScintilla that allows a user preference for mouse wheel action while the ctrl key is pressed down. The default is zoom in/out, but I prefer pageup/pagedn. I'm not sure who to work with on core editor enhancements?

My next goal is making the cursor in windows point to the right while hovering over the line numbers about to make a line selection.

Another "level 1 priority" for me is fixing the rectangular paste action. I believe this is a Scintilla bug. Rectangular copy/paste done right is an amazing feature that you don't realize how handy it is until you really experience it. ConTEXT is the sole program I have seen that does it right.

A level 2 priority is implementing virtual space in the editor, or allowing positioning the cursor at an arbitrary location after the end of a line.

-----------------
Code styling features:

Line endings, hard/soft tabs, etc. are options that are project specific more than user specific. Makefiles have separate rules on this all together. A project should be able to include a set of such rules. That way everyone that works on a project I create can have the editor automatically set up to work with 4 space soft tabs and DOS endings regardless of what they are used to.



That's all I can think of for now. I'm willing to implement any of these.

Thanks,
Sam

[mandrav]

Hi Sam,

I am interested in creating a Scintilla lexer and plugin that reads and uses ConTEXT highlighter files.

why not make a simple converter then?

Keyboard shortcuts are now configurable. This is another huge plus for me. Unfortunately mouse actions are still fixed.

This is going to change. We 're not *that* happy with wxKeyBinder...

Don't be afraid to ask any questions you might have during the process

Yiannis.

[dbtsai]

I could help translate tradition Chinese ( locale zh_TW) usually use in Taiwan and HK.

where could I obtain the po file??

Sorry for my poor english   

[Olorin]

Hi all,
I can help in c++ programming, starting from non-invasive code cleanup and small fixes upto (once obtained a decent knowledge of CB internal architecture) active development.
I don't know if there are style guidelines... if yes, where can I find them? If not: what about proposing them? From the code I saw (rc2 sources) formatting is left to each programmer taste and this, for personal experience, can lead to misunderstandings (read as: bugs). I just ask because while walking through source files I could also reformat them (not a nice job, but cleaner formatting helps my comprehension of the code itself. I can post a proposal about this, if appreciated.

[rickg22]

Olorin: Just try to be consistent with existing source code.

If's should have { and } even if it's a one-liner. {'s should be just below the if/while.

My recommendation: Start searching for opened bugs in Sourceforge, and submit patches to fix said bugs. I became a C::B developer that way

[Olorin]

Thank you very much for your reply, rickg22.

Olorin: Just try to be consistent with existing source code.

I'll try... I raised the point as I couln't see any strong consistency, especially in regard to tab/spaces

If's should have { and } even if it's a one-liner. {'s should be just below the if/while.

That's my way of thinking, apart from the "{ below" side
I'll enclose one-liners in { and }, if I'll find any (apart from

Code

return

s, maybe), as I strongly believe that they can easily become sources of errors, especially in combination with indentation.

My recommendation: Start searching for opened bugs in Sourceforge, and submit patches to fix said bugs. I became a C::B developer that way

Ok, your suggestion is really welcome, but I think that I'll focus mainly on simple tasks for now.
Thanks again!

[thomas]

Mithrandir, you may find using the source code formatter plugin in ANSI mode very helpful.

[280Z28]

What he may be noticing is the wxSomething modules don't follow the same rules necessarily. wxScintilla uses a different style from the one you use.

[shikaku]

I will gladly help with Japanese translation.

[Olorin]

Mithrandir, you may find using the source code formatter plugin in ANSI mode very helpful.

Thanks for your suggestion (and for remembering me of my many names ), I'll give it a try.

I've seen other threads (eg. http://forums.codeblocks.org/index.php?topic=1642.0) that talks about (lack of) coding style guidelines... personally I don't really like to be forced to a particular scheme (especially if it's not my usual one , but I think that it is necessary in projects involving so many developers.
A description of how to effectively become a developer would be useful, too, unless this procedure is a first test of our skills . I've found this http://forums.codeblocks.org/index.php?topic=1636.0, but I fear that my attempt was not so succesfull (I suppose that one should never do this late at night .
May I suggest to insert one (or two) locked (or sticky?) topics baout this matters at the beginning of the Development forum? They would be quite useful and make development easier, faster and better.

[knue]

hi, I have allready intruoduced myself some time ago (October, the fifth).
I have not too much time but I can help to fix some bugs. I have allready started:

http://forums.codeblocks.org/index.php?topic=1645.msg11995;topicseen#msg11995

[280Z28]

Mithrandir, you may find using the source code formatter plugin in ANSI mode very helpful.

Thanks for your suggestion (and for remembering me of my many names ), I'll give it a try.

I've seen other threads (eg. http://forums.codeblocks.org/index.php?topic=1642.0) that talks about (lack of) coding style guidelines... personally I don't really like to be forced to a particular scheme (especially if it's not my usual one , but I think that it is necessary in projects involving so many developers.
A description of how to effectively become a developer would be useful, too, unless this procedure is a first test of our skills . I've found this http://forums.codeblocks.org/index.php?topic=1636.0, but I fear that my attempt was not so succesfull (I suppose that one should never do this late at night .
May I suggest to insert one (or two) locked (or sticky?) topics baout this matters at the beginning of the Development forum? They would be quite useful and make development easier, faster and better.

The Wiki is a better place for this since things are unlikely to change with time and the thing that is needed is a nice reference. That's what Wiki's are good at. A stickied thread with a link to the Wiki might be a good idea though.

[Olorin]

Wiki! Never thought about it...
Thanks for the hint!