World: r3wp

It's not proportional resizing ONLY, if you want your elements to 
stay whey they were, you're free to do so.

Chinese used to be right to left and top to bottom... but I think 
they've changed

Is Arabic still right to left?

But the old way (fixing the corners to the container) is goog enough.

Graham: yes, but AFAIK, they write their numbers mostly L->R. Strange.

Our numbering system is based on the arabic one ...

yes, but it seems, that the origins of the system go back to Babylon

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.

Not to Babel ?

Yes, R->L. I'm tired today :)

Wasn't the babylonian system base-60? Or was that someone else?

ah sorry, Babylon is a transcription used in Cz

Anway, I just want to know if faces resize to their text and we don't 
explicitly have to set them

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.

Rebolek .. if it works in 90% of the cases ... for many people, that's 
good enough

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.

People can code around the other cases hopefully

These phones are changing screen sizes every release

Babylonians had base-60 numbers, indeed, but the evidence exists, 
that they founded our positional system

Graham, it may work for the desktop, but it's not working for mobile 
devices.

Brain, exactly.

the invention of zero was a considerable breakthrough, taking into 
account, that even nowadays there are people hesitating to call zero 
"a number"

it's a bit, actually :-)

Just read a new Droid review - larger screen than a iPhone 4, less 
resolution. I'm starting to want a device-independent coordinate 
system :(

But iPhone is very consistent. It had the same resolution and now 
it doubled it. Android is almost unpredictable in that manner. Unfortuately.

well, there is the iPad too. I imagine there will be more different 
screensizes in the future.

also now that Microsoft seem to be releasing a new mobile OS per 
week...

Nope, just new form factors. They still only have the 2 mobile OSes.

Plus legacy versions of those two of course.

so do faces adjust for text size automatically??  anyone know?

Graham, they do not. Right now.

UI still needs lot of work.

oh ...

Just keep it in mind please guys!

Actually, it's one of my favourite features :)

Motorola Droid X

Anyone know if one can update the GUI from a network event?

I'd like to know, inter alia, if one can build a progress meter for 
downloads

As for resizing - how much I can influence the scaling aspects? I 
mean - e.g. I have simple reblet, a calculator. Now while it resizes 
buttons etc., what if I want it also to properly scale on large display? 
I mean - making the UI element just bigger, including borders, font 
metrics, etc.?

Does R3Gui have scaleable fonts?

Graham, all your questions: yes.

Henrik - so what happens next? Resizing model is incorporated into 
GUI, and then we can see some beta? Or is it still too early?

Too early I think. I haven't seen the dialect yet.

Henrik, how?

Graham, don't know, but if it wasn't possible, I wouldn't use R3 
at all.

since it's a very basic function

Does anyone know ?

Ladislav - I do understand the need for having vertical vs horizontal 
arrangement (panel vs group). But it is hardly "acceptable", if those 
two differe visually, because then we can't say, that one is the 
opposite of the other :-)

Hello guys, just few notes from my side regarding the layout sematics 
and min/max-size etc:
-the layout will be still as simple as in the current R3GUI

-most of the time only 'style maker' will need to handle min/max/init 
size of the specific style

-by default layout elements have to be organized either in PANEL 
or GROUP structures (though it is possible create your super special 
style for circular layouts or whatever ;))

-at the PANEL/GROUP layout level there will be only three kinds of 
elements:
1) style with absolute size (in any axis)
2) style with elastic size (in any axis)

3) optional RETURN keyword used for line breaking to create variable 
number of rows/cols(default ehaviour is to set fixed number of cols/rows 
for GROUP/PANEL)

-to achieve more complex layout user can redefine min/max sizes according 
his needs

Pekr: the new resizing model is not yet integrated to R3 GUI. We 
are finalizing the prototype so it is fine-tuned.  The integration 
to R3GUI part will start from the next week.