r3wp [groups: 83 posts: 189283]
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r3wp

[!REBOL3 GUI]

Ladislav
24-Jun-2010
[1701x2]
But, are you saying, that you could get a picture like 216 being 
scaled so, that the two boxes in the middle do not change their sizes, 
while the first one and the last one do so, that the boxes remain 
next to each other all the time?
(Cyphre was pretty sure, it was not possible)
BrianH
24-Jun-2010
[1703]
I am not asking about the math - I trust you and Cyphre to make the 
math absolutely perfect. I am at the moment asking about the semantics 
of the resize model
Ladislav
24-Jun-2010
[1704]
yes, but I was asking, whether that layout was possible, expressing 
the opinion it was not, but I may be wrong, of course
Rebolek
24-Jun-2010
[1705]
I don't like max-size, but the way it's done now, I think, that it 
can be omited from style-writing and R3/GUI can take care of it. 
But that's just a guess right now. There's now code to support my 
guess.
Ladislav
24-Jun-2010
[1706]
factors: min-size, max-size, group, panel
Rebolek
24-Jun-2010
[1707]
now=no
BrianH
24-Jun-2010
[1708]
It was theoretically possible with Carl's resize model - ignoring 
whether the math worked - but it was really awkward to specify. That 
is my main concern.
Ladislav
24-Jun-2010
[1709]
Rebolek, actually you are wrong, you cannot define layouts with elements 
having max-size/min-size without having a direct support for these 
features (maximally, you can get some "ugly approximations", but 
surely not the same behaviour)
BrianH
24-Jun-2010
[1710]
The main problem with Carl's resize model was that it was difficult 
to specify proportional scaling independent of max-size. This made 
layouts fail on unexpectedly large screens, or made it necessary 
to put in a lot of very large numbers in max-size.
Ladislav
24-Jun-2010
[1711]
That dependency does not exist in the new resizing model
BrianH
24-Jun-2010
[1712]
Well then that is really good news :)
Ladislav
24-Jun-2010
[1713]
And, yes, that was a motivation for me to invent something more convenient
Rebolek
24-Jun-2010
[1714]
I know I'm wrong regarding the min-size, but not the max-size.
Steeve
24-Jun-2010
[1715]
I just think  proportional resizing feature is the problem. It's 
usually useless and hard to code.
Graham
24-Jun-2010
[1716x2]
re language support .. I think primarily faces have to adjust for 
different lengths of text
when you translate from one language to another
BrianH
24-Jun-2010
[1718]
Hard to code, yes. Useless, no, not unless you're on a fixed-size 
screen.
Steeve
24-Jun-2010
[1719]
Proportionnal resizing without font resizing has no use, IMO.
Ladislav
24-Jun-2010
[1720]
Well, Steeve, you do not have to use it, but it will be available 
in case it is needed
BrianH
24-Jun-2010
[1721]
Steeve, that would defeat the purpose of buying a large screen so 
you can see more stuff. Used a spreadsheet lately? Graham, that can 
change the whole layout. If it autoadjusts, cool, but you'd at least 
need different layouts for languages that go in different directions.
Steeve
24-Jun-2010
[1722x2]
I do no  say we don't need resizing
*not
Graham
24-Jun-2010
[1724x2]
well I think I'll restrict to languages that go from left to right
and are horizontal
Rebolek
24-Jun-2010
[1726]
It's not proportional resizing ONLY, if you want your elements to 
stay whey they were, you're free to do so.
Graham
24-Jun-2010
[1727x2]
Chinese used to be right to left and top to bottom... but I think 
they've changed
Is Arabic still right to left?
Steeve
24-Jun-2010
[1729]
But the old way (fixing the corners to the container) is goog enough.
Rebolek
24-Jun-2010
[1730]
Graham: yes, but AFAIK, they write their numbers mostly L->R. Strange.
Graham
24-Jun-2010
[1731]
Our numbering system is based on the arabic one ...
Ladislav
24-Jun-2010
[1732]
yes, but it seems, that the origins of the system go back to Babylon
BrianH
24-Jun-2010
[1733]
I also want a combination of proportional resizing for scale, and 
expanding sections for size. Fot instance, an iPhone 4 has a higher 
resolution screen than a Droid, but the Droid's screen may be larger. 
So I want to both scale to higher resolutions on platforms that support 
them, but make use of more physical space when available, as needed. 
I don't want my menu/ribbon to expand to fill more of the screen 
unless I am going to be further away from it.
Graham
24-Jun-2010
[1734]
Not to Babel ?
Rebolek
24-Jun-2010
[1735]
Yes, R->L. I'm tired today :)
BrianH
24-Jun-2010
[1736]
Wasn't the babylonian system base-60? Or was that someone else?
Ladislav
24-Jun-2010
[1737]
ah sorry, Babylon is a transcription used in Cz
Graham
24-Jun-2010
[1738]
Anway, I just want to know if faces resize to their text and we don't 
explicitly have to set them
Rebolek
24-Jun-2010
[1739]
I don't want resizing. It's mostly useless. You need to define UI 
for each device. Abstraction doesn't work. That's the sad truth.
Graham
24-Jun-2010
[1740]
Rebolek .. if it works in 90% of the cases ... for many people, that's 
good enough
BrianH
24-Jun-2010
[1741]
I want resizing for the desktop, and scaling for devices like Android-based 
phones where you can't necessarily know the resolution/size ahead 
of time.
Graham
24-Jun-2010
[1742x2]
People can code around the other cases hopefully
These phones are changing screen sizes every release
Ladislav
24-Jun-2010
[1744]
Babylonians had base-60 numbers, indeed, but the evidence exists, 
that they founded our positional system
Rebolek
24-Jun-2010
[1745x2]
Graham, it may work for the desktop, but it's not working for mobile 
devices.
Brain, exactly.
Ladislav
24-Jun-2010
[1747]
the invention of zero was a considerable breakthrough, taking into 
account, that even nowadays there are people hesitating to call zero 
"a number"
Steeve
24-Jun-2010
[1748]
it's a bit, actually :-)
BrianH
24-Jun-2010
[1749]
Just read a new Droid review - larger screen than a iPhone 4, less 
resolution. I'm starting to want a device-independent coordinate 
system :(
Rebolek
24-Jun-2010
[1750]
But iPhone is very consistent. It had the same resolution and now 
it doubled it. Android is almost unpredictable in that manner. Unfortuately.