see https://github.com/BBasile/Coedit/releases/tag/2_gold

On Friday, 12 February 2016 at 16:09:36 UTC, Basile Burg wrote:
> see https://github.com/BBasile/Coedit/releases/tag/2_gold

I was just overjoyed to install this and hit "w" ctl+space and see writeln! It takes a bit of effort to get this stuff packaged so well. Great work!

On Friday, 12 February 2016 at 16:54:56 UTC, Taylor Hillegeist wrote:
> On Friday, 12 February 2016 at 16:09:36 UTC, Basile Burg wrote:
>> see https://github.com/BBasile/Coedit/releases/tag/2_gold
>
> I was just overjoyed to install this and hit "w" ctl+space and see writeln! It takes a bit of effort to get this stuff packaged so well. Great work!

Thx. We can thank Brian Schott too, what I call the "IDE-level-features" in CE are possible thanks to DCD and libdparse.

On Friday, 12 February 2016 at 17:05:39 UTC, Basile Burg wrote:
> On Friday, 12 February 2016 at 16:54:56 UTC, Taylor Hillegeist wrote:
>> On Friday, 12 February 2016 at 16:09:36 UTC, Basile Burg wrote:
>>> see https://github.com/BBasile/Coedit/releases/tag/2_gold
>>
>> I was just overjoyed to install this and hit "w" ctl+space and see writeln! It takes a bit of effort to get this stuff packaged so well. Great work!
>
> Thx. We can thank Brian Schott too, what I call the "IDE-level-features" in CE are possible thanks to DCD and libdparse.

Basile,

I just want to say thank you for releasing this! I've really enjoying using Coedit for doing D development. Thanks for your hard work.

Robert

On Friday, 12 February 2016 at 16:09:36 UTC, Basile Burg wrote:
> see https://github.com/BBasile/Coedit/releases/tag/2_gold

Are you planning to support osx too someday ?

--Stephan

On Saturday, 13 February 2016 at 08:50:39 UTC, extrawurst wrote:
> On Friday, 12 February 2016 at 16:09:36 UTC, Basile Burg wrote:
>> see https://github.com/BBasile/Coedit/releases/tag/2_gold
>
> Are you planning to support osx too someday ?
>
> --Stephan

The few missing details to compile CE under OSX have been added today. However it has to be build by the user, which might not be easy. I cannot help with this (except for eventual bugfixes).

On 2016-02-17 14:18, Basile Burg wrote:

> The few missing details to compile CE under OSX have been added today.
> However it has to be build by the user, which might not be easy. I
> cannot help with this (except for eventual bugfixes).

Can't you use Travis CI to build it if you don't have a Mac yourself?

-- 
/Jacob Carlborg

On 2016-02-17 12:19 PM, Jacob Carlborg wrote:
> On 2016-02-17 14:18, Basile Burg wrote:
>
>> The few missing details to compile CE under OSX have been added today.
>> However it has to be build by the user, which might not be easy. I
>> cannot help with this (except for eventual bugfixes).
>
> Can't you use Travis CI to build it if you don't have a Mac yourself?
>

I've been keeping an eye on building Coedit on OSX for a while now, but it blows up on launch.  The top bit of the stacktrace:

0   com.apple.CoreFoundation      	0x954f7234 __CFRunLoopFindMode + 20
1   com.apple.CoreFoundation      	0x955636f9 CFRunLoopTimerSetNextFireDate + 505
2   com.apple.HIToolbox           	0x913b8b62 InstallEventLoopTimerInternal + 706
3   com.apple.HIToolbox           	0x913ca362 InstallEventLoopTimer + 55
4   com.company.coedit            	0x00110276 CARBONINT$_$TCARBONWIDGETSET_$__$$_CREATETIMER$LONGINT$TWSTIMERPROC$$THANDLE + 150 (carbonobject.inc:1570)
5   com.company.coedit            	0x0015a997 CUSTOMTIMER$_$TCUSTOMTIMER_$__$$_UPDATETIMER + 135 (customtimer.pas:129)
6   com.company.coedit            	0x0015aaef CUSTOMTIMER$_$TCUSTOMTIMER_$__$$_SETENABLED$BOOLEAN + 47 (customtimer.pas:192)
7   com.company.coedit            	0x0036d010 CE_WIDGET$_$TCEWIDGET_$__$$_BEGINDELAYEDUPDATE + 64


I'm not sure as to how to proceed from this though... :/

On Thursday, 18 February 2016 at 04:52:13 UTC, Andre Kostur wrote:
> On 2016-02-17 12:19 PM, Jacob Carlborg wrote:
>> On 2016-02-17 14:18, Basile Burg wrote:
>>
>>> The few missing details to compile CE under OSX have been added today.
>>> However it has to be build by the user, which might not be easy. I
>>> cannot help with this (except for eventual bugfixes).
>>
>> Can't you use Travis CI to build it if you don't have a Mac yourself?
>>
>
> I've been keeping an eye on building Coedit on OSX for a while now, but it blows up on launch.  The top bit of the stacktrace:
> [...]
> I'm not sure as to how to proceed from this though... :/

I'll try to follow and help here: https://github.com/BBasile/Coedit/issues/16
With the hope it'll succeed this time. You can post the stack trace there.

Travis might be used in the future.