World: r3wp

Correct, the look and feel is a work in progress at the moment.

screen shots of the newest RebGUI

 ... I've created a snapshot release here: http://www.dobeash.com/RebGUI/rebgui112.zip


Just unzip and run %tour.r and %RebDOC.r to get a feel for where 
things are at.

How's your resize support? The tour and RebDOC were too big for my 
screen resolution (1024x768) and the windows weren't resizable.

Resize works, but only %tour.r uses it at present. If resizing is 
enabled then the *minimum* screen size is set to starting screen 
size unless explicitly set via a refinement. Problem in this case 
is %tour.r has "grown" to 696x785 and %RebDOC.r is 800x829 (and I've 
not used 1024x768 for a couple of years now). I'll fix this for the 
next build though.

Isn't Brian saying that the windows were too big for his 1024x768 
 ??

Ashley, Very cool...
After Dinner  will make you a small log LOL  clearly you need it.

Having trouble with the #HWLVXY codes. I have two group-boxes next 
to each other. When I resize the window They overlap. I want them 
both to expand in size "H" and "W" but not overlap. Is this possible?

No. You can however have this:

display "Test" [
	group-box "A" #HW data [field]
	group-box "B" #HX data [field]
]


The resizing model is *very* basic and only supports one widget in 
a row / column resizing horizontally / vertically.

Ok, here are some other examples, and considerations when sized.


For example, when you get small, the "hand" looks like the REAL hand 
on the screen, which could confuse people.  So while it is fun at 
larger sized, it won't work once the pixels drop to less than 4x4 
each (my guess).


I think you might like the one in the lower right.  It is very RACEY, 
the italics make it look "fast" and the black and red were something 
I think you requested.

If you want me to try something special, or do a treatment like something 
else you have seen out there, just say the word.


This one is a Qtask syndicated Folder.  So any file we put in this 
folder from inside Qtask can be accessed by people outside of Qtask


http://www.qtask.com/files.cgi?tab=sFolderList&uuid=YG82XF3CFW8AQ6W5NYTXV9NKE3QT


So for example, since this came from the "REBOL SIG" project inside 
Qtask, Ashley, you can go into that project, and delete this file, 
which will effectively put it in the Trashcan, and this link will 
then point to an empty folder for people.

Ashley, please bear in mind that laptop screens these days are: 1280 
x 800.

I can resize RebDoc, Tour because it's to high.

BTW: RebDOC is very nice.

Looks that I have to backport a lot of stuff to a new RebGUI.

Ashley, did you note my problem with drop down lists in a scroll 
panel?s

I did. Correct me if I'm wrong but it's only a problem in scroll-panel's 
that can scroll vertically? Is there a real (as opposed to theoretical) 
usage case where you'd need a drop-list in a vertical scrolling panel?

the screenshot is from my real application :(

Just had a look at the source again ... as the droplist-mode for 
drop-list gone?  We used to have the option of setting 'auto, 'middle, 
'upward and  'dowward

Defaults to auto now, and has for some time.

So, we can no longer change this?

IOT, auto doesn't work for me .. my drop lists disappear at the bottom 
of the window losing data.

Please post a small test case that demonstrates this. Thanks.

Looks like my problem was that I had nested tab-panels,and the inner 
one with the drop list was deeper r than the outer one.

and the outer tab-list cut off the bottom of the drop list.

tab-panel

Temporarily solved the drop-list problem in a scroll panel by just 
doubling the data in the list ...

So it no longer matters if I can't see the bottom.

Just wondering how hard it would be to do a predictive text like 
widget

I couldn't predict that ;)

What exactly is it?

auto-complete?

I was thinking of cellphones that use predictive text to guess what 
you're trying to write.  if the word isn't correct, you hit a special 
key and it cycles thru all the choices for you changing the current 
word in-situ.

Now predictive text is trickier cause each key has 3 choices of letters 
whereas a full keyboard there is no doubt about the letters you are 
typing.

so, perhaps more interested in the cycling ....

the idea is to greatly speed up text entry at the keyboard

OpenOffice does predictive text on the basis of words you've previously 
typed. It seems cool until you use something like manager, managed, 
managing and management in it. It then quickly becomes annoying and 
slows text entry down.

how so .. you type man and get 5 choices so save on typing all the 
rest ...

With Open Office you type man and get management whether you like 
it or not?

I think they do it that way to avoid having to use the mouse ...unless 
you can make the selection without using the mouse, choosing will 
be slower than typing.

On my mobile I use the * key to switch between choices

If a gui pops up, perhaps a key combination could be used to make 
a selection

Carl's Rebodex has something like what you describe.  It filters 
the data in a list rather than a drop-down type widget, but that 
would be easy enough to change.

... for you guys.  ;-)

Note that drop-list / edit-list already have this feature.

Ashley, you look at the art I uploaded?

graham, to me it would be faster to type than to select from a list, 
for most words. so it would really be just annoying. it can only 
help on longer words of which i'm not sure about the spelling...

it's a need on cell phones because of the small keyboard.

Textmate only autocompletes when pressing escape. when pressing escape 
multiple times, you can switch between alternative completions.

Still ergonomists have thought hard on how to speed up typing on 
restricted keyboards .. maybe there is something there that can be 
taken to a full keyboard

different point - is it necessary for the highlight to be removed 
from a text widget if the focus has gone elsewhere?
It doesn't happen with list widgets

Yes, text focus is implemented via View's caret handling functions 
which enable portions of text to be highlighted ... contrasted with 
list widgets which either highlight the entire row (or not).

Reichart, yes ... I'm deferring my decision until I've gone further 
with the UI changes; no point settling on something only to find 
it needs changing as the base look changes. I'll message you privately 
once the UI look is finalized and I'm ready to proceed with the [complementary] 
logo look.


Also, is there anything more comprehensive on the Quilt UI I can 
look at? I've got the Quilt Design Style Guide and the Search Sketch 
mockup, but really need something that either explains or shows color 
state changes (e.g. what happens as the mouse moves over various 
widgets and different states are triggered by clicking things)? Is 
there the equivalent of a Quilt "tour" I can take ... something that 
demos all widgets in action?

Logo - Cool


Quilt - Not yet.  In fact, state changes and gestures (mouse moves, 
drag and drop) is not done yet.  However, ya'll can be the first 
to learn, Richard (Cypher) will be taking over as head of development 
for Quilt.


Jason, Will and my self designed it up to this point, and now Richard 
and I will carry it forward, with Jason and I moving on to building 
a complete and fast Rich Text Editor for Qtask, and Will and I will 
be making our Calendar more dynamic.

Edgar will be leading the API back end...