Danke Frank,
I will ask you for support. Not today... because I am simply tired;
beside YOU DID A DAMNED GOOD JOB !!
Bjoern

Frank Benoit (keinfarbton) Wrote:

> > 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.

BLS schrieb:
> Danke Frank,
> I will ask you for support. Not today... because I am simply tired;
> beside YOU DID A DAMNED GOOD JOB !!
> Bjoern

thx.
i hope you succeed in building the lib and headers. Please contact me to
get commit permission for the svn.
Frank

bobef wrote:
> 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?

Definitely! In my opinion small cute debugger front-end (with editing support) could be worth $20.

And small cute debugger front-end with full-blown intelisense (class browser, 'jump to definition', 'find references', etc..) could be easily worth $50.

-- 
serg.

bobef wrote:
> 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

Thanks, I actually wasn't aware that total commander messes up the unzipping like that.  You should probably put a file in that dir so that it doesn't get skipped.  Lots of broken unzipping tools in use.

I have two questions for starters:

Is it supposed to show source code?  Didn't do that for me, but I didn't do anything specific to make it happen either.

Are the keyboard shortcuts the same as another IDE/debugger?  They don't match msvc 6 exactly.  Then run to cursor would have to be ctrl-f10 instead of shift-f10.  So I'm guessing a later msvc, or even windbg?

Yes, of course I will. DWT is clearly dead. I even aliased it so I don't have any dwt.* in my code ;) But I wasted like an hour or two trying to compile tioport swt without success, so I will wait for the next tango version in hope it will compile ok...

BLS Wrote:

> 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
> 

I am not familiar with eclipse. I just use it for its visual editor for swt. I have this design in mind since the old days when I was developing akide, but I think yes, it is something similar.

BLS Wrote:

> 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
> > 
> 

Yes, it shows the source. You need one more empty plugin dir - flower.docmanager . It does when it reaches a breakpoint or you can drag and drop to open files.

torhu Wrote:

> bobef wrote:
> > 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
> 
> Thanks, I actually wasn't aware that total commander messes up the unzipping like that.  You should probably put a file in that dir so that it doesn't get skipped.  Lots of broken unzipping tools in use.
> 
> I have two questions for starters:
> 
> Is it supposed to show source code?  Didn't do that for me, but I didn't do anything specific to make it happen either.
> 
> Are the keyboard shortcuts the same as another IDE/debugger?  They don't match msvc 6 exactly.  Then run to cursor would have to be ctrl-f10 instead of shift-f10.  So I'm guessing a later msvc, or even windbg?

Yeah, me too. And please post a tutorial or something if you do :)


Frank Benoit (keinfarbton) Wrote:

> thx.
> i hope you succeed in building the lib and headers. Please contact me to
> get commit permission for the svn.
> Frank

torhu Wrote:

> 
> Are the keyboard shortcuts the same as another IDE/debugger?  They don't match msvc 6 exactly.  Then run to cursor would have to be ctrl-f10 instead of shift-f10.  So I'm guessing a later msvc, or even windbg?

Oh.. Yes. I am using the msvc6 scheme. I probably misspelled it. You can edit plugins\flower.debugger\accelerators.kfg and change them as you like. Just keep in mind that line endings should be LF (\n) or it will probably not work.

bobef schrieb:
> Yes, of course I will. DWT is clearly dead. I even aliased it so I don't have any dwt.* in my code ;) But I wasted like an hour or two trying to compile tioport swt without success, so I will wait for the next tango version in hope it will compile ok...
> 

For linux I use Tango from the  current trunk, DMD 1.012 and the updated
"rebuild"
Can you give more informations about the problems you had?