7 Commits (7efe3cac3d5e728ee471bbccfd1043e06e4dcafe)

Author	SHA1	Message	Date
Adrien Delorme	ddd96c513b	first draft at self refreshing loading bar centralized/controlled by Ui	8 years ago
Adrien Delorme	9cefd69f0d	change progress bar display rate to 5s to reduce 'spamminess' (#6640) ... #6625	8 years ago
Ali Rizvi-Santiago	cf9bbe3ecf	Incorporated the hack demonstrated by @SwampDragons in order to deal with packer.rpc.Ui not exporting any information about what it's doing to anybody.	8 years ago
Ali Rizvi-Santiago	5726927cba	Moved the progress bar out of packer.Ui and unlinked it out of all the packer.Ui implementations. Split up the terminal-related functions into a separate terminal.go and calculate the progress bar width by traversing through packer.Ui to avoid the issue with github.com/ugorji/go/codec serializing private members (or unsafe pointers) of structs. Shuffled some arguments around in getConsoleScreenBufferInfo in common/terminal_windows.go so that the interface forces the user to correctly declare a _CONSOLE_SCREEN_BUFFER_INFO type.	8 years ago
Ali Rizvi-Santiago	0f10032b3d	Moved the progress bar from common to the packer.UI interface and refactored it so that the terminal width is calculated based on each interface which returns a custom progressbar specific to its ui.	8 years ago
Ali Rizvi-Santiago	fd2fef8738	Added support for the progress bar to automatically determine its width using the minimum length from a packer.UI and the terminal dimensions via kernel32.GetConsoleScreenBufferInfo or an ioctl (TIOCGWINSZ) to "/dev/tty".	8 years ago
Ali Rizvi-Santiago	16ecb3ad9a	Reverted removal of progress-bar that was done by commit 5d97b105a8 and added some missing arguments that were missed during the rebase. Modified the default progress bar's width to 80 as a result of the conversation on PR #5851.	8 years ago