Re: Setup feature request: adding a Skipped view
Robert Collins wrote: On Thu, 2003-01-30 at 23:07, Max Bowsher wrote: To Brian: cygwin-apps is the preferred place to discuss setup development. Transferring this thread there. To cygwin-apps: Here is a patch from Brian Keener which got forgotten. It adds 2 additional views, Only Keeps and Only Skips. I think this could be valuable, and these very features are in the setup todo list. I think this got lost ... Max, do you recall? On the contrary, it's been applied for some time. The Up to Date and Not Installed views. Max.
Re: Setup feature request: adding a Skipped view
On Thu, 2003-01-30 at 23:07, Max Bowsher wrote: To Brian: cygwin-apps is the preferred place to discuss setup development. Transferring this thread there. To cygwin-apps: Here is a patch from Brian Keener which got forgotten. It adds 2 additional views, Only Keeps and Only Skips. I think this could be valuable, and these very features are in the setup todo list. I think this got lost ... Max, do you recall? Cheers, Rob -- --- GPG key available at: http://members.aardvark.net.au/lifeless/keys.txt. --- signature.asc Description: This is a digitally signed message part
Re: Setup feature request: adding a Skipped view
To Brian: cygwin-apps is the preferred place to discuss setup development. Transferring this thread there. To cygwin-apps: Here is a patch from Brian Keener which got forgotten. It adds 2 additional views, Only Keeps and Only Skips. I think this could be valuable, and these very features are in the setup todo list. Max. Brian Keener wrote: Actually the last change I submitted at Roberts request was against HEAD (at the time) and can be found at: http://sources.redhat.com/ml/cygwin-patches/2002-q3/msg00110/ViewChng The actual discussion on the change and my posting of the change begins with message: http://sources.redhat.com/ml/cygwin-patches/2002-q3/msg00080.html on July 12 2002.
RE: setup feature request
On Mon, 2 Dec 2002, Kris Thielemans wrote: [snip] I have a different opinion. First, note that the radio buttons don't act like radio buttons at all. When you click them, they alter the state of all the packages spin controls to meet the criteria of that button. I.e. they really should be action buttons, not radio buttons. With that in mind, Keep does fit with Curr and Exp. I agree that if the radio buttons actually acted like radio buttons, to modify a hypothetical AutoUpgrade action, then Keep does not fit so well with them. Recently I've been thinking tab control. Well, actually I was thinking that for the view type. Then again, I just now thought of the best idea yet: drop-down list boxes for both. -- Gary R. Van Sickle Brewer. Patriot.
RE: setup feature request
On Tue, 2002-12-03 at 19:03, Gary R. Van Sickle wrote: Recently I've been thinking tab control. Well, actually I was thinking that for the view type. Then again, I just now thought of the best idea yet: drop-down list boxes for both. Let me say this: Anything that is more intuitive will be an improvement. Heck, a dotted border might help. What I'd love would be a good control-window hierarchy to break the chooser up more, and then we could simply replace the controls with different window types to experiment more freely. Cheers, Rob -- --- GPG key available at: http://users.bigpond.net.au/robertc/keys.txt. --- signature.asc Description: This is a digitally signed message part
Re: setup feature request
Hi Max, just a final thought on the 'keep' sutff (maybe you've gone ahead and coded it already, so then you forget about this). This is on the question to put 'keep' in the spin control or a radio button. we had kris so maybe it makes more sense to add a 'keep' to this sequence, than kris to add a 'keep' radio button. Then there's a nice distinction: kris - radio buttons signify 'trust level' kris - default et al signify what you want to do. max I don't like it. Setup's clicky spin control things are not the easiest max thing to use. I would much prefer a radio button. I now think that putting 'keep' as a radio button on the same level as 'current' and 'experimental' is actually bad (sorry, I suggested it myself!). If you intreprete it as a trust level, you invalidate the 'install' setting of the spin control, as 'install' shouldn't do anything in that case. I think this is a serious source for confusion. By the way, an alternative to the spin control would be to have a drop-down list for every category, with the list of settings in there: upgrade to current versions upgrade to experimental versions keep remove (or uninstall) install current install experimental reinstall Less clicking, more familiar user interface, but more programming work I guess. All the best, Kris Thielemans (kris.thielemans at ic.ac.uk) Imaging Research Solutions Ltd Cyclotron Building Hammersmith Hospital Du Cane Road London W12 ONN, United Kingdom web site address: http://www.irsl.org/~kris
Re: setup feature request
On Mon, 2 Dec 2002, Kris Thielemans wrote: KT just a final thought on the 'keep' sutff (maybe you've gone ahead and coded KT it already, so then you forget about this). This is on the question to put KT 'keep' in the spin control or a radio button. we had I coded it and sent a patch to this list a while ago, but Robert didn't like the radio button either. Don't worry about lost time, though, the patch was truly trivial (*1 line* of actual logic, and the rest was renaming the button from Prev to Keep) KT kris so maybe it makes more sense to add a 'keep' to this sequence, than KT kris to add a 'keep' radio button. Then there's a nice distinction: KT kris - radio buttons signify 'trust level' KT kris - default et al signify what you want to do. KT KT max I don't like it. Setup's clicky spin control things are not the easiest KT max thing to use. I would much prefer a radio button. KT KT I now think that putting 'keep' as a radio button on the same level as KT 'current' and 'experimental' is actually bad (sorry, I suggested it KT myself!). KT If you intreprete it as a trust level, you invalidate the 'install' setting KT of the spin control, as 'install' shouldn't do anything in that case. I KT think this is a serious source for confusion. I have a different opinion. First, note that the radio buttons don't act like radio buttons at all. When you click them, they alter the state of all the packages spin controls to meet the criteria of that button. I.e. they really should be action buttons, not radio buttons. With that in mind, Keep does fit with Curr and Exp. I agree that if the radio buttons actually acted like radio buttons, to modify a hypothetical AutoUpgrade action, then Keep does not fit so well with them. KT By the way, an alternative to the spin control would be to have a drop-down KT list for every category, with the list of settings in there: KT upgrade to current versions KT upgrade to experimental versions KT keep KT remove (or uninstall) KT install current KT install experimental KT reinstall KT KT Less clicking, more familiar user interface, but more programming work I KT guess. Ah yes. I've been secretly vowing that one day I would make drop-downs out of those spinny things since I first set eyes upon them. Max.
RE: setup feature request
I'm not promising anything, but there's a slim chance I'll have a patch ready in time for upcoming setup release at the weekend / early next week. It's already in place. Just click 'default' beside 'all' twice and you should get 'keep'. comments about that: - the setup version that is currently on the cygwin home page does not have this feature: it cycles between default, install, reinstall - it's not an incredible piece of user friendly design. I didn't have a clue you could click there and what the effect would be. Don't get me wrong, being able to do global stuff per category *is* a very nice feature. So, maybe some online help (or just 1 or 2 sentences at the bottom of the dialog box) could sort that out. - what's the difference between 'default' and 'install'? - it should be very easy to add 'remove' as well. This will finally give us a means to remove cygwin (or just a part of it) easily. Kris Thielemans (kris.thielemans at ic.ac.uk) Imaging Research Solutions Ltd Cyclotron Building Hammersmith Hospital Du Cane Road London W12 ONN, United Kingdom web site address: http://www.irsl.org/~kris
Re: setup feature request
It's already in place. Just click 'default' beside 'all' twice and you should get 'keep'. Kris Thielemans [EMAIL PROTECTED] wrote: comments about that: - the setup version that is currently on the cygwin home page does not have this feature: it cycles between default, install, reinstall There is no such option even in CVS. - it's not an incredible piece of user friendly design. I didn't have a clue you could click there and what the effect would be. Don't get me wrong, being able to do global stuff per category *is* a very nice feature. So, maybe some online help (or just 1 or 2 sentences at the bottom of the dialog box) could sort that out. - what's the difference between 'default' and 'install'? default == install only for the 'Base' category. - it should be very easy to add 'remove' as well. This will finally give us a means to remove cygwin (or just a part of it) easily. Present in CVS. Max.
RE: setup feature request
- what's the difference between 'default' and 'install'? ok, now I know there's no a difference for Base and Misc, but I still don't know what the difference is for the others ... (I guess I'm missing something obvious here) - it should be very easy to add 'remove' as well. This will finally give us a means to remove cygwin (or just a part of it) easily. Unfortunately, setup's remove is not an uninstall. That is, the registry entries for mount points, and shortcuts in the start menu are not removed even if you remove all packages. ok fine. But it does remove the files. That's already something... Patches to address this are welcome :]. sure!
Re: setup feature request
Kris Thielemans [EMAIL PROTECTED] wrote: - what's the difference between 'default' and 'install'? ok, now I know there's no a difference for Base and Misc, but I still don't know what the difference is for the others ... (I guess I'm missing something obvious here) Yep. Default == Keep, unless depended on my something else, in which case, install. Max.
RE: setup feature request
On Sat, 2002-11-30 at 02:15, Kris Thielemans wrote: - what's the difference between 'default' and 'install'? ok, now I know there's no a difference for Base and Misc, but I still don't know what the difference is for the others ... (I guess I'm missing something obvious here) Ah yes. Default = If the package is installed, upgrade to the selected trust level (prev, current or experimental). If the package is not installed, but is in base or misc, install the select trust level's version of that package. Install = Install the selected trust level's version of that package. On categories, default and install apply the above logic to each package contained therein. Rob -- --- GPG key available at: http://users.bigpond.net.au/robertc/keys.txt. --- signature.asc Description: This is a digitally signed message part
RE: setup feature request
Ah yes. Default = If the package is installed, upgrade to the selected trust level (prev, current or experimental). If the package is not installed, but is in base or misc, install the select trust level's version of that package. Install = Install the selected trust level's version of that package. On categories, default and install apply the above logic to each package contained therein. thanks, so maybe it makes more sense to add a 'keep' to this sequence, than to add a 'keep' radio button. Then there's a nice distinction: - radio buttons signify 'trust level' - default et al signify what you want to do. much better I think. Then the question is only how to call things. Suggestions: default - upgrade installed install - upgrade all if this is too long, I'd go for default - upgrade install - install reinstall - reinstall and add 'keep' and 'remove' of course I think it would be helpful to have a few lines saying Please click on default for a category to change which packages are installed. Select if you want the current or experimental versions. Maybe you want to open a category to select settings for a particular package. Then hit 'Next' to start the installation! Kris
RE: setup feature request
I don't like it. Setup's clicky spin control things are not the easiest thing to use. I would much prefer a radio button. well, obviously I thought so as well, as I didn't even see the 'spin control'. but now that I know they're there, I like them. I agree that the functionality of the category headings and radio buttons overlaps. Indeed, you could theoretically get rid of the radio buttons entirely, and put the curr/exp selection into the click-sequence as well. yes, you could, but you'd have to almost double the click-sequence upgrade current upgrade experimental keep remove (or uninstall) install current install experimental reinstall that's a lot of clicking... Kris
Re: setup feature request
Kris Thielemans [EMAIL PROTECTED] wrote: I don't like it. Setup's clicky spin control things are not the easiest thing to use. I would much prefer a radio button. well, obviously I thought so as well, as I didn't even see the 'spin control'. but now that I know they're there, I like them. I agree that the functionality of the category headings and radio buttons overlaps. Indeed, you could theoretically get rid of the radio buttons entirely, and put the curr/exp selection into the click-sequence as well. yes, you could, but you'd have to almost double the click-sequence upgrade current upgrade experimental keep remove (or uninstall) install current install experimental reinstall that's a lot of clicking... It's already a lot of clicking. Which is why I advocate a radio button. Max.
RE: setup feature request
It's already a lot of clicking. Which is why I advocate a radio button. but you can't have a radiobutton for every category...
RE: setup feature request (THREAD MOVING to CYGWIN-APPS)
Setup design discussion happens on [EMAIL PROTECTED] This thread is moving there. sorry. Will it be implemented? (I hope so, and the implementer can get a really nice email from me). I volunteer. fantastic! But I suggest we remove the prev radio button - definitely. it doesn't make sense at all. I'm not promising anything, but there's a slim chance I'll have a patch ready in time for upcoming setup release at the weekend / early next week. you're a hero! by the way, I wouldn't mind seeing full words there instead of curr and exp. maybe 'current' could be replaced by 'up-to-date'? would that be clearer? (was this email nice enough?) Kris
Re: setup feature request
From: Robert Collins [EMAIL PROTECTED] It's already in place. Just click 'default' beside 'all' twice and you should get 'keep'. Default - Install - Reinstall - Uninstall - Default Nope. Max.
Re: setup feature request
On Fri, 2002-11-29 at 06:54, Max Bowsher wrote: From: Robert Collins [EMAIL PROTECTED] It's already in place. Just click 'default' beside 'all' twice and you should get 'keep'. Default - Install - Reinstall - Uninstall - Default Ah. Well seems to me this is the appropriate place to put it, it's more flexible as a category manipulator than a trust level. And less complex to code. Rob -- --- GPG key available at: http://users.bigpond.net.au/robertc/keys.txt. --- signature.asc Description: This is a digitally signed message part
