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

Set scrum board column widths according to issue percentages #2

Closed
wants to merge 1 commit into from
Closed

Set scrum board column widths according to issue percentages #2

wants to merge 1 commit into from

Conversation

rombert
Copy link
Member

@rombert rombert commented Sep 14, 2011

Allowing the columns to have widths set as percentages of the issues
show in the column from the total issues gives better results in terms
of layout.

There is still room for improvement, as the percentages may not be
multiples of the size of the scrum cards, but I don't see how this can
be done without using Javascript to detect the client's viewport
dimensions.

Tested on FireFox 6, Opera 11, Chromium 15 and IE 9 ( including
IE 8 mode ).

Fixes #222: Scrum board columns do not always fill all available space

Allowing the columns to have widths set as percentages of the issues
show in the column from the total issues gives better results in terms
of layout.

There is still room for improvement, as the percentages may not be
multiples of the size of the scrum cards, but I don't see how this can
be done without using Javascript to detect the client's viewport
dimensions.

Tested on FireFox 6, Opera 11, Chromium 15 and IE 9 ( including
IE 8 mode ).

Fixes #222: Scrum board columns do not always fill all available space
@rombert
Copy link
Member Author

rombert commented Sep 14, 2011

Querying the document.getElementsByClassName('scrumboard')[0].clientWidth property will ( should ? ) give us the width we need, and then we can decide how many cards we can display, and assign them to each column, e.g. first column gets 2_card width, second gets 3_card width, third gets 1*card width.

But I have no idea how to pass this information to the plugin without moving all the logic to JS, which I'd like to avoid.

dregad added a commit that referenced this pull request Mar 12, 2014
@dregad dregad closed this Mar 12, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants