Init dialog should remember settings between sessions

[Dr Al]

It is likely that most users will use a single workflow. As such, every time they access the "init" dialog, they will select the same workflow. Bazaar Explorer should remember the selected workflow and present it as the default the next time that the user initialises a new repository.

[OldAl (algis.kabaila)]

On Wednesday 02 December 2009 00:29:27 Al wrote:
> Public bug reported:
>
> It is likely that most users will use a single workflow. As such, every
> time they access the "init" dialog, they will select the same workflow.
> Bazaar Explorer should remember the selected workflow and present it as
> the default the next time that the user initialises a new repository.
>
> ** Affects: bzr-explorer
> Importance: Undecided
> Status: New

Sheesh. Al Budden is NOT OldAl. *I* am OldAl - akabaila[at]pcug.org.au. I
did not raise this bug, nor do I think it is a bug... Just making it clear
that OldAl and Al are two different people.

Al, the init dialog is only used when one starts a new repository or new
storage location, so in any workflow, other than trying to reinvent the wheel
repeatedly and creating a new storage location for evey "new" wheel, would it
be sensible to remember what you did last time.

I think it right that the explorer does not remember the location of the last
init. No bug IMHO!

OldAl.
--
Algis Kabaila, MEngSc, PhD(Eng)
http://akabaila.pcug.org.au/StructuralAnalysis.pdf

[Martin Pool (mbp)]

I think it's reasonable to remember the workflow model you chose, but
not the location. I think that's what non-Old Al was asking for.
--
Martin <http://launchpad.net/~mbp/>

[Dr Al (abudden)]

As Martin has said, that is indeed what I was thinking: it would make no sense to remember the location, but I expect that most people would either always use the "Feature Branch" option or always use the "Plain Branch" option or whatever. This should be selected by default.

In my case, I always use the "Remote Feature Branches" option (lp:~abudden/bzr-explorer/remote-feature-branches) with the "lightweight checkout" option unticked and I'd like this to be remembered when I come back in. Every project I work on has a separate repository (as I understand it, this is a common way of working) rather than having everything in one big repository. Therefore, every time I start a new project, I use the init dialog to create that new repository. Every time I do that, I have to change the radio buttons in exactly the same way. In my opinion, that shouldn't be necessary.

[OldAl (algis.kabaila)]

On Wednesday 02 December 2009 16:39:12 Martin Pool wrote:
> I think it's reasonable to remember the workflow model you chose, but
> not the location. I think that's what non-Old Al was asking for.
> --
> Martin <http://launchpad.net/~mbp/>
I confess that I did not think about that - yes, that is reasonable and as
soon I get a bit of work that I set myself on my own project done, I will look
into it. Hopefully with Ian's help.

OldAl.
PS: In future, I will sign reports by OldAl or Algis, so there will be no
confustion with the other Al.
A.
--
Algis Kabaila, MEngSc, PhD(Eng)
http://akabaila.pcug.org.au/StructuralAnalysis.pdf

[OldAl (algis.kabaila)]

On Wednesday 02 December 2009 19:14:46 Al wrote:
> As Martin has said, that is indeed what I was thinking: it would make no
> sense to remember the location, but I expect that most people would
> either always use the "Feature Branch" option or always use the "Plain
> Branch" option or whatever. This should be selected by default.
>
> In my case, I always use the "Remote Feature Branches" option
> (lp:~abudden/bzr-explorer/remote-feature-branches) with the "lightweight
> checkout" option unticked and I'd like this to be remembered when I come
> back in. Every project I work on has a separate repository (as I
> understand it, this is a common way of working) rather than having
> everything in one big repository. Therefore, every time I start a new
> project, I use the init dialog to create that new repository. Every
> time I do that, I have to change the radio buttons in exactly the same
> way. In my opinion, that shouldn't be necessary.
OK, let me amplify my own position - currently I am doing a bit of work on my
own project easmy - a lot more fun then going backwards and forwards in some
other area. If no one takes this bug on, I would give it a go, subjec to my
limitations of Qt design (I have retired from Delphi to hack Python a few
years ago). I have planned to look at Qt GUI interface and read part of
Summerfield's book on Qt GUI design. That is not a good qualification to do bug
fixes of GUI, but I am a sucker for punishment.

I mention this, because I don't want to be in the way of someone else keen to
fix this bug.

Al, i also apologise for misinterpreting your wish for GUI behaviour - it is
not spurious at all!

OldAl.
--
Algis Kabaila, MEngSc, PhD(Eng)
http://akabaila.pcug.org.au/StructuralAnalysis.pdf

[Dr Al (abudden)]

2009/12/2 OldAl <email address hidden>:
> On Wednesday 02 December 2009 19:14:46 Al wrote:
>> As Martin has said, that is indeed what I was thinking: it would make no
>> sense to remember the location, but I expect that most people would
>> either always use the "Feature Branch" option or always use the "Plain
>> Branch" option or whatever.  This should be selected by default.
>>
>> In my case, I always use the "Remote Feature Branches" option
>> (lp:~abudden/bzr-explorer/remote-feature-branches) with the "lightweight
>> checkout" option unticked and I'd like this to be remembered when I come
>> back in.  Every project I work on has a separate repository (as I
>> understand it, this is a common way of working) rather than having
>> everything in one big repository.  Therefore, every time I start a new
>> project, I use the init dialog to create that new repository.  Every
>> time I do that, I have to change the radio buttons in exactly the same
>> way.  In my opinion, that shouldn't be necessary.
> OK, let me amplify my own position - currently I am doing a bit of work on my
> own project easmy - a lot more fun then going backwards and forwards in some
> other area.  If no one takes this bug on, I would give it a go, subjec to my
> limitations of Qt design (I have retired from Delphi to hack Python a few
> years ago).  I have planned to look at Qt GUI interface and read part of
> Summerfield's book on Qt GUI design.  That is not a good qualification to do bug
> fixes of GUI, but I am a sucker for punishment.

To be honest, I'd also have no problem with the idea of fixing this
one, only I'm not sure of the best place to put the settings or read
them. I've already added a few settings to QBzr and to the
configuration window of Bazaar Explorer, but found myself at a bit of
a loss when I was looking through the initialisation dialog code.

> I mention this, because I don't want to be in the way of someone else keen to
> fix this bug.

Likewise.

> Al, i also  apologise for misinterpreting your wish for GUI behaviour - it is
> not spurious at all!

No problem at all!

> --
> Init dialog should remember settings between sessions
> https://bugs.launchpad.net/bugs/490814
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Explorer: New
>
> Bug description:
> It is likely that most users will use a single workflow.  As such, every time they access the "init" dialog, they will select the same workflow.  Bazaar Explorer should remember the selected workflow and present it as the default the next time that the user initialises a new repository.

[OldAl (algis.kabaila)]

On Wednesday 02 December 2009 21:09:02 Al wrote:
> 2009/12/2 OldAl <email address hidden>:
> To be honest, I'd also have no problem with the idea of fixing this
> one, only I'm not sure of the best place to put the settings or read
> them.

Al,

Go for it! What I would really appreciate, Dr Al, if you would tell OldAl how
you did it. OldAl is always keen to learn. In case it helps, I took a branch
of bzr-explorer and started to look at revision 1. I think that it would
become clearer how the GUI was constructed if one were to step from revision 1
onwards. Ian is a very experienced, clever, competent and tidy programmer. I
was surprised to see how well he had planned the whole bzr-explorer right from
the word go.

Particularly nice connection of signals to bits of Python code, all done in
one loop in revision 1. Smart staff.

It was interesting to see the (probably widely known, but not known to me)
technique of making tuples of items of data by listing items, followed by a
comma, viz my_data = x1, x2, x3,

I would have thought that the last comma was superfluous and not meant to be
there. There were some other bits of programming there that I could not
fathom. :(

What a shame that we only have one life at a time (:

OldAl.

PS: Yes, I do hold a doctorate from Uni of NSW, awarded to me at a mature age
of 42 in 1967. My wife and I had already three kids. She deserves at least
half of that and other degrees. I urge both our sons to sign their names with
their Dr titles. They do not want to do, but have not given me a satisfactory
explanation. Why not - they worked for it! I am sure you did too, Al.

--
Algis Kabaila, MEngSc, PhD(Eng)
http://akabaila.pcug.org.au/StructuralAnalysis.pdf

[Ian Clatworthy (ian-clatworthy)]

This is now a preference.