If the terminal opens in the current directory, we should create a
variable to hold the current directory and also use this for the "Open
file"-dialog, so if you choose a file, you start at the same directory
as the file you are editing right now.
How to get this variable? Just filepath minus filename, or is there a
GTK function to get the current directory?
And how can I launch programs/processes with C or GTK?
Well, let's look at those plans.
Features for the project:
- Bug tracking system (bugzilla?)
We already have one. http://savannah.nongnu.org/projects/beaver
But we thought the mailinglist is more accesible for everyone, so that's why we direct bugs to the mailinglist and don't look at the bug tracker too often.
Features that should be implemented int he editor:
Probably, we will be implementing these things in the version after 0.4.0. We want to release 0.4.0 as soon as possible, just fixing some bugs.
- Documentation Doxygen documentationing will be included in 0.4.0
- Change tab size Don't know how important this is. We just want to include things in Beaver that are really important. We want to keep it as small as possible.
- Allow drag-and-drop to main window
- Allow changing of highlight colors
- Move HOME to start of text, not line (shouldnt be hard, just some
work with GtkTextIter)
- Use "autohell" tools and gettext Yeah, we'll have to start with translations again someday...
- Highlight braces/parens too
- Add 80th char column marker
- Find prev/next option (gtk_text_iter_*_search() for common text and
a better implementation of
regex search/replace function)
- Add side and bottom panels (notebooks) for plugins (they are hidden
and empty by default,
plugins will self add to the panels on load depending on the configuration)
- "hello world" like plugin, so users will be able to understand a
bit about how beaver's plugin system works. We have a demo plugin for developers. But we may indeed also have to show it to users.
Features that should be implemented as plugins (doesnt mean it should
be implemented NOW): some good ideas! We just need time to create those plugins. But we hope to attract developers that like our program and will write plugins.
- The plugin Double was talking about.
- Function list or Code browser (ctags ?)
- Integrated terminal (VTE ?)
- File browser
- "Open in browser" menu option
- Compiling options (make all or make clean on the current file directory)
- Color selection button we already have that in the "tools"-plugin
|