World: r3wp

(Ooops, I shouldn't have said that...)

Today, I made some tests (again) with vectorial fonts using draw.

And... It's not that bad when the gamma correction is... corrected.

My test:

font: ["verdana" size: 15]
gamma 2.0
pen none 

http://sites.google.com/site/rebolish/test-1/not_bad.png
(look at the white text)

Can anyone say what the criteria was for how functions were split 
under draw and shape? Seems that the shape ones could just as well 
be under draw.

steeve is doing an irc mini client like ... the font is well designed 
but a gamma correction 2.0 isn't it a bit too clear ? why 2.0 and 
not 20.0 ? seems something completly arbitrary again a speudo hack 
to solve a lack of real work ...

so in conclusion another week without any real progress ...

CAn we have a better calling for R3 hostkit package ... since it's 
supposed to haven't change on API level can't we distinguish the 
number for the hostkit api version and a number for the GUI related 
engine ? something like r3-hostkit-102-GUI-still-the-same.zip ?

BTW, the gvoice2 script http://rebol.wik.is/GoogleVoicecould just 
as easily be written in R3GUI ... if it were available

ahh.. retract that .. no table style I guess

correct

IIRC there was a screenshot showing grid is available for new gui? 
Done by Cyphre?

not used yet as it has not been adapted for the new resizing

where's the link Pekr?

http://rebol.hmkdesign.dk/files/r3/gui/208.png

I just wonder if it is so difficult to adapt styles to the new resizing 
model, as we can hear about the adaptation process for several weeks 
already? I expect that the work is being done on some other things 
right now?

Cyphre has been out of town for the past week and has not yet reported 
back on his progress, and he's also focusing on many host kit issues 
that need to be solved.

Bolek has spent some time at the hospital.

Carl is asking for suggestions for A105

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