World: r3wp

thanks for the heads up... If you are going to rewrite it... please 
allow more selections in this kind of thing... curved interpolation 
IS much better, for things like shadows, for example... but the need 
to select filter types (from all available... not just one or two), 
interpolation curve types, start-end snap on beziers, things like 
this are all essential, if we want to allow the next REBOL to be 
able to properly compete.  


defaults are good and often this is all that is needed, but for any 
graphic app, this quickly becomes essential (as you will agree, on 
your own usage), and is a weekness of current toolset.

the other big weekness is our inability to extract any kind of data 
from the AGG computed visuals.  cv info (for a text curve, for example... 
to match a graphic to its corner) , curvature data (length, coord 
+ angle at offset,  etc), box size, centroid (for quick searching 
of  computed visuals), all of this is vastly faster (we are talking 
like 10000 times or more here) when done in binary and available.

but dumping top of my head since the topic was opened briefly  :-)

it might spur other ideas from other gfx coders.

yes, the new gradients will be even more configurable. Regarding 
the access to the AGG  internal representation. I have talked about 
 this with Carl and we agreed in R3 it would be allowed to do functional 
programming of DRAW blocks. But all this needs more thinking...

Maxim, regarding this: "somehow, it seems like its missing a color 
blend mode selection, multiply, add, screen, etc. right now its a 
ramp which fades to 0 on each side, such that when two successive 
colors do not have any bit in common it creates an alpha channel 
premultiplication grey zone..."

blending is not a part of gradient definition, look at Flash or SVG. 
Gradients work the same as in Rebol inthis case.

A style a day keeps the doctor away:

New idea for a style: A "FLATTEN-PANEL" is a PANEL which "explodes" 
its
pane directly into the parent face's pane. eg:

A normal PANEL and resultant face hierarchy:

	layout [
		panel [
			label
			field
			check
		]
	]

	window
		panel
			label
			field
			check
	
A FLATTEN-PANEL and resultant face hierarchy:

	layout [
		flatten-panel [
			label
			field
			check
		]
	]
	
	window
		label
		field
		check

Implementation and test:

	view window: layout [
		style flatten-panel PANEL with [
			append init [
				foreach face pane compose [

     face/offset: face/offset + (do bind [where] first find second :layout 
     [new-face:])
				]

    append get in get first find second :layout [new-face:] 'pane pane
				clear pane
			]
		]
		
		at 500x200
		flatten-panel [
			label "hello"
			field
			check
		]
	]

Full document here:
http://anton.wildit.net.au/rebol/doc/flatten-panel.txt

updated.

Hmm.. not as useful as I would like.

Hi, has anyone any newer version of Todo List script? My intention 
is not to replace Qtask, just having something VERY easy, kind of 
check-list, for controlling tasks - http://www.xidys.com/rebol-view/image38.jpg

retask?

I can give you an .exe for windows if you want to test it out.

its even fully documented!


http://www.pointillistic.com/open-REBOL/moa/steel/retools/retask/index.html

retask? what is that? liquified version of qtask? :-)

bzzzz .... loading

nope just simple task tracker.

with presets and a bg mode which asks you what you are doing...

instead of you having to remember to fill out forms.

I've juste noticed the nice values we get for event key when pressing 
function keys !!!

in order: console listen tcp udp icmp dns local odbc oracle

is that 2.7? that is a bug, will be fixed in next release.

they should give f1 f2 etc of course :)

Hmmm, I've always gotten f1, f2, etc., though I don't use them much, 
so this may be new.

gregg, yes, they are supposed to be f1 etc.

I know they have been in the past.

there's a bug with 2.7 where event/key, when it should be a word, 
is wrong

that's probably because of the internal changes... probably wrong 
pointer or something like that

ins, del, home, end, pgup and pgdown have the same problem

1.3.2 is OK.

Ah, just 2.7 then; OK.

yep. the bug was introduced in 2.7

sorry... forgot to specify that its only 2.7 related... I just tought 
the values where funny... I assumed the break was that the keys didn't 
actually trigger... but then, on inspection... figured out what was 
really happening.

When is the next release, by the way ? I ask because we keep stumbling 
on this same bug, and I think it's an easy one to fix, judging by 
how fast those other string bugs were fixed.

i guess when Carl manages to escape from thread prison ;)

Does anyone know a way how to detect when all rebol windows are inactive 
(ie. because a non-rebol window became active) ?

I can trap inactive events sent to a rebol window, but I want to 
know whether that was because another rebol window was activated 
or a non-rebol application window was activated.

If it is a rebol window, that window gets an active event --- but 
this is *after* the previous inactive event.

another window in the same rebol process or a differen rebol process?

Same process.

I need something like a "none-active" event that lets me know when 
all rebol windows are inactive.

I would like to know that too. A program I'm making has a timer mechanism 
where the program must be active all the time and I want to display 
an alert if the window gets out of focus.

Maybe the system port ?

Let me dig around...

never messed with it

How many windows in your program ?

If only one, it's easy - just trap inactive event.

If more than one, and since you are running a timer, you can track 
the state of all windows and react when a timer event comes along 
after an inactive event which was not followed by an active event.

Probably that's my solution too - run a timer.

excellent, time events are still running even when all rebol windows 
are inactive. This means it's possible.

active-windows: []
insert-event-func event-func: func [face event][
	;print event/type 

 if event/type = 'active [if not find active-windows event/face [append 
 active-windows event/face]] 

 if event/type = 'inactive [if find active-windows event/face [remove 
 find active-windows event/face]] 
	if event/type = 'time [
		if none-active? <> empty? active-windows [
			none-active?: empty? active-windows
			if none-active? [
				print "all windows inactive!!"
			]
		]
	]
	event
]
view/new win1: layout [size 400x250]
view/new win2: layout [size 500x200]
win1/rate: 0 show win1 ; start time events
none-active?: false
do-events

Can you see any holes in this method ? (Apart from the fact that 
it requires time events.)