Aspect Ratio Identification
Reported by Brian Michalski | September 26th, 2010 @ 04:08 PM
Identify the aspect ratio of a screen given it's height and width in pixels. We use this to suggest templates, display a screen icon, and a few other small things.
Comments and changes to this ticket
-
Zach Rowe March 17th, 2011 @ 03:40 PM
are we only interested in 4:3 vs 16:9, or should we identify other aspects as well
-
Brian Michalski March 17th, 2011 @ 08:24 PM
Good queston Zach. 4:3 and 16:9 are the two we definitely need to support.
I could see a use for recognizing 9:16 displays (like a portrait monitor)
but I don't know how critical that use is. Perhaps we can simple add a
fraction into an array somewhere (like this new method?) telling it what
sizes it should recognize... -
Haris Khan March 17th, 2011 @ 09:12 PM
There would also be value in 16:10 ratios (ie computer displays)
-
Zach Rowe March 18th, 2011 @ 12:04 AM
so does it make sense to store the ratio separately? I 'm trying to think end-to-end, what would be the best way to retrieve such information. We could store the value pair, and do computation in the screens controller
-
Brian Michalski April 10th, 2011 @ 03:48 PM
- Assigned user set to “Zach Rowe”
- State changed from “new” to “open”
(from [69043b31ddac8712f157b1852b8582859c8f30ee]) storing screen resolution, calculating aspect ratio [#131 state:open assigned:'Zach Rowe'] [#111 state:open assigned:'Zach Rowe'] https://github.com/wtg/concerto/commit/69043b31ddac8712f157b1852b85...
-
Brian Michalski April 11th, 2011 @ 01:34 AM
- Tag changed from “v2” to “screen, v2”
-
Brian Michalski April 12th, 2011 @ 08:47 PM
Zach - Any chance you want to write a test case to go along with this? If you do, I think we can mark this resolved. If you'd rather I write the test that's fine to, just let me know!
-
Brian Michalski April 30th, 2011 @ 10:37 PM
- State changed from “open” to “resolved”
(from [867b52e56b1084aa26b549667de9fef71347542e]) added test for aspect ratio [#111 state:resolved] https://github.com/concerto/concerto/commit/867b52e56b1084aa26b5496...
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Concerto is an open source digital signage system that makes it easy to engage a large community of people with graphical and text-based announcements, bulletins, and other messages... but enough about us, you came here to get involved.
<br />
If you think you've <b>found a bug in Concerto</b>, please click 'Create new ticket' and let us know about it.
<br />
Looking to peek at our source code? Head to <a href="https://github.com/concerto/concerto_v1">https://github.com/concerto/concerto_v1</a> (Concerto version 1) or <a href="https://github.com/concerto/concerto">https://github.com/concerto/concerto</a> (Concerto version 2).
<br />
Our getting started guide is available here: <a href="https://github.com/concerto/concerto/wiki/Getting-Involved">https://github.com/concerto/concerto/wiki/Getting-Involved</a>.
People watching this ticket
Brian Michalski
Haris Khan
Michael DiTore
Zach Rowe
Referenced by
-
131
Identify Screen Aspect Ratio
(from [69043b31ddac8712f157b1852b8582859c8f30ee])
storing...
-
111
Aspect Ratio Identification
(from [69043b31ddac8712f157b1852b8582859c8f30ee])
storing...
-
131
Identify Screen Aspect Ratio
What's the difference between this and #111? Is
calculati...
-
131
Identify Screen Aspect Ratio
You're right. Duplicate of #111.
-
111
Aspect Ratio Identification
(from [867b52e56b1084aa26b549667de9fef71347542e])
added t...