AltME groups: search

Anyway, setting header/to: none works but it puts the entire list 
there as you mentioned. Hmmm, maybe I have to do it individually.

Just wondering how one matches a GUI like VID to an asynchronous 
data source. I am thinking of building a mulit tab panel application 
with an asynchronous backend.  If the user requests some data on 
one screen, and then changes their mind by switching to another screen, 
what does one do with the data when it arrives?  Does one refresh 
the original screen request and move focus from where the user switched 
to ?

view center-face layout compose [
   across origin 0x0 space 0x0 backdrop black
   style btn btn gray black
   btn {Close} [quit]
   btn {Send} []

   btn {Add Attachment} [append Attachments/text join mold request-file 
   newline show Attachments]
   return

   Attachments: area 300x100 do [Attachments/feel: make Attachments/feel 
   [engage: none]]
   return
   txt 100 {To:}
   To: field 200 {[Izkata-:-GMail-:-com]}
]

Ouch to me... Oh well.  I guess I'll have to make a "Do not repeat" 
file from now on. Now I remember, I did the exact same thing with 
the exact same word some time ago...

as for Windows console being slow - it has nothing to do with your 
gfx card imo :-) Windows console is known having rather slow performance 
:-) IIRC Rebol alpha used windows(dos) console, but we know that 
Windows console really sucks, so RT implemented native one. With 
Linux imo REBOL is usig Linux console, not its own one ...

What do you need the focus for? To enter text or to catch something 
else?

I ask, because if you wanna enter text, the question is, how to get 
rid or the cursor in general. If you wanna catch other events, you 
do it with the FEEL functions.

but I needed to set the focus from within the code and before volkers 
solution I couldn't do that with turning on the cursor

:-) Why do you need to set focus on box in code? It'll get the events, 
when the user press the box.

A couple of questions: Is there a switch to start view in the console 
mode (CLI)? I know I can do something in the user.r but I'd like 
to do it from a prompt on demand. And also, anyone have any idea 
why my emails sent via a rebol program take so long to arrive. Any 
special settings in the header or hints. I 've created a program 
that sends emails to a list but I notice that it takes a long time 
(30 minutes or more) to receive the email. I checked by sending from 
Outlook and through the command line in rebol and it  was instantaneous. 
There's something happening and I wonder if any on you  have seen 
this.

Thanks Mike. Can this be done programatically? I mean when I start 
rebol, I use I call it from the command line. What I'd like is to 
be able do something like "view.exe -console" for example.

OK, then my english is twisted or I do post too many thoughts in 
parallel .... if there would be some ability to attach particular 
message as an reaction to another one, it would be clearer, but I 
am not sure there is any kind of "thread based" IM client around 
:-)

... and I don't expect Carl (RT) to check every bit of changes, as 
he imo expects us to do testing and post reports :-) Anyway - bug 
is submitted, let's hope it will get corrected ...

To change data, you could do:
clear next find face/effect/draw 'line
append face/effect/draw data-block

do points have to be done with circles ?

So - to be constructive - I reported error into RAMBO and it was 
market as critical, although I am not sure if it will be fixed, mostly 
ppl will not try to run rebol app directly, or they will simply install 
it, but currently View 1.3 is UNUSABLE in environment, where you 
want to use it over network, starting in login script, and do some 
maintanance to your machines - because desktop will pop-up. I also 
reported how Rebol should check for proxy settings, where those are 
placed in Registry, as it seems to me current method is weak ...

is it possible to affect the key repeat rate? I'm trying to read 
a magnetic card through a reader which delivers one char at a time. 
I'm reading it into a face which has a feel that reads each key event. 
But the keys are read very slowly, about at the maximum key repeat 
rate set by the OS, so it takes 5-10 seconds to read a card with 
only 116 chars. Is there a different way to do this or can I manipulate 
the key repeat rate for that face?

have you set it prior to do gui, or later? when face/rate is updated, 
iirc 'show is needed, dunno ...

can I have always-on-top window somehow easily with View? And also 
- how difficult is it to get Rebol working in system tray? Do I need 
SDK for that? (I do own one, not just 1.3 yet)

again :-) two questions:

1. if I use word-browser and evaluate an example, a rebol command 
promt will open (usually) and show the example .... shouldn't it 
be possible to close this example prompt window without closing the 
word-browser as well .... maybe this is just a problem on my system 
- I don't know

2. certain programs on viewtop close immediately after starting them 
or some part - eg. Canvas.r or also under viewtop in the Rebol Tools 
folder Rebol Logo, DL or Icon Maker .... on the command prompt with 
canvas.r one can see that the programs return immediately instead 
of staying in the event-loop and when typing again 'do-events it 
returns immediately as well


I tried now the current view 1.3.1d and there happens the same in 
my system. Has anybody an idea ?

I see the note what I can do with the logo maker and then should 
appear the logomaker window. I used to see this (maybe in an older 
version, don't know any more).

Volker: what I think it should be like is, that you have during coding 
always the word-browser open and if we have the option to evaluate 
the examples by mouse-click we do so .... but do this a couple of 
times and you have a window mess, so closing them seams natural, 
doesn't it ? :-)

well, I still don't like it as somehow this is a kind of hidden connection 
which one doesn't expect - kind of "if something is on the screen 
it should be obvious what's going to happen if I do this or that" 
:-)

Yes, that might work Volker. The first thing to do is make all the 
code examples consistent and define the standard for how to write 
them, so we know which "output channels" we need to handle. e.g. 
Carl put in a proxy for the VIEW function, so examples that use it 
would do a VIEW/NEW automatically.

If anyone wants to know how DO EVENT works in WAKE-EVENT, then they 
might find this script interesting:
http://www.lexicon.net/antonr/rebol/gui/mimic-do-event.r

Purpose: {Mimic DO EVENT (which is called in wake-event) with a mezzanine 
function of our own.
	The mimicry is good for two things:
	1) as a document of how DO EVENT works inside

 2) as a way of achieving crazy magical tricks not otherwise possible, 
 like 
	   - faces transparent to events

    - restoring and saving facets of iterated faces before and after 
    events are sent to them 
	     (see shell-list.r)
}

Currently shell-list, with the help of mimic-do-event, is iterating 
buttons and toggles, and they operate just like standalone buttons 
and toggles. If you've tried putting buttons and toggles in a list 
you know it is not easy to achieve.

I've just submitted a patch to RAMBO which should allow progress, 
slider and scroller to also be iterated without problems.

Brock, just try iterating scrollers (changing face/data on each iteration) 
and you see that it is much better this way. :)

This patch doesn't try to do everything, but makes a small step to 
ease iteration.

Having said that, I discovered that my patches show visual artefacts 
when resizing under other scrollers etc.. Agh! !
But I will try to isolate the cause of that, too...

When I test locally, I do not want to download files I already have 
each time, do I ?

I could do stuff like that, but I am a perfectionist, reluctant to 
admit there might be a simple way that's good enough for now. But 
I'm coming round... :)

My original thought process was that I don't want to automate the 
deleting of files in the cache, on my computer or someone else's. 
I think if the user wants to delete their files, they should do it 
themselves. I don't want to get involved in any data loss.

So I thought it preferable to do an intelligent update. But for that 
I need an intelligent interface... -> shell-list.

except for large files, i have to do some "dont-delete" for them.

More, what do we do with it now? About using it, building demos, 
maybe 10000 buttons in a row or such things. Where doyou want to 
go with us?

Good question. The idea of shell-list is to make things simpler. 
It should be *easy* to make lists of things.
Why do I publish it now, when it's still in such an early stage ?

I can't seem to figure out the solution to do this elegantly: If 
I have a pane with 4 faces [a b c d] and I want 'b to move to position 
'd: [a c d b], is there no easier way than to copy, remove and append 
'b?

So do I, which is why I think it would be nice to get bugs fixed 
and some simple features added like a search/replace and maybe a 
simple undo. I use it alot.

Also a realtime search bar could be nice. I don't think it would 
be hard to do.

Is upload complex, or do you need to search script?

A good programming approach helps more than a lot of tools. But good 
tools help when you stop on "strange" problems or just need to maintain 
an "old" piece of code or code wrote by others. Do you agree?

Gabriel wrote this:
Add a face/refocus function.

   face/refocus: func [shift] [
      ; shift is true if this is shift-tab
      ; do your own refocus handling here
   ]


This  should  be  enough to solve most of your issues. In the past

(View  1.2.8)  there  were  even  more problems, so that I wrote 
a

number  of  patches  and  a Field style that *never* handles focus
automatically. So I could validate and handle focus myself.

http://www.mail-archive.com/[rebolist-:-rebol-:-net]/msg02722.html

AH. Do not know how to do that.

I understand. but i do not now how to trap that question.

I would do it this way:

1) Attempt to read the URL, with a TRY

2) if there's an error, check if it is an authorization required 
error
3) if so, ask the user for credentials
4) go back to 1

IMHO passwords belong into the protocol. 

- If possible they should never be exposed to the application. More 
like browsers do, with a password-manager. Unfortunally that is not 
really possible with rebol.

- urls go thru multiple layers. after read-thru you dont have any 
error-information.

Been trying for an hour or so to do that with no success. With a 
text field I can do it, but I haven't been able to get it to work 
for a money field. A simle example is what I need, I think.

DideC, thanks. I'll do some studying and see if I can figure out 
what you mean. Problem is that I haven't been getting to do much 
programming during this past year, and I have forgotten much of what 
litte I knew.  :>(

I wonder if there's a more efficient way to do this than combining 
lots of line draws together?

hmm... how do I set the default entry in a CHOICE at layout time? 
I wanted to do something like this:

view layout [choice "1" "2" "3" with [data: next face/data]]

view/new layout [
    the-field: field feel [
        engage: func [face action event] [
        	if action = 'key [
			if all [ greater? (to-integer event/key) 47
				 lesser? (to-integer event/key) 58 ] [
				 append face/text event/key 
				 show face 
			]
		]    
        ]
    ]
    new-field: field
]
focus the-field
do-events

first question, is how can i get the first text field to accept mouse 
click events?  how then do i get it to recognize the tab key to switch 
focus to the next field?

Henrik, your choice problem. I think, you have to redefine choice. 
The problem is in the multi/text function. You can do it at layout 
time this way:

view layout/size [choice "1" "2" "3" with [multi/text: func [face 
blk] [if pick blk 1 [face/texts: copy blk]] text: "2"]] 400x400

why do you want to do that, compressed in a field?

Henrik, your second example actually does "damage" to the system.

You are modifying the default FEEL object that is MAKEd from every 
time FIELD styles are created by LAYOUT.
It's basically like the following example. Here we set the ENGAGE
function to NONE to disable user interaction to the field:

	view layout [
		field with [feel/engage: none] 
		field
	]


But the second field also does not respond to user activity, nor 
do fields created in new windows:

	view layout [field] ; <- this field also does not respond

It can be confusing.

You have to remember that the FEEL objects are shared by default, 
to save memory.
These two examples may look the same but they are not:


 layout [field feel [engage: none]] ; this one clones and modifies 
 the FEEL


 layout [field with [feel/engage: none]] ; this one modifies the original 
 FEEL


The LAYOUT dialect has a FEEL keyword, and that causes a MAKE of 
the feel (ie. it is cloned
before being modified by your spec block).

The LAYOUT dialect WITH keyword, however, gets you out of the LAYOUT 
dialect and back into "normal" rebol code, but also binding you inside 
the new face object (the field) that is being created by LAYOUT.

So the "feel" inside the LAYOUT spec block and the "feel" inside 
the WITH block are not the same.

view/new layout [
	the-field: field feel [

		;;;; 
		engage: func [face act event][
			switch act [
				down [

     either equal? face focal-face [unlight-text] [focus/no-show face]
					caret: offset-to-caret face event/offset
					show face
				]
				over [
					if not-equal? caret offset-to-caret face event/offset [
						if not highlight-start [highlight-start: caret]
						highlight-end: caret: offset-to-caret face event/offset
						show face
					]
				]
				key [
					edit-text face event get in face 'action
				]
			]
		]
		;;;;

	]
	new-field: field
]
focus the-field
do-events

Oh no! We get an error message! "edit-text has no value".
Where is EDIT-TEXT ? It is not defined in the global context.
If you go looking in the system you will eventually find it here:

	CTX-EDIT/EDIT-TEXT


What happened ? The original EDIT-TEXT word, as found in the FIELD/FEEL, 
is bound to CTX-EDIT 

(it's not found in the global context, open a new console and try 
it), but we only bound our new EDIT-TEXT 
word to a new function context (ie. our ENGAGE).


So how do we keep the original bindings of a function, when making 
a copy of it ?
SECOND gives you the body of a function.

	second get in svv/vid-styles/field/feel 'engage


We should COPY that, which keeps the bindings, then modify that copy. 
*Then* we can create the function:

	; copy the engage function body
	body: copy/deep second get in svv/vid-styles/field/feel 'engage

	; <-- modify the body here

	; make the new function
	engage: func [face act event] body

Let's test that to see which keys we want:

view/new layout [
	the-field: field feel [

		use [body at-key-block key-block][

			; copy the engage function body

   body: copy/deep second get in svv/vid-styles/field/feel 'engage


   ; modify the copy to move the block with the EDIT-TEXT word in it
			; to a new IF then-block
			at-key-block: next find select body [switch act] [key]
			key-block: at-key-block/1

   change/only at-key-block compose/only [probe event/key if true (key-block)]

			; make the new function
			engage: func [face act event] body

		]

	]
]
focus the-field
do-events

view/new layout [
	the-field: field feel [

		use [body at-key-block key-block][

			; copy the engage function body

   body: copy/deep second get in svv/vid-styles/field/feel 'engage


   ; modify the copy to move the block with the EDIT-TEXT word in it
			; to a new IF then-block
			at-key-block: next find select body [switch act] [key]
			key-block: at-key-block/1
			change/only at-key-block compose/only [
				if find "-0123456789.^H^-" event/key (key-block)
			]

			; make the new function
			engage: func [face act event] body

		]

	]
	new-field: field
]
focus the-field
do-events

view/new layout [
	the-field: field feel [
		engage: func [face act event] bind bind [
			switch act [
				down [

     either equal? face focal-face [unlight-text] [focus/no-show face]
					caret: offset-to-caret face event/offset
					show face
				]
				over [
					if not-equal? caret offset-to-caret face event/offset [
						if not highlight-start [highlight-start: caret]
						highlight-end: caret: offset-to-caret face event/offset
						show face
					]
				]
				key [
					edit-text face event get in face 'action
				]
			]
		] in ctx-text 'self in system/view 'self 
	]
	new-field: field
]
focus the-field
do-events

is there a good way to do font substitution? I can see that under 
Windows, when I attempt to use the Tahoma font, OSX uses Lucida Grande 
and Linux turns to Courier for some reason. Is there a way to control 
that+

AFAIK os takes that long to report an error. and with sync, rebol 
can do nothing before an os-reply.

View already tells you, that you should do system settings, but then 
it tries to connect, which is imo incorrect aproach ...

Why a browser? getting rich-text is not everything you know :-) Who 
would write parsers for all that web "standards" out there, plus 
support for various browser quirk modes? And what would you do about 
java-script? Are we going to reimplement javascript in rebol too? 
:-)

I thought of this little idea regarding the editor: Currently, it's 
depending on running a script from file, if you want to test something. 
But I was wondering if it were possible to edit data directly with 
it and just store it in memory?


Sometimes I like to debug a function without having to save it to 
a file and then run a program stored in a different file to run the 
test, e.g. Ctrl-E is useless.


It would be nice to directly in the editor, create a big function, 
say from a paste and do a few edits, press Ctrl-<something> and have 
that evaluated directly. Then you could quit the editor and use the 
function directly in the console without having to save any files.


Also if you want to re-edit the function, type in something similar 
to:


editor 'my-big-function and the editor would pop up with the function 
source and the word its bound to.

scratch: func['value][
 save/header %console-scratch.r either word? :value[
  reduce[to-set-word :value get value]
 ][
  :value
 ][Title: "Console-scratch"]
 launch: func[file /secure-cmd][do file]
 editor %console-scratch.r    
]
halt

;since nobody is perfect:
scratch: func['value][
 save/header %console-scratch.r either word? :value[
  reduce[to-set-word :value get value]
 ][
  :value
 ][Title: "Console-scratch"]
 launch: func[file /secure-cmd /local err][
  if error? set/any 'err try[do file][unview/all err]
 ]
 editor %console-scratch.r    
]
scratchme: func[][]
scratch scratchme

This is pretty cool! I added do-events at the end of the scratch 
script.


Now I'm running a GUI program, and I can exit to the console though 
a "halt" button in the GUI. I 'SCRATCH the function I need and CTRL-E 
the changes and I can continue working with the GUI program with 
the new changes without quitting the editor. :-)

If you wanna export some face attributes outside, you could do that 
with the action attribute (the action block following many styles 
in VID for example) or in the feel functions.
a: false
view layout [toggle [a: face/data]]

This will change a according to the state of the toggle.

it _would_ have been nice to be able to do the other thing, but the 
code is almost as streamlined as I wanted it to be now. I guess I 
need to study more on datatypes...

Why do you think so?   My natural reaction is to expect something 
blank, or at least not have to close a file that I don't want open. 
  While you don't "close" a document in editor, I have to sit and 
think, "is this something that I want to be open right now or not?" 
   I find it disruptive from a UI standpoint

The caching stuff you mentioned is something I partially did for 
my old listview. Correctly the listview was very fast, but also very 
memory hungry, took a long time to initialize and the code was 5 
times bigger and a lot harder to maintain.


This one simply doesn't paint anything other than what is seen, so 
if you have a million rows, only 15 will be painted, if you have 
15 visible rows on screen. The backside to the LIST which this one 
is based on is that it uses iterated faces. This means that if I 
only do a small change to one face, it has to repaint the entire 
list view with all rows. That's why mouse over became too slow to 
be practically useful. I'm not sure yet how to fix this problem.

Henrik, I advise building this style from FACE (ie. not an existing 
style, like LIST). Makes it less dependant on other code, more portable 
(ie. to RebGUI), and you will be forced to write your own pane function, 
which you will need to do anyway . :)

I based a lot of styles on existing styles, and this is a great way 
to learn, but I found as existing styles were changed (bugs fixed 
or ottherwise), my styles would break. Then it's a run-around to 
do a version-dependant fix for the problems.

anton, I'll see what I can do about it (would also learn a bit about 
iterated faces), but I'm focusing on getting things to work for now 
:-)

If I were to create it purely derived from FACE, how do I add it 
as a style under VID?

Mmm. FIELD access functions do not take into account whether the 
face has the focus or not. I think they should check that and set 
the caret to the field's new text facet (if it is new).

Henrik - as for the focus - do you try to focus/hilite particular 
cell, or just a row?

Robert: I will look at right click unsorting.


Realtime filtering is really up to the field that provides the string 
and updates the list, not the list itself (more flexible that way). 
I've done it before, where realtime performance could be achieved 
with more than 30000 entries in the list, so it's not a problem to 
do.

I don't know yet, but I plan to just let it draw empty cells. It 
should do the same if you filter for something not in the list

I could make a block of widths, but somehow it'll get less than managable 
when OUT-COLS will start to get dynamic. I'm not sure yet how to 
do it easily, so all columns simply have a standard width of 100 
pixels.

are the row heights adjustable ... or do I have to hard code them 
?

The list doesn't work in the browser as the list needs AGG.  It works 
in View, but doesn't do anything at present except display online 
status.  It scales for me fine up to 1024x768.

the AGG part... right. the sort button uses AGG to display the sorting 
arrow. I could make that into an image and do some tests on an older 
View and see if it can run there...

Graham - please slow down with new features, unless basic ones do 
work :-) I would like to ask you, if you or your users do really 
heavy drag and drop and what is more, even in between several grids?

but I can tell you what our 300 users are used to, working with 3 
grids we introduced within last 10 years, what they valued most - 


- column resizing was not an issue at all - proper grid can calculate 
size to set it automatically - we had two modes, auto column-width 
adjust, or static, set in config

- drag and drop was rarely used for columns. You can do it othe way 
around - let users to choose which columns they want to see, in what 
order. Let them save the config!!! Without it, forget about your 
grid being powerfull - what ppl are looking for is comfortable view 
of their data. Each person is used to slightly different view

- horizontal scrolling is a must. How cbut I can tell you what our 
300 users are used to, working with 3 grids we introduced within 
last 10 years, what they valued most - 


- column resizing was not an issue at all - proper grid can calculate 
size to set it automatically - we had two modes, auto column-width 
adjust, or static, set in config

- drag and drop was rarely used for columns. You can do it othe way 
around - let users to choose which columns they want to see, in what 
order. Let them save the config!!! Without it, forget about your 
grid being powerfull - what ppl are looking for is comfortable view 
of their data. Each person is used to slightly different view

- horizontal scrolling is a must. How cbut I can tell you what our 
300 users are used to, working with 3 grids we introduced within 
last 10 years, what they valued most - 


- column resizing was not an issue at all - proper grid can calculate 
size to set it automatically - we had two modes, auto column-width 
adjust, or static, set in config

- drag and drop was rarely used for columns. You can do it othe way 
around - let users to choose which columns they want to see, in what 
order. Let them save the config!!! Without it, forget about your 
grid being powerfull - what ppl are looking for is comfortable view 
of their data. Each person is used to slightly different view

- horizontal scrolling is a must. How cbut I can tell you what our 
300 users are used to, working with 3 grids we introduced within 
last 10 years, what they valued most - 


- column resizing was not an issue at all - proper grid can calculate 
size to set it automatically - we had two modes, auto column-width 
adjust, or static, set in config

- drag and drop was rarely used for columns. You can do it othe way 
around - let users to choose which columns they want to see, in what 
order. Let them save the config!!! Without it, forget about your 
grid being powerfull - what ppl are looking for is comfortable view 
of their data. Each person is used to slightly different view

- horizontal scrolling is a must. How cbut I can tell you what our 
300 users are used to, working with 3 grids we introduced within 
last 10 years, what they valued most - 


- column resizing was not an issue at all - proper grid can calculate 
size to set it automatically - we had two modes, auto column-width 
adjust, or static, set in config

- drag and drop was rarely used for columns. You can do it othe way 
around - let users to choose which columns they want to see, in what 
order. Let them save the config!!! Without it, forget about your 
grid being powerfull - what ppl are looking for is comfortable view 
of their data. Each person is used to slightly different view

- horizontal scrolling is a must. It is so basic feature, I wonder 
why noone is requesting it? grids based upon list show its main flaw 
- non ability to scroll horizontally. Real life apps do consist of 
more fields usually then you can fit into your screen ;-)

- sometimes users requested split-view, so that few left columns 
got locked and did not scroll horizontally ....

- proper keyboard handling is a must - enter=edit, ins=insert record, 
del=delete record, move by arrows, pgdn, pgup, end home, ctrl plus 
pgdn, pgup, home, end, left, righ ....

pekr, config saving will come, but I'm not sure yet how to do it. 
maybe an object or something.


Horizontal scrolling, I need to figure out. It will be an additional 
mode that can be activated by setting FIT-WIDTH to FALSE. By then, 
a scroller will appear along the bottom and different policies regarding 
column drawing need to be made. A little complex to figure out, but 
it will come.

pekr, MAIN-COL is resizable, because that was easy to do and I use 
that in my design. It works very well in my older implementation.that's 
why I continued using it.

aligning column headers with list data doesn't work yet when using 
a custom row face. there are apparently still issues with MAIN-COL 
and it really wants to autoadjust the column width. otherwise the 
solution would be to just provide a set of pixel widths. I'll see 
what I can do about this.

For those that want to set up there own site, OK, but then what they 
should do is feed an RSS to the central site.

I could do that, but I need to generate it...

I use the docs as kind of a testing ground too. If you see something 
in the docs which you are trying to do, it should work, because the 
images in there are always generated from the latest version

I dont need view, its just easier to do using it, since the project 
involves layering gif images. My expectations were that View would 
work as long as I didnt try to show a window. Luckily I have a a 
backup plan in place, just use core, so I set that up core last night.

I was hoping Cyphre's style creation talk would be much on this exact 
topic of the steps needed to create a new style and walking through 
the creation of one.  Mainly to see if this was something that was 
rudimentary (even newbies could do) or very involved (only for the 
seasoned programmer).

Do you plan to use the 'words facet to allow a VIDish way to specify 
(i.e) data.
So you can write :

	view layout [list-view data ["one" "two" "three"]]

didec, I would if I knew how to do that :-)

Have a look to the current list style. Use Anamonitor and look at 
the 'words facet. It's pretty easy to do.

It does get complex, and possibly too slow, but you may be able to 
patch show usefully for your application.

Check out a patched SHOW near the bottom of http://www.lexicon.net/antonr/rebol/gui/mimic-do-event.r

When using a text-list, how do I reset the slider to the top if the 
data changes? For example: The slider is at a lower position, now 
I change the content to some smaler list and want to redrag the slider 
to the top and have the text-list show the first entry at the top.

In 1.3 text-list style has an 'update function to do so.

Why is cleanliness of uninstallation so important to you right now 
? I don't see thousands of requests from new users of rebol saying 
"how do I cleanly uninstall rebol ?" Uninstalling by hand is pretty 
easy too.

well, to not sound so anti-IOS - main obstacle is the lack of source 
codes for me to translate into czech, or even more languages. Simply 
put - wrong model. I suggested RT to do IOS-SDK, for the price of 
IOS, so ppl could do some changes ...

I'm not addressing "you" and M$ does not care about Linux.  But what 
they did do was make a system that allows multiple people to use 
the same computer and keep their date apart.  It is wrong, and badly 
done, but the "correct" way to do it for thier system.



As to Carl allowing other ways to do it, that is the real question 
I assume you are asking.