AltME groups: search

I tryed a port for MDP-Viewer to RebGUI system and what I can say 
is that lot of thing are missing...

- capability to add a pane: [] to a rebgui box widget

Most of this is [hopefully] answered here: http://www.dobeash.com/it/rebgui/


While VID provides a nice set of styles to work with, RebGUI aims 
to provide a rich set of [functionally complete] widgets to work 
with. The specification syntax of RebGUI is similar to that of VID 
as:

	1) They are both built on top of View
	2) The VID specification syntax is near optimal

 3) I wanted to be able to swap between View / VID and RebGUI coding 
 without *too* much of a mind-set change!;)

yep and we have to keep in mind that VID is about 5 years old and 
rebgui is about 2 month old ;)

As Shadwolf has done a super job to get the MDP-Browser (that's how 
I want to name it) done, based on Ashleys base, I want to playback 
the result to the community. And IMO we should take this project 
to stress-test RebGUI because it's quite complex.

Latest build available at: http://www.dobeash.com/files/RebGUI-023.zip

Highlights include:

	- Changed default font from "Arial" to "Verdana"
	- Added label and table widgets
	- Added window-level 'do block support

 - Added 'reverse keyword to support windows style right-to-left widget 
 placement
	- Renamed set-title to show-title
	- Merged %request-file.r into %requestors.r
	- Renamed %gui.r to %rebgui.r and prefixed other files with same

Read more about these changes here:

	http://www.dobeash.com/it/rebgui/display.html#section-2.2
	http://www.dobeash.com/it/rebgui/display.html#section-3.3.2
	http://www.dobeash.com/it/rebgui/display.html#section-3.4
	http://www.dobeash.com/it/rebgui/display.html#section-4.3
	http://www.dobeash.com/it/rebgui/display.html#section-5.15
	http://www.dobeash.com/it/rebgui/display.html#section-5.26

Is there a tree widget for RebGUI being developed already?

I've been checking out RebGUI.  A number of very good design decisions 
were made.  I've ported my pair-edit style to be rebgui widget.
http://www.lexicon.net/antonr/rebol/rebgui/demo-pair-edit.r
(It needs editing to locate your rebgui directory.)

Actually, locating rebgui is a problem.  How does a script such as 
the above get the latest distribution and unzip it ?  I would prefer 
the rebgui files to be uncompressed (or compressed using rebol, at 
least) and there should be a standard way of determining the latest 
version.

So a script should be able to check for the latest version and download 
it into the public cache (which may be successful or not, depending 
if net connection is available), eg:
	do load-thru http://www.dobeash.com/it/rebgui/get-latest.r
and then just
	do path-thru http://www.dobeash.com/it/rebgui/rebgui.r

to initialize (which automatically falls back to any previously cached 
version).

Another issue:  Excuse me if this has come up before..  

The archetypal View face has some of its facets set to none, which 
makes using VID styles alongside RebGUI more difficult (because the 
VID-based styles are not expecting those facets to be changed.)

Suggestion: create widgets/rebgui-face and encourage widget creators 
to make from that.

And now a question:
	widgets: make widgets [ my-widget: make face [ ... ] ]

the best (or only) way to add your widget to rebgui, making it available 
to DISPLAY ?

mixing vid with rebgui has also some api-problems. some i found:

 /action: has in vid this args: [face value]. value is something usefull, 
 like area/text, slider/tdata, first text-list/picked etc. maybe its 
 not needed, "value" saves not much to "face/text". but supporting 
 that arg would be compatible

 /init: in vid this is a block and 'done. in rebgui it is a function. 
 vid has the advantage that init can be easily extended in substyles, 
 just add to it. rebgui has locals because it uses a function.
 /init2: not called by vid. 

resizing: not in vid, but one could write a /resize and plug it in 
the vid-face.

also there are some global changes which may break other things (removing 
event-func and changing global face IIRC).


If there is interest in making such small changes, i would help with 
making the rest compatible. adding #xh - parsing to 'layout and such. 
for "keep small" rebgui could have a "load-time-flag" to decide about 
using vid-stuff or all own.

What i would really like is rebgui for complex style-building (area 
with slider etc). this is closer to raw faces. and vid for quickly 
writing "pages", IMHO it has a rest of advantages there. (maybe not, 
i am a rebgui-beginner).

http://shadwolf.free.fr/rebgui-list49.r

Anton

 1) Design decisions: thanks; if you think any of them were *bad* 
 then let me know, that's the reason it's still alpha ;)

 2) I like the edit-pair demo, I'll look at adding a cut-down version 
 of it to %tour.r

 3) Versioning / caching was something I was going to look at once 
 RebGUI goes beta and / or we have more of a handle on how REBOL/Services 
 works.
	4) "local" face definition: good point, added to next build.

 5) Extending widgets object: Yes, RebGUI doesn't have a "stylize" 
 system so you have to extend the widgets object when you need to 
 add your own. My hope is that with a functionally rich set of widgets 
 this will be the exception rather than the rule!

Robert

 Action handler not yet added to table widget. I'll add odd/even coloring 
 to the ToDo list.

Volker

 [face value] - less important for RebGUI as face/text or face/data 
 covers almost all cases; but I'll think on it a bit more as the compatibility 
 aspect is worth considering.
	/init - I'll look at making this a block in the next build.

 event-func removal - I'm considering a "load-time-flag" as you suggested
	system/standard/face - as per comments to Anton above
	"If there is ..." - agree fully with everything stated here ;)


RebGUI development is taking a slight pause until View 1.3 is released, 
as I want to baseline against that and remove all the pre-1.3 exceptions 
that have crept in.

Ashley you are right we need to base RebGUI on REBOL/View 1.3 that's 
the way it must be done ...

Nice, try just typing rebgui into the location bar on FireFox...

Ammon :when I type rebgui in the firefox 1.0.4 location bar I get 
the redirection to the rebol france article (in french) I wrote ;) 
king of little presentation for french readers

Latest build available at: http://www.dobeash.com/files/RebGUI-024.zip

Highlights include:


 - New edit object / feel added in a separate file, %rebgui-edit.r

 - Documentation on above at: http://www.dobeash.com/it/rebgui/edit.html
	- Face redefinition localised to widgets object
	- Radio-group color toned down from green to leaf

Known issues:

	- auto-fill broken for the time being

 - edit feel needs to support tab / shift+tab into and out of "grouping" 
 widgets

 - cursor down goes to end of text instead of next line?! (yell if 
 you know the answer as I'm stumped on this one)

On the drawing board

	- area widget needs a scroller added to it by default
	- field format / validation masks
	- inline spell-checker

Regarding use of color in RebGUI:


I don't think color choices for LEDs in RebGUI are good, which is 
namely because the default colors are red and green.

That not only excludes the color blinds, but even the red-green-blinds 
(sort of lesser color blinds), which applies to even more people 
(mainly male ones). 


Using blue and yellow would make things slightly better, but would 
still be a hurdle for full color blinds. Probably different shapes 
would be more usefull here, as they'd give an additional clue.


And, finally, the colours are named wrong in the LED group: check-group 
60x4 data ["Red" true "Green" false "Blue" none]

Believe me, I had to measure the valve values to find that out ;-)

And personally, I find the visuals of the sliders and draggering 
irritating, too.


The gradient in the sliders container IMHO doesn't integrate in the 
overall RebGUI appearence - since it's (button left aside) nearly 
the only pseudo-3d effect - and the visual contrast between dragger 
an container IMHO isn't very strong. I usually find me clicking in 
the container when I expected to grab the dragger.


The gradient in itself is somewhat unsual, too, since it makes the 
container appear standing out of screen, if one assumes that light 
falls from upper left corner (which is how most pseudo-3d screen 
elements are designed).

Yep. And the current style doesn't fit to the rest of RebGUI.

Here's another issue:
rebgui 0.2.4 defines a new global word 'edit

  This interfered with my custom edit function, which I use to launch 
  my favourite editor.
  I'm not changing it for you ! :)

  This is an example of the problem of adding words to the global context 
  without doing
  an environmental impact study first.

  The user should be given the choice whether to export your words 
  to the global context or not.
  But probably most of them don't need to be out there at all.

  My advice is to add only these words to the global context: [

 ctx-rebgui display show-text show-data show-title splash request-color 
 request-date request-file
  ]
  
  --- rebgui.r ---
  
	CTX-REBGUI: context [

		...

		edit: none
		widgets: none
		requestors: none
		display: none

		foreach [word file][
			edit		%rebgui-edit.r
			widgets		%rebgui-widgets.r
			requestors	%rebgui-requestors.r
			display		%rebgui-display.r
		][
			if none? word [set word do file]
		]
	]

	;if not value? 'edit [do %rebgui-edit.r]
	;if not value? 'widgets [do %rebgui-widgets.r]
	;if not value? 'requestors [do %rebgui-requestors.r]
	;if not value? 'display [do %rebgui-display.r]

	; export DISPLAY and the accessor functions to global context
	foreach word [display show-text show-data show-title splash][
		set word get in ctx-rebgui word
	]


  And each file no longer has a *named* context:

  --- edit.r ---

	REBOL [...]
	
	context [...]


  The above changes should mean few changes to the rebgui code. For 
  example, the body

  of the display function refers to the widgets context, but this is 
  still accessible
  because both DISPLAY and WIDGETS are inside ctx-rebgui.

One consideration though; how would this scheme be extended to handle 
SDK use of #include's (as folks using the SDK won't want to ship 
rebgui-*.r files with their executables)? Oh for a #do-include command! 
;)

I think this may work (not sure, can't test):
sdk?: is-this-sdk? ; <--- need to find out a real flag

set 'edit	do #either [sdk?][#include %rebgui-edit.r][%reb-gui-edit.r]

set 'widgets	do #either [sdk?][#include %rebgui-widgets.r][%rebgui-widgets.r]

set 'requestors do #either [sdk?][#include %rebgui-requestors.r][%rebgui-requestors.r]

set 'display	do #either [sdk?][#include %rebgui-display.r][%rebgui-display.r]

CTX-REBGUI: context [

	...

	edit: none
	widgets: none
	requestors: none
	display: none
		
	#do [edit: do #include %rebgui-edit.r]
	if none? edit [edit: do %rebgui-edit.r]
	#do [widgets: do #include %rebgui-widgets.r]
	if none? widgets [widgets: do %rebgui-widgets.r]
	#do [requestors: do #include %rebgui-requestors.r]
	if none? requestors [requestors: do %rebgui-requestors.r]
	#do [display: do #include %rebgui-display.r]
	if none? display [display: do %rebgui-display.r]
	...

]


CTX-REBGUI: context [

	...

	edit: none
	widgets: none
	requestors: none
	display: none
		
	smart-do: func ["helper function to reduce repetition"
		ignored [issue!] block [block!]
	][
		if none? get first block [do replace copy block [#include][]]
	]
	smart-do #do [edit: do #include %rebgui-edit.r]
	smart-do #do [widgets: do #include %rebgui-widgets.r]
	smart-do #do [requestors: do #include %rebgui-requestors.r]
	smart-do #do [display: do #include %rebgui-display.r]
	...

]

Earlier builds of RebGUI used the following code to minimise the 
problem:

	context [
		show*: :show
		set 'show func [face [object! block!]] [show* face recycle]
	]

which kind of points to the GC as the problem.

Question for the bind experts out there. Given two files (named %include.r 
and %test.r respectively):

	REBOL []

	context [
		a: "A"
		b: does [print reform ["Value:" a]]
		c: does [print reform ["Value:" d]]
	]

	REBOL []

	RebGUI: context [
		d: "D"
		ctx: #include %include.r
		if issue? ctx [ctx: do %include.r]
	]

	RebGUI/ctx/b
	RebGUI/ctx/c


How do I bind %include.r to the RebGUI context such that it can see 
'd (as the #include successfully allows).

another option is to embedd a smaller and faster "prebol" in rebgui 
and build everything on startup, then doing it altogether.

REBOL []

load-include: func [include [any-block!]][

    either parse inlcude reduce [to-issue 'include file!][load include/2][include]
]

RebGUI: context [
	d: "D"
	ctx: do bind load-include [#include %include.r] 'self
]

RebGUI/ctx/b
RebGUI/ctx/c

Ashley roadmap: 1) set of widget complet (what widgets are in it 
?)  2) functionnality of this set (what they do how we use them ?) 
3) esthetic of the widgets is dicted by the low people working on 
RebGUI and the nececity to make a simplier set of widgets. The fact 
that AGG was not official have make diffucut to put in line a good 
estetical consept. As REbGUI philosophy is to be light and easy  
we can't make a lot of heavy imge insertion and image drawing

Here is a preview of what the roadmap will look like: http://www.dobeash.com/it/rebgui/roadmap


Not withstanding the fact that all the blanks need to be filled in, 
if there is anything else you believe should be covered / included 
then just holla.

AS I propose to orgenise the devs we need as we are in stage one 
to have the overall list of the widgets that ashley wants to have 
in rebgui. We can make it on dokuiki rebolfrance.info a little table 
with widgets name | widget description | author that takes in charge 
the dev of this widget | dev stage % | integrated to rebgui |

Ashley if you want you post me here the list of remaining list you 
want to see in rebgui then I build a dedicated editable page in the 
dokuwiki rebolfrance.info  :)

Ashley I make the spanish.dat for rebgui  you can find it there http://shadwolf.free.fr/spanish.dat

Ashley I have one little ask why the tabpanel with scrollable header 
Have not been inserted to rebgui until now  ?

Ashley, you found the issue way too. :) Chris' function looks very 
good.
Here's another way:

 edit: do either any [#do [false]] [%rebgui-edit.r][#include %rebgui-edit.r] 
 ; (false is actually not needed)

(*possible* way, I should say. I haven't tested that, and it needs 
bind in ctx-rebgui 'self.)

I eventually solved it with:

	ctx-rebgui: context [
		...
		edit: #include %rebgui-edit.r
		if issue? edit [edit: do bind load %rebgui-edit.r 'self]
		...
	]

it's two lines as opposed to one, but *much* clearer! ;)

Graham: Next RebGUI build, 0.3.0, requires View 1.2.124 or higher.

Pekr: difficult without a global event system (as shadwolf asked 
about before). If I can achieve the same effect (i.e. close when 
mouse leaves widget) without it then I'll implement it that way instead 
(global event handling is just too expensive for the few cases it 
is required).

Graham: RebGUI encap needs:
	#include %gfx-colors.r
	#include %gfx-funcs.r
I've added these to the next build.


Pekr: I've updated the choose func (used by drop-list / edit-list) 
to issue a hide-popup when the mouse leaves it. Feels pretty intuitive 
to me, but I'll see what folks think once the next build is out. 
;)

Vincent: Agree, I'll see about adding that for 0.3.0 as well.

Excellent! Just tried it with RebGUI and it works beautifully; even 
with global events killed. I think the edit-list / drop-list problem 
is solved. ;)

Latest build available at: http://www.dobeash.com/files/RebGUI-030.zip


*** Note that this version requires View 1.2.124 or later, and that 
the zip file is unusually large (346Kb) as it includes a dictionary 
file (future builds wont). ***

Highlights include:

	- New language, dictionary and spellcheck functionality added

 - Documentation on above at: http://www.dobeash.com/it/rebgui/edit.html#section-4
	- All objects merged into one context
	- Major code reorganization / restructure
	- Reduced number of global words to 11
	- Pre-0.3.0 comments removed
	- Pre View 1.2.124 code removed
	- New text-list widget added
	- Added show-color accessor function

 - rebface and rebfocus synonyms to avoid collision with face / focus
	- Large number of bug fixes
	- http://www.dobeash.com/it/rebgui/roadmap.htmlupdated

Known issues:


 - edit feel needs to support tab / shift+tab into and out of "grouping" 
 widgets

 - cursor down goes to end of text instead of next line?! (yell if 
 you know the answer as I'm stumped on this one)
	- focus

 - edit-list / drop-list should use show-popup/away (some compatibility 
 problems)

On the drawing board

	- area widget needs a scroller added to it by default
	- field format / validation masks
	- menu widget
	- better keyboard navigation / focus

ashley: testing RebGUI-030. When I click a tab in the big pane and 
then click the last pane in the sub-pane, it sometimes crashes to 
console

Ashley, I am not sure I like name of rebface. I think it would be 
better just as face (ctx-rebgui/face). I don't see the need to distinguish 
so much from standard View face. Indeed, I think it will make porting 
code a little slower.

do http://www.lexicon.net/antonr/rebol/rebgui/demo-slider.r

(you will need to modify demo-slider.r to point to your rebgui installation 
directory)

I am thinking of integrating arrows as options in the slider. This 
means a scroller would just be a slider with the arrows option. But 
this violates the rebgui principle of each widget being self-contained. 
However, the case for code reuse here is very strong, and so I want 
to do it. Any comments on that ?

Anton, rebface word only comes into play during widget creation; 
all other references to face (e.g. feel, focus, etc) have not changed. 
In fact, that was one of my motivations for introducing it ... I've 
seen far too many people tripped up by code like the following:

	engage: func [face action pos] [
		...
		insert tail blk make face [
			...
		]
		...
	]


where the "make face" should have been "make system/standard/face". 
When a RebGUI widget refers to rebface it is now unambiguous that 
we are not referring to a face argument nor the global face.


Looking at your demo slider now. If slider / scroller can be combined 
without a net increase in code size then I'm all for it as they are 
functionally and stylistically similar (vsplitter and hsplitter were 
combined into splitter for much the same reasons quite a while back).

list-view has been updated to comply rebgui 0.30 can be found here 
http://www.rebolfrance.info/articles/regui-cooking-widgs

** Script Error: Invalid path value: rebfaceeither
** Where: wake-event

** Near: show-data ctx-rebgui/rebfaceeither none? face/data [true]
>>

** User Error: RebGUI requires View 1.2.124 or lat
er to work.
** Near: to error! :value

I'm thinking for example of transparent popupmenu in menu style of 
Cyphre this is an other example of how we could use draw/AGG to enhance 
RebGUI global interaction

DideC My idea is not to make rebgui complicated but only to make 
it wither but thinking of it the scrolling down effect can be made 
without AGG in fact

Ashley, your argument has swung me to your point of view. The only 
thing is I would prefer rebgui-face instead of rebface, just to be 
totally unambiguous.

Anton: no harm in using do-face, but "face/action face" is usually 
enough. I chose rebface (even though it is an SDK component name) 
as it is consistent with rebfocus and any other VID words I need 
to redefine. I didn't want a proliferation of rebgui-* function names. 
On the other hand, it's a lot easier to rename rebface / rebfocus, 
etc than the original face to rebface change! ;)

maybe we should think about a name change? rebface looks a lot like 
"the face inbuild in rebol." rebgui works as "a gui for rebol", but 
rebface?

Ashley: How about adding a main link to each rebgui document to go 
back to start page of RebGUI.

If anyone can work out why popup/away doesn't work from within display 
(by uncommenting the display line and commenting the view line), 
please let me know.

	REBOL []

	do %rebgui.r

	;display "test" [
	view layout [

  button "Click here" [show-popup/away make system/standard/face [] 
  do-events]
		text "Then here."
	]

	do-events

It would be very good to get this working [with RebGUI].

load-thru/update site/rebgui/slider.r
do site/rebgui/demo-slider.r

I know, the RebGUI approach ...

Graham, is there an error message ? RebGUI is now at 0.3.0, Rebol/View 
is at 1.3.0 (I am sure you noticed.. :) and demo-slider.r 1.0.2, 
slider.r 1.0.3

>> view-root
== %/d/rebol/view/temp
>> site: http://www.lexicon.net/antonr/rebol/
== http://www.lexicon.net/antonr/rebol/
>> load-thru/update site/rebgui/slider.r
== [
    context [
        slider: [
            size: 4x40
            data: 0
            color: ctx-rebgui/colors/widget
    ...
>> do site/rebgui/demo-slider.r

** Access Error: Cannot open /d/rebol/view/programs/rebgui/rebgui.r
** Where: halt-view
** Near: do view-root/../programs/rebgui/rebgui.r
include [
    site/rebgui/slider.r [slider]
]
query/clear

It's expecting to find rebgui in /d/rebol/view/programs/rebgui/

Ah, sorry Graham, I forgot to mention you will need to modify demo-slider.r 
to point to your installation of rebgui 0.3.0...

The reason is there's no easy way for a rebol script such as this 
to install rebgui from the zipped distribution.

I could handle it by keeping a distribution of rebgui on my site, 
unpacked.

or the script looks to see if rebgui is in the local directory ?

Anton can you add an entry to the rebgui on cooking page ?

I don't get the point ...  people that work on a widget of rebgui 
must be noticed to the public  ;)

Yes, I just realised I didn't put much credits in the source. I should 
have credited at least Ashley, because I started from rebgui scroller 
style, listed in rebgui doc as authored by Ashley.

we all know that the most of the work was done by ashley our intervention 
is most a support one (well in listview it's 100%  my own code ... 
 but that the only one and it's not ended it lot to bet that AShley 
will adapt it befor intergring it to rebgui  :))

re: check actions - by omission; fixed in next build. I've also updated 
the roadmap to include a link to the RebolFrance Wiki (shadwolf) 
and a link back to the RebGUI Home page (Robert).

i'm testing RebGUI for my project

; définition du style de l'objet et intégration dans le context de 
RebGUI :
ctx-rebgui/widgets: make ctx-rebgui/widgets [ 
	;; Object' Style definition :
	object: make ctx-rebgui/rebface [
		size: 20x20
		title: ""
		pane: []
		; gestion des évènements :
		feel: ctx-rebgui/widgets/default-feel
		
		; Initialisation :
		init: has [tmp-sze] [
			tmp-sze:  size
			; list countainer
			insert tail pane make ctx-rebgui/rebface compose [
				size: tmp-sze   offset: 0x0 pane: [image img-barre]
			]
			; Insert TitleBar :

   insert tail pane titlebar: make  ctx-rebgui/widgets/image compose 
   [

     image: img-barre size: (as-pair tmp-sze/x 30) offset: 0x0 edge: ctx-rebgui/widgets/default-edge
			] titlebar/init
			; insert scrollers 

   insert tail pane v-scroll: make  ctx-rebgui/widgets/scroller compose 
   [
			 	size: (as-pair 15 tmp-sze/y) offset: (as-pair tmp-sze/x 0)

     ;action: does [scroll-table/y parent-face/pane/1 self] ; put here 
     scrolller function calls
			] v-scroll/init

   insert tail pane h-scroll: make  ctx-rebgui/widgets/scroller compose 
   [
			 	size: (as-pair tmp-sze/x 15) offset: (as-pair 0 tmp-sze/y )

     ;action: does [scroll-table/x parent-face/pane/1 self ]; put here 
     scrolller function calls
			] h-scroll/init
			; insertion  scrollable countainer 
			insert tail pane/1/pane make ctx-rebgui/widgets/box compose [

     size: (as-pair pane/1/size/x (pane/1/size/y - 15))  offset: 0x0 pane: 
     []
 			] 
		]
	]
]

With regards to the image size problem, try adding "effect: 'fit" 
to your make image code. Also, it's probably easier to make the image 
directly from a face, as in:

	insert tail pane make ctx-rebgui/rebface [
		offset:	0x0
		size:	as-pair tmp-sze/x 30
		image:	img-barre
		edge:	ctx-rebgui/widgets/default-edge
		effect:	'fit
	]

site: http://www.lexicon.net/antonr/rebol/
load-thru/check site/rebgui/slider.r 1.0.4

do site/rebgui/demo-slider.r  ;<-- modify this file to point to your 
rebgui installation

Now, scroller should be able to be implemented in rebgui-widgets.r 
by just:

http://www.lexicon.net/antonr/rebol/doc/create-a-rebgui-widget.r

http://www.lexicon.net/antonr/rebol/doc/create-a-rebgui-widget.html

Good introductory doc BTW, I've added a link to it from the RebGUI 
Home page already. ;)

Hi. I 've had a look at REBGUI and it looks terrific!

However, when I run the tour.r script there is some kind of memory 
usage display at the bottom which increases by 6 KB every second 
even if I don't do anything. Would that mean REBGUI is eating memory 
without control??

http://www.dobeash.com/it/rebgui/edit.html#section-4

The dictionary, if present, is then loaded into the dict block.

site: http://www.lexicon.net/antonr/rebol/
load-thru/check site/rebgui/slider.r 1.0.5
load-thru/check site/rebgui/pair-edit.r 1.0.1

do site/rebgui/demo-slider.r  ;<-- modify this file to point to your 
rebgui installation

load-thru/update site/rebgui/slider.r ; (just now updated slider.r 
again, same version)

Latest build available at: http://www.dobeash.com/files/RebGUI-031.zip


*** Unzip this file into your existing RebGUI 0.3.0 distribution. 
Requires View 1.3. ***

Highlights include:


 - Replaced scroller & slider widgets with Anton's new combined slider
	- Updated widgets to use same and set dragger size
	- Tab-panel now accepts actions (to enable dynamic tab displays)
	- Improved text-list selection logic
	- Prototype request-dir function added (needs a lot more work)
	- Large number of bug fixes
	- http://www.dobeash.com/it/rebgui/display.htmlupdated

Known issues:

	Unchanged.

On the drawing board

	Unchanged.

Unzip into your existing rebgui 0.3.0 installation.

SCROLLER has not been defined in the lastest rebgui-widgets.r

I get the same error.  A quick hack is to add this before the last 
line in rebgui-widgets.r:

site: http://www.lexicon.net/antonr/rebol/
load-thru/check site/rebgui/slider.r 1.0.6
do site/rebgui/demo-slider.r

Sorry guys, my fault for the confusion as I forgot to include the 
modified %tour.r. I've refreshed the zip with a "b" suffix to avoid 
any caching issues, and added Anton's fix as above:

	http://www.dobeash.com/files/RebGUI-031b.zip

rengu mean rebgui  I don't know why I have some problems to tip text 
today :)

Done. Correct link is: http://www.dobeash.com/it/rebgui/

like the initial intro. on what rebgui is..as oppose to 'why NOT 
VID'

a very clear focus of rebgui purpose

RebGUI intents to extant and embeter VID but it's obviously a layer 
over VID ;)

3) on refresh with new data  I get an internal  crash in rebgui

see the rebgui list code in the rebolfrance.org page ;)

Anton

 1) Code size. What it loses in code size it gains in aesthetics and 
 simplified behaviour (check out the request-color and request-date 
 actions in %tour.r to see the extra "state" code required by the 
 original implementation). I like Brian's base64 solution.

 2) Tab-panel color: I've based this on the WinXP color scheme. Try 
 changing it to colors/window, it just doesn't look right. But slider 
 can be used on a colors/widget or colors/window background. WinXP 
 solves this by using a gradient / edge so that it is distinguishable 
 on either. So for RebGUI, a number of solutions are possible:

  - add a new colors/slider background that "works" with both widget 
  and windows background colors

  - add a new colors/tab-panel background that "works" with both widget 
  and windows background colors

  - use an effect like gradient to distinguish the slider background 
  color
		- or edge
		- or?
	I'm open to suggestions on this one. ;)

Brian
	1) I like the in-line image solution

 2) I like the base 64 solution even better! One problem, the button-down 
 image renders the same as button-up (i.e. 1st and 2nd images render 
 the same ... even though a quick glance at the data suggests they 
 are different?)

Graham
	Any examples where the desired behaviour is used?

shadwolf

 I did the same (replaced scroller call with "slider data [arrows]") 
 for text-list / table and it worked fine for me. Check for code that 
 tried to reference sub-faces in the old scroller widget (as Anton 
 refactored slider to use just one face).

Hm...  Show and Hide are Natives I wonder what RebGUI is doing to 
stop them from working...

Not with a pre-1.3 SDK. %rebgui-widgets.r uses some 1.3 specific 
words such as case, unless, etc. Once it starts making greater use 
of AGG-specific draw commands there will be no going back.