World: r3wp

resolves for me

Hi Ashley, i would like ask you how to make new widget after you 
have removed function append-widget. I have not found any function 
to do it... sorry i am a dommies and may be there similar func exists 
 :-)

The RebGUI documentation looks great.   Is there also an advanced 
comprehensive example application for viewing ala CureCode as a Cheyenne 
application?

Bobik, to create a new widget:

	1. Add your new widget to the %Widgets/ directory

 2. Edit %rebgui-widgets.r to add an #include entry for your new widget

 3. Run %create-ditribution.r which will "compile" a new version of 
 %rebgui.r for you

MikeL, thanks. Have a look at %tour.r, then %RebDOC.r ... there's 
not many comments but the code should be fairly easy to follow.

Sweet! Sorry I missed %tour.r on my first look.

Ashley: thanx a lot! :-)

So i have just one question - is it possible to get  position info 
of mouse on event ON-CLICK , for example when i have box 10x10 on-click 
[get mouse position ....] ?

I know - VID method engage has EVENT, where can i get event/offset...... 
so how to get such value in rebgui to avoid do new widget :-) ?

Hmm, on-click gets face argument. The only thing I am able to come-up 
quickly is

box red 10x10 on-click [print face/offset]


But that just gives you face offset. From face/offset and face/size, 
you can get idea about the area, but not sure about the mouse event 
offset ...

face/offset - you get offset of face(in such case offset of box) 
but not offset of mouse

That is what I said - "but that just gives you face offset".

box red 10x10 on-click [print mold get in face 'feel]

make object! [
    redraw: none
    detect: none
    over: none
    engage: func [face act event][
        case [
            event/double-click [face/action/on-dbl-click face]
            event/type = 'time [face/action/on-time face]
            act = 'up [face/action/on-click face]
            act = 'alt-up [face/action/on-alt-click face]
            act = 'key [
                face/action/on-key face event
                face/action/on-edit face
            ]

            act = 'scroll-line [face/action/on-scroll face event/offset]

            act = 'scroll-page [face/action/on-scroll/page face event/offset]
        ]
    ]
]


Now how to get into the feel, and hook somehow into 'engage method 
:-)

I never used RebGui, but if you can get the object constructed like 
with VID:
b: box red 10x10 on-click [print face/feel/pos]

then you can patch b with something like:

b/feel: make b/feel [
	pos: 0x0 
	engage: func [f a e] compose [
		pos: e/offset 
		(get in b/feel 'engage) f a e
	]
]


That overloads the engage function wihout losing her actual content.

In VID you specify the feel directly, in RebGUI you let the widget 
worry about these low-level implementation details. None of the default 
widgets need to pass mouse offsets back to the application, so if 
you need to do this then creating a new widget is the way to go. 
Having said that, I could always add another action handler (on-anything 
face action event) which would fire instead of the above case statement 
(i.e. handle the event as in VID or let RebGUI delegate it to the 
appropriate handler).

would be nice.

why not allowing the event as a default parameter for any action 
?

I mean, you only furnish the face as argument, can't you add the 
event too ?

Steeve it sounds good! FYI:   I needed widget "box" with drag and 
drop features :-) I know it is possible to make new widget atc.. 
So after append-widget was removed, new widget creating is a little 
bit  cumbersom  and i have tried to catch FAE values directly in 
rebgui dialect...:-) I think there are more cases where to catch 
FAE would be useful for app programmer......

can't you add the event too?

 ... I can, but that breaks a lot of the internal handler code. I'm 
 more interested in seeing what the other FAE cases are (I've yet 
 to hit any myself).

As append-widget removal was oversimplification imo, especially for 
the widget authors, I created short script, which kind of automates 
the process ....

1) Save the script, e.g. make.r, into the RebGUI root dir

2) create one file, called %my-widget-list.r, containing unnamed 
block, containing file-names. Your widgets can be placed anywhere

3) create backup of %rebgui-widgets.r, call it %rebgui-widgets.old.r, 
in order to be able to easily "remove"  widgets by commenting them 
out in file 2)

Here's the script:
REBOL []

;--- to enable removal of unwanted own widgets, create
;--- copy of rebgui-widgets.r into rebgui-widgets.old.r

;--- remember to do so, when official distro release contains new 
widgets!
if exists? %rebgui-widgets.old.r [
  write %rebgui-widgets.r read %rebgui-widgets.old.r
]

;--- load list of widgets you want to include
;--- file containing un-named block of list of files to include
widgets-to-include: load %my-widget-list.r

template: "^-#include %widgets/^/"

;--- read RebGUI widget list (%rebgui-widgets.r)
tmp: read %rebgui-widgets.r

widget-buffer: copy "^/"

foreach widget-filepath widgets-to-include [ 

   widget: last split-path widget-filepath

   ;--- copy widget to the widget-directory
   write join %widgets/ widget read widget-filepath
  
   ;--- build string containing widget names you want to add ...

   ;--- but only when not already on the list - prevent duplicate entries
   if not found? find tmp widget [

        append widget-buffer (head insert find/tail copy template "/" widget)
   ]

]

;--- append to RebGUI widget-list (%rebgui-widgets.r)
change back back tail tmp (append widget-buffer "]")
write %rebgui-widgets.r tmp

;--- rebuild RebGUI distribution ...
call "create-distribution.r"

I'd like to see a generic accordion widget if possible.   So, if 
you had 4 "tabs" in the accordion, then each tab is associated with 
a layout.  If you click on a tab, the others collapse, and the clicked 
on one expands to show the hidden layout underneath.  If you click 
on an open tab, it should collapse .. so that the bottom tab's layout 
is exposed.


I've hard coded this stuff before but was wondering if a generic 
one could be written.

An accordion is like a tab panel but vertical as there is no horizontal 
space.

Is there a Javascript one I can play around with somewhere?

http://jqueryui.com/demos/accordion/

Here's an accordion I did last night in Rebgui .. hard coded still 
though http://www.youtube.com/watch?v=VYSPNtpNaVU

That's cool anyway :-)

A lot of work doing this manually!

The navigation panel on the left in Altme is an accordion :)

http://www.dobeash.com/RebGUI/user-guide.html

Typo: bought (search for it)

event handling management in rebgui ....  that's a topic i wanted 
to discuss 3 or 4 month ago when i tryed to adapt  area-ct to rebgui 
...

ok but with new vid  in R3  what will be the future of rebgui ? ashley 
do you plan to keep rebgui as an enhancement and laboratory ground 
for new kind of widgets design in the new VID ? Or does the new VID 
will kill  rebgui ? What will be the link betwin R3/VID and rebgui 
do you think some of the fun widgets from rebgui will be adapted 
by default in R3/VID ?


If you remmeber i asked this like 1 year ago to carl and didn't get 
any reply...

hi, i find a probleme on rebgui-218 bluid with menu widget when i 
select a item !!!!!

here is the message => "result: pick data first picked"   near "on-click" 
         on source rebgui.r  function choose !!!!

picked return []

re: RebGUI and R3/VID. I'll probably put something up on my website 
on this topic as I get asked this quite a lot. Basic thinking at 
this stage is:

	I need to create SDK GUI apps for Windows and OSX
	R2/RebGUI is the only practical alternative at present for *me*
	I'd love to use R3/VID to create SDK GUI apps today
	This probably won't be possible for quite some time

 If and when this *is* possible I'll port all my apps over to R3/VID

 To do this I'll either create a compatibility layer that lets RebGUI 
 apps run on R3/VID, or

 Write a conversion script that tries to convert (if possible) RebGUI 
 scripts to R3/VID

 I'd hope R3/VID is complete enough that it doesn't require any of 
 RebGUI's basic widgets!

ashley do you have a solution for the menu bug ?

Yes, but the next build will be a while yet.

Does the TABLE widget support horizontal scrolling?

No, there is Cyphre's grid, but it was not adapted to new API changes 
....

thanks

I need to popup a menu where the cursor is.  I guess caret-to-offset 
will get me the offset into the face ....

this doesn't seem to change much in edit-text

caret-to-offset face find/tail/last head view*/caret view*/caret

removingt the /tail seems to help :)

how to set the check-group ?


display "" [ cg: check-group data [ "1" none "2" none "3" none ] 
button "Set" [ set-data cg [ true true true ] probe cg/data] ] do-events

doesn't work for me

BTW, set-values.r seems to be missing from the distribution now.

I often have the need to set a date on a field ... and use a symbol 
to invoke the request-date .. .but this usually means I have to name 
the date field like this


datefld: field 25 symbol data 'look on-click [ use [d][ if d: request-date 
[ set-text datefld form d ]]]


To avoid naming the datefield, I have this function which returns 
the prior face


get-prior-widget: func [ f
    /local pane priorface
][
    pane: f/parent-face/pane
    priorface: pick pane -1 + index? find pane f
]

and here's a request date that uses it


request-date-priorface: func [ f /local d ]
[
    if d: request-date [
        set-text get-prior-widget f form d
    ]
]

so we can now do:


 field 25 symbol data 'look on-click [  request-date-priorface face 
 ]

Can't use funct as using the SDK :)

1) set-values.r ... removed in build#212. Plan is to add accessors 
(e.g. add, update, delete) to each "complex" widget.

2) named widgets ... don't forget the 'in-widget function, it does 
what you want above (see biuld#213 release note from Aug 27).

3) funct ... you'll have to build your own collection of SDK+ mezz 
funcs as the SDK diverges further from R3 (and R2 releases without 
an SDK update).

and how to set  a check-group?

Just looked at in-widget, and it does different things. I want to 
find a specific widget ...