AltME groups: search

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

feel: make object! [
		redraw: detect: over: none
		engage: func [face act event /local txt] [
			probe act
			
		]; fin engage
	]


then i create the distrubution then i run my "demo" app in the widget 
area-tc (custom) I see time and mouse related events but i never 
see keyboard related event

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

I'm open to suggestions ... and if someone could setup an account 
and give me a 101 intro on how to use/access it I'll upload the latest 
source there and repoint my site links to it. Thanks.

assemblia (the track i use for viva rebol and area-tc is easy to 
register but then the url are quite the pain

Do you need access to geekisp.com ?  I got an email from Jaime yesterday 
and could ask him ...

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

Any subversion experts out there?  I tried to relocate my copy to 
the new site, but get a UUID mismatch.  The new repository  UUID 
doesn't match the existing one on my local copy, and presumably gets 
created when I created the new projecct.

Ok, I hacked it this way ... I created a new directory and checked 
out from the new repository.  Then I copied all the files from my 
local copy to the new directory but deleted all the svn directories. 
 I then committed all these files .. and it says it created a 116 
build ... I think it's supposed to be 118 :(

I then published the project http://rebgui.codeplex.com/

Ashley, this is what I think you should do ..  after signing up as 
a contributor, checkout the repository I uploaded.  Then copy all 
your source files over the ones in this new checkout, and then commit. 
 That should give us the latest.

codeplex has a source code browser and issue tracker.

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.

And if you sql thingy returns a block .. you don't need the extra 
[ ]

Graham and Izkata, thanks for the help.  But I must be misunderstanding 
something, as it is still not working. Here is what I have:

CONNECT/create/flat %cl.db

if error? err: try [
	SQL "select * from projects"
][
	er: disarm err
	if find er/arg1 "no such table" [

  SQL "create table projects (Priority, ProjectName, ExchangeRate, 
  Objectives, Deliverables)"
	]
]

do show-cc: make function! [] [
	display "CRITICAL LINKS Version 1.0.0" compose/only/deep [
		;image %chain.jpg
		return

  group-box "Critical Chain and Theory of Constraints principles" #W 
  data [

   text "1. REMEMBER YOUR PURPOSE" font [color: blue size: 26 shadow: 
   1x1]
			return
			;bar
			;return

   text "2. Free Up Your Major Constraint" font [color: red size: 20 
   shadow: none]
			return

   text "3, Focus on one project at a time---don't multi-task." font 
   [color: black size: 12 shadow: none]
		]
		at 103x14
		image %critical-chain.jpg 30x6
		at 133x2
		group-box "Redeem the Time" #W data [
			after 2
			label "   System Clock Time:" my-time:    text 28x7 "0:00:00"
			return
			bar
			return
			label "Average session time:" my-session: text 28x7 "0:00:00" 
		]
		return


  ;******************************************************************
		tab-panel #HWLV data [

                           ;******************************************************************
			"Projects" [
				label "Project Name:" ProjectName: field  141x5 

    label "Priority:" Priority: drop-list 30 #W "1" data ["1" "2" "3" 
    "4" "5" "6" "7" "8" "9" "10"] 10x5
				return
				label "Objectives:" 
				pad 131
				label "Exchange Rate" ExchangeRate: field 20x5
				return
				Objectives: area 200x10 
				return
				label "Deliverables:" 
				return
				Deliverables: area 200x10
				return
				label "Current Projects:"
				return

    current-projects: table (tab-size + 80x35) #HWLV options ["Priority" 
    right .03 "ProjectName" left .2 "ExchangeRate" left .2 "Objectives" 
    left .3 "Deliverables" left .1] data [(SQL "select * from projects")]
				return

                                                     button "Save" [

                     SQL reduce ["insert into projects values (?,?,?,?,?)" Priority/text 
                     ProjectName/text ExchangeRate/text Objectives/text Deliverables/text]
				    current-projects/redraw
			              ]
                                                      pad 20

                                                      radio-group 60x5 data [1 "Add" "Edit"]
				pad 20
				button "Quit" [quit]
                                         ]

Graham, thanks. That fixed it.  Strange. I took those braces off 
right after you told me to, and it didn't work.  Well, I had been 
up all night working on this. So maybe I just did it in my mind. 
 : >)   Thanks again.

You look at the error message .... and fix it.

display "" [
	text "Enter some text and then enter" return
	field 
	on-focus [ clear-text face true ]
	on-click [ print face/text ]
]

do-events

when you enter text and enter, the text is cleared ....

it's to be like the search fields you see on web pages .. click on 
it .. and the existing text disappears allowing you to enter your 
search term.

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

Well, in the meantime I have wrapped the into-widget with an error 
try and return none if there is an error.

Basically a table with focus, and the only widget inside a panel 
will cause a stack overflow as it tries to tab out looking for the 
next widget that can accept focus.

Since we no longer have access to the geekisp trac and issues database 
... would all of those who remember any existing issues please enter 
them into the new issue tracker.
http://rebgui.codeplex.com/WorkItem/List.aspx

And Graham, this statement is not TO YOU, but rather to anyone here 
would like to "help"

it is paid service? how much does it cost? Qtask offer is fair of 
course, but if guys are used to trac service, and it is not expensive, 
maybe we could sponsor it ...

I don't mind where the source resides, as long as:

	a) It doesn't cost me anything
	b) It's accessable via standard SVN clients
	c) It's simple


Jamie very kindly sponsored the first 3 years of hosting on geekisp, 
and when that ceased Graham created a project on CodePlex (which 
I assume offers free hosting?). That seems to be working OK so far, 
but I'm happy to move across to Qtask if it meets above three source 
hosting requirements.

Uploaded build 120 which addresses the stack-overflow issue (and 
as a by-product drastically cuts the number of calls to next-field/back-field 
when tabbing) ... please test.


I'll also echo Graham's call for issue tracker submissions, as I'm 
now prioritzing fixes based on what's in there.

Pekr, it cost $5 a month on geekisp.  But codeplex is better .. as 
it is free, and it is much easier for anyone to join, and add comments. 
 However i miss the diff that geekisp had ... unless it is on codeplex 
as well somewhere.

I had a trac also on geekisp, but it was plagued by trac spam, and 
the site owner wasn't willing at that time to upgrade the trac to 
block spam.  So the only way to stop spam was to block all comments 
.. so I abandoned it.

there are also websites that offer free hosting (with issue tracking 
and other typical stuff ) of OS projects for distributed vcs-s Bazaar, 
Mecurial and Git ... I stopped using svn and went to bazaar and I 
like it  ... there is comparison of various such sites here http://en.wikipedia.org/wiki/Comparison_of_free_software_hosting_facilities

Uploaded build 121 with a completely rewritten tabbing system. Tabbing 
into/out of tables and text-lists is now supported (you need to copy 
new behavior/tabbed and behavior/cyclic values across into %ui.dat). 
Will add remaining widgets next build plus ability to exit a cyclic 
widget (e.g. press a key to exit a group-box). What keystroke/combo 
do folks want to map the later functionality to?

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?

In build 122, in tour.r  and in List/Tree the right hand tree is 
now missing.

In List/Table, if you click on the table,  you can tab in and out 
now if the Look & Feel/Behaviors/Tabbing .. if you add table and 
text-list

Uploaded build 123 with tab-thru implemented as described above (except 
that tab-panel doesn't cycle each tab). Also fixed initial text case 
(stack overflow) and a long-standing text-list bug (no cursor control 
when select-row used).

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

Ashley I think we discussed this before .. is there a way to have 
a hidden id so we have both a display element in the tree, and a 
hidden id.

Yes and yes ... but the tree widget really needs to be totally rewritten 
to support that.


If I have tree data like this [ A [  B B B ] ] ...how can I tell 
which of the B's that I am clicking on?

 Isn't this the same issue with drop-lists, edit-lists, text-lists, 
 tables, radio-groups and check-groups? In what case does it make 
 sense to have user options (text strings) that appear identical but 
 have different "real" ID's behind the scenes?

HTML selects handle this by having different display and value attributes.

But if you're asking them to select an option and the option display 
text is the same how do they know which to select? And if it doesn't 
matter then why the need to display multiple options with the same 
display text in the first place?

The tree data could be in the form [ A [ B [p] B [q r] B [s t u] 
]

and so the user could differentiate between the different B's by 
examining their contents.

Here's a movie to show what the effect is.  Basically I am opening 
up an XML file, turning it into a REBOL object and browsing it.
http://screencast.com/t/5K3dkL3Y7

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

What?? removed symbol, and question ?? :(

and options [ info ] is now gone too??

Isn't this a personal thing "Get rid of the cruft (removal of little-used 
widgets and options)" ?

There seems something to be wrong in the newest version with sizing 
and moving of the main window.

Just move the mouse to the upper border, wait until the mouse cursor 
has changed and then click!
Or try to move the window with cursor keys.

removed symbol

 ... not cross-platform (depends on a specific symbol font) ... icon 
 is a better approach IMHO anyway
and question
 ... use confirm instead
options [ info ] is now gone too

 ... yep, soon to be replaced by a global disable/enable system (unlike 
 the widget-specific info implementation
Isn't this a personal thing 

 ... less is more (and easier to debug/fix and maintain). pie-chart 
 (as an example) was a good widget, but anyone wanting to use it would 
 probably want a full range of graphing widgets, not just a single 
 representative example. Having said that, yell if I've removed something 
 vital and I'll add it back (or provide a functional alternative).

symbol ... use it beside a field to indicate a lookup widget is available
 ... use an icon or {button -1 "..."} instead (or an arrow)
sqlab ... what OS?
password field is now showing the text as text
 ... noted

I clicked on request-char in rebdoc.r and got this


** Script Error: request-progress expected steps argument of type: 
integer
** Where: get-fonts
** Near: request-progress/title (length? s) / 3 [
    foreach [fn reg style] s [
        fn: trim first parse/all fn "("
       ...
>>

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

I used it, to set boxy design instead of rounded, and also to change 
some colors. I for one like scroller/dragger look, but don't like 
gradiented buttons/tabs ... they look like W9x, which is imo a bit 
of UI regression. I thought Ashley wanted to go more web way, not 
desktop app way (from the design pov)  ...

Windows XP with 1366 x 768


After start of tour.r the upper border is outside the screen and 
the status line not visible.

After moving the window down with the cursor keys, the status line 
gets visible.

After moving  the cursor to the upper edge with every click there 
the main windows moves down a step.

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

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.

>> display "" [panel data [button] disable panel data [button] disable] 
  ;;== it only disables second panel and first can't be disabled 
even later in code

Sounds like display is now always modal?

 ... I thought modal is when only the active dialog/popup can accept 
 user input? That's still the case, try the follwing:

	display "Test" [
		area
		button "A" [display "A" [button]]
		button "B" [alert "B"]
	]


Press "A" and type some text into the area, then close "A" and try 
the same thing with "B".

Another discovery. One can only select one table at a time. This 
is more serious problem, me thinks. The previous one seems to work 
later, but directtly from display.
And it seems tha I can send more than 1 line at the time now.

It must be my poor accent. Not all panels or widgets inside of them 
can be disabled in layout. Later, when program is run seems to be 
no problem.

There is another little problem with tables. When last column is 
right justified with no scroller there is small gap between text 
and edge of table. when scoller kicks in
there is no gap at all.

Finally let me have little wish. Would it be possible for table to 
have 'no-sort option? Would it be usefull to anybody else?

I'd rather have fixed sort so you can choose which column to sort 
on, and not let it change .. as an option.  similar I guess to your 
wish?

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

This should address the table and disable issues raised above. WRT 
other issues:

stack overflow return
 ... could not duplicate this.
One can only select one table at a time

 ... select = focus, and yes, as focus shifts so to does the "selected" 
 row
And it seems tha I can send more than 1 line at the time now

 ... not sure I understand what the issue is here.Are we saying 'multi 
 is always on now?
hidden column

 ...I plan to properly support hidden columns ... if column width 
 is zero the face iterator will not create a face and it will not 
 otherwise be treated as a "column"
button widths

 ... the width sizing algorithm changed for button, label, heading, 
 etc (basically anything that appears on a single line)

 - previously you had to use -1 (or larger widths) to accomodate larger 
 text as the width was fixed

 - now it is fixed to the greater of it's specified width and it's 
 natural text width; and -1 sizes to the maximum of text width and 
 a line

 - there is no checking for button height (as it is assumed you would 
 either leave it at default 5 or have it larger

- title-group and image RebDoc section depend upon images from /images 
directory, which are now deleted hence not available anymore ....

- scrollbars are behing a little weirdly. When you press mouse button 
down, and you go away from scrollbar (or not), the content starts 
scrolling even before the scroller is visually moved. Nicely visible 
with RebDoc for e.g.

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 hope I nailed down my table problem now.

It seems that one can select from all text-lists on display, but 
only one table is selected from - selecting next one deselects previous 
one. Tabbded on not is not the problem.


Drop-list and edit-list cannot be closed by clicking elswhere but 
this is still to be fixed, isn'i it.

title-group and image RebDoc section depend upon image ...
 Fixed in next build
scrollbars are behing a little weirdly
 ... noted

basically when one specify [button 100] one get old [button 103] 
but that's ok if we know it
 ... ah, I understand the issue now. Fixed in next build.

I hope somebody else was using this feature so it's not only me using 
before and wanting it.

 ... don't worry, I think the issue is that table needs to differentiate 
 between a selected row and a row that has focus. This was not an 
 issue in previous versions as table was not a tabbable widget. Will 
 be fixed in a future build.

Drop-list and edit-list cannot be closed by clicking elswhere but 
this is still to be fixed, isn'i it.
 ... on the list to fix
Another little observation.

 ... that's an interesting bug and I have no idea at this stage why 
 the 2nd case doesn't work. Needs further investigation.


Good work marek (and others) ... we're slowly but surely ironing 
out the issues.

I still insist, that LED design is absolutly terrible - the circle 
is way too big and it really imo ruins the feel of the design :-)

With gradients, I have a bit difficulcy to imediatelly distinguis, 
what is the active part of the scroller, and what is the background. 
Couldn't the background be somehow "more relaxed"?

Other than that (and pop-up bugs), it really looks as a polished 
system ...

LED design is absolutly terrible
 ... please provide a link/image of a better design

Why horizontal scroller shows different dragger symbol than vertical 
one?

 ... vertical uses "=", horizontal wasa "||" but those characters 
 don't center to well

what is the active part of the scroller, and what is the background
 ... you mean the dragger is hard to distinguish from the gutter?
Other than that (and pop-up bugs)
 ... table, text-list and tree still need a lot of work
zero-divide error with  tour.r
 ... thanks, added to the list of bugs to fix

pop-ups ... e.g. menu allowing you to enter all three menus at once, 
looks a bit weird, but it is enough for me, that the rework is planned 
:-) The only thing I want for menu and lists, is, being able to close 
them clicking elsewhere ...

LED design - I don't mind how LED is represented, I do mind its proportional 
size. IMO LED (and maybe even radio) circle is way too big.

Looks nicer and polished. The only note to UI from my side - button 
gradient - makes white text badly readable ... but other than that 
it looks good. Nice addition with row-coloring for table and text-list 
- such small detail and it looks much more pleasant ...

Yeah, my major insight over the last year concerning UI design is 
that it's not a question of "great graphics" but simple attention 
to numerous small details ... get the details right and the whole 
lot comes together.

Maybe tree widget could benefit from row coloring too? Would look 
consistent with table and text-list.

nothing pops up when clicking the button, why?

 ... the display function exits if it hits a duplicate window title 
 (before calling layout) ... this means you don't have to worry about 
 the user hitting a button that calls a display multiple times and 
 getting multiple (near identical) windows popping up!

tree widget could benefit from row coloring too?

 ... it will, once I've rewritten it to use the same face-iterator 
 func that table and text-list use (which means it'll get all the 
 extra goodies like auto-slider support as well!

I remember that a previous tour had the tree inside a scroll panel 
and as you expanded the tree, sliders appeared in the scrollpanel. 
 Sometimes you can now display all elements of a tree without that 
functionality.

Note the reworked tree widget only has one option [only], and currently 
defaults to expanded mode with no leading graphics. It accepts input 
in either nested block or file/path notation. Selected items are 
now fully qualified by default. Due to it's use of face-iterator, 
it no longer has practical data limits (previous version created 
a face for each item).

Now I do seem to understand, what still feels kind of wrong with 
scroller:


- normally, scroller has arrows. One arrow press scrolls data upon 
some number of items

- in regards to above, when you click anywhere else on the scroller, 
it should not jump directly under the mouse pointer, but only once 
again it should move by defined amount of data


... and it is not the case with our scroller. I should note that 
the "wrong feel" is just of a cosmetic nature, nothing annoying ...

Graham and Ashley - thanks for window title hint, so simple...


The other big problem I'm still having is crash when tabbing. It 
worked with 204 and  before. I doesn't work with 205 - 208 .

>>display "" [panel data [field]]   ;; click on field and press <TAB> 
button - bingo!?

Group-box and scroll-panel seem to have the same problem.

I'm sorry, I copied wrong code.

>>display "" [panel #H data [field #H]] do-events ;; panel doesn't 
resize at all

>>display "" [group-box #W "" data [field #W]] do-events  ;; group-box 
resizes and looks like panel, why both?

Build 209
- Fixed #LV span options for
	- button
	- group-box
	- panel
	- pill
- Fixed tab-panel tabbing
- Removed redundant scroll-panel from request-dir
- Reworked on-resize handling for most widgets
- Removed #O span option (made redundant by on-resize)
- Renamed span-size to span-init
- Improved popup handling (drop-list, menu, etc)


Note that this build has [temporarily] broken dialog modality (you 
can click outside of a dialog) and tab-panel action blocks.

The over effect is mild too, and without Tooltip, I would not probably 
use toolbar in my app ...

Build 210
- Fixed dialog modality bug
- Fixed tab-panel actions
- Enhanced radio-group (auto-size label widths)

- Added back #R and #O span directives to handle imbedded reverse 
widgets

- Moved window-feel out of display func and share across all displays

The #R and #O directives handle this case:

display "Test" [
	panel #L data [
		field #L
		reverse
		button #R "Cancel"
		button #O "OK"
	]
	return
	bar 75
]

Pekr, above issues noted. Tooltips are being added back to toolbar 
[only] as they were in the early builds. I'm also looking at ways 
of reducing memory usage (sharing more objects in layout and pre-building 
certain common font usage cases (e.g. align: 'center)).

You're on the right track. I'm trying to get an image in there without 
creating another face. The 3 places you can have an image in an existing 
face are: image, effect and edge. The first image I want to get in 
there is a folder icon so request-dir looks a bit better! ;)

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?

Not sure it was Gabriele - Cyphre did something upon contract for 
me, and I released it 2 years ago? :-) IIRC Cheyenne uses it too 
...

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.

RebDOC.r fixed and uploaded.

Ashley, I only get the 'load-stock error using the latest rebgui.r, 
and not on earlier versions.

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.

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.

just that I was able to find 1px difference on our company website 
- 14 vs 15 pixel in one paragraph

 NP, I've actually been using DigitalColor Meter on my Mac to find 
 both pixel and RGB discrepancies ... so when you see something like 
 "pad 0x-1" in request-edit you now know its because I wanted to collapse 
 two 1 pixel edge borders into a single shared 1 pixel border. As 
 I mentioned elsewhere, its attention to trivial aesthetic details 
 like this that make the overall UI "look good".

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.