[Geany-devel] GProject - the second attempt
dimitar.zhekov at xxxxx
Fri Jul 9 17:49:39 UTC 2010
On Sun, 4 Jul 2010 00:54:17 +0200
Jiří Techet <techet at gmail.com> wrote:
> Hi everybody,
Hi. I finally had the time to read the long list of suggested gproject
changes and the discussion on them.
> Rewrite tab switching queue
> Remove the "set" button from the project properties dialog
All hail, it's confusing. I press "Set", and it looks like nothing
happened. After switching to the "Build" tab, some of the entries are
changed, but colored as default. And %p is set even for the empty
commands, which are colored as non-default...
> Use relative paths in the project files
> However, when the project is saved, all paths are converted to relative.
I haven't tested, so correct me if I'm wrong, but it looks like it'll
convert even paths outside the project directory, resulting in names
like "../../testing/gsm/CHANGES". So if I move the project in a
different directory on the same machine, it's quite possble that
all ../ names will become invalid, while absolute names would have
The reasonable compromise, IMHO, will be to use relative names for the
files under the project directory only.
> Make it possible to change project patterns by plugins
> Add signals for project options dialog opening and closing
Generally, you want gproject integrated seamlessly in Geany. However,
in 0.19, the plugins are even less integrated than before, with a
separate "Plugin preferences" function.
Without changing the Geany core, you can make the gproject preferences
available in Edit -> Plugin Preferences, or with a button in the panel,
and define whatever validators you need. Then, you can use the project
name from the plugin data and save the preferences.
> Make the project menu accessible by plugins
The project menu is probably easy to find, with something like
g_object_get_data((gpointer) geany->main_widgets->window, "project1").
But the real question, as pointed out by Lex, is about the ammount of
plugin intergation. I see that you got an "OK" from Nick for this -
perhaps I should request access to the Edit menu, which contains all
the Insert-Some-Text functions, and put the Insert Numbers [from
> Plugins can override project patterns. In that case the "file patterns"
> field is made inactive in the Project tab of the project properties
Can you please remind me what was the reason for that?
> Use project patterns in the FIF dialog
> When "use project patterns" is selected, the project patterns are copied
> to the "files" edit box and it becomes not editable.
Not editable - but what if I want to add/remove a pattern for this
particular search? I'd prefer the Nick's suggestion, "Always append
project patterns to the Files drop-down list [...], it's up to the user
to choose it."
> It should be considered whether the "files" checkbox should exist
Indeed. If patterns are entered in the edit field, there are patterns.
If the field is empty, there are no patterns. FIF may (and probably
does) work in a different way with patterns, but there's no such
tooltip or any other suggestion related to the Files checkbox. And if
there was, it could be have been displayed directly for the edit field.
(BTW, when you check Files, and don't enter anything in the patterns
field, nothing will be found. Which is formally correct. :)
More information about the Devel