World: r4wp

and fact1 must be initialized accodingly.
Either with 'a either with 'a/a

question:
an object 'a always has only one property called 'a ?

yes

ok it's simpler then, let me try...

fact1: 'a
get-prop: func [o][either object? o [first next second o][o]]

blk: [greater? to-decimal get-prop do bind reduce [fact1] obj num1]objs: 
[]

another question. 

Why are you using the blk variable instead of coding directly in 
the foreach loop ?
The code would be simpler.

meaning?

This is the same thing without the need of the blk code:

foreach obj objs [
	if num1 < get-prop obj/:fact1 [print obj/a]]
]

much simpler, no need to rebind anything

small mistake, missed the to-decimal.

foreach obj objs [
	if num1 < get-prop to-decimal obj/:fact1 [print obj/a]]
]

arghhh

foreach obj objs [
	if num1 < to-decimal get-prop obj/:fact1 [print obj/a]]
]

Anyway, you see the idea

yes...

much simpler

Is it possible to change the background color of the view led? Or 
are the only states available 'true' and 'false' which are green 
and red? I want different background colors for 'true' and 'false' 
states.

view center-face layout [
	across
	l1: led
	label "State" state: field

	btn "Change led state" [
		either l1/data [
			l1/data: false
			state/text: "False"
		][
			l1/data: true
			l1/data: true
			state/text: "True"
		]
		show [l1 state]
	]
]

caelum, take a look at the style code. the colors are likely embedded 
in it:

>> get in get-style 'led 'colors
== [0.255.0 255.0.0]

Then something like this:

stylize [
	led: led with [colors: [<your colors here>]]
]

should probably be STYLIZE/MASTER, sorry.

you can also do this:

view layout [led with [colors: [<your colors here>]]]

Got it, exactly what I was looking for. Thanks.

You're ramping up fast sujoy. Most people don't get to using BIND 
for a long time. :-)

As Steeve has pointed out "it can be done" is *almost* always the 
answer with REBOL, and usually done in many ways. REBOL is great 
for practical use, as well as learning to think about problems in 
new ways.

thanks Gregg. am loving rebol... :)

you took the red pill then :)

haha! looks like it Endo!

He's one of us now Endo. Next thing, he'll b3 wondering why every 
other programming language has only 6 or 8 datatypes and why they 
don't have a PARSE function. :-)

has anyone written parse rules for phone numbers?   I need to setup 
a set of rules for international numbers, local numbers, cell numbers, 
1800 etc for use in asterisk and prevent users from making toll calls 
unless authorise

To make it easier I will strip out alll non-digits first

I guess i should just make a rule for each type of call and then 
combine them.

Here's something for US phone numbers I did a long time ago

set 'parse-phone-num func [
        num [string!]
        /local  digit digits sep _ext_  ch nums pin ext
    ] [
        digit:  charset "0123456798"
        digits: [some digit]
        sep:    charset "()-._"
        _ext_:  ["ext" opt "." | "x"]

        nums: copy ""
        rules: [
            any [
                some [sep | copy ch digit (append nums ch)]
                | _ext_ copy ext digits
                | "pin" copy pin digits
            ]
            end
        ]
        either parse trim num rules 
            [reduce ['num nums 'ext ext 'pin pin]]
            [none]
    ]

    set 'well-formed-phone-number? func [num /local data] [
        either none? data: parse-phone-num num [false] [
            any [
                found? find [7 10] length? data/num
                all [11 = length? data/num  data/num/1 = #"1"]
            ]
        ]
    ]

And a formatter that goes the other way:

set 'format-phone-number func [
        num [string! object!] "String or object with /text value"
        /def-area-code area-code [string! integer!]
        /local left right mid obj res
    ] [
        left:  func [s len][copy/part s len]
        right: func [s len] [copy skip tail s negate len]
        mid:   func [s start len][copy/part at s start len]

        if object? num [obj: num  num: obj/text]

        res: either data: parse-phone-num num [
            ; discard leader if it's there.
            if all [11 = length? data/num  data/num/1 = #"1"] [
                data/num: right data/num 10
            ]
            rejoin [
                rejoin switch/default length? data/num [
                    7  [ compose [

                        (either area-code [rejoin ["(" area-code ") "]][])
                        left data/num 3 "-" right data/num 4
                    ]]
                    10 [[
                        "(" left data/num 3 ") "
                        mid data/num 4 3 "-" right data/num 4
                    ]]
                ][[data/num]]

                reduce either data/ext [[" ext" trim data/ext]] [""]

                reduce either data/pin [[" pin" trim data/pin]] [""]
            ]
        ][num]

        if obj [
            obj/text: res
            attempt [if 'face = obj/type [show obj]]
        ]
        res
    ]

Ok, so this checks for legally formatted numbers.  Or formats numbers 
into the common format.

need to reboot .. clipboard not working.  When is openme coming :(

Yes. :-)

p: format-phone-number "1800-123456"
== "(180) 012-3456"

might need a ittle tweaking for international numbers

How are international numbers formatted?  +181812345678  ?

As I said, it was just for US phone numbers. The +1 was not included, 
since it wasn't meant for dialing.

If you're asking how they're formatted in general, it depends.

ok, so always 3 numbers in the first group if not international?

Yes.

( we use 2 numbers for the first group unless it's cellular  when 
it's 3 or 4 )

can a number start with 1 ?

IIRC, some places use 4, grouping them into 2 sets of 2 for the area 
code.

ohh ....

I guess users are going to have to make their own parse rules then

The code I posted doesn't do any validation according to what might 
work in the real world when dialed.

http://msdn.microsoft.com/en-us/goglobal/bb688129
http://en.wikipedia.org/wiki/Telephone_numbering_plan


I think the number of options are limited enough that you could get 
pretty far, but a custom system would be great. If you could template-ize 
things, users could submit their templates for others to use, or 
to be integrated into the default system.

These rules are going into a cgi script to allow local and national 
dialiing (and emergency) but stop international