Future WPI feature requests! 8.0.0

[Kelsenellenelvian]

Lets have them here guys and gals!

Edited May 10, 2010 by Kelsenellenelvian

[mritter]

@Wazer: Added 120Hz and 240Hz for giggles. Deleted your thread since this thread already existed.

[xure]

How about an option in wpi_theme.js to have the install button be able to be placed in the bottom corners (same as Theme_ExitButtonLocation does for the exit button)? I would love to be able to have the exit button in the lower left corner and the install button in the lower right.

[ghaffar]

How about an option in wpi_theme.js to have the install button be able to be placed in the bottom corners (same as Theme_ExitButtonLocation does for the exit button)? I would love to be able to have the exit button in the lower left corner and the install button in the lower right.

Being able Install, Options, Config , ... buttons to be placed in the right side is a good idea for right to left Languages like Persian and Arabic.

and

What do you think about placing the options

Shut down

Restart

computer after installation is complete

in the main or the installer window?

Edited May 28, 2010 by ghaffar

[Kelsenellenelvian]

@ Ghaffer = Please look in the options section better. For the restart\Shutdown options.

The option is already built in. It just isn't on the main interface.

Edited May 28, 2010 by Kelsenellenelvian

[ghaffar]

@ Ghaffer = Please look in the options section better. For the restart\Shutdown options.

The option is already built in. It just isn't on the main interface.

Thank you 'Kelsenellenelvian'

May be I couldn't explain my idea well.

I know restart\Shutdown options and I always use Restart option which is in option menu.

But sometimes (not always) I don't want to wait until completing the installation and restarting the computer and then manually shutting down the computer.

In such cases I want the computer to be off after I came back to work.

I want to be an option to ignore the Restart option and instead of it, the computer goes to shutdown.

Only when I don't have time to wait and I have to leave the work for a long time.

Edited May 28, 2010 by ghaffar

[Kelsenellenelvian]

OK I see now!

I have an idea I will run past mritter you will like.

[ghaffar]

OK I see now!

I have an idea I will run past mritter you will like.

Thank you Kelsenellenelvian

mritter did it for me exactly what I wanted.

Here you can see the new installer window

Also I want to know other users opinion here:

Edited June 6, 2010 by ghaffar

[icnocop]

Hi.

Thank you for WPI v8.0.3.

I am re-requesting the following features:

icnocop

Posted 24 November 2009 - 05:40 PM

...

[The ability to redirect the stdout of a command from a console application] does not work if the program I want to execute has quotes around it or one of its command line parameters (if there is a space in the name for example).

For example, the following command does not work as expected

cmd /c "D:\some\path\on\dvd\app.exe" "param1" >c:\app.txt

It produces 'D:\some\path\on\dvd\app.exe" "param1' is not recognized as an internal or external command, operable program or batch file.

However, if I remove the quotes, it works as expected:

cmd /c D:\some\path\on\dvd\app.exe "param1" >c:\app.txt

and\or

cmd /c D:\some\path\on\dvd\app.exe param1 >c:\app.txt

I do not have a long path name just yet, so this work around works great for me, so this may be another request in the future.

I also tried testing escaping the quotes like so

cmd /c "\"D:\some\path\on\dvd\app.exe\" \"param1\"" >c:\app.txt

and

cmd /c "\"D:\some\path\on\dvd\app.exe\" \"param1\" >c:\app.txt"

but they both produced a similar error as before.

Thanks again.

mritter

Posted 25 November 2009 - 06:51 AM

...

Will look into the quotes.

icnocop

Posted 10 December 2009 - 06:33 AM

Hi again,

I would like to request two new global options in wpi:

1. optionally stop running the rest of the commands if a failure was encountered

(ex. "1")

2. optionally execute the following command if a failure was encountered

(ex. "cmd /c c:\some\path\to\exe parameter1 parameter2")

Thank you very much.

icnocop

Posted 17 December 2009 - 02:54 PM

Hi.

I would like to request a new feature.

I have a program that returns an exit code of 3010 to indicate a reboot is required.

I would like wpi to automatically reboot the system and then re-run the same command until the exit code is 0, and then continue on to the next command.

In this way, I can re-use the same command as it may behave differently on each machine I run wpi on.

Thank you.

Kelsenellenelvian

Posted 17 December 2009 - 04:39 PM

Reboots are no real issue.

The problem is this:

How are we to know what the heck the exit code is every time and then tell WPI that information?

icnocop

Posted 17 December 2009 - 04:55 PM

the wpi log file indicates the exit code of each command, so i don't see that as an issue.

i would imagine two additional program settings:

return_code_reboot[pn]=['3010'];

rerun_on_reboot_return_code[pn]=['yes'];

[mritter]

I sent icnocop a beta copy with 2/3 of his requests done for beta testing.................

[AlBundy33]

I'd like to see nightly builds or public betas.

Al

[mritter]

I'd like to see people who I send betas to to get online and download them in under a week's time.

[mritter]

@icnocop: Did you try out the beta copy I sent you via PM?

[icnocop]

@icnocop: Did you try out the beta copy I sent you via PM?

No, sorry, I have not had time to look at it yet.

[icnocop]

Hi.

Thank you for the updates.

I took the time to test this out and here are my results.

1. stdout redirection and quotes in the path: Pass

Ex. command: cmd /c """ping.exe"" ""127.0.0.1"" >c:\test\ping.txt"

2. abort installation process if failure occurs: Pass

3. script or program to execute if failure: Pass

4. Continue next installation where failed: Pass

Thank you!