Let people select multiple packages to install at once

[chrissie1]

Make it possible for the user to install multiple packages at once. Let them select and then click install selected or something.

[bsara]

Is this a feature that will be included soon? I would desperately love to have it. Any way that I can help with the implementation?

[gep13]

At present, no, not likely :-( We have just had our first child, so my time will be limited. In the current pre-release version of chocolatey, there is a system to allow multiple packages in a single command, so I suspect that if we implement this, we should be able to take advantage of this new functionality. There is a question whether we take a dependency on the beta version though, or whether we wait for the official release. I suspect the latter.

[bertvanbrakel]

+1 for this feature. Usability really suffers. It would be great if it could download everything in the background, and only when all packages have been downloaded run the installs. This means a user on a brand new machine could simply tick all the progs required, go away and have some coffee then in one sitting go through each individual installer without needing to wait between downloads

[RichiCoder1]

Multi select could be a thing, but splitting downloads and installing probably wouldn't, at least not in the short term. Thats a limitation of chocolatey, not choco GUI.

[gep13]

@RichCoder1 what are you thoughts on this one? Should we include in the 0.12.0 release, which I am terming the "WPF Refresh" release, or push out to vNext, which will be 0.13.0?

[RichiCoder1]

Probably vNext. Multiselect is something I need more time and brainpower to tackle probably.

[gep13]

Okay, for now, let's push it out, and concentrate on the other stuff.

[philweb]

+1, any news on this? Functionality seems to be implemented in chocolatey. Additionally pre-selecting multiple options via config would be neat.

[gep13]

Hey,

At the minute no, this is not something that have progressed anywhere yet :-(

Gary

[jrkd]

I'd be keen to implement this. Need to have a look a the UI setup, so don't assign me or anything, but I'll fork and see how we go.

[compwiz21]

Why can't we have it so that when users select multiple items, it adds it to a que that gets processed? Still installing one at a time, but without any manual intervention by users?

[ziziz]

Next to Half-Life 3 and 'long, (really long) range Wi-Fi', this would improve my life ;-)

In the scope of ChocolateyGUI, selectability is far more useful than categories or improved filter functions In my opinion. I realized that more than 30% of my 'chocolatey installs' was for multiple apps.

I realized that most often in those cases ive started with a clistin the terminal followed by either searching in the chocolatey web-galley or in the gui to get some visual aid and confirmation needed.

When searching the gui I made one install there followed by going back to the terminal for installing more apps. Looking at that popup progress-bar/term-output is a frustrating experience if you have more apps to install!

[vertigo220]

This seems to be related to issue #87, and is one of the things I came here to suggest. A batch feature would make a HUGE difference in the usability of Chocolatey, especially for those of us with relatively slow connections, where installing many programs requires a lot of waiting. This is further compounded by the fact that, as I mentioned in issue #595, the GUI is painfully slow at loading search results. I think Chocolatey would benefit greatly from this, and imagine a simple "Add to Queue" and/or plus sign followed by a command to download and install all queued items would be the best way to do it. In order for it to work properly, it would have to log any errors and present them all at the end, instead of halting on them, and it would ideally allow you to continue adding items to the queue as it's processing (and perhaps start processing right away, or have an option to do so), so you can get it going while selecting programs, instead of wasting time having it idle during that process, but not then be unable to keep adding more to keep it busy overnight or whatever.

[sigino]

Is this feature still not implemented? I might have a look if not?

[AdmiringWorm]

@sigino I do not believe it has yet been implemented.

[mkevenaar]

+1 I would love to see this function implemented.

[pherwanikar]

Is this feature still not implemented? I might have a look if not?

[Xoph]

I'm interested at taking a look at this. I'm basically new to Git, and totally new to this project, so if someone can "sponsor" me please reach out to me directly and I'll try to tackle this.

Looking to improve my personal skills by contributing to an actual project that is relevant to me.

[AdmiringWorm]

@Xoph I don't know about sponsoring you, but if you got any questions regarding git, feel free to reach out to me on gitter (If the link don't work, I am AdmiringWorm on gitter).

What I recommend you start with though, is to familiarize yourself with the basic commands on git (I do not recommend using a gui until you at least know what some of the commands do, and how to use them).

The commands I consider basic are (In no specific order):

• git clone (this command clones a remote repository to your local machine. IE git clone https://github.com/Xoph/ChocolateyGUI.git << assuming you have created a fork of the ChocolateyGUI repo here on github).
• git switch (changes the current branch on your local machine. You will see people mentioning git checkout, but that is the old way to do it)
  • Example: you got three branches locally, master, develop, and gh-12. Using git switch gh-12will change your current branch to thegh-12branch. (Usegit switch -c branchName` to create a new branch) WARNING: Never do work on the master or develop branch, but always do it in a branch not existing in the upstream (In this case ChocolateyGUI) repository.
• git fetch (fetches the meta information from the remote repository based on the repository you are tracking for your current branch).
• git pull (pulls in the updated data from the remote repository branch that your local branch is tracking)
• git push (pushes out your local changes to the remote repository+branch that your local branch is tracking).
  • For new branches, they aren't tracking any branches, which means when you have done some work you need to specify where to push the changes with the following: git push -u origin branchName (origin being the reference point of the repository you originally cloned, and branchName being the branch you wish to push)
• git add (this command requires additional arguments, it wants the relative path to the files you wish to include in your changes. ie: git add src/ChocolateyGUI.sln src/ChocolateyGUI/SomeSourceFile.cs, basically it will stage those two files)
• git commit (this will typically open up a text editor that you can enter some text for the changes you have made, you may also use the `-m "Input text" argument instead of having a text editor pop up).

That is what I can think of right now.

Basic workflow on github is (example commands, may differ from what you decide):

1. Fork the repository ()
2. Clone your fork (git clone https://github.com/Xoph/ChocolateyGUI.git)
3. Create a work branch (git switch -c gh-12)
4. Do some work
   1. Stage your changes (git add filesChanged)
   2. Create a commit/change message (git commit)
   3. Repeat until all necessary changes have been made...
5. Push your changes to your fork (git push -u origin gh-12) (You will be asked for your github username and password the first time).
6. Open a Pull Request on the repository (https://github.com/chocolatey/ChocolateyGUI/compare )
   1. Change the base branch to your work branch ( )
   2. Press Create Pull Request, and input a title and body message.

I unfortunately don't got any hands-on tutorials to follow, as the ones I used when I started no longer exist 😞.

Yes, there is quite the learning curve for using git. But once you get used to it, you won't be able to do without it 😺.

[AdmiringWorm]

For the project specifically, I think the Contributing Guidelines pretty much goes through what is necessary to contribute (With the exception of using git itself of course).

[Xoph]

I've contributed to repos before using the tooling available on the website, I just haven't used the git command-line.

The Contributing Guidelines page doesn't appear to highlight all the project dependencies. Is there any documentation on that?

[umarabdullahmansoori]

why every idea just remains an idea on chocolatey? why its not been implemented since 7 years

[ppvnf]

Any update on this?

[yaomtc]

Nope.

Personally, I just stopped using Windows. For those stuck there, I'm sorry for the mess you have to deal with.

[CynicalWilson]

WOW! Issue opened in pretty much exactly 10 years ago, and still no ability in Choco-GUI to simply select multiple packages to install in succession?? so sad.... and I love the tool

[gep13]

and still no ability in Choco-GUI to simply select multiple packages to install in succession?? so sad.... and I love the tool

There are lots of reason as to why this function hasn't been implemented in Chocolatey GUI. Primary amongst them that time and other commitments haven't allowed for it.

If you are interested in helping with a PR to provide this functionality, I would happily provide feedback on any suggestions that you might have.