Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
mariocup:
Hi oBFusCATed,
some time ago I collect some requirements that I see for a debugger, especially if you want to use it for embedded application (see Section Embedded at http://wiki.codeblocks.org/index.php?title=User_talk:Mariocup).
The most important features in my eyes are:
- Extension Points for options
- Mixed Mode
- Multiple Watch Windows
If you are refactoring it, perhaps there will be some new concepts to integrate some of the features :D.
oBFusCATed:
--- Quote from: MortenMacFly on July 28, 2009, 03:20:27 pm ---Sure - who can stop you anyways?! ;-)
--- End quote ---
That is true, but I don't want to maintain extremely modified copy of CB, so if the changes would be accepted in the main source, I'll do better work.
--- Quote from: MortenMacFly on July 28, 2009, 03:20:27 pm ---If it's working and well written I am happy to keep track and apply if ready. Please just try to use the same style as in the debugger plugin.
--- End quote ---
Coding style?
Another thing:
I need to keep the thing in a VCS, shuffling patches around would be nasty.
There are some options:
1. I could import the thing in a git repo and publish it, but I'm not sure how well does git works on windows. And I've never used git before.
2. You could make me new branch in the official repo, and give me write access to that branch, so you can follow the progress and stop me from doing stupid things early in the process.
3. Any other option you could think of, and I've missed.
p.s. I don't insist on option 2
p.s.s. mariocup: It is too early to think about such features, though some of the sound logical and not that hard to implement, so time will tell what will happen :)
MortenMacFly:
--- Quote from: oBFusCATed on July 29, 2009, 12:04:29 am ---Coding style?
--- End quote ---
Yes - we have some instructions accordingly in the WiKi.
--- Quote from: oBFusCATed on July 29, 2009, 12:04:29 am ---I need to keep the thing in a VCS, shuffling patches around would be nasty.
3. Any other option you could think of, and I've missed.
--- End quote ---
Granting access on out repo can only one: The Admin Yiannis.
But I suggest you create yourself an account on BerliOS (so that we share the same platform) and have your own repo there... just as a lot other plugins do it, too. It's very simple to setup.
oBFusCATed:
I'm not sure that I like berlios, so if it will be external repo I'll go with GIT.
Because it has svn integration, so syncing my repo with trunk will be easier.
And it's time to learn it :)
oBFusCATed:
I've started working on it ... and I have a little problem:
Where do I put a new header that should not be visible to the users in the sdk, only by the implementation?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version