World: r3wp

At least in R2.

in know the trick with struct!, but my tests show that it's not faster 
than using [debase to-hex]

for info, to convert an integer to a binary with struct! , we do.
>>str: make struct! [int [integer!]] [0]
then
>>str/int: 150
>> third s 
== #{XXXXXXXX}
which is the integer in little endian format

i don't know why but  it seems that it's not faster than the [debase 
to-hex] method

Observe progress of internal releases here:

http://www.rebol.net/wiki/R3_Releases

... noses pressed against  window ...

noses pressed against gobs

gobs in the noses pressed against the glass in front of the gobs

Small status update:


- Mostly doing code cleanups and bug fixes now, so changes are not 
very visible.

- Carl has worked on window positioning and popup offsets, which 
were not working correctly. This should finally enable us to get 
popup styles done. Actually I've already done the first for date 
field. Popups are very simple to do, compared to VID. Just open a 
modal window without a border.
- Icarii has begun working on R3 styles too now. Thanks!

- Still baffled at the concept of MAX-SIZE. There are some places 
where it just doesn't work (see my later screenshots with a funny 
curled-up scroll-bar).

- I'm very pleased with my container style. It has proven to be very 
useful and we will build many more styles with it.

- Autogenerated style list and style tree (will publicize this soon 
here. R3-alpha users can see them in Users/Henrik/style-tree.rmd 
and style-list.rmd)
- Over 80 styles now. I suspect there will be 10-20 more.

- Color policies are being settled, so you can abstract colors away 
from a style into a theme.

- Each style will eventually get a tag block. This makes it possible 
to tag a style as 'internal or 'advanced, depending on where it's 
intended to be used and what it can do. This is very useful in documentation, 
and for some styles that need to work together in specific ways. 
It also makes it possible to hide advanced styles from end-users, 
who won't need to use them directly.


For those who have missed it, screenshots and videos are here: http://rebol.hmkdesign.dk/files/r3/gui/index.rsp

Is orientation of group vs panel fixed already? Btw - that you very 
much for update!

Henrik - the problem with the list is its complexity. I am not sure, 
I would like to see hidden advanced styles, but various variants, 
and styles as 'clicker, which has no benefit for an end user, unless 
he/she is ready to produce his own ones, based upon 'clicker.

Simply put - when you look into RebGUI widget directory, you can 
see all widgets, which imediatelly make sense for user - when you 
compare it with the list provided, the difference is very obvious 
- every one single self-descriptory, usable, vs. chaos ...

The distinction boundary and suggestion of how to think about tagging, 
is imo - VID level user, making GUI, not wanting to create style, 
vs style tweakers, vs style authors ... - but that is only suggestion.

As for MAX-SIZE - what does Carl thinks conceptually about your concerns?

Carl has not responded much to MAX-SIZE, so I am only thinking that 
he will at some point solve the issue when he gets annoyed with it 
enough himself. :-)

The style list is only there to describe the styles as they exist 
and are defined in the system: As a single flat list. The 'parent 
value is the only thing to make it into a tree. A tag block would 
help us group it however we want. I don't think there will be problems 
describing the styles in the documentation in a clear fashion.

How it looks with unicode in VID texts?

not yet

Henrik - what is in system metrics? Is there resolution only? Or 
also other aspects? In the past, I tried to wrap rebol to win32 funcs, 
to detect properly multiple monitors and their orientation, but was 
not successfull at the task. It would be nice, if we would have such 
funcitonality ...

pixels are used here

I will try today one test with r3-alpha - connecting my notebook 
to LCD TV. IIRC, REBOL then reports screen size of monitor1-X + monitor2-X/max 
(monitor1-Y, monitor2-Y), or something like that ...

Henrik, I went through all of your videos and it looks awesome. Had 
there been any discussion on an HTML viewer widget?

Not at this time, no. I think that will be left up to a 3rd party 
to do such a thing.

I'm wondering now if it's going to be possible to write an R2 client 
for RebTalk. I've not asked Carl about this yet.

Why not ? It's just using LNS isn't it?

Is the source available?

to Rebtalk?

Is rebtalk downloadable yet?

only for the chosen ones ...

ie. the famous five

I wish the teasing would stop or at least be backed by a well thought 
out and valid date.

I think actually it's just using HTTP.

Graham, it's currently useless due to HTTP bugs. So it was a pretty 
good thing to work on.

Oh ...?  I looked at the data format and it looked similar to LNS 
format

Oh yeah ... I used a web client!  :)

Rebtalk is very small, smaller than the entire of LNS.

So plain ordinary http

looks like it.

http bugs??  Oh oh ... Gabriele has some work to do then :(

Carl and Maarten are working on it now.

Henrik, you're sleep talking!

well, I did express my opinion that we needed a BBS ...

CharlesW: for html viewer, it would be best to wrap webkit :-)

Henrik - nice - http://rebol.hmkdesign.dk/files/r3/gui/166.png

Just two questions - 1) what it the space at the bottom grid? A layout 
bug? Or just wrongly set container size? 2) Will there be anything 
done to font rendering? Some letters look rather blurry. Is it a 
bug, or just we are not still using more advanced font rendering 
techniques? I thought that moving to AGG will solve it for us ...

1. Some kind of error, possibly due to the wonders of MAX-SIZE.
2. Cyphre will need to handle that.

I wonder what Carl thinks about MAX-SIZE concept. In fact, when thinking 
about scallable apps, I am not sure you can make it work in required 
way.

What is the style the picture shows? List-view? Or some grid prototype?

I will explain the construction in a minute. Need to run an errand...

Ok, I'm building it of several parts. (This may change if I find 
some more clever way of doing it.) First there is a DATA-GRID, which 
is a TIGHT style that contains actors to generate a grid view and 
links to a block of data. DATA-GRID is a slave style in that you 
link it to a data block and then it will display what it can display 
of that block from a start index set in the style, so it works like 
a data window. TEXT-GRID is currently just a variant of DATA-GRID 
with different spacing between cells.


Next, we can move that start index around by attaching a scroller 
to the DATA-GRID, and set the DATA-GRID's ON-SCROLL actor to set 
a new index, based on the input from the scroller. The scroller will 
be set based on the size of the data block versus the size of the 
data grid. Presto, a functioning list view.

I will explain sorting, filtering and all that later.