Re: [anjuta-devel] Documenting the git plugin: where to start?

["Johannes Schmid" <jhs jsschmid de>]

Hi!

Sorry, not sure you got my answer yesterday on IRC. I am not following IRC
very closely currently and it doesn't look like that is going to change
any time soon. Sorry for that.

> To do something like that would require a good deal of changes to GDL
> (that's what I use to lay out the panes in git shell.) I can do this,
> but I have no idea how long it will take because I really have no clue
> how GDL works internally. ;)

I don't think that this involves GDL in the first place. What I mean is
basically something like this:

if (some_dialog_pane_is_already_shown)
    hide_that_pane();
show_requested_pane();

And it shouldn't be able to keep track if a pane is shown.

> Would you rather I work on things like this, as well as the problems Seb
> mentioned, before I start working on docs?

Yes, I think so, basically because docs can be written later in the
release cycle and usuability is currently still more important than docs.
If things are obvious, nobody needs to read the docs.

Regards,
Johannes