Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to also bounce when scaling #795

Merged
merged 9 commits into from Dec 18, 2015
Merged

Add option to also bounce when scaling #795

merged 9 commits into from Dec 18, 2015

Conversation

@ssalinas
Copy link
Member

ssalinas commented Dec 10, 2015

screen shot 2015-12-10 at 10 12 58 am
(extra options for incremental bounce only appear when bounce is checked)

return unless data
bounce = $('.vex #bounce').is ':checked'
incremental = $('.vex #incremental-bounce').is ':checked'
@scale(data, bounce, incremental).done =>

This comment has been minimized.

@tpetr

tpetr Dec 10, 2015 Member

how come you're passing bounce and incremental to @scale()?

$(".vex #incremental-bounce-option").show();
else
$(".vex #incremental-bounce-option").hide();
}

This comment has been minimized.

@tpetr

tpetr Dec 10, 2015 Member

we should figure out a way to do this in the view instead

@ssalinas
Copy link
Member Author

ssalinas commented Dec 10, 2015

@tpetr updated form your comments, also the checkbox label just says "Bounce after scaling" now

@ssalinas
Copy link
Member Author

ssalinas commented Dec 15, 2015

Added a field in the request so that you can default that box to checked if you want

@@ -229,6 +232,10 @@ public ScheduleType getScheduleTypeSafe() {
return readOnlyGroups;
}

public boolean isBounceAfterScale() {

This comment has been minimized.

@wsorenson

wsorenson Dec 17, 2015 Contributor

You need one that is the Json getter that just returns the actual value.

If you want to add a helper, you should @JsonIGnore it.

@wsorenson
Copy link
Contributor

wsorenson commented Dec 17, 2015

Is the request option only used by the UI?

@ssalinas
Copy link
Member Author

ssalinas commented Dec 17, 2015

Yes, only used by the ui. Developers wanted a way to have the checkbox default to checked for some requests but not others

@tpetr
Copy link
Member

tpetr commented Dec 17, 2015

This could be addressed in a subsequent PR, but I think it'd be worth packing the bounce + scale functionality into the backend. The "dumber" the UI is, the better.

<label for="bounce" id="bounce-label">
<input type="checkbox" id="bounce"{{#if bounceAfterScale}} checked{{/if}}>
Bounce after scaling
</label>

This comment has been minimized.

@tpetr

tpetr Dec 17, 2015 Member

I'd consider moving the bounce checkbox to after the scale input to fit in with the "bounce after scaling" wording.

This comment has been minimized.

@tpetr

tpetr Dec 17, 2015 Member

bonus points for indenting the incremental bounce option + greying it out if the bounce checkmark is unchecked

This comment has been minimized.

@ssalinas

ssalinas Dec 17, 2015 Author Member

right now the incremental option isn't show if bounce checkmark is unchecked and appears when you check it. would you rather see it greyed out instead of having it hidden?

@ssalinas
Copy link
Member Author

ssalinas commented Dec 18, 2015

New look of the prompt (radio buttons are hidden when bounce isn't checked):
screen shot 2015-12-18 at 8 49 07 am

tpetr added a commit that referenced this pull request Dec 18, 2015
Add option to also bounce when scaling
@tpetr tpetr merged commit 896444e into master Dec 18, 2015
0 of 2 checks passed
0 of 2 checks passed
continuous-integration/travis-ci/pr The Travis CI build is in progress
Details
continuous-integration/travis-ci/push The Travis CI build is in progress
Details
@tpetr tpetr removed hs_qa labels Dec 18, 2015
@tpetr tpetr added this to the 0.4.6 milestone Dec 18, 2015
@ssalinas ssalinas deleted the bounce_and_scale branch Dec 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.