World: r3wp

resizing: This is a quite complex topic and we need to make tests, 
try different approaches and fine tune tor the special cases we find. 
So, we don't do it completely up-front, but we adopt it on the way 
until it stabilizes.

In my GUI trial, the resizing of styles use a small amount of primitives.
When a resize event is triggered. I mix them in an intuitive way.

....
when [
	resize [resize xy]  ;full resizing both direction
	resize [resize x]   ; resize the height only (for menu bar)

 resize [move x resize y] ; move the x offset, resize the width (for 
 right scroll bar)

 resize [move y resize x] ; move the y offset, resize the height (for 
 bottom scroll bar)

 resize [resize xy do-childs [trigger resize]] ;full resize + pass 
 the resize event thru all child gobs (for container)
]

...must say that it's allowing fractionnal resizing.

resize [resize xy * 50%]

Easy, no ?

Why do you write 
	[resize x]  ; resize the height only
I was expecting 
	[resize y]  ; resize the height only

menu is vertical ??

I still don't understand it.

I think he means that the menu bar widens but does not deepen

Surely, then, the comment should be "resize the width only".

so the second to last example ...


move y ( move the bottom menu bar down ) resize x ( and widen but 
do not make it taller )

engish is his 3rd language

It seems unlikely to that Steeve has confused this:
<----- Width ----->
	^
	|
	|
      Height
	|
	\/

Maybe his monitor fell on its side?

or, he has a swivel monitor?

Or he's programming from the couch?

they're all the reverse way one would expect

maybe y = horizontal axis?

Ah.... silly me.
Nobody was supposed to read it

should not post it then! lol

A bit of status: Lots of work on resizing right now, specifically 
a bug that occurs on maximize.

And this bug is OS version specific... hard to hunt down.

I know old-size and old_offset are hidden properties of gobs.

I just think it would be convenient to be able to read them (during 
the resizing process).

Any R3VIDs available for playing with yet??

what do you think? :-)

The question was directed to Steeve, Ashley and anyone else writing 
GUIs for R3.

James Marsden was also writing a GUI for R3

I need a code/prototype reviewer for reviewing the validation prototype 
and the dialogs prototype.

I need a review of specific source code, the concepts and prototype 
documents. This is to ensure that the prototype doesn't lack important 
features that I didn't think about, before the prototypes are integrated 
into the R3 GUI.

still too high-level mumbo-jumbo (albeit needed later for app developers), 
instead of real styles work :-)

ok, Pekr, you're not the one to use as reviewer :-)

Im waiting for a more stable R3 before I continue GUI work.  Too 
busy at the moment to play with the host-kits.

R3 GUI now builds and runs with the new build system. Nice and clean. 
:-)

Does resizing work correctly with all existing styles already? :-)

nope

the built GUI is 193 kb and 53 kb shrinked.

Is there anything about this GUI that will make it standout from 
other languages's GUI's? or is this first version going to be standard 
stuff?

it'll just be very nice to use.

Henrik - it still has to be seen ... I require all keyboard navigation 
being OS compatible - can't wait to stress test tabbing, tree-view, 
etc. :-)

pekr, yes, that will be nice, but the code review is required for 
these functions to go in. I hope you see how important that mumbo-jumbo 
is.

what functions? form validation related you were talking about earlier? 
OK, do you have anything to test, including some basic instructions? 
If so - send it in ...

I'll pack it up within the next hour.

ok, I am leaving for a tomorrow's management meeting, so first day 
I will be able to play with it is Sunday, and maybe some of evenings 
next week, we will see ...

http://rebol.hmkdesign.dk/files/r3/gui/r3-gui.r3

I guess you need that one. :-)

Please download it to avoid stressing my poor little connection, 
btw.

argh... I don't like those compressed scripts, i don't run them if 
can't have a look before :o

one sec

inflated

uh ? are you sure ?

could be cached

try again