World: r3wp

Robert:
	1) global words: they are not. Try the following:


  f: has [v] [display "Test" [v: field button [unview halt]] do-events]


 My normal approach is to wrap each display in its own function with 
 something like:


  display-account-summary: make function! [id [integer!] /local f1 
  f2 f3 f4 f5 f6] [
			...
			display "Account" [
				f1: field
				f2: field
				...
			]
			...
		]


 2) tab-panel: works, just take a look at how it is used in %tour.r. 
 Note that it defaults to "size: -1x-1". Maybe you need to make the 
 panel contents bigger?

face/picked: try adding a "print mold face/picked" to the table action 
so you can see what block value(s) are being selected. Perhaps, in 
a particular case, it is returning an empty block?

Does image still only take a filename and not an image type?

I'm looking at capturing images from a web cam and inserting them 
into my program.

The following works:

	a: load my-image.png
	display "Test" compose [image (a)]

Ahh .. forgot needed to compose.

Sorry for the proliferation of my dots, I'm forcing a resync and 
I'm being disconnected at about 25%... :-(

.

.

.

.

.

Have you considered broadband ?

Ashley: Do you use several display functions in your apps? At the 
moment I have one. I use tab-panels a lot. Hence I have one big display 
function.

Have about half a dozen, and I make use of 'unview-keep to only have 
2 or 3 open at the same time (also useful when multiple data entry 
screens are open at the same time and the user clicks "commit" ... 
data is saved and all windows except the Main Menu are closed).

Ok, I think I have to make some tests.

Next one: What's the best way to create "user-selection-dependent-layouts"? 
For example the User select one entry in a drop-down box and depending 
on the value, a different layout should be shown below the drop-list.

Hmm.. you can do it many ways. What's the application to do and what 
will the window layout have in it ?

Oh... probably you would use tab-panel.

Yes, it's in a tab-panel and depending on the selection of one drop-list 
the data-input form that follows the drop-list has to display different 
labes & fields.

How many entries has the drop-list ?  Because if it's small I might 
suggest using another tab-panel. Otherwise I would try to create 
the layout for each selection before the window is displayed.

Or, if most of the time the labels and fields are common, but with 
some differences, I might use the drop-list action to hide all and 
show only those fields which go with the current selection.

ie. all the fields are placed in the same panel :)

Tab panels can't be used, because it's XOR. So either show A or B.

Doing a hidden layout and than plugging it into the current one would 
be best. But than I have to deal with PANE etc. IMO that's to low-level. 
I would like to have a way to alter the layout dynamically.

Ashley, thanks for the answers.   I cant figure out from the tour 
how to show some new values of data in a table.  What is wrong with 
the instructions in the two buttons.

Rebol []
#include %rebgui.r
unless value? 'ctx-rebgui [do %rebgui.r]

display "ProspectGUI" compose/deep/only [

 ex-table: table 120x40  #HW options ["ID" left .2 "Nom" left .4 "Prenom" 
 left .4] data [1 "Vac" "Gus"] []

 button "Delete1" [ ex-table/data: [2 "Cah" "Sug"] ex-table/redraw 
 ]

 button "Delete2" [ show-data ex-table [2 "Cah" "Sug"] ex-table/redraw 
 show ex-table]
]
do-events

try working with the existing data, and not creating new lists.

insert head clear ex-table/data  [2 "Cah" "Sug"]
ex-table/redraw

when I was tabbing .. got this

** Script Error: Cannot use path on none! value
** Where: next-field
** Near: all [
    item: find face/parent-face/pane face
    while [
        if tail? item: next item [item: head item]
       ...

Ashley, what's the state for the load/save OPTION implementation 
into RebGUI? Did you start already? If not, let me know. That's something 
I want to push forward.

load/save: I mean get back/fill in all fields in a structured way 
so that it can be used with SQLite.

what do you mean by this?

If you have a form with several fields I want to have something like:
	store data-form
and get back a block like this:
	[name text  "Graham" rebol value true ...]

So for all widgets where the SAVE flag is set, the name of the widgit 
word, the word and value is returned. With this it's possible to 
handle records very comfortable.

put-form/all my-display block-of-values-returned-by-sql-call
blk: get-form my-display


I've got as far as thinking about how it could / should be implemented 
(there are some interesting issues with grouping widgets like group-box, 
table, text-list, etc); but my focus at the moment is to complete 
the SVN setup / structure / documentation / usage instructions so 
as collaborative development can begin (and I am no longer the bottle-neck 
in changes being implemented). Unfortunately, I'm two weeks into 
an intensive four week certification course (non-IT related) so REBOL 
things are on the back burner for a while (although I'm popping in 
here to answer the odd question here and there where I can).

I'm not sure that this is relevant, but I did some basic screen validation 
for vid, and documented here


http://en.wikibooks.org/wiki/REBOL_Programming/Language_Features/Parse/Screen_Validation

manual resync...

Is there a "fit" for images as in Vid?

umm... the other way round... display an image in it's native size.

unscaled.

image effect 'fit
image effect [fit]

i can't undestand - what's the best way to change view of widgets, 
for example i want to change arraws of slider in textarea?

this is rebgui ...

image effect 'aspect ... was what I was looking for.

?

want to change arraws of slider in textarea?

 ... change in what way? Look? Feel? Where the arrows are located? 
 Arrows or chevrons? Colour?

I think Julia wants to do skinning, changing the look of the slider. 
Well, I programmed the slider/scroller, and I can say that it is 
not easy to reskin. You will have to get your hands dirty :)  When 
rebgui first came out, it was intended to be very lightweight, so 
I think Ashley only started to want to add fancier abilities like 
skinning later. When I wrote slider/scroller, I was trying to be 
as minimalist as possible, so it's quite "hard-wired" with respect 
to how it draws itself.

Maybe Julia means how to change the colours ? Well, as I remember, 
I just used button colours.

Ashley, how's the splitting of widgets into separate files going 
? What method are you using to integrate them into the final context 
?

Here is a very simple patch to slider, which makes a nice half-second 
pause at the beginning of a scroll:
				if find [down time] act [
					if act = 'down [face/rate: 2]
					if act = 'time [face/rate: 16]