AltME groups: search

REBOL[]


rebgui-build: %./rebgui-116/
rebdb-build:  %./RebDB-203/


#include %/home/ramcla/Documents/rebol/rebol-linux-sdk-276/source/gfx-colors.r

#include %/home/ramcla/Documents/rebol/rebol-linux-sdk-276/source/gfx-funcs.r
#include join rebgui-build %rebgui.r
#include join rebdb-build %db.r

do  join rebgui-build %rebgui.r
do  join rebdb-build %db.r

to-amount-text: func[
	data
	/local
	d
][
	d: to-string to-money (to-decimal data)

 return either d/1 = #"-" [join "-" (skip d index? find d #"$")][(skip 
 d index? find d #"$")]
]

table-exist?: func [
	table [string!]	
	/local
	w
][
	w: to-word table
	either error? err: try [db-describe :w][
		disarm err
		return false
	][
		return true
	]
]

create-table: func [
	table [string!]	
	/local
	w
	tables
][
	tables: [

  t_joueurs [id nom prenom date_naissance adresse code-postal commune 
  pays]
		t_periodes [id nom date-debut date-fin status]
		t_jeux [id period_id date lieu]
		t_resultats [jeux_id personne_id manche_1 manche_2 manche_3]

  t_resultat_historique [jeux_id personne_id manche_1 manche_2 manche_3]
	]
	
	w: to-word table
	db-create :w (select tables w)
]


create-db: func [
	/local
	table
][
	if not table-exist? table: "t_joueurs" [create-table table]
	if not table-exist? table: "t_periodes"  [create-table table]
	if not table-exist? table: "t_jeux"     [create-table table]

 if not table-exist? table: "t_resultats"     [create-table table]

 if not table-exist? table: "t_resultat_historique"     [create-table 
 table]
]

create-db

;print screen avec F3
ctx-rebgui/on-fkey/f3: make function! [face event] [
    save/png %screen.png to image! face
    browse %screen.png ; or call %screen.png
]


words: copy []

;	clear words in global context

query/clear system/words

;	show splash screen

splash join rebgui-build "images/logo.png"

;	compose pie-chart data

pie-data: compose [
	"Red" red 1
	"Red-Green" (red + green) 1
	"Green" green 1
	"Green-Blue" (green + blue) 1
	"Blue" blue 1
	"Blue-Red" (blue + red) 1
]



;	wrap display in a func so it can be called by request-ui


display/close rejoin ["Carte (build#" ctx-rebgui/build ")"] [
	

 ;	button "Configure Look & Feel" 50 [if request-ui [unview/all show-tour]]
	
	tight
	after 1
	menu #LW data [
		"Maintenance" [
			"Bienvenue"	[panel-master/select-tab 1]
			"Joueurs" 	[table_joueur 'rsh panel-master/select-tab 2]
			"Periodes" 	[panel-master/select-tab 3]
			"Jeux"		[panel-master/select-tab 4]
		]
		"Option" [
			"Quit"		[quit]
			"Print Screen"  [alert "coucou"]
		]
	]
	
	panel-master: tab-panel options [no-tabs] #LVHW data  [			
		"Bienvenue" [
			
			title-group %./images/setup.png data  "bienvenue" "toto"	
		]
		"Joueurs" [
			label "nom : "
			ask_nom: field 50 
			label "prénom :"
			ask_prenom: field 50
			button "Trouver"
			return
			maintenance_table_joueurs: table 200x50 #LW options [

				"id"                  left     .1
				"nom"                 left     .3
				"prenom"              left     .3
				"date de naissance"   center   .3				
			] data [] [table_joueur 'rtv]

			return
			label "ID :"  35 
			m_joueur_id: field  50 options[info] 
			return
			label "Nom :"  35
			m_joueur_nom: field  50
			label "Prénom :"  35
			m_joueur_prenom: field 
			return 
			label "Date de Naissance :"  35
			m_joueur_date_naissance: field  43 tip "coucou" on-unfocus [
				use[d][
					d: copy face/text
					either empty? d[
						set-text m_joueur_age ""
					][
					 	either error? err: try [to-date d][
							disarm err
							set-color face red
						][
							set-color face CTX-REBGUI/COLORS/page
							d: to-date d
							set-text m_joueur_age (now/year - d/year )
							set-text face to-date d
						]
					]
				]
				true
			]
			arrow [
				use[d][
					if not none? d: request-date[
						set-text m_joueur_date_naissance d
						set-text m_joueur_age (now/year - d/year)
					]
				]
			]
			label "Age :"  35 
			m_joueur_age: field  50 options [info]
			return
			label "Adresse :"  35 
			m_joueur_adresse: area  100x20 [print coucou]
			return
			label "Code Postal :"  35 
			m_joueur_code-postal: field  50
			label "Commune :"  35 
			m_joueur_commune: field 50 
			return
			label "Pays :"  35 
			m_joueur_pays: field 50
			return
			button "Ajouter" [table_joueur 'add]
			button "Refresh" [table_joueur 'rsh]
			button "Update" [table_joueur 'upd]
			button "Supprimer" [table_joueur 'rmv]
		]

		"periodes"[text "lolo"
		]
	
	"jeux"[
text "lolo"]
	] 
	
	message-area: area #LW "" 10x-1	

][question "Vraiement ?"]



table_joueur: func [
	act [word!]
][
	switch act[
		clr[
			clear maintenance_table_joueurs/data
			maintenance_table_joueurs/redraw
		]
		rsh[
			table_joueur 'clr

   insert tail maintenance_table_joueurs/data copy (db-select [id nom 
   prenom date_naissance ] t_joueurs)
			maintenance_table_joueurs/redraw
			probe 	maintenance_table_joueurs/rows
		]
		cmt[
			db-commit t_joueurs
			table_joueur 'rsh
		]
		rmv [
			probe compose[id = (to-integer m_joueur_id/text)]

   db-delete/where t_joueurs compose[id = (to-integer m_joueur_id/text)]
			table_joueur 'cmt
		]		
		add [
			db-insert t_joueurs 
			compose[
				next 
				(m_joueur_nom/text)
				(m_joueur_prenom/text)
				(to-date m_joueur_date_naissance/text)
				(m_joueur_adresse/text)
				(m_joueur_code-postal/text)
				(m_joueur_commune/text)
				(m_joueur_pays/text)
			]
			table_joueur 'cmt
		]
		upd [
			db-update/where t_joueurs 
			[nom prenom date_naissance adresse code-postal commune pays]
			compose [
				(m_joueur_nom/text)
				(m_joueur_prenom/text)
				(to-date m_joueur_date_naissance/text)
				(m_joueur_adresse/text)
				(m_joueur_code-postal/text)
				(m_joueur_commune/text) 
				(m_joueur_pays/text)
			]
			compose[id = (to-integer m_joueur_id/text)]
			table_joueur 'cmt
		]
		rtv[

   foreach [id nom prenom date_naissance adresse code-postal commune 
   pays] db-select/where * t_joueurs compose[id = (first maintenance_table_joueurs/selected)] 
   [
				probe maintenance_table_joueurs/selected
				set-text m_joueur_id id 
				set-text m_joueur_nom nom
				set-text m_joueur_prenom prenom
				set-text m_joueur_date_naissance date_naissance
				set-text m_joueur_age (now/year - date_naissance/year)
				set-text m_joueur_adresse adresse
				set-text m_joueur_code-postal code-postal
				set-text m_joueur_commune commune
				set-text m_joueur_pays pays								
			]
		]
	]
]



do-events

for this code working you need   REBDB-203 & REBGUI build 116 in 
the same folder of this code and a folder "images" with an image 
like this %./images/setup.png

or perharps it will by better to give all of  us a example of best 
praticies to use reb-db table and rebgui  ????? :-)

i find this one in docuement of rebgui

;print screen avec F3
ctx-rebgui/on-fkey/f3: make function! [face event] [
    save/png %screen.png to image! face
    browse %screen.png ; or call %screen.png
]

RebGUI build#117 released. Release notes here:http://www.dobeash.com/RebGUI/release.html#section-11

http://www.dobeash.com/RebGUI/release.html#section-11

http://www.dobeash.com/RebGUI/release.html#section-11

panel-1: copy [
	text "coucou"
]

display rejoin ["test (build#" ctx-rebgui/build ")"] [
	
	panel-master: tab-panel  #LVHW data  [			
		"Bienvenue" [
			title-group %./images/setup.png data  "bienvenue" 			
		]
		"panel 1"  :panel-1

		"panel 2" [
		]

	] 
]

panel-1: copy [[
	text "coucou"
]]

do compose/deep [
	display rejoin ["test (build#" ctx-rebgui/build ")"] [
		tab-panel  #LVHW data  [			
			"Bienvenue" [
				title-group %./images/setup.png data  "bienvenue" 			
			]
			"panel 1"  (panel-1)

			"panel 2" [
			]

		]
	]
]




do-events

Oh well, I just added some trapping to rebgui-widgets.r

		selected: make function! [/local blk] [
			if empty? picked [return none]	; are any rows selected?

   either any [find options 'multi all [ value? 'parent-face parent-face 
   in parent-face 'type parent-face/type = 'table ]] [

Beer, Orca, RebGUI, Synapse were all setup by Jamie AFAIK (or did 
you setup Synapse).

http://trac.geekisp.com/rebgui
is up again

Ashley .. are Rebgui display objects so diferent from VID ones?  
I'm just wondering why henrik's to-postscript function doesn't work 
... see postscript group.

Shouldn't be ... both display and layout just generate a bunch of 
view faces at the end of the day. If it's really an issue you can 
always call system/words/layout from within RebGUI for those layouts 
that must be VID generated.

What I need is an object browser for Rebgui

Graham - not sure about RebGUI, but VID generates face structures 
at the end anyway. So - I am not sure you can easily make F keys 
local to certain screen. Well, maybe you can, but you would have 
to look how RebGUI handles events underneath. What I disliked about 
some tab styles was that all your tabs are always instantiated, whereas 
I wanted load-as-selected behaviour. That could help a bit in your 
situation.

Didier, I'll have to look at Rebgui to see if it can do this .. but 
at present I can use the window text.

it is imo not question of particular GUI system, but the question 
of widgets available. That is why I also wanted split-screen, resizable. 
But - those issues are not RebGUI related, so we are most probably 
chatting in wrong group ...

Anyone using the RebGUI tree widget?  I'd like to use it ... but 
I don't see a way to have a hidden field that could be used to retrieve 
a db record

REBGUI 117 whaoooo version  the looks really really pro and mature 
project congratulation Ashley

how can i add a custom rebface to rebGUI  to make it dynamical know 
the existance of my custom rebface

documentation is not reflecting actual rebGUI structure T___T (reb-widget.r 
is old)

not my code .. it's Rebgui code

Hi Giuseppe, I'll respond in full to your questions here as I've 
had quite a few emails recently asking similar questions about the 
future of R3 and RebGUI.

As you have created the best GUI solution for REBOL2

 ... Thanks, remember that "best" is in the eye of the beholder though 
 ;) ... RebGUI was created only because VID wasn't up to the task.

I ask to myself why your still not involved in REBOL3 GUI.

 ... Apart from the fact that I cannot give the project the time it 
 requires, the R3 GUI is in far more capable hands than mine. I'm 
 looking forward to it making RebGUI obsolete! ;)


Are you waiting the final VID version to port your great experience 
in this area ?

 ... When the R3 GUI is stable I'll look at how best to port apps 
 from RebGUI to it. I'm thinking either a compatibility layer or an 
 outright script conversion utility. But while we wait for that glorious 
 future (stable R3/GUI SDKs on Windows, Mac and Linux) RebGUI is still 
 the only R2/GUI game in town (IMHO).

RebGUI was created only because VID wasn't up to the task. damn right 
ashley but nothing guaranty us the VID next set of widget will be 
hum more reliable (to not say more usefull ...) but still VID remain 
 a powerfull things so with our without cool widget set from base 
since VID stay a powerfull base and draw still remains too it's still 
possible to make a set of widgets more hum .. more to feet our taste 
and needs ?

R3 is not for tomorow ( or maybe Carl done some crazy amount of work 
in the night and gets all ready for tomorow morning ???) so rebGUI 
still has a couple of years to go on ^^ and as a matter of fact i 
prefer i good VID /DRAW  system with no widget than lot of widgets 
with a not extendable dialect what makes all the interrest of VID 
is therefor the high flexibility of it and it's relative simplisicity 
and that aspect have to remain and even been enhanced

however main goal of rebGUI was to provide a cool widget enhancement 
library for VID propose a "example" set of widget people want to 
use the most in their software ( well that list of widgets can be 
found in any advanced graphical library such as GTK+ winap32 aqua 
QT WxWindows Tcl/tk etc...)

REbgui has in a background to show to that VID has many lacks (because 
no one really focus his attention only to design it. at least on 
teh VID2 version)  widget and event system could be simplier and 
provide more efficiency (less memory use more widget set ). REbgui 
was done in waste that's my own opinion

This isn't strictly a Rebgui question ... but here goes.  I want 
to double click on a word and perform an action.  That action involves 
interacting with some gui elements on the current screen.  Now, there 
is a function 'hilight-text inside the rebgui 'edit object which 
is inside the rebgui-ctx context.  So, I can hook in there with my 
dbl-click function.  But how to make it call my function which is 
defined for each window?

Anyway, this looks very promising at solving a lot of Rebgui issues 
I've had over the last few years... where I've clicked on a table 
row and the on-click function has collapsed because the face/selected 
path is not present.

As I mentioned above, it is something to do with rebgui's double 
click handler.

Ashley, why is double click here producing two windows?

do %/c/rebgui9/rebgui/rebgui.r

nw: func [ ][

 view/new/offset layout compose [ label text (form now/precise) ] 
 to-pair reduce [ random 400 random 400 ]
]

display "Double Click Test" [
	table 40x40 options [ "Dbl Click me" left .9 ] data [ "one" ] 
	on-click [ nw ]
	on-dbl-click [ ]
]

do-events

this illustrates the problem.


do %/c/rebgui9/rebgui/rebgui.r
do http://www.fm.tul.cz/~ladislav/rebol/default.r
do http://www.fm.tul.cz/~ladislav/rebol/closure.r

nw: func [ /local lab ][
	view/new/offset layout compose [
		below 
		lab: text (form now/precise)
		button "show" [ probe lab/text ]  
	] to-pair reduce [ random 400 random 400 ]
]

nw2: closure [ /local lab ][
	view/new/offset layout compose [
		below 
		lab: text (form now/precise)
		button "show" [ probe lab/text ]  
	] to-pair reduce [ random 400 random 400 ]
] 

display "Double Click Test" [

 table 40x40 options [ "Func Dbl Click me" left .9 ] data [ "one" 
 ] 
	on-click [ nw ]
	on-dbl-click [ ]

 table 40x40 options [ "Closure Dbl Click me" left .9 ] data [ "two" 
 ] 
	on-click [ nw2 ]
	on-dbl-click [ ]
]

do-events

Rebgui's 'display function prevents the second window opening ... 
so I don't understand why the problem is still occuring.

a print statement after this confirms the layout function is called 
twice on a double click

 ... as per documentation ( http://www.dobeash.com/RebGUI/user-guide.html#section-3.2.3
 ) "Every on-dbl-click event is preceded by an on-click event, as 
 shown in the following example: ..." But, the real problem here (as 
 you've discovered) is that the method for checking window uniqueness 
 relies upon a [title] string that only manifests *after* a layout 
 is substantiated. I suppose RebGUI could manage its own window title 
 cache, but then you introduce another point of failure (if the cache 
 gets out of sync with view*/screen-face/pane). I wonder if putting 
 a small wait value *before* the current title string test would "fix" 
 the problem (i.e. give the preceeding layout sufficient time to substantiate)?

I am trying to adapt Cyphre's old grid to recent RebGUI requirements. 
I got myself past color adaptation, so actually I can get it displayed, 
internally it returns correctly API function results, but I need 
to adapt to event handling. I am facing two problems:

- editing, double-click etc do not work
- during some actions as resizing I get following error:

** Script Error: action has no refinement called on-click
** Where: set-data
** Near: face/action/on-click face


I looked into: help ctx-rebgui/widgets/grid/action, but those funcs 
are not set. Is there any need to set those function for particular 
widget? I looked at some other styles as e.g. button, but button 
is not using its face/action/on-click either, so I am a bit confused 
....

http://trac.geekisp.com/rebgui/browser/widgets/button.r

yes, but there is no code in grid, which calls on-click. My asumption 
is, that it is being called by rebgui internally for my widget. So 
I have to probably define it. Dunno. Most probably I am not able 
to proceed further. There is not clear description of that functionality.

yes, but you use probably old Rebgui distro, no?

Graham - it is not true. IIRc I prepared package which I sent to 
you, with primitive initial doc, with included rebgui version, and 
it was working. The bad thing is, that it is some early version I 
paid for, but at that time there were some API changes to RebGUI, 
and I was not able to further contract Cyphre to adapt it ...

I think I know why - because it worked with some 2006 version of 
RebGUI, but not later ... well, I'll see, what I can do ....

The problem with the grid widget was that it relied on custom changes 
in rebgui-edit.r (i.e. it wasn't self-contained) and it was just 
too big to easily "grok" (and hence port). A good grid widget should 
have as few features/options as possible IMHO (i.e. get something 
that handles the text-only 80% case before worrying about more complex 
sub-widget support).

I do understand your point of view, which is - you try to keep Rebgui 
to its original idea. But - VID styleset is not real alternative 
to R2 GUI navadays, so refusing more complex widgets, especially 
in the case where noone really pushes anyone to use them, is escaping 
my understanding.

Of course if grid breaks some RebGUI habits, then it is not good 
.....

RebGUI is in maintenance mode so at least no more drastic (widget 
breaking) changes are in the pipeline ;)

i'm trying to port area-tc to rebgui ... and I don't understand why

I don't understand how to handle  events with rebGUI

rebgui-ctx.r >> 

system/view/screen-face/feel: none	; kill global events system (used 
by 'insert-event-func) 


the reason why area-tc will not be adapated to rebgui until ashley 
explain me how to map custom events for a custom face

on-key might be what you're after ( http://www.dobeash.com/RebGUI/user-guide.html#section-3.2.8
)

I guess Ashley wants to place Rebgui into a state of closure and 
move on.

Maybe we need to shift rebgui over to another site eg. codeplex

I've created the rebgui project on codeplex.com and will have a go 
at uploading the sources I have.

If anyone wants write access to the project, just sign up to codeplex 
and let us know so that we can join you to the Rebgui project.

In rebgui-widgets.r , any objections to changing

			attempt [remove find span #X]
			attempt [remove find span #Y]

to 

			all [ find span #X remove find span #X]
			all [ find span #Y remove find span #Y]

ctx-rebgui/behaviors/action-on-enter has 'field in it by default 
... so pressing enter *does not leave the field* but instead causes 
the field to regain focus.

well, I mean I know it is coming from rebgui-edit.r and the 'into-widget 
function which has a recursive find ....

Yes, but make sure you use the updated versions of both %ctx-rebgui-edit.r 
and %set-focus.r. I've also uploaded build 122 to correct a typo 
in back-field.


With regards to the question as to "what key should escape from cyclic", 
I've come to the conclusion that the best way of handling this is 
to just "tab through" cyclic widgets, so:

	f1: field
	panel data [f2: field f3: field]
	f4: field

would tab as f1, f2, f3, f4, f1, etc. tab-panel would operate as:

	f1: field

 tab-panel data ["a" [f2: field f3: field] "b" [f4: field f5: field]]
	f6: field

with a tab sequence of f1, f2, f3, f4, f5, f6, f1, etc


This way we don't have to worry about what keystrokes to change tabs 
or exit grouping widgets. What do you think?

Ashley and others, before I go about it,  do you have any experience 
with rebgui under the present browser plugin?

RebGUI v2 RC1 (build 200) uploaded to SVN

Focus of this version has been:
	* Make it look good (color scheme based on Windows 7)

 * Take into account OS sensibilities (different corner rounding, 
 window colors, system fonts)

 * Get rid of the cruft (removal of little-used widgets and options)
	* Improve tabbing
	* Make it load and run faster



Added
	icon
	get-fonts
	confirm
	request
	request-calc
	requesst-verify
	rebface/old-color
	rebface/over?



Reimplemented
	arrow
	calendar
	drop-list
	password
	slider
	tool-bar
	set-state
	set-color



Enhanced
	chat
	edit-list
	spinner
	table
	request-char
	request-font



Removed
	question
	request-ui
	pie-chart
	symbol
	options [info no-click]
	options [arrow options]


WIP
	A disable/enable function and layout option
	Rewrite of led widget
	Rewrite of tree widget

Works on XP. Did previous versions of RebGUI/tour.r exhibit this 
problem on Windows 7?

Graham, you mentioned in the Linux group that you had to change the 
RebGUI front from Verdana to something else. What font did you end 
up using?

Hmm, Rebgui somehow changed from single color web like look to some 
W9x look, was there any reason?

hmm, SVN says:

RebGUI v2 RC1

Added
	icon
	get-fonts
	confirm
	request
	request-calc
	requesst-verify
	rebface/old-color
	rebface/over?

Reimplemented
	arrow
	calendar
	drop-list
	password
	slider
	tool-bar
	set-state
	set-color

Enhanced
	chat
	edit-list
	spinner
	table
	request-char
	request-font

Removed
	question
	request-ui
	pie-chart
	symbol
	options [info no-click]
	options [arrow options]

WIP
	A disable/enable function and layout option
	Rewrite of led widget
	Rewrite of tree widget

changed from single color web like look to some W9x look, was there 
any reason?
 ... commercial reality ;)
where would I have changed the font?
 ... ctx-rebgui/effects/font
request-char somehow misbehaves here
 ... bug, noted
fonts must be handled differently in w7s

 ... I don't have access to W7 at home, but will check this Monday 
 at work
where do I set my UI options?

 Design time with ctx-rebgui/effects, /colors /behaviors and /sizes

 Adding request-ui back so you can alter these values from a GUI is 
 trivial ... what I've removed is the rebind logic that enabled you 
 to dynamically change values (i.e. you would have to re-do %rebgui.r 
 to see any UI changes take effect ... not very practical for an SDK 
 app)
they look like W9x

 ... the color scheme (with the colors/page change noted above) is 
 taken straight from W7
don't like gradiented buttons/tab
 ... based on W7 and Mac
I thought Ashley wanted to go more web way, not desktop app way

 ... I've actually gone for something halfway (simpler than OS, more 
 complex than Web)
is it using a smaller font?

 ... 12pt by default as always (maybe W7 renders it differently than 
 XP?)
everything seems much smaller
 ... bigger screen? ;)
I would welcome tour.r would fit 1280x800 notebook

 ... RC1 is about getting the basic functionality right, %tour.r and 
 %RebDOC.r will both be made to run 1024x768
used to fit
 ... they havn't been reworked yet
Windows XP with 1366 x 768 ...
 ... will be fixed with above

Henrik .. just do a google search for rebgui codeplex

Build 202 uploaded ( https://rebgui.svn.codeplex.com/svn/)
- Fixed password
- Added icon to tour.r
- Resized tour.r to fit smaller screens

- Reworked layout and display functions to remove duplicate show 
and do-events calls
- Removed do-events from tour.r and RebDOC.r


The layout/display change (apart from correcting numerous rendering 
anomolies and improving layout speed) may have caused other unforseen 
side-effects. At the very least it changes RebGUI in the following 
manner; previously you would write:

	display "A" [...]
	print "A"
	do-events

and get "A"  printed to the console. Now you write:

	display "A" [...]
	print "A"


and only get "A" printed to the console once the display has been 
closed. This now lets you write code like:

	display "A" [ ;do some stuff to set result]
	process result and display "B" or "C" based on result

This change is still experimental so let me know what you think.


Also, who actually uses tool-tips??? I've been debating whether to 
fix them so they work properly, or just remove them entirely. Thoughts?

I am just trying new RebGUI and like it a lot. There is one, at least, 
big problem with disable.

Build 203
- Better icons for alert, help, info & stop
- Removed tool-tip widget and supporting code
- Added ctx-rebgui/on-error object
- request-error: added icon
- request-password: added icon
- request-password: added cancel button
- request-value: added icon
- request-verify: added icon
- request-progress: added icon
- display: added no-wait option to fix request-progress
- Table: fixed resizing artifacts
- Table: added 'no-sort option
- Table: added 'no-resize option
- Table: added 'fixed-sort option
- Fixed layout/only (it ignored disable)
- Removed %images dir
- updated tour.r and RebDOC.r

About my previous musing...

stack overflow return

 ... This is my fault as I  put ctx-rebgui/behaviors/tabbed: [... 
 (no table in)] in my little program. Need another safe way to do 
 that.
one can only select one table at a time
 ... not tabbable table is the only way
hidden column
 ... will use 0.01
button width

 ... basically when one specify [button 100] one get old [button 103] 
 but that's ok if we know it.

More about stack overflow and tables.

When taking 'table from ctx/behaviors/tabbed it still works any extra 
tabbable widget like so

>> [table options ["A" left 1.0] data [1] table options ["B" left 
1.0] data [1] button]

but selecting from one table deselects the other. All tables selection 
was possible with previous incarnation of RebGUI. I hope somebody 
else was using this feature so it's not only me using before and 
wanting it.

I've reverted the wait [] (do-events) behaviour back to what it was 
prior to build#203 ... so the logic is:

RebGUI v1
	display
		show face
		do-events
		attach window feel
		show face
		if dialog do-events
	do-events

RebGUI v2
	display
		attach window feel
		show face
		if dialog do-events
	do-events

which means the sample code above should now be written as:

	do %rebgui.r
	display "Main" [
		button 100x50 "Sub" [
			display "Sub" [button 50x25 "Error" [1 / 0]]
		]
	]
	if error? set/any 'err try [wait []] [request-error err]


In fact, that last idiom (wrapping the main event loop around a 'try 
/ request-error) is so basic I think I'll redfine it as a self-contained 
func (redefine do-events?).

Memory footprint reduced? RebGUI tour.r always showed 11something, 
now it starts over 12MB usage ....

http://www.dobeash.com/RebGUI/user-guide.html#section-4.1.4... note 
the action-on-* behaviors

Build 211
- Moved base objects from ctx-rebgui to system/view
- Removed all dependencies on View/VID mezz code
- Rewrote and added show-popup & hide-popup functions
- Removed style widget
- Inlined popup logic
- Converted internal images from base 16 to base 64
- Cursor keys now work in choose (drop-list, edit-list & menu)
- pad option in layout enhanced to accept pair! (pixels)
- Added tooltips to tool-bar
- Added request-edit
- Improved resize logic
- Fixed request-dir (resize bug)
- Fixed slider (resize bugs)

Ashley, I am using build 210 (I'll update shortly), but wow, I love 
this little library. No compromises, fault intolerant, and best of 
all, ZERO learning curve.


Would it be an idea to add some systray functions to RebGUI for Windows?

Maarten: Thanks. The Systray.r file Steeve linked to above is pretty 
self-contained (and explanetory), so I don't see much value in duplicating 
it in RebGUI (apart from the fact it is Windows specific, which is 
why I've left native requestors out as well).


Graham: The only SDK file that RebGUI now requires is gfx-colors.r 
(plus prot.r if you need protocol support). load-stock is one of 
the many View funcs loaded when you include view.r.

Here's my encap code

probe in system/view/vid 'image-stock  ; this works

#include %/c/rebgui10/rebgui.r ; 9/rebgui/rebgui.r

probe in system/view/vid 'image-stock ; this fails now

and here's the output 

image-stock
** Script Error: in expected object argument of type: object port
** Near: probe in system/view/vid 'image-stock

the error occurs on the second probe

above is a result of trying to mix vid and rebgui in the same script 
.. can no longer do this.

hence no further ability to mix VID with RebGUI. I am not sure Ashley 
did not oversimplified it :-) Because - there was a promise of "much 
lower" memory requirements, but the opposite is true, even if RebGUI 
gets optimised. Older version consumed some 11600 memory, new versions 
do consume over 12megs ...

I never mixed them like this .. just used different screens with 
vid and others with rebgui

re append-widget; close to ditto Graham, but I now use append-widget 
when I need to link RebGUI fields to persistent RebDB store.  Well 
it's a general purpose data-field widget that can stash code in the 
data (RebGUI keyword) attribute of the gui widget.   See http://www.rebol.org/view-script.r?script=rebdbgui.r
for a (very ineffficient) sample I posted way back when when someone 
asked for a way of getting persistent RebGUI fields.   Used to be 
the same for an overlay panel, but Ashley put in the 'no-tabs option 
for tab-panel and my copy was sent to a shallow grave as the hack 
it was deserved.

Wow, RebGUI really picked up speed again. I'm still not biting the 
bullet to backport my fork of RebGUI.

But it looks like the current version of RebGUI is highly matured.

1. Put your new widget in the widgets directory
2. Add it to %rebgui-widgets.r as an #include
3. Run %create-distribution.r

I only get the 'load-stock error using the latest rebgui.r

 & "rebgui.r is doing something funny to VID" ... yes, it sure is. 
 The guilty lines of code are in %ctx-rebgui.r:

	view*: system/view
	screen*: view*/screen-face

 screen*/color: screen*/edge: screen*/font: screen*/para: screen*/feel: 
 none
	view*/VID:
	view*/popface-feel:
	view*/popface-feel-nobtn:
	view*/popface-feel-away:
	view*/popface-feel-away-nobtn:
	view*/popface-feel-win:
	view*/popface-feel-win-nobtn:
	view*/popface-feel-win-away:
	view*/popface-feel-win-away-nobtn: none


There's a long explanation for this, but the short explanation is 
that previously RebGUI could co-exist with VID (and I was careful 
not to redefine existing VID words/functions), this made sense so 
long as RebGUI shared some of the same basic View/VID mezz code (in 
particular the popface-feel-* functions, hide-popup and show-popup). 
Once RebGUI v2 went down the path of using its own, simpler, popface 
code then the need to maintain "Chinese walls" between VID and RebGUI 
lessened ... and the option to reuse/redefine View's basic objects 
(instead of creating parallel RebGUI objects) made sense. Once I'd 
made the decision to cut with VID support it made other decisions 
like redefining standard VID requestors (alert, confirm, etc) a lot 
easier. RebGUI can now be developed without worrying about VID compatibility 
or "breaking" VID.

Any suggestions for a replacement for the VID toggle?

 ... isn't the toggle just a drop-list less the drop component? It's 
 a fairly trivial widget to add to RebGUI, but it's not a widget I've 
 seen in any Windows or Mac apps. What do folks think about this widget 
 from a UI POV?

Shame about breaking vid compatibility .. there were somethings I 
could not do in rebgui so I would switch to using ViD in the same 
application.

For instance I use VID to do a print preview ... using a draw dialect. 
 Never tried it with rebgui

hence no further ability to mix VID with RebGUI
 ... correct.
promise of 

much lower" memory requirements, but the opposite is true" ... not 
quite. A lot has been added, in particular 4 inline images, without 
noticeably increasing memory. Also remember that many of the improvements 
(reduced dependency on View/VID mezz code) will only be apparent 
when using RebGUI with enface/rebface (tour.r uses 13,817Kb under 
rebview here, and 11,223Kb under rebface). Lastly, reduced memory 
usage is not apparent with tour.r as it doesn't reuse a lot of the 
same widgets (i.e. tour.r is a good reflection of "base" memory usage 
not runtime memory usage). If I find the time I'll knock up an example 
that demonstrate runtime memory differences.

looks like the current version of RebGUI is highly matured

 ... thanks, I hope to have an "official" release with updated docs 
 by the end of September.

there were somethings I could not do in rebgui so I would switch 
to using ViD in the same application

 ... there shouldn't be any. Both VID are RebGUI are just "face factories" 
 ... feed them a spec and they produce a face object. All other functionality 
 is neither VID nor RebGUI specific. I get a lot of emails asking 
 "how do I do x in RebGUI", but 99% of them are really "how do I do 
 x in REBOL", or, "how do I use the SDK to do x" type questions.

I use VID to do a print preview ... using a draw dialect

 ...RebGUI's use of the effect facet (and hence draw) is no different 
 to VID's. Also note that 'draw is available as a native from the 
 console (i.e. you don't event need VID or RebGUI to use it).

The slow-down is from the query side not the RebGUI/table side. Table 
uses an iterator function so whether the table has 10 rows or 1,000,000 
it should be the same speed ... fetching 10 rows or 1,000,000 across 
a network is another story.

Going to try the older rebgui....

** Access Error: Cannot open /C/Rebol/rebgui/icons/16x16/actions/document-new.png
** Where: load-icon
** Near: icon: load file

Yes, I probably need to inline them (in %rebgui-images.r).

That rebgui was just one build earlier ...

My main screen was ViD based as it used a toggle widget .. and then 
the rest was rebgui

And when I tried to port it to the latest build .. then I discovered 
vid/rebgui were no longer bed mates

I made small CMS using Rebgui, so sometime i lack this feature :-)