[Cgdb-devel] CGDB 1.0 Proposal
Brought to you by:
bobbybrasko,
crouchingturbo
|
From: Mike M. <mmu...@cs...> - 2003-08-14 01:51:28
|
Hi Everyone,
Just wanted to get this discussion going. In the next week or two,
we should really identify what exactly CGDB version 1.0 will do.
The idea is that this should be doable in a matter of a couple
months, that it'll be fully documented, and basically feature
complete. Advanced features can be left for a possible second
revision, but we want to keep things simple right now.
I've got a list of features here, and I'm hoping Bob will add
anything that I've missed. If any of you have feedback and/or
additional suggestions, please send them. I'll maintain an updated
copy of this proposal, and it'll go on our web site when it's done.
Proposal:
The CGDB GUI should have the following features:
- Configurable:
o Config file containing :ex commands
o Key bindings for any :ex commands
o Color schemes
- Robust source viewer:
o Fast syntax highlighting
o Regular expression searching
o Token identification (for displaying data)
o Assembly view (source, asm, and mixed modes)
o Hyperlinking (for viewing help files)
- Windowing system:
o Arbitrary number of source windows
o Bindable to currently executing source
o Resizable. Movable?
o Inferior process window (tty)
- Macro support (vim-style)
- Support reloading a new inferior program (gdb 'file' command)
The TGDB library should have the following features:
- GDB Interfaces
o Annotate 2
o GDB/MI
- Support for advanced GUI features
o Reloading new inferior application
o Providing a TTY for the inferior window
o Providing assembly instruction as well as file:line info
- Well-thought out API that will never change
I know I'm missing some things, so hopefully Bob can fill them in.
Let me know what you guys think! When we have this figured out
completely, we can more accurately slap version numbers on our
releases. As well, it's important to get CGDB more solid-looking,
so that when people do use it, they get a good impression.
Documentation is going to be very important for this, as we've
already seen sites describing CGDB as poorly documented.
I'm excited to get working on it again!
Mike
|