World: r3wp

>> system/version
== 1.3.50.3.1
>> yello
** Script Error: yello has no value
** Near: yello

>> system/version
== 1.3.61.3.1
>> yello
** Script Error: yello has no value
** Near: yello
>>

View 1.3.50 is actually older than 1.3.2

hmm.. which is latest then?

I've renamed mine thus:
rebview1.3.050.3.1.exe
rebview1.3.061.3.1.exe
rebview1.3.2.3.1.exe
rebview2.7.000.3.1.exe
etc. so that they sort correctly in the file list.

(I knew when they decided to version those betas that way that it 
would cause confusion...)

>> system/version
== 2.7.5.3.1
>> yello
== 255.240.120
>>

went by date

Yep, that's the latest.

thanks

That's what I've been testing with. It has a problem with some keys 
like page-up/down. Apparently Maxim patched those keys. I suppose 
he added an event-func.
There's a new version coming soon which should fix that.

the desktop needs a make-over

(The View desktop , that is.. )

also known as the "viewtop".

2.6.3 is the latest stable release with a matching SDK version.

2.7.5 also has a matching SDK version, but is slightly less stable 
(works for me).

Install is nonfunctional in 2.7.5, but that wouldn't affect encapped 
apps.

Install wasn't completely functional in 1.3.2 either, or any prior 
version, as I have explained at length before :(

Hmm.. I've gone over all the GUIs and I've come to an observation 
(not a criticism)... 
There's no graphic designers here.

That's a known fact I think :)

After looking at all of the various UI for Rebol that's currently 
available, and although they are all great in their own right, I 
can't help but think there's something missing.  I've found the rebol 
mashups I've done using Javascript, HTML, CSS and Flash.. to be so 
much more flexible, and of a higher quality... perhaps not in things 
like speed etc., but when it comes to eye-candy, View, and all of 
it's GUI libs come in third at best.


If you're running windows.. take a look at RASH.. a simple blue button 
that floats on top of all your other windows.. click it, and a panel 
pops up.. 

It uses Flash as the UI.. and it's really quite easy to tie Rebol 
into Flash..  and you can do it with core. Why there isn't more Flash 
/ Rebol mashups is weird

Sorry, probably the wrong group for this rant

If you happen to have some X10 stuff lying around, you can control 
your appliances with RASH too.. 

Add this to codes.txt .. change the path to your x10comm.exe 


q [fp "kettle on" 20][call "c:\x10\x10comm.exe a1 on" speakout "Kettle 
has been activated" closed]

q [fp "kettle off" 20][call "c:\x10\x10comm.exe a1 off"  speakout 
"Kettle disengaged" closed]


text-to-speech while  flipping on the kettle from Rebol.. serious 
cool factor.

oops.. misposted

when it comes to eye-candy, View, and all of it's GUI libs come in 
third at best

 ... I'd exclude View from that statement. With AGG support built-in 
 it enables you to be as creative as you want; the fact that no-one 
 has built a nice Konfabulator-like dialect that uses View to its 
 full potential is another issue.

Agreed.

Ashley have you been able to reproduce the boundary issues with the 
area widget .. basically when trying to type into the widget at the 
bottom, and either have the caret fold back to the start of the same 
line, back into the word you're typing.

Since I've never seen this in the area face I presume it's fixable.

able to reproduce the boundary issues

 No, and I use area everywhere in my apps. Never come across this 
 problem before. What's the sequence of actions? i.e. it's gotta be 
 more complex than, "just type until it happens". I suspect you've 
 hit a nasty interplay between arrow/slider scrolling and caret positioning. 
 Fixable if I know how to reproduce it.

 the fact that Konfabulator-like dialect that uses View to its full 
 potential is another issue.


did you look at (short on time, cause everyone else was late ;-) 
 elixir devcon session ?


that just what it is...  100% AGG gui engine... with full AGG element 
based interaction and per stroke feel.

Max .. none of us saw the screen ... the broadcast videos appeared 
to concentrate on the rear of things!

AGG + Autofocus = Extra aliasing

AGG without a dialect? Might as well code in assembly, or openGL

Ashley, I can't reliably reproduce this boundary issue.  How about 
putting in a check for when the caret moves to the next line after 
<enter>, to ensure it is not on the same line, and then writing this 
to the rebgui.log ?

Is there a way to make a horizontal scroll bar on a table?  Or maybe 
to make a text-list or area have the horizontal scroll bar?  It may 
be to use the slider widget, but documentation is a bit scarce.

Also, how do I set effects/radius: 0 for group-boxes?

graham... darn... should be putting time on elixir and liquid next 
week *I think*  but with all the things going on in my life right 
now I can't be sure.

TimW - there is very robust grid style, done by Cyphre, under contract. 
It is just there were some API changes, so the grid was never further 
adapted ....

effects/radius: 0 for group-boxes?
 ... effects/radius is global. It is currently used by:

	group-box
	panel
	tab-panel
	tooltip

and can be set as follows:

	ctx-rebgui/effects/radius: 0

Is there a way to make a horizontal scroll bar on a table?

 No, nor with text-list or area. Same issue with tab-panel. This is 
 quite deliberate and you may wish to refer to my comments from 10th 
 March this year headed, "A word on my design philosophy, ...", to 
 see why. ;)

what's the magic incantation to have a widget hidden by default in 
the layout?

display "" [field false]

Thanks .. I managed to work it out :)

The chat widget .. can we get it so that text is selectable?

and links active?

This is more of a general question on gui design... but should one 
keep all buttons on screen, or, provide buttons as required?

I'm of the "don't tell me about it unless I can do it camp" here. 
Nothing worse than hunting through a complex menu to work out what 
I can and can't do. 80% of what I want to do or see should be no 
more than one click away IMHO.

re: chat widget. I'm waiting on R3's rich text enhancements before 
I do much more with this widget.

I agree with Ashley, that user should be provied with valid option 
in particular context. But I don't agree with dynamically rearranging 
menus, or hiding buttons. It is imo confusing. That is why we should 
have ability to disable/enable some elements, but not to hide them 
....

I too would prefer to have visibly disabled buttons on screen .. 
but have to go with removing/adding buttons for the moment.

maybe we could hack in disable/enable functions? I did some, and 
Anton (or Volker) fixed it to work even with keyboard. The solution 
was to put transparent face with some effect into front of "disabled" 
element ...