flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ariel Jakobovits <arielj...@yahoo.com>
Subject Re: [IDEAS] Flex: New user interface design
Date Tue, 28 Feb 2012 00:17:33 GMT
Two ideas that may be worthless, but:

1. can we determine ppi from the mouse cursor/arrow - is it a standard size that we can measure?
2. can we develop a preloader/component that can query the user to define 1 inch that we can
then use for the app to be sized correctly?
Ariel Jakobovits
Email: arieljake@yahoo.com
Phone: 650-690-2213
Fax: 650-641-0031
Cell: 650-823-8699

 From: Erik Lundgren <erik@lndgrn.se>
To: flex-dev@incubator.apache.org 
Sent: Monday, February 27, 2012 2:58 PM
Subject: Re: [IDEAS] Flex: New user interface design

27 feb 2012 kl. 23.18 skrev Alex Harui:

> Let's assume it won't be fixed but you may be able to get a rough, but not exact idea
of resolution/density via other means (JS, ANE).

I've researched this all day and I cant find any cross browser js api that allows you to break
out of the 96 ppi abstract screen that the browser assumes for rendering. In extreme cases,
like the iPhone 4, I belive the user agent recalculates the pixel values.

If we could do it in air using native extensions, but not on the web should we do it anyway?
I don't know.

> It sounds like the problem remains unsolved in browsers as well in that the reported
resolution or density isn't 100% accurate.  Seems like that would
> have always been the case for any analog screen anyway, wouldn't it?

It's broken. Thats why I hoped we could fix it. :)

> What is the measure of success?  Is it that a 1-inch button is roughly 1 inch or exactly
1 inch?  Or is it to guarantee a workflow that allows good printing?

Perfection is good. I would like to abstract away the device scaling factor, making lives
easier for designers/developers.

For me the functionality would offer a paper, to screen, to paper workflow.

I do a lot of early wireframes on paper. A unified measuring stick would be really helpful.
You could simulate a device you don't own on paper. You could easily study a early layout
in the users own context without the device or any code.

Designers/developers would train their eyes to one scale-set allowing them to better understand
it and how to apply it to images, text, usecases etc.

And in the end it would be a great foundation for advanced printing out of Flex applications.

I can think of many more benefits, but sadly we seem to operate on one system abstraction
to high for that to happen. (If someone else can't think of something smart.)


(Sorry for my english)
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message