Re: Context menus
On Wed, 5 Nov 1997, Behan Webster wrote:
> Jason Gunthorpe wrote:
> >
> > I see no reason why the slang versions can't have a context menu as well.
> > It's actually more work to remove it :P
>
> Really? Well then, I've underestimated the potential of the slang
> version of deity! I will adjust my expectations accordingly!
Hehe, so long as it will fit on the screen it should be doable.
> > > Again, the concept of "hold" is unessesary. By not upgrading to the
> > > next version of a package there is an implicit hold placed on the
> > > package by the user.
> >
> > Hm, I was thinking 'hold' has a single use -- to prevent a pacakge from
> > being automatically installed.
>
> That is what "keep" means. The state in which the user leaves the UI is
> the state it should come up again in the next invocation of deity. This
> includes if a particular package was not upgraded (or in other words the
> old version was kept). If you liken this to dselect, if the last thing
> a user did was not upgrade a package, then there is an implicit hold.
> The new version will be offered to the user on successive invocations of
> deity, but the left hand buttons will remain on "keep" until the user
> clicks "inst" again. At this point deity will automatically assume that
> the user will want to upgrade to progessive versions again. Does that
> make sense?
Hrm, this doesn't really help the situation I'm thinking of, lets say..
-I wish to never have libreadline changed.
-Right now I have Version 2.2 installed which is also the install
version
-Because of that the UI shows the state as 'keep' (no action needed)
-Since keep is already selected how can I indicate I don't want it to
be auto upgraded?
(This might be handled with the version thingy below?)
> > The trouble is
> > if the user specifies a specific version it vastly complicates things
> > because forevermore that package is attached to that version - period.
>
> Explain please?
Well, if you say 'I want 2.2' then when does the program decide that you
no longer want to remain at 2.2 and it is free to offer new versions for
installation. Or does it simply never offer a new upgrade.
I suppose it could decide that if you want 2.2 and 2.2 is already
installed then you don't really want 2.2 and it should remove 'Target
Version'. However that strikes me as a bit unintuitive..
The way I have been working it is that the user can flexably control the
Install Version field which has a direct effect on what will be installed.
Parameters like TargetVersion and TargetDistribution control what is
offered for each package.
So once you set the parameters you effectivly close off a set of versions
for that package, unless you look at (the status window?) you will
never even know there is a newer version for upgrade. I think that is the
proper way to implement your gui, but perhaps I missed something?
> > The UI prototype has had my interpritation of your web page for a while
> > now, so we should check that it is okay..
>
> I haven't managed to check it out yet, because I haven't been able to
> compile it yet!
Heh, someday we have to fix that :> I don't know any more than 'It didn't
work' so I'm not sure what to suggest.
> In our case we're pretty sure it's the PCI chipset. It's crashing both
> Linux and NT machines (both no mean feats), and it is only really
> affected by activity of PCI devices (SCSI and video cards). We're
> trying to get the manufacturer to replace the motherboards, but we're
> having problems. 8(
Yuk, crappy BrandX motherboards?
Jason
Reply to: