プロジェクト

全般

プロフィール

Vote #72442

未完了

Add support for HDPI screens (retina)

Admin Redmine さんが約4年前に追加. 約4年前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
UI_10
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
10
version_id:
0
issue_org_id:
11757
author_id:
22476
assigned_to_id:
0
comments:
7
status_id:
1
tracker_id:
2
plus1:
1
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

Adding support for the HDPI screens that are coming (and also here already) would be a good thing for redmine (at least in the interface).
Currently the app looks good generally, but some parts like the icones are fuzzy and become distractive on HDPI screens.

There is a choice concerning the method of implementation:


journals

I would like to help with the move to hdpi.

I can help with the implementation I will simply need the graphic assets in hdpi.

Can someone help me locate suitable assets?

Where do the original assets come from?
--------------------------------------------------------------------------------
After reading some material about HDPI for web applications I came to the following conclusion: javascript might not be the most efficient way of loading hdpi.

The best way seems to be : send everything in x2 versions to everybody.

While using javascript would allow HDPI support without any ruby code modification this would lead to double download of images. This approach leads to a lot of changes on the client side during rendering. Maybe it's the best solution while there are relatively few HDPI devices out there, but in the end - I believe - support for higher resolution images should be handled with a cookie and on the server side.

So I started tinkering with the code. Currently when I call image_tag there is no way to get the real size of the image without reading each image. Is there a way to store these values in a cache after the first read?

I intend to also collect data about image versions (cancel.png, cancel-1.5x.png, cancel-2x.png ...). Should I store that in a cache to avoid nailing the disk on every request?

I might create a second function hdpi_image_tag to allow enabling/disabling the option and leave image_tag to its current purpose.

Would this be the right approach?
--------------------------------------------------------------------------------
Should I go with the ruby changes or should I try the javascript approach first?
--------------------------------------------------------------------------------
+1 Time has come, I guess. ;-)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------


related_issues

relates,Closed,24927,Render high resolution Gravatars and Thumbnails
relates,Closed,24922,Support high resolution images in formatted content
relates,New,23980,Replace images with icon fonts

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0