World: r3wp

I hope mine will be able to do that when I get something more meaningful 
done. selected columns for viewing is already now something you don't 
need to worry about in my list, but I still have much work to do...

Robert, I'm waiting for a few things in the REBOL world to stabilize 
a bit before proceeding. Specifically:

1) The new REBOL/View system documentation
2) The new OS X version of REBOL/View
3) New SDK builds
4) Couple of AGG fixes

The two big design issues I'm grappling with at the moment are:


1) Look & feel, especially in light of the availability of View on 
OS X

2) Whether to revert to View 1.2 compatibility (and not use AGG) 
given the lack of a 1.3 SDK

and although it is the most complete style we saw yet 

 when I see comments like this I doesn't  want to make efforts ... 
 Have you tryed my listview widget ?

see http://www.rebolfrance.info/articles/regui-cooking-widgs

2) IMO RT can provide them quite fast. So we just need to bug Carl 
about it. Shouldn't be a show-stopper.

buing Carl should work better, as he then can bui other people. Throwing 
more bugs at him would slow things down?! But to do that, someone 
would have to buy us, so we can buy, hmmm...

simply said - and as most are probably scared to say it loudly, so 
here is "Bad" pekr once again :-) Current marketing model of RT still 
does not seem to work. Although community involvement was big help, 
it still does not seem to solve overal situation - publicly visible 
roadmap, schedules, case studies on website, etc.

I thought VitalNeeds announcement can change things, but I am not 
sure ... still waiting how they will help to make REBOL more publicly 
visible ...

OTOH i had a really interesting look at my floor, suddenly sitting 
there, after reading there is a running OS/X, in such a short time 
after 1.3 and Carl saying "now we really do that". OK, he said that 
the n-th time, but this time he did, in short time. so..

I know ... I just received email from old time reboller who's name 
I will not disclose, but he is right - why we are still pretending 
we have some secret weapon? The rest of the world really does not 
care:


  I don't want to know anything that the public won't be told. Why 
  do I
need a special handshake just to find out what REBOL intends 
  to do
someday? I just want to be a satisfied customer, I have no 
  desire to
be part of a secret club. Aren't plans and roadmaps what 
  you share
with customers? I have no need for secret organizations, 
  closed door
policies, or special preferential relationships.

Good 
  ideas need to withstand the harsh light of day, which is a
by-product 
  of openness and transparency. MS and other companies do not
care 
  one bit if REBOL is open-source-- they are so far beyond caring
about 
  that. RT has no first-mover advantage or special secret that
makes 
  REBOL a dangerous disruptive technology, and if it did,
open-source 
  or not, they could recreate it within a year (maybe not
compact, 
  but no one will care). Remember MS employs some of the top
scientists 
  from functional programming in their labs.

ah, wrong group for all the discussion, sorry ... just last note 
here - I still see urgent need for RT to change their public image, 
towards developers, customers, investors ... better website is needed.

... all good things here - as working cooperation of dev community 
with RT should be used as marketing advantage and should be described 
on web-site as a good, working model .... that should happen on REBOL.com 
- but creating of new site needs real strategy, especially marketing 
wise ...

What is the latest RebGui version that can be used with Rebol/View 
< 1.3  ?

022

but  what enoys me is that ppl here are too pending on the will and 
effort of RT and not ready to participate actively apporting code 
to this project or others

Thanks..

0.2.4 actually. ;)

** Script Error: white has no value
** Where: context
** Near: edit: white
over: gold
menu:
** Press enter to quit...

Error message when running tour.r with the new encap.

I would have liked "** Script Error: White is no color" more ;-)

Occurring here ...

	colors: make object! [
		window:		236.233.216		; used by display.r
		widget:		244.243.238
;		widget:		248.248.248
		edge:		127.157.185
		edit:		white			; area, field, password, etc
		over:		gold			; active button, tab, splitter, etc
		menu:		49.106.197		; menu, popup highlight
		btn-up:		200.214.251
		btn-down:	216.232.255
		btn-text:	77.97.133
	]

which is odd because 

#include %gfx-colors.r

occurs before this

Ooops, change 'do %rebgui.r to #include %rebgui.r, and comment out 
#include %gfx-funcs.r

next error .. got the splash screen now, and then this

** Script Error: Cannot use path on word! value
** Where: init
** Near: effect/4: size - image/size
** Press enter to quit...

This is fixed by adding a reduce to the button data (rebgui-widgets.r), 
as in

		data:	reduce [
			#[image! 7x14 64#{
				...

working .. had to also include mezz-xml.r

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


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


Minor synchronization release to align with latest REBOL/View 1.3.1 
builds and documentation. I've also removed all SVG related code 
until such time as AGG fixes allow SVG Renderer project to complete.

** Script Error: focus expected face argument of type: object
** Where: switch
** Near: focus f
if f/type =
** Press enter to quit...

Place the text cursor in the edit-list widget, and then press tab.

This is for tour.r

If there are multiple fields, and one enters text in one field that 
is larger than the visible field, and then tabs to another field, 
the text in all the other fields shifts left (as though there is 
some global text pointer).

shared para object.

shared para object
 is practical nonsense ;-)

Rebol uses inverse logic just to save resources ...

inverse logic

 triggered a thought: what about a 'share-keyword and clone by default? 
 for performance [  text share[para] ]

If para was converted to a block, then make would copy it for us 
automatically.

The trick of para is to share, to save space. else we could just 
do it in 'layout.

Actually, yes, the default face has a para object, even though a 
lot of styles don't necessarily use para features (or even text at 
all), so sharing is worthy.

Well, I consider it a bug if you alter the text in one field, and 
experience unwanted side effects in other fields.

So, when you create a text field, it needs it's own paragraph object.

I agree that this is an undesired feature, I also agree that sharing 
the para object is generally a good idea. One way around this would 
be to change the focus function such that the shared para object 
is "reset" upon change of focus.

Seems a reasonable thing to do.

display "" [ button "Print" ]


shows a button with text "Imprimer" , and one with "Save" shows "Enregistrer" 
...

Isn't localization wonderful? ;)  [just edit / delete %locale.dat 
to "fix"]

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


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

Highlights include:

	- request-dir requestor updated
	- alert and question requestors added

 - Tab focus expanded to include edit-list handling (see %focus-demo.r 
 for details)
	- Button image now resizes correctly

 - text-list widget totally rewritten to use [newly documented] View 
 1.3.1 iterated faces
	- text-list now supports Ctrl+click, Shift+click, Ctrl+A

 - text-list scrollbar now reacts to current display state (eg. disappears 
 if not required, alters dragger ratio as rows are added, etc) 
	- check and radio widget aesthetics improved

 - added options support to layout function and text-list and check 
 widgets

 - changed base-size from 4x5pixels to 5x4 pixels (better granularity)
	- reworked all widget sizes to account for above
	- fixed scaling problems with many widgets
	- updated focus-demo.r

 - greatly enhanced and expanded %tour.r to demonstrate more variations 
 and usage cases
	- added "live" unit-size and font-size drop-lists to %tour.r
	- numerous other minor bug fixes and coding improvements

In the works


 - table widget being rewritten along the same lines as the new improved 
 text-list widget
	- aiming for a 0.4.0 beta release prior to DevCon2005

Great work, Ashley!

I like it, nice work.

The shared para object problem still exists, and I notice it now 
screws up the text in the tab panels - so that they disappear.

Unlike 1.3 VID alerts, you can't use the space bar to close the alert.

** Script Error: Cannot use path on none! value
** Where: edit-text

** Near: if all [tmp/x < 0 tmp2/x < 0] [face/para/scroll/x: tmp2/x 
- tmp/x]
tmp3:
** Press enter to quit...

on tabbing out of an edit box.

With the text in an edit list highlited, click on the drop down arrow, 
click on a new item, then tab .. and the above occurs.

Thanks, these will be fixed in the next build. I'm assuming that 
all other issues are resolved as of this build, so if anyone has 
others (even if previously raised) that have not been addressed then 
now is the time to raise (or re-raise) them. Please exclude issues 
relating to the following unfinished widgets:

	- table
	- grid
	- svg-toolbar
	- icon (SVG-based)
	- auto-fill
	- spinner
	- menu