Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Splitting debugger in two - specific debugger and common GUI

<< < (2/136) > >>

MortenMacFly:

--- Quote from: oBFusCATed on July 26, 2009, 09:30:08 pm ---Morten how could I (in the GDB/mi plugin) derive from classes in GDB plugin?

--- End quote ---
Erm... just like

--- Code: ---class Gdb
{
    public:
        void GdbFunction(){ // gdb code }
};

class NewGdb : public Gdb
{
    public:
        void GdbFunction(){ // new_gdb code }
        void NewGdbFunction(){}
};

void new_gdb_plugin()
{
    NewGdb new_gdb;
}

--- End code ---
etc... But probably I have misunderstood?

oBFusCATed:

--- Quote from: MortenMacFly on July 28, 2009, 08:34:50 am ---Erm... just like

--- Code: ---class Gdb
{
    public:
        void GdbFunction(){ // gdb code }
};

class NewGdb : public Gdb
{
    public:
        void GdbFunction(){ // new_gdb code }
        void NewGdbFunction(){}
};

void new_gdb_plugin()
{
    NewGdb new_gdb;
}

--- End code ---
etc... But probably I have misunderstood?

--- End quote ---
First you have missed the virtual up there:)
The question was a bit rhetorical, though. I can derive from a class that is not exported (no public include, no __declspec(export/import)).
To be able to derive from such class, some changes should be made in the current debugger plugin. Also my new plugin would become dependent on the old one, but it should work with the old plugin, there should not be related in any way.

Decoupling the gui from the debugger plugin will make writing of both easier. Also the plugins would be easier to read, understand and extend.

MortenMacFly:

--- Quote from: oBFusCATed on July 28, 2009, 10:52:07 am ---First you have missed the virtual up there:)

--- End quote ---
Nar... but you got the idea.


--- Quote from: oBFusCATed on July 28, 2009, 10:52:07 am ---Decoupling the gui from the debugger plugin will make writing of both easier. Also the plugins would be easier to read, understand and extend.

--- End quote ---
So - I have no doubts about that but again my question is: If we "polish" the current interfaces / classes so we can derive from them where needed may b less work. But it's really just a question - so it's probably not.

oBFusCATed:
I suppose the simpler windows (call stack, threads, registers) could be modified, and not rewritten from scratch.
But the most complex and time consuming window, the watch window, could not.
In my opinion it should be rewritten using the PropGrid class/widget (or something similar). At the moment it is quite annoying and not user friendly.

So do I have a green light to start working on such a feature/refactoring? And would my work be accepted in C::B?

MortenMacFly:

--- Quote from: oBFusCATed on July 28, 2009, 01:14:22 pm ---So do I have a green light to start working on such a feature/refactoring?

--- End quote ---
Sure - who can stop you anyways?! ;-)


--- Quote from: oBFusCATed on July 28, 2009, 01:14:22 pm ---And would my work be accepted in C::B?

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

Navigation

[0] Message Index

[#] Next page

[*] Previous page