[Geany-devel] Build system 2.0, default configuration dialog

[Lex Trotman]

Hi All,

As suggested by Nick, this is a new thread to discuss what should be in the
default build configuration dialog, the full configurability will be
provided by a plugin that replaces the default one.

Below is pasted from previous thread.

...

> > > I think for the
> > > core Execute command(s) a checkbox for whether to run without xterm/VTE
> > > per command for GUI programs is good.
> > >
> >
> > This gives me an opening to start discussion on what functionality should
> be
> > exposed by the core configuration dialog, thanks Nick. ;-)
> >
> > I actually went back to 0.18.1 and looked at what is available there, and
> I
> > think that the following need to be added, but I'm open to suggestions:
>
> Hmm, this seems quite complicated. You know we accept current trunk as
> good, no need to rethink everything.
>

It is actually slightly simpler than current trunk.

The current trunk arrangement has one major problem though, the project
settings and the non-project settings are configured in separate dialogs,
having settings that interact in different places is very poor user
interface design (which I accept responsibility for creating).  I want to
put them in one place.


>
> > 1. edit each of the "make" commands individually (0.18.1 has single
> setting
> > shared by all three)
> > 2. edit project build settings (don't exist in 0.18.1) for "make"
> commands
> > only, not filetype
> > 3. edit working directory for each command (doesn't exist in 0.18.1)
> > 4. if above, remove "make in base path" since its no longer needed
> > 5. for execute commands only, the option to run without terminal,
> checkbox
> > (new)
> > 6. single shared parsing regex per filetype (hidden setting, not in GUI
> in
> > 0.18.1, this is used for make commands as well based on current document)
> It
> > might be less confusing to have another regex for the make commands as
> well?
>

Actually I made a mistake here, the current trunk does have a separate
"make" regex so keep that

>
> > Things to not make available (to avoid "dialog shock"):
> >
> > 1. edit menu item label
> > 2. which commands are parsed and which are not
> > 3. which commands are stopable and which are not
> > 4. extra commands in sections (propose simple dialog allows editing 2
> > fieltype,3 make,2 execute)
> > 5. change internal command locations (next/prev error, show dialog)
> > 6. project filetype commands (just so the dialog is smaller)
> > 7. parsing regex per command, source or global
> > 8. viewing settings from non-editable sources ie default, system
> filetypes,
> > plugins/internal
>
> ...

Cheers
Lex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geany.org/pipermail/devel/attachments/20100304/cb9d5253/attachment.html>