World: r3wp

Printing should be a big priority at some point. Rebol will not be 
taken seriously in commercial circles until we can hook into printing 
systems directly. I know it maybe a boring area for developers to 
work on. It's it is a hard sell when one has a great looking RebGUI 
interface without a print option.

HTML has is limits, PDF generation is more of an option.

I use postscript

it works

Yes, of course. Not everyone has a PS printer or a rendering sub-system 
though. (e.g. Ghostscript). I've also output to LaTeX on the backend. 
If the system is client server then the backend can handle printing.

Ashley;  Thanks for that.  I kinda wish I hadn't cleared the database 
before taking 

the screenshots.  I just noticed the screens look fairly empty.  
:)

We do need a directory selector that can access directories across 
the network.  At present i have to resort to using request-file,and 
selecting a file in the target directory.

wonder if the background colour to an info field shouldn't be more 
obvious to indicate that it is an info field

I'm currently building an interface.  I have a tip which works ok 
until I open a dialog, say request-ui or question. There are no actions 
hooked up to the dialogs yet. Once the dialogs are dismissed, the 
tip does not show again. Every other widget is responding to events 
BTW.


The tip is attached to symbol text. Lots of head scratching going 
on here. It feels like some event has been killed. Any ideas anyone?

Thanks.

directory selector that can access directories across the network

 We're limited to what "read %/" can pick up. Real solution is to 
 have a native request-dir func (and request-color, request-font).

background colour to an info field
 ... how about making it the same color as tooltips?

	field ctx-rebgui/colors/tooltip-fill

Any ideas
 ... looks like a RebGUI bug as I can reproduce it with:

	display "" [
		box tip "Some text"
		button [alert "Text"]
	]


Hmm, also noticed that tooltip and tooltip-time are dynamically escaping 
to the global context. Will look at this later today.

Build#94 uploaded to SVN. Contains minor tooltip, drop-list, request-menu, 
on-click and on-alt-click fixes.

Ashley, thanks for the quick fix. Previously, I've used the files 
from the demo in the Rebol directory via Viewtop. As an end user, 
how can I easily get hold of build#94, not having used SVN before 
BTW.

Cheers.

23-Apr-2007 11:50:36 Caret trap password origin: 2x2
margin: 2x2
indent: 0x0
tabs: 0
wrap?: false
scroll: 0x0

23-Apr-2007 13:02:38 Caret trap password origin: 2x2
margin: 2x2
indent: 0x0
tabs: 0
wrap?: false
scroll: 0x0

24-Apr-2007 10:08:44 Caret trap password origin: 2x2
margin: 2x2
indent: 0x0
tabs: 0
wrap?: false
scroll: 0x0

24-Apr-2007 22:30:03 Caret trap password origin: 2x2
margin: 2x2
indent: 0x0
tabs: 0
wrap?: false
scroll: 0x0

17-May-2007 23:11:58 Caret trap password origin: 2x2
margin: 2x2
indent: 0x0
tabs: 0
wrap?: false
scroll: 0x0

18-May-2007 17:53:46 Caret trap password origin: 2x2
margin: 2x2
indent: 0x0
tabs: 0
wrap?: false
scroll: 0x0

Dave, easiest way to grab the latest SVN build (without using any 
client s/w) is via a simple REBOL script like this:


 write %rebgui.r read http://trac.geekisp.com/rebgui/browser/rebgui.r?format=raw


%rebgui.r (the complete merged distribution sans %tour.r) is now 
regenerated and uploaded every build.

that was my rebgui.log

Cool. Many Thanks.

Hmm, looks like the caret problem is confined to password, and the 
"current word" problem seems to have been fixed. This makes it a 
*lot* easier to track down now.

Tip fix works fine Ashley.

Is the V2 already at release-candidate state? I'm thinking about 
migrating all our added code to the new version.

Yes, all the big structural/naming changes were done some time ago.

There's a large medical trade show in Dallas next week.  About 170 
exhibitors.  Synapse EMR using Rebgui .. should be there too demonstrating 
a bidirectional interface to Schiller medical instruments.

Alas, I won't be there to see it ... http://www.medrecinst.com/conference/tepr/index.asp

I saw that in V2 there are a lot of the ON-* handlers. When writing 
code how about a way to specify it like this:
a: field "Input here" on [
	reset [...]
	translate []
	focus []
	unfocus []
]

IMO makes the code much better to handle.

Agreed, good suggestion; I'll add it to the next build.

:-) Great.

Is there a way to make the scroll automatically go down when adding 
text to an area?  I have an area I'm using as a status terminal window 
and I can't see the feedback until the task is done because the scroll 
stays at the top.

When you type in an AREA, it scrolls to keep the entered text visible. 
Therefore, we should follow the trail to find out which code does 
this scrolling.

print mold svv/vid-styles/area/feel  ; <-- this shows use of EDIT-TEXT, 
which is in CTX-TEXT, so..

print mold make ctx-text  [view*: none] ; <-- the reference to system/view 
gives too much output, so we disable it for now.

; If you search that text for "scroll", you find yourself near the 
bottom of the EDIT-TEXT function body, looking at this:

if face: focal-face [
            if flag-face? face hide [
                unlight-text 
                insert/dup clear face/data "*" length? face/text 
                do swap-text
            ] 

            tmp: any [caret-to-offset face caret caret-to-offset face caret: 
            tail face/text] 
            tmp: tmp - (face-edge / 2) 
            tmp2: face/para/scroll 

            all [tmp/x < 0 tmp2/x < 0 face/para/scroll/x: tmp2/x - tmp/x] 

            all [tmp/y < 0 tmp2/y < 0 face/para/scroll/y: tmp2/y - tmp/y] 
            action: face-size - tmp - face/para/margin 

            if action/x < 5 [face/para/scroll/x: tmp2/x + action/x - 5] 

            if action/y < liney [face/para/scroll/y: tmp2/y + action/y - liney] 
            show face
        ]

Scrolling is achieved by modifying face/para/scroll, where FACE is 
your AREA face.

I am sure you can pick the parts you need from the above code, to 
create a nice little function which only appends text.
Note also the definition of LINEY, from further up in EDIT-TEXT: 
        textinfo face line-info 0 
        liney: line-info/size/y 
This depends on LINE-INFO, which is in system/view/line-info

So you will need to either bind your code to system/view and ctx-text, 
or refer to line-info and unlight-text using paths, eg:
	system/view/line-info
	ctx-text/unlight-text

(Ah heck, I'm in the RebGUI group... not sure how much of the above 
applies. I know some of it doesn't.)

btw - there is some area style, which scrolls when you hilite-by-mouse. 
It is for VID only and comes from french community, at least that 
is what Bobik said to me ...

I'm still having area issues.  If I reach the bottom of an area widget 
and hit return at the end of a line, the caret will often jump to 
the beginning of that line instead of making a new line.

Pekr: yes It's my area-scroll-style in rebol.org

on vid i attacgh a scroller and set that to 1.0 . maybe that works 
with rebgui too?

re: area scrolling. Try the following:

	display "" [
		a: area (form system/locale/colors)
		button [insert tail a/text join newline now show a]
		button [a/pane/1/data: 1.0 show a]
	]

Oops, that shoud read:

	a/pane/data: 1.0 show a

or just:

	set-data a/pane 1.0

Okay.  That works great.  The only issue is if you only have one 
line of text it pushes it to the bottom, but that's easy to work 
around.  thanks.

e.g:

	all [a/pane/ratio < 1 set-data a/pane 1]

from the rebol demos.. 

Finished processing manifest.
** Script Error: yello has no value
** Where: append-message
** Near: get msg-color

now im no expert, but my guess is 'yello' should be ''Jello'

>> system/version
== 1.3.2.3.1
>> yello
== 255.240.120

Short answer is that it requires REBOL/View 1.3.2 or greater.

running 1.3.5

>> 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...)