Hello, guys. How are you doing. It's been quite some time since my last announce here. I see a lot of development going on. Keep up the good work.

Two weeks ago I had some time to waste so I checked what is going on in the D community and I saw announcement or something about Ddbg. I gave it a try and it worker very good. The thing is that in the moment I am trying to save some money for my education so I came up with this idea. I want to try to make a commercial application. Initially it will be a ddbg front end, if there is interest it may grow up to a full featured editor and project manager. Here is a little demo I did in the last two weeks. In it is not fully functional but most of the debugger's functionality is working. Please take a look and tell me what you think. Do you like it? What do you not like? Would you be willing to pay something like say 5$ when it is complete for it?
Fore some more info take a look in the readme.txt

And... I hate to sell anything, so when I raise enough money (no matter by what means) it will be released as open source. The project is in D/DWT. The design is fully modular so it will be easy to extend (once DDL is working :)

http://www.sendspace.com/file/1hhwux

I'd gladly pay $20 for something that's simpler to use than codeblocks or windbg, and has better D support than msvc 6.  That would save me hours every week.  It would probably have to be a debugger gui only, since a full-blown IDE written by a single person would most likely never reach a usable state.  It's just too much work.  I don't think the world needs another dead project in that category.

But a  dedicated gui for ddbg that actually works, is more or less stable (on windows, cross platform apps tend to only be stable on the platform that they're primarily developed on), and can be used without causing more hair pulling than it's worth, would be worth its weight in gold.  I challenge you to pull it off. :D

If I coded D for a living, I'd probably pay $500 for someting like that.

What do I need to do to start a debugging session?  I've put ddbg.exe in the same dir as flower_demo.exe, but it only says "Select a debugger interface fist" when I press F5.  And the debugger interface dropdown is empty.

torhu wrote:
> I'd gladly pay $20 for something that's simpler to use than codeblocks or windbg, and has better D support than msvc 6.  That would save me hours every week.  It would probably have to be a debugger gui only, since a full-blown IDE written by a single person would most likely never reach a usable state.  It's just too much work.  I don't think the world needs another dead project in that category.
> 
> But a  dedicated gui for ddbg that actually works, is more or less stable (on windows, cross platform apps tend to only be stable on the platform that they're primarily developed on), and can be used without causing more hair pulling than it's worth, would be worth its weight in gold.  I challenge you to pull it off. :D
> 
> If I coded D for a living, I'd probably pay $500 for someting like that.

I second this. I know an operation that is looking at using D in for-profit projects. One of there biggest reservations is debuggers. Make Flower work and that starts looking like a vary small issue.

BTW how hard would it be to put the who thing in a .DLL so that other programs could host it? That might get you a lot of the IDE side for free.

Check the status window. It should say

plugin loaded: debugge_ddbg

or something like that. I guess your unzipper is skipping the empty folders inside the plugins folder, so the debugger interface plugin for ddbg is not loaded. You can create it manually: plugins\flower.debugger_ddbg



torhu Wrote:

> What do I need to do to start a debugging session?  I've put ddbg.exe in the same dir as flower_demo.exe, but it only says "Select a debugger interface fist" when I press F5.  And the debugger interface dropdown is empty.

BCS wrote:
> 
> BTW how hard would it be to put the who thing in a .DLL so that other programs could host it? That might get you a lot of the IDE side for free.

FTW.

Seriously, this is an excellent idea.

-- 
- EricAnderton at yahoo

Hi bobef,
Glad to pay something.
But I would suggest to create the IDE/Debug frontend in TIOPORT SWT.
Once your tool is open source this will be nessesary; IMO
And YES I know, creating the Windows lib and di files for TIOPORT SWT is difficult.. try it since about 4 hours :-(

Bjoern

bobef Wrote:

> Hello, guys. How are you doing. It's been quite some time since my last announce here. I see a lot of development going on. Keep up the good work.
> 
> Two weeks ago I had some time to waste so I checked what is going on in the D community and I saw announcement or something about Ddbg. I gave it a try and it worker very good. The thing is that in the moment I am trying to save some money for my education so I came up with this idea. I want to try to make a commercial application. Initially it will be a ddbg front end, if there is interest it may grow up to a full featured editor and project manager. Here is a little demo I did in the last two weeks. In it is not fully functional but most of the debugger's functionality is working. Please take a look and tell me what you think. Do you like it? What do you not like? Would you be willing to pay something like say 5$ when it is complete for it?
> Fore some more info take a look in the readme.txt
> 
> And... I hate to sell anything, so when I raise enough money (no matter by what means) it will be released as open source. The project is in D/DWT. The design is fully modular so it will be easy to extend (once DDL is working :)
> 
> http://www.sendspace.com/file/1hhwux

It is already a DLL. But since D sucks on DLLs and DDL is not working for me it is statically linked. The design of the program is modular. Everything is a module but I need some kind of runtime linker that will allow the plugins to use the same runtime as the host, otherwise they can't modify the UI directly. The design is as this. The debugger plugin is kind of general debugger. It need interfaces. Another plugin is the ddbg interface, which could easily be turned into a DLL (I mean a DLL independent of the flower framework), because it's whole job is to be a proxy between the debugger and ddbg.exe. The debugger plugin or the application knows nothing about ddbg. I forgot to mention but the whole thing is kind of framework. It is the base of the program. A framework for modular program. This framework will be released as open source when the API matures a little bit, but the plugins which do the actual work will remain closed for some time. But I will release one of the plugins as an example plugin. This could be the ddbg interface. We will see about that. Everything is too unmature now to tell anything...


Pragma Wrote:

> BCS wrote:
> > 
> > BTW how hard would it be to put the who thing in a .DLL so that other programs could host it? That might get you a lot of the IDE side for free.
> 
> FTW.
> 
> Seriously, this is an excellent idea.
> 
> -- 
> - EricAnderton at yahoo

> And YES I know, creating the Windows lib and di files for TIOPORT SWT is difficult.. try it since about 4 hours :-(

Please come to IRC and let me assist you. I really don't want you to
loose time :)
#d or #d.tango keinfarbton

Or at least use the tioport forum to get my support.

Does this mean that you are thinking about something similar to the netbeans *platform* respective the eclipse *platform* ? using a plugin technologie based on DDL ?
Bjoern

bobef Wrote:

> It is already a DLL. But since D sucks on DLLs and DDL is not working for me it is statically linked. The design of the program is modular. Everything is a module but I need some kind of runtime linker that will allow the plugins to use the same runtime as the host, otherwise they can't modify the UI directly. The design is as this. The debugger plugin is kind of general debugger. It need interfaces. Another plugin is the ddbg interface, which could easily be turned into a DLL (I mean a DLL independent of the flower framework), because it's whole job is to be a proxy between the debugger and ddbg.exe. The debugger plugin or the application knows nothing about ddbg. I forgot to mention but the whole thing is kind of framework. It is the base of the program. A framework for modular program. This framework will be released as open source when the API matures a little bit, but the plugins which do the actual work will remain closed for some time. But I will release one of the plugins as an example plugin. This could be the ddbg interface. We will see about that. Everything is too unmature now to tell anything...
> 
> 
> Pragma Wrote:
> 
> > BCS wrote:
> > > 
> > > BTW how hard would it be to put the who thing in a .DLL so that other programs could host it? That might get you a lot of the IDE side for free.
> > 
> > FTW.
> > 
> > Seriously, this is an excellent idea.
> > 
> > -- 
> > - EricAnderton at yahoo
>