Hey all,

as I already posted in D.ide newsgroup, I am working on an improvement for D support in the codeblocks IDE.
Now I've made a patch and posted it in the codeblocks forum:
http://forums.codeblocks.org/index.php/topic,12246.0.html
It would be cool, If there are some D user, whow can try out and test this patch.


What should be done:
- check out the newest sourcecode of codeblocks
  http://svn.berlios.de/svnroot/repos/codeblocks/trunk
- apply the patch mentioned above
- test the D features and report any bug, comments and wishes in the same thread as the patch. (remember, this patch is only a start!)
- and of course feel free to send new patches yourself!!


greets
nocide

On 29/03/10 08:24, Matthias Pleh wrote:
> Hey all,
>
> as I already posted in D.ide newsgroup, I am working on an improvement
> for D support in the codeblocks IDE.
> Now I've made a patch and posted it in the codeblocks forum:
> http://forums.codeblocks.org/index.php/topic,12246.0.html
> It would be cool, If there are some D user, whow can try out and test
> this patch.
>
>
> What should be done:
> - check out the newest sourcecode of codeblocks
> http://svn.berlios.de/svnroot/repos/codeblocks/trunk
> - apply the patch mentioned above
> - test the D features and report any bug, comments and wishes in the
> same thread as the patch. (remember, this patch is only a start!)
> - and of course feel free to send new patches yourself!!
>
>
> greets
> nocide


Hey cool! Does it support D2?

Am 28.03.2010 23:54, schrieb Bernard Helyer:
> On 29/03/10 08:24, Matthias Pleh wrote:
>> Hey all,
>>
>> as I already posted in D.ide newsgroup, I am working on an improvement
>> for D support in the codeblocks IDE.
>> Now I've made a patch and posted it in the codeblocks forum:
>> http://forums.codeblocks.org/index.php/topic,12246.0.html
>> It would be cool, If there are some D user, whow can try out and test
>> this patch.
>>
>>
>> What should be done:
>> - check out the newest sourcecode of codeblocks
>> http://svn.berlios.de/svnroot/repos/codeblocks/trunk
>> - apply the patch mentioned above
>> - test the D features and report any bug, comments and wishes in the
>> same thread as the patch. (remember, this patch is only a start!)
>> - and of course feel free to send new patches yourself!!
>>
>>
>> greets
>> nocide
>
>
> Hey cool! Does it support D2?

yep!
Just try it out and report any bugs!

On Sun, 28 Mar 2010 16:24:30 -0300, Matthias Pleh <matthias.pleh@gmx.at> wrote:
> Hey all,
>
> as I already posted in D.ide newsgroup, I am working on an improvement for D support in the codeblocks IDE.
> Now I've made a patch and posted it in the codeblocks forum:
> http://forums.codeblocks.org/index.php/topic,12246.0.html
> It would be cool, If there are some D user, whow can try out and test this patch.
>
>
> What should be done:
> - check out the newest sourcecode of codeblocks
>    http://svn.berlios.de/svnroot/repos/codeblocks/trunk
> - apply the patch mentioned above
> - test the D features and report any bug, comments and wishes in the same thread as the patch. (remember, this patch is only a start!)
> - and of course feel free to send new patches yourself!!
>
>
> greets
> nocide

This looks like a great start. However, I'm not sure which patches I should apply. The thread has couple of patches by 'bernard' but I can't seem to find the main patches by nocide. I'm probably blind, but could you point out where the links should be located? Thanks.

Am 29.03.2010 18:51, schrieb Robert Jacques:
> On Sun, 28 Mar 2010 16:24:30 -0300, Matthias Pleh <matthias.pleh@gmx.at>
> wrote:
>> Hey all,
>>
>> as I already posted in D.ide newsgroup, I am working on an improvement
>> for D support in the codeblocks IDE.
>> Now I've made a patch and posted it in the codeblocks forum:
>> http://forums.codeblocks.org/index.php/topic,12246.0.html
>> It would be cool, If there are some D user, whow can try out and test
>> this patch.
>>
>>
>> What should be done:
>> - check out the newest sourcecode of codeblocks
>> http://svn.berlios.de/svnroot/repos/codeblocks/trunk
>> - apply the patch mentioned above
>> - test the D features and report any bug, comments and wishes in the
>> same thread as the patch. (remember, this patch is only a start!)
>> - and of course feel free to send new patches yourself!!
>>
>>
>> greets
>> nocide
>
> This looks like a great start. However, I'm not sure which patches I
> should apply. The thread has couple of patches by 'bernard' but I can't
> seem to find the main patches by nocide. I'm probably blind, but could
> you point out where the links should be located? Thanks.


Hello Robert,

you have to log in to see the attached files.
So just register and login :)
Ther are 2 files attached in the 1.post.
* d_win_v2.patch
* d_nix_v2.patch   -> for *nix (it's really the same, just *nix lineendings)

If you have further questions, don't hesistate to ask again!

greets
nocide

On Mon, 29 Mar 2010 16:41:52 -0300, Matthias Pleh <matthias.pleh@gmx.at> wrote:

> Am 29.03.2010 18:51, schrieb Robert Jacques:
>> On Sun, 28 Mar 2010 16:24:30 -0300, Matthias Pleh <matthias.pleh@gmx.at>
>> wrote:
>>> Hey all,
>>>
>>> as I already posted in D.ide newsgroup, I am working on an improvement
>>> for D support in the codeblocks IDE.
>>> Now I've made a patch and posted it in the codeblocks forum:
>>> http://forums.codeblocks.org/index.php/topic,12246.0.html
>>> It would be cool, If there are some D user, whow can try out and test
>>> this patch.
>>>
>>>
>>> What should be done:
>>> - check out the newest sourcecode of codeblocks
>>> http://svn.berlios.de/svnroot/repos/codeblocks/trunk
>>> - apply the patch mentioned above
>>> - test the D features and report any bug, comments and wishes in the
>>> same thread as the patch. (remember, this patch is only a start!)
>>> - and of course feel free to send new patches yourself!!
>>>
>>>
>>> greets
>>> nocide
>>
>> This looks like a great start. However, I'm not sure which patches I
>> should apply. The thread has couple of patches by 'bernard' but I can't
>> seem to find the main patches by nocide. I'm probably blind, but could
>> you point out where the links should be located? Thanks.
>
>
> Hello Robert,
>
> you have to log in to see the attached files.
> So just register and login :)
> Ther are 2 files attached in the 1.post.
> * d_win_v2.patch
> * d_nix_v2.patch   -> for *nix (it's really the same, just *nix lineendings)
>
> If you have further questions, don't hesistate to ask again!
>
> greets
> nocide

Thanks. I got a build working and have tested it out. It seems that you've made a substantial change to the default syntax highlighting, both in the terms you use and their settings. Now, most of them I can fix to how I want, but the normal 'selected' settings are substantially better and more complex than a simple foreground and background color. Also, I'd strongly recommend keeping the current code::block standard highlighting if you're planning to have your trunk merged into the mainline tree.

On Tue, 30 Mar 2010 20:21:02 -0300, Robert Jacques <sandford@jhu.edu> wrote:
> On Mon, 29 Mar 2010 16:41:52 -0300, Matthias Pleh <matthias.pleh@gmx.at> wrote:
>
>> Am 29.03.2010 18:51, schrieb Robert Jacques:
>>> On Sun, 28 Mar 2010 16:24:30 -0300, Matthias Pleh <matthias.pleh@gmx.at>
>>> wrote:
>>>> Hey all,
>>>>
>>>> as I already posted in D.ide newsgroup, I am working on an improvement
>>>> for D support in the codeblocks IDE.
>>>> Now I've made a patch and posted it in the codeblocks forum:
>>>> http://forums.codeblocks.org/index.php/topic,12246.0.html
>>>> It would be cool, If there are some D user, whow can try out and test
>>>> this patch.
>>>>
>>>>
>>>> What should be done:
>>>> - check out the newest sourcecode of codeblocks
>>>> http://svn.berlios.de/svnroot/repos/codeblocks/trunk
>>>> - apply the patch mentioned above
>>>> - test the D features and report any bug, comments and wishes in the
>>>> same thread as the patch. (remember, this patch is only a start!)
>>>> - and of course feel free to send new patches yourself!!
>>>>
>>>>
>>>> greets
>>>> nocide
>>>
>>> This looks like a great start. However, I'm not sure which patches I
>>> should apply. The thread has couple of patches by 'bernard' but I can't
>>> seem to find the main patches by nocide. I'm probably blind, but could
>>> you point out where the links should be located? Thanks.
>>
>>
>> Hello Robert,
>>
>> you have to log in to see the attached files.
>> So just register and login :)
>> Ther are 2 files attached in the 1.post.
>> * d_win_v2.patch
>> * d_nix_v2.patch   -> for *nix (it's really the same, just *nix lineendings)
>>
>> If you have further questions, don't hesistate to ask again!
>>
>> greets
>> nocide
>
> Thanks. I got a build working and have tested it out. It seems that you've made a substantial change to the default syntax highlighting, both in the terms you use and their settings. Now, most of them I can fix to how I want, but the normal 'selected' settings are substantially better and more complex than a simple foreground and background color. Also, I'd strongly recommend keeping the current code::block standard highlighting if you're planning to have your trunk merged into the mainline tree.

And one more thing, it doesn't appear that the -g option when linking in debug mode is working.

>>
>> Thanks. I got a build working and have tested it out. It seems that you've made a substantial change to the default syntax highlighting, both in the terms you use and their settings. Now, most of them I can fix to how I want, but the normal 'selected' settings are substantially better and more complex than a simple foreground and background color. Also, I'd strongly recommend keeping the current code::block standard highlighting if you're planning to have your trunk merged into the mainline tree.
>
> And one more thing, it doesn't appear that the -g option when linking in debug mode is working.


Thanks for your report!

to 1.)
I haven't changed any code for the lexer (It's anyway not code from
codeblocks but
rather from scintilla)
I only have added more tags in the xml-file and  have changed the colors.
But this is only a draft. The most colors was taken from the examples on the
DigitalMars Page,
couse I think this is rather the official standard for D.
I also don't understand, why we should take the same colors, as it is used
in C++ ??
But feel free to send me your version (lexer_d.xml) or a description how you
want it and I would have a look at it.

I have also tried a version with 8 different keywordgroups (as it is in
Poseidon) and different
colors for normal-string, raw-string, and so on ...
but for my taste this is too much, I like it simple.

to2.)
which OS/compiler?

On Wed, 31 Mar 2010 03:34:00 -0300, Matthias Pleh <matthias.pleh@ltw.at> wrote:

>
>>>
>>> Thanks. I got a build working and have tested it out. It seems that
>>> you've made a substantial change to the default syntax highlighting,
>>> both in the terms you use and their settings. Now, most of them I can
>>> fix to how I want, but the normal 'selected' settings are substantially
>>> better and more complex than a simple foreground and background color.
>>> Also, I'd strongly recommend keeping the current code::block standard
>>> highlighting if you're planning to have your trunk merged into the
>>> mainline tree.
>>
>> And one more thing, it doesn't appear that the -g option when linking in
>> debug mode is working.
>
>
> Thanks for your report!
>
> to 1.)
> I haven't changed any code for the lexer (It's anyway not code from
> codeblocks but
> rather from scintilla)
> I only have added more tags in the xml-file and  have changed the colors.
> But this is only a draft. The most colors was taken from the examples on the
> DigitalMars Page,
> couse I think this is rather the official standard for D.
> I also don't understand, why we should take the same colors, as it is used
> in C++ ??
> But feel free to send me your version (lexer_d.xml) or a description how you
> want it and I would have a look at it.

First, the normal code::block selector uses smart colors which are based upon the underlying text color, etc. Essentially, it only changes the background color (like many other editors) and doesn't change the foreground color. This makes selection easier to read and extend. It also doesn't play havoc with code::blocks' thread search feature.
Second, languages don't have color conventions, IDEs do. Code::blocks is different from Visual Studio which is different from Scintilla ad nauseam. My recommendation was simply to follow code::blocks' style and XML tags where possible because a) all the existing code::blocks users are comfortable with this or have already overwritten those tags we don't like with our own preferences. And b) following the existing style may smooth the entire process of getting the patch accepted into the mainline trunk.
Third, out of curiosity, the background color for DMD code samples seem to be gray. Where did you find/why did you choose beige?
Forth, for the lexer, I have a vague memory up patches/updates to Scintilla being posted a long time ago. You might want to look into SciTE4d and SEATD.

> I have also tried a version with 8 different keywordgroups (as it is in
> Poseidon) and different
> colors for normal-string, raw-string, and so on ...
> but for my taste this is too much, I like it simple.
>
> to2.)
> which OS/compiler?

Win32/DMD 2 though I don't remember seeing separate D1 and D2 entries in the compiler selection menu.

>
> First, the normal code::block selector uses smart colors which are based
> upon the underlying text color, etc. Essentially, it only changes the
> background color (like many other editors) and doesn't change the
> foreground color. This makes selection easier to read and extend.
This are only colorsettings and can be overritten be the user

It
> also doesn't play havoc with code::blocks' thread search feature.
I don't know what you mean

> Second, languages don't have color conventions, IDEs do. Code::blocks is
> different from Visual Studio which is different from Scintilla ad
> nauseam.
Just open a Smalltalk file in codeblocks, the colorscheme is completly different

> My recommendation was simply to follow code::blocks' style and
> XML tags where possible because a) all the existing code::blocks users
> are comfortable with this or have already overwritten those tags we
> don't like with our own preferences. And b) following the existing style
> may smooth the entire process of getting the patch accepted into the
> mainline trunk.
What is codeblocks-style? Smalltalk,C++,Ruby,ASM ... ??
They all have different colorschemes!

> Third, out of curiosity, the background color for DMD code samples seem
> to be gray. Where did you find/why did you choose beige?
OK, the backgroundcolor was badly choosen.

> Forth, for the lexer, I have a vague memory up patches/updates to
> Scintilla being posted a long time ago. You might want to look into
> SciTE4d and SEATD.
There is already a d-lexer in the scintilla and codeblocks project
This is what I use!

> Win32/DMD 2 though I don't remember seeing separate D1 and D2 entries in
> the compiler selection menu.
I tested with Wn32/DMD2 and it works just fine.
There are 3 different compiler for D
- Digital Mars D1 compiler
- Digital Mars D2 compiler
- GDC D Compiler

You should see all 3 compiler or your compilation failed.
Please follow this wiki page:
- http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows