World: r3wp

So, no 'select, 'insert, 'change or 'delete then...

Sorry, 'remove, not 'delete...

What is the suggested replacement where a port is used as a data 
interface?

Though I'd still advocate a separate type for this -- adapter! if 
you will...

Chris, actually ports in R3 support a lot of different actors, though 
it is not clear yet if it should or not.

ok, the prob with the new file port is that we can not have a direct 
access using an index.

Instead we have to maintain a relative offset because we only can 
use read/seek wich use negative and positive offset. I think READ 
should allow to use an absolute index  too. (like with a refinement 
 /at )

I think read/seek uses absolute offsets. What is your question?

If you want it to work properly you should also use the /seek option 
when you open the file port.

it's not a question Brian, when the port is opened, you must use 
relative offset to advance or go back in the file.

Sorry, I said offsets when I meant indexes. And read/seek doesn't 
allow negative indexes - the index parameter is always a non-negative 
offset from the beginning, 0-based.

have u tested that ?, negative offsets work properly whit read/seek 
on an opened port.

Are you opening the file port with open/seek? I haven't tried seeking 
without opening in seek mode.

yes i done that

read/seek wotk on opened file (port) and u can use negative offset, 
to read back

*work

I'm testing it now. All read/seek calls go to a 0-based index from 
the beginning of the file. Negative offsets cause an error. What 
version of REBOL are you using?

hum, i can't say it know, i have to go back to my job to check  it 
;-)

When you do, please tell us. I am testing with 2.100.13.3.1, and 
can also test 2.99.4.3.1 if you like.

i think it was the first alpha released

is there a link to dowload the last alpha release ?

I can't find the /seek refinement on the READ function in the last 
public release. The OPEN, READ and WRITE functions changed quite 
a bit with the Unicode changes. All of the docs and my comments relate 
to the versions since the Unicode changes.

ok

There is not a public link to the internal releases for the development 
group of REBOL 3, and that includes the Unicode releases. There isn't 
much point in posting one either, since Carl's GUI changes are just 
as extensive as the Unicode changes, and we haven't seen them yet.

I'll be posting more information as I get it, but things are promising 
so far :)

Fun fact: Compressed size of the new R3 GUI is 13.8 kB.

Gabriele's VID?

No, Carls new VID

Uh, sounds oversimplified. Can it draw at least simple button? :-)

I don't think styles are counted in yet, but there are a few styles 
in the design.. Carl sounds very pleased with the design. He's working 
out a few bugs, before I can get my hands on it.

So how do you know its size? I thought you might have it already 
...

He told me. :-)

ah :-)

Brian, i'm sorry i made a mistake, it was not the /seek refinement 
i used (which don't exist) with the 'read function but the /skip 
refinement.

Anyway, it seems that we can do a seek position with an obsolute 
index only when opening the file. After that, we can only skip the 
port. with relative offset. I think a /seek  refinement is missing 
in 'read function

(to seek in an opened file like with can do with R2)

*like we can do

Henrik, Pekr, the VID3 of Gabriele was really hudge (IIRC only the 
style sheet was 100Kb). 

It should not be too hard to do better even if the Gabriele' contribution 
was great.

i'm especialy curious how Carl managed the dynamic inheritance of 
styles (if i hunderstood correctly its ads)

Well, if I compress ALL of my VID, I get 37k. So, I'm not really 
sure it is that much bigger...

... and ... your VID was almost complete, whereas noone really knows, 
what Carl's version can('t) do ....

Steeve, the public build doesn't reflect what you will be able to 
do with REBOL 3. The docs refer to later builds.

Petr, anyone who reads the docs, has perhaps talked to Carl, and 
has done some deduction can tell quite a lot about what Carl's new 
VID will do. We aren't totally in the dark.

For instance, Steeve's question about the dynamic inheritance of 
styles can be answered by looking at the docs and the blogs Carl 
wrote about the extensions to BIND and IN. IN could handle dynamic 
inheritance, BIND handles static inheritance.

BrianH: I know. But we were talking size here. And the engine itself 
might be rather small, but once you add new styles, it grows. And 
also - to save some space, Gabriele e.g. introduced another abstraction 
- make-gobs dialect. Carl has another preference here - not abstracting 
this one, so it might make source code even larger. My point was, 
that current measure Henrik posted compared to Gabriele's almost 
complete VID3 is no measure at all, unless we know, what is inside 
in Carl's version ....

He posted this Monday, and am not sure it would hurt to publish it:

Delay in upload caused by:


1. Resize needed some more work.  That has been done, and it is much 
better.  We will probably see a few more bugs, and may still want 
to make some general adjustments.  The main idea of resize has changed 
from earlier VID releases. I will write a DocBase page on it to explain 
how it works and why I changed it. 


2. A few styles broke in recent changes. These need to be fixed. 
Should only take a few hours.


3. A few weeks ago, when making larger changes, I removed some of 
the compound styles. I want to add back at least one or two, probably 
LIST for text lists at minimum.

nice, thanks ... wondering why resize model needed to change - it 
looked good ...

Gabriele's resize model was a bit slow and difficult to understand 
- no offence to Gabriele, he just adapted the TeX sizing model. The 
problem is that the TeX sizing model was designed for desktop publishing 
and that doesn't require fast resizing, just complex layouts. It 
was overkill for UI layout.

The main reason that Carl's UI is so small is that he simplified 
the implementation to the point where something like make-gobs wasn't 
required to make the UI fast. The resize model is so easy to use 
that most of the time you don't need to specify sizes at all.

I wonder if there are specific needs for resizing document layouts?

BrianH: user-wise,  TeX model was rather easy to understand. It is 
a proven model. I hope Carl's model works .... when I can hear overkill 
for something which works, I fear underfeatured in Carl's terms ... 
I don't want VID3 to be built on compromises.

IIRC make-bogs was not here to make UI fast ...