On 05/05/2010 06:41 PM, Bernard Helyer wrote:
> On 06/05/10 11:00, Ellery Newcomer wrote:
>>
>> Don't know why. Does it not like 64bit executables?
>
> For some reason you have to manually specify the path in the settings.
> '/usr/bin', most likely.

Weird. What's wrong with searching $PATH?

Hi,

Ellery Newcomer wrote:
> 
> Well, that was a bugger to install (fedora 12 x86_64)
> 
> yum gtk2.i686
> 
> mod to /etc/ld.so.conf
> 
> # /sbin/ldconfig
> 
> And it works! (for some reason LD_LIBRARY_PATH didn't seem to have any effect)

That's because of missing appropriate 32-bit libraries.

> create workspace, create project, import source directory? With these IDEs I'm always afraid they're going to do something weird with my source code.. 

You should make a backup in case of undefined behavior, however the 'Import Directory' operation only adds references to the actual files.

> Compiling. one. file. at. a. time. Is there a way to give all the files to dmd at once?

No there's no way in this release.

> 
> In the compiler window, it only shows the name of the file being compiled. Is there an option to show the full package of the file? (without the package part, many of my modules share the same name)
> 

Not this time.

> No autoindent in editor? Oh, I get it. It just doesn't understand vim's indenting. Any way to format?
> 
> I like the source code coloring. It's quite pleasant compared to vim's. I don't think comments and string literals should share the same color, though.
> 
> also, you seem to be missing the /+ +/ comments
> 
> doesn't color 'invariant', does color 'string' but not 'wstring' or 'dstring'
> 
> doesn't color #line
> 
> It'd be nice if it emboldened the escape sequences inside string literals, e.g. "\u0000", since I often forget how many digits need to follow \u vs \U, etc.
> 
> missing wysiwyg string literals, hex string literals, character literals
> 

I will look on that.

> when I type something like
> 
> wagga w;
> 
> it says `Identifier 'wagga' is not defined`
> and then it says `Wagga is used as a type` (note the capitalization which is going to annoy the bejeebers out of me)

The intention was to make an error message to start from the capital letter. Now it doesn't work in all cases, will remove this .

> 
> Ooo.. And when you cancel build, build, it restarts the build from scratch. Here we go again.

No, incremental compilation is not performed.
However, it's possible to rebuild single source and append resulting
object code to the target image. You can do this by opening context menu
in the source tree on the exact file and selecting menu 'Build'.
In this case, however, the result may be broken because of module dependencies(which may require whole recompilation).

> 
> Error: Cannot find GDB Debugger executable (gdb).
> 
> 

You must set the path to the GDB in the Settings->Options dialog in the debugging section. Did you read the readme file?

Thanks for the feedback.


Alex Makhotin,
the founder of BITPROX,
http://bitprox.com

Ellery Newcomer wrote:
> On 05/05/2010 06:41 PM, Bernard Helyer wrote:
>> On 06/05/10 11:00, Ellery Newcomer wrote:
>>>
>>> Don't know why. Does it not like 64bit executables?
>>
>> For some reason you have to manually specify the path in the settings.
>> '/usr/bin', most likely.
> 
> Weird. What's wrong with searching $PATH?

On my system I have the regular distributive of the GDB.
I also have the patched GDB to support D language in another directory.
I want to be sure what version of the debugger is used.
What's weird with that?
I will definitely try to make automation of such actions
in the future.


Alex Makhotin,
the founder of BITPROX,
http://bitprox.com

On 06/05/10 15:23, Alex Makhotin wrote:
> Did you read the readme file?

:D

Nobody reads the manual (I didn't). Users; you gotta love 'em!

Bernard Helyer wrote:
> On 06/05/10 15:23, Alex Makhotin wrote:
>> Did you read the readme file?
> 
> :D
> 
> Nobody reads the manual (I didn't). Users; you gotta love 'em!

So, is it working for you?
Maybe something you do not like from the user interface?
Because I would like to heart it first before I start to make correlation port to Windows.


Alex Makhotin,
the founder of BITPROX,
http://bitprox.com

Alex Makhotin wrote:
> heart it first before I start to make 

*hear


Alex Makhotin,
the founder of BITPROX,
http://bitprox.com

On 06/05/10 16:11, Alex Makhotin wrote:
> Bernard Helyer wrote:
>> On 06/05/10 15:23, Alex Makhotin wrote:
>>> Did you read the readme file?
>>
>> :D
>>
>> Nobody reads the manual (I didn't). Users; you gotta love 'em!
>
> So, is it working for you?
> Maybe something you do not like from the user interface?
> Because I would like to heart it first before I start to make
> correlation port to Windows.
>
>
> Alex Makhotin,
> the founder of BITPROX,
> http://bitprox.com

Well, just off the top of my head, when I was adding paths, you didn't use a file dialogue of any kind.

Bernard Helyer wrote:
> Well, just off the top of my head, when I was adding paths, you didn't use a file dialogue of any kind.

Well this is the behavior of wxPropertyGrid component
http://wxpropgrid.sourceforge.net/cgi-bin/index

There is a class for the directory selection(wxDirProperty) but it doesn't apply to a list of path, therefore I decided to replace it with a wxArrayStringProperty.
I will look if I can change default window for property set.
Maybe I will find a workaround.
I agree that the Visual Studio way could be much better.


-- 
Alex Makhotin,
the founder of BITPROX,
http://bitprox.com

"Alex Makhotin" <alex@bitprox.com> ???????/???????? ? ???????? ?????????: news:hrqug4$1299$1@digitalmars.com...
> Hello,
>
> I would like to introduce the first beta release of the IDE for D: BITPROX Development Environment 1.0 Beta 1
>
> You can download the trial beta version from the address: http://bitprox.com/en/download/bde1.0beta1.zip
>
> Please, try it.
> I would like to listen for your opinion.
> Thank you.
>
> Alex Makhotin,
> the founder of BITPROX,
> http://bitprox.com
>
>
Have you seen other wxWidgets IDE's like Code::Blocks or CodeLite? Why to put someones efforts to make what is already done, or at least almost done?

>You may now download the fully functional 30 day trial beta version of the software for GNU/Linux from the download page.

I doubt it's commercial usage, there are so many powerful open source IDE's supporting D - Code::Blocks, Ecipse, etc or commercial IDE's like SlickEdit or MS VS.