konqueror的大图形元素问题？ [英] large graphic elements troubles in konqueror?

问题描述

我已经使用这种技术大约一年

来创建装饰标签和圆形角落

盒子（窗户？）

http://www.alistapart.com/articles/slidingdoors/


一切正常（从MacOs09，IE5一直到来） >
到Firefox）。


因为我们的产品有时会产生大量的b $ b（SQL）结果设置，我们的用户有时候会这样做b $ b发现图形不够大

足够。


所以我将图形设为2560宽（新的Mac显示器）

3500像素深（所有浏览器都滚动）


一切似乎都很好，除了看起来好像

Konqueror并不喜欢这个。

显示是正确的，但很慢。


我会很乐意承认使用2560x3500图形

来放置块上的角落看起来有点矫枉过正:-)


有没有其他人经历过这个？


BugBear

解决方案

bugbear< bugbear@trim_papermule.co.uk_trim>写道：

一切似乎都很好，除了Konqueror看起来好像没有享受这个。
显示是正确的，但很慢。

我很乐意承认，使用2560x3500图形将圆角放在一个块上似乎有点矫枉过正： - ）

使用图形查看器用于查看此（这些）图像的属性，

查找类似未压缩大小的内容。然后考虑这个

数据量需要由图形处理器在视口中的内容的每次移动时用

抽出。


然后考虑资源有限的系统，如移动设备，而不是最近的桌面系统。


-

Spartanicus

bugbear写道：

我一直在使用这种技术一年左右创建装饰标签和圆角框（窗户？）

http://www.alistapart.com/articles/slidingdoors/

一切正常（从MacOs09，IE5到Firefox）。

因为我们的产品有时会提供大量的SQL结果，我们的用户有时会发现图形不够大。
3500像素深（所有浏览器都滚动）

一切看起来都很好，除了Konqueror似乎是
不是很享受这个。
显示器是正确的，但速度很慢。

我会很乐意承认使用2560x3500图形来放置一个块上的圆角似乎矫枉过正： - ）

考虑到图像被转换回逐像素

形式，这样的图像大约需要26Mb到显示在浏览器窗口带有

a正常颜色深度。

~26Mb圆角内存不是一种矫枉过正 - 这是超级技能

:-)

（如果你使用的是PNG图像，在顶部加上这个尺寸的1/4）

计算机可能只有比其他人更小的RAM（？）

Spartanicus写道：

bugbear< bugbear@trim_papermule.co.uk_trim>写道：

一切似乎都很好，除了看起来Konqueror不喜欢这个。
显示是正确的，但非常我很乐意承认，使用2560x3500图形将圆角放在一个块上似乎有点矫枉过正:-)

使用图形查看器查看这（这些）图像的属性，
寻找类似未压缩的大小的东西。然后考虑到图形处理器需要通过视口中内容的每次移动来抽取大量数据。

该软件需要愚蠢才能做到这一点。

简单的边界框交叉点裁剪

会大大减少数据传输的大小。

然后考虑资源有限的系统，如移动设备，而不是最近的桌面系统。

我们的强加我们客户的机器/浏览器规格

相当新近且相当强大。


我的设计不是网站，而是网络交付的应用程序利基市场
。


BugBear

I''ve been using this technique for around a year
to create "decorated" tabs and round cornered
boxes (windows?)

http://www.alistapart.com/articles/slidingdoors/

Everything worked fine (all the way from MacOs09, IE5
to Firefox).

Because our product sometimes puts large
(SQL) results sets up, our users sometimes
found that the graphics weren''t big
enough.

So I made the graphics 2560 wide (the new Mac display)
by 3500 pixels deep (all browsers scroll)

Everything seemed fine, except that it appears
that Konqueror isn''t enjoying this.
The display is correct, but very slow.

I will readily admit that using a 2560x3500 graphic
to put round corners on a block does seem overkill :-)

Has anybody else experienced this?

BugBear

解决方案

bugbear <bugbear@trim_papermule.co.uk_trim> wrote:

Everything seemed fine, except that it appears
that Konqueror isn''t enjoying this.
The display is correct, but very slow.

I will readily admit that using a 2560x3500 graphic
to put round corners on a block does seem overkill :-)

Use a graphics viewer to view the properties of this (these) image(s),
look for something like "uncompressed size". Then consider that this
amount of data needs to be pumped around by the graphics processor with
every movement of the content in the viewport.

Then consider systems with limited resources like mobile devices and not
so recent desktop systems.

--
Spartanicus

bugbear wrote:

I''ve been using this technique for around a year
to create "decorated" tabs and round cornered
boxes (windows?)

http://www.alistapart.com/articles/slidingdoors/

Everything worked fine (all the way from MacOs09, IE5
to Firefox).

Because our product sometimes puts large
(SQL) results sets up, our users sometimes
found that the graphics weren''t big
enough.

So I made the graphics 2560 wide (the new Mac display)
by 3500 pixels deep (all browsers scroll)

Everything seemed fine, except that it appears
that Konqueror isn''t enjoying this.
The display is correct, but very slow.

I will readily admit that using a 2560x3500 graphic
to put round corners on a block does seem overkill :-)

Taking into account that images are converted back to pixel-by-pixel
form, such image takes ~26Mb to be displayed in the browser window with
a normal color depth.
~26Mb RAM for rounded corners is not an overkill - it is a superkill
:-)
(add 1/4 of this size at the top if you''re using PNG image) That
computer may simply have lesser RAM than others (?)

Spartanicus wrote:

bugbear <bugbear@trim_papermule.co.uk_trim> wrote:

Everything seemed fine, except that it appears
that Konqueror isn''t enjoying this.
The display is correct, but very slow.

I will readily admit that using a 2560x3500 graphic
to put round corners on a block does seem overkill :-)

Use a graphics viewer to view the properties of this (these) image(s),
look for something like "uncompressed size". Then consider that this
amount of data needs to be pumped around by the graphics processor with
every movement of the content in the viewport.

The software would need to be dumb to do that.
Simple "Bounding box" intersection clipping
would greatly reduce the sizeof the data transfer.

Then consider systems with limited resources like mobile devices and not
so recent desktop systems.

Our "imposed" machine/browser spec for our customer
is fairly recent and fairly powerful.

My design is not a website, but a web-delivered app
in a niche market.

BugBear

这篇关于konqueror的大图形元素问题？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！