[valtam]

Please also be aware that after you have merged your changes, I may sometimes go in and make small adjustments. Just a reminder to always pull before you push :)

[ralphy]

What do you think of the idea of going back to the Task Selector once packages have been installed or removed?

Clearly a good point considering that users can select multiple packages for installation! Yup, I like the idea of going back to the Task Selector once packages have been installed or removed. Great catch!

In the process of evaluating this, I noticed that we are wrongfully exiting the loop on Install/Removal confirmation. When applications are selected for install or removal a confirmation dialogue appears "The following software has been selected: software_name - Do you want to proceed with the installation/removal?"

If the user clicks No we should loop them back to the install/remove panel they came from. Right now they are being taken out of the loop, back to Task Selector.  <= Not happy

Think about end users selecting an application for installation/removal by mistake and therefore changing their mind about what to install or remove... The current loop exit is obviously wrong at that point. That needs to be changed I believe. Do you agree?

[ralphy]

Also wondering if the user clicks the X in the corner of the application in the Install or Remove window, we can make it quit Lite Software altogether?

This is not possible with zenity. Remember we are getting only two values from zenity to work with $0 $1... and the X and 'Cancel' button are the same value always.

[ralphy]

Please also be aware that after you have merged your changes, I may sometimes go in and make small adjustments. Just a reminder to always pull before you push :)

I actually check if there are changes in master to pull before pushing (just in case) :P  I don't want to overwrite each other's work. If it ever happens it can safely be assumed an accident.

[valtam]

Agreed Reply #31

[ralphy]

Agreed Reply #31

Changes committed to master. I think it is a good time to test what we have up to this point. We've made substantial improvements in the last few commits to lite-tweaks and lite-software.

[valtam]

Will do, cheers Ralphy.

[valtam]

FYI, in Series 4.x we will have just one Lite Software package. In the rare case there is a 64bit only version of a package (which I'm likely to avoid including anyway) we'll use a uname check then offer the correct arch version of that software.

[valtam]

UPDATE: I've just done a check going from i386 and amd64 in the Debian Control file to all and then installing the newer package into a test box on both archs and it works fine. This means we don't have to maintain 2 versions anymore. Just need to find a way to have the all version without losing our commit history in Github.

[ralphy]

Well, if nothing else I don't think that history keeping should be a deal breaker.