World: r3wp

Yes, the lists will be the most work of all the widgets. And, will 
all widgets be able to be listed (iterated) ?

I found that for group box the frame color makes it too discreet 
... maybe having it in black color by default could be better

Ashley why do you supress text+ ?

list (single or multi column): I once have hired Cyphre to create 
a style for me. Very useful and powerful. If someone is interested 
I can provide the code as a starting point (or at least as idea pool). 
You can find some documentation for it on my homepage under project 
data-form dialect.

I think list must be  multi colum is good, so multi colum must have 
a title (enable/disable), row design (enable/disable), sorted capability 
when clicking . Row is capable to display text, images, progressbar, 
checkbox, button all kind of widgets. Maybe as base we must have 
a dialect to format heavyly the content

Ammon: Impressive! Little time to dive into the code, are there docs? 
And what SDK/View version is required?

I tried to keep sufficient comments in my code so that the code is 
the doc...

I built the styles kind of as examples of how to do things.

If you have a question feel free to ask.  I get feature requests 
but most of the features that get requested are already there.  Take 
a peek at the code, if it isn't self explanatory, I'm glad to explain.

Actually, I was hoping you could point me to RebGUIs docs :-)

Oh, RebGUI...  http://www.dobeash.com/it/rebgui/

I thought you adapted some styles already, but now I see you were 
offering to convert your own.

Ashley's website.

Yes.

(I should go to bed early tonight :-)

Why?

;~>

can you give us the link to your work AMMON ?

Goodnight ;-)

Ammon we can work together ...

oki I found your set of widgets

I'll add the popup code to the Display function as a refinement...

display/popup

I take drop-down

That way we can use it to build menus, dialogs and the like...

oki

I'm looking to dropdown and I can't see in the popup list the choice 
entries you supply in the data field...

I'm using 1.2.48.3.1

Nice work Ashley...

There's actually two copies of the dropdown on rebol.org dropdown.r 
and drop-down.r

drop-down.r should work with all versions, which did you download?

i downloaded dropdown.r

That's the problem then.  It is depreciated and replaced with drop-down.r 
and says so in the script header.  Eventually the Library will recognize 
this and automatically redirect you to the correct version of the 
script but for now...

oki it's fixed I just download it

the 0.0.5 version

it's good now I'm starting the adapatation

to rebgui

Interesting... Somehow I have a newer version number on the depreciated 
script...  I'll fix that...

You're "Installer" example script looks a lot like my Wizard.r style. 
 My Wizard style works alot like a tabpanel but includes a simple 
way to validate information before or after a particular pane is 
loaded and it automatically positions the navigation buttons, etc...

Is that something we'd like in RebGUI?

Ashley, on this page: http://www.dobeash.com/it/rebgui/display.html
 What does this mean? "Unless otherwise specified, text size reverts 
to 200x9999 if the string contains a newline."

it's hard to port the dropdown

Yes, I've been looking closer at display.r and finding that there 
are actually many things that are going to make it slightly difficult. 
 For example, my popup code use Insert-Event-Func which doesn't work 
with RebGUI...

yep layout

isn't usefull too

Vincent: 'list behavior & features - less is more at this stage, 
once we have something to look at we can refine it.


shadwolf: 'text+ removal. While a useful widget for certain domains 
(like WYSIWYG editors / browsers) it's not a basic building block 
widget. There were also some unresolved implementation issues with 
it at this stage - I'll add it back in at a later date as an optional 
or advanced widget.


shadwolf: multi-column list. An implementation model I liked was 
that adopted by Gui4Cli ( http://users.hol.gr/~dck/g4c/) which allows 
simple "table" representations (including column type and alignment 
definitions). Can't say I've come across that many UI's that use 
anything other than text / numbers in a standard list (thumbnails 
and scrolling check-box options are usually implemented in an app 
specific manner).


Ammon: 'display/popup. If it's sufficiently different from 'display/layout 
then I'm all for it.


Ammon: Wizard style. A wizard widget, if simple enough, would be 
a good addition. Like 'group-box and 'tab-panel it is a meta-widget 
that groups / uses other widgets. I'll make this distinction clearer 
in the next version of the docs. On a side note, my install example 
has convinced me of the need for an 'indent option (and the fact 
that use of 'offset should reset the line-height calculation).


Ammon: "Unless otherwise specified, text size reverts to 200x9999 
if the string contains a newline." I probably need to rephrase this, 
but what I was trying to say was that by default 'text is 9999x20 
which let's you write a string without having to know it's width 
in advance (9999 will auto-size it), *but* if the string contains 
a newline then it is the height that is the more important variable 
so it'll use 200x9999 instead. Of course it'll only do this if you 
don't provide an explicit size yourself (the "unless otherwise specified" 
bit). Hope that makes a bit more sense.

multi-column: It should have an auto-filter option like Excel. This 
is very handy to filter out records that meat common criterias without 
having to write queries.

Display/Popup is significantly different from /Layout.  /Display 
appends the face that is generated to System/View/Screen-face.  This 
makes it so that a popup can extend beyond the window of your application.

The only problem that I have building it is that we are killing the 
global event system which is what I've been using to make the popup 
disappear when you click away from it. ;~>

If the global event system is the best way of handling this, then 
we can always reinstate it (a pity though as nothing else has needed 
it yet).

You need to be able to catch all click events so that if the user 
clicks anywhere off of the popup you can hide it.