home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
WebService and Mobile Access
Popular Plugins
MPExtended
WebMediaPortal Design
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Aredon" data-source="post: 829864" data-attributes="member: 113994"><p>Back several posts to your original comment on drop downs, and you'll find it <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" />.</p><p></p><p><a href="http://harvesthq.github.com/chosen/" target="_blank">http://harvesthq.github.com/chosen/</a></p><p></p><p>This isn't true, mobile browsers display rendered images and do not obey pixel density. They load the page, create an image that approximately holds all the content, and then display that to fit the resolution. This is why there is never side scroll, so 960 stretches to roughly the full 1280, and anything above 1280 gets compressed. Ergo: when you attempt to add more content and use the "extra space" you will effectively shrink the rest of the page. Unless you fit it exactly inside the 1280 resolution, but then you'd have no margin on that page, and you'd also be neglecting devices with smaller resolutions.</p><p></p><p>This is why many mobile designers attempt to do fluid width. The problem is that fluid width will cause all sorts of problems with floats and images, and just the layout in general. You rapidly lose control of the user experience across platforms. While it is possible to create a resolution responsive design experience, they're a huge pain to work with. I prefer to use fixed width and keep the page looking the same on all platforms.</p><p></p><p> </p><p>This could be added to the group-by dropdown could it not?</p><p></p><p> </p><p>The sorting itself may be faster, but if you do your sorting on the back end you have to add in page load times. Which means more data fetching and more load. It's easier on the user to sort client side in most cases.</p><p></p><p></p><p>Is that really much different than skins? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /> That sounds doable, I can't promise I'll have time to do both (but i'll try). Really the only reason I'm doing this is I don't have any projects that are earning me money while I'm on break. I need my code fix <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" />.</p></blockquote><p></p>
[QUOTE="Aredon, post: 829864, member: 113994"] Back several posts to your original comment on drop downs, and you'll find it :). [url]http://harvesthq.github.com/chosen/[/url] This isn't true, mobile browsers display rendered images and do not obey pixel density. They load the page, create an image that approximately holds all the content, and then display that to fit the resolution. This is why there is never side scroll, so 960 stretches to roughly the full 1280, and anything above 1280 gets compressed. Ergo: when you attempt to add more content and use the "extra space" you will effectively shrink the rest of the page. Unless you fit it exactly inside the 1280 resolution, but then you'd have no margin on that page, and you'd also be neglecting devices with smaller resolutions. This is why many mobile designers attempt to do fluid width. The problem is that fluid width will cause all sorts of problems with floats and images, and just the layout in general. You rapidly lose control of the user experience across platforms. While it is possible to create a resolution responsive design experience, they're a huge pain to work with. I prefer to use fixed width and keep the page looking the same on all platforms. This could be added to the group-by dropdown could it not? The sorting itself may be faster, but if you do your sorting on the back end you have to add in page load times. Which means more data fetching and more load. It's easier on the user to sort client side in most cases. Is that really much different than skins? :D That sounds doable, I can't promise I'll have time to do both (but i'll try). Really the only reason I'm doing this is I don't have any projects that are earning me money while I'm on break. I need my code fix :). [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
WebService and Mobile Access
Popular Plugins
MPExtended
WebMediaPortal Design
Contact us
RSS
Top
Bottom