@SmackMacDougal maybe not a minimal example, and doesn't display the options, but you could look at the Red Console sources.
@SmackMacDougal General idea, but unfinished (sorry, have to go):
blk: [
["Blog" http://www.red-lang.org]
["Download" http://www.red-lang.org/downloads]
["Documents" http://www.red-lang.org/documents]
]
view [
at 10x33 tl: text-list hidden data [] on-change [
dd/text: copy pick face/data face/selected
face/visible?: no
]
dd: drop-down focus on-change [
collect/into [
foreach b blk [
case [
empty? face/text [clear tl/data tl/visible?: no]
find/match b/1 face/text [keep b/1]
]
]
] clear tl/data
tl/visible?: not empty? tl/data
] on-key [
switch event/key [
down [tl/selected: either tl/selected = -1 [1][max tl/selected + 1 length? tl/data]]
up [tl/selected: either tl/selected <= 1 [-1][tl/selected - 1]]
]
] on-enter [
if all [tl/selected > 0 tl/visible?] [
face/text: copy pick tl/data tl/selected
clear tl/data
tl/visible?: no
]
]
]
Toomas that is a start and I shall give it much thought. I've toyed with capturing keys and pushing sub faces, so this should be interesting.
@toomasv agreed. Having not touched drop-down for a while, this was my quick hack earlier:
choices: [
"Testing A"
"Testing B"
"Profile"
"Process"
"Func"
"Function"
"Functor"
]
filtered-list: none
view [
dd: drop-down data choices on-key [
filtered-list: copy choices
if not empty? face/text [
remove-each str filtered-list [not find/match str face/text]
]
face/data: filtered-list
]
button [print mold dd]
]For a combo box (edit+list), we need to data/text facets for some things.
I just get lots of
a has no value
seems like something that should be really easy to do
obj: context [a: 'a]
; make object! [
; a: 'a
; ]
obj/a
; a
?
I remember someone saying something about function specs letting you type return values - is there some way to do that?
I think I heard you can write them, but the compiler/interpreter just ignores it for now
thanks
I remember someone saying something about function specs letting you type return values - is there some way to do that?
routines support that. Not sure how compiler treats it.
Also:
>> a: 1
== 1
>> set o: object [a: none] a
== 1
>> o
== make object! [
a: 1
]
@nd9600 The precise syntax for functions as opposed to routines is
return: [<any sequence of datatypes and typesets>] ; see e.g. this spec.
Note (1) there is as yet no check on this and (2) when compiling, the typeset names must be of built-in (pre-defined) typesets -- user-defined typesets are not allowed in that case; see also red/red#3285
@nd9600 your first example is a great "think like Red" experiment:
a: 1
o: context [
a: a
]To create a context and bind the words to it, context (or object) has to first find and collect all the set-word! values. Now, while you know that the a you want to evaluate is global, Red doesn't. A slight change should make this clear:
a: 1
o: context [
a: self/a
]That's how Red sees it, which lets you express things with locality in mind.
a: 1
o: context [
a: 2
b: a
]Red's design choice is based on the premise that you shouldn't have to say self/a (though you can if you want). This is a huge win overall. Using compose or a path to another context also make it clear when you are reaching outside the spec for values.
I am trying to make the Abyss Web Server work with Red. My red scripts work and I am able to print the date correctly:
print ["Date/time is:" now] When I tried to use a CGI form and use print input the server hangs and doesn't print the form content. Is there anyone that has any experience with this server ?
Not used Abyss Web Server, but you can check this document out, if you didn't already, https://github.com/red/red/wiki/%5BDOC%5D-Using-Red-as-CGI
Ah, I see that it mentions
For the POST method, you can get the POST data using input
So I might be wrong.
I have another question regarding parse. I want to parse strings of the following outlook:
So there are outer brackets and a
It becomes tricky with the following strings:
Is there any easy solution using parse?
Thank you in advance.
(abc OR def)/TISo there are outer brackets and a
/TI at the end. I am not interested what is inside the brackets, as long as there is a /TI.It becomes tricky with the following strings:
(abc OR (def AND GHI) )/TI( ( abc AND JKL) OR (def AND GHI))/TI( ( ((abc AND JKL) OR (def AND GHI) )) )/TIIs there any easy solution using parse?
Thank you in advance.
@AndreasWagnerBerlin Please be more specific:
1) Do you expect just logic return or collected output?
2) What result do you expect in your last case
3) Can
1) Do you expect just logic return or collected output?
2) What result do you expect in your last case
( ( ((abc AND JKL) OR (def AND GHI) )) )/TI?3) Can
/TI occur inside and outer parens be without ending /TI, e.g. ( ( ((abc AND JKL)/TI OR (def AND GHI) )) )?
@toomasv Sorry for the confusion. I try to be more specific as follows:
re 1) logic return (true or false) would be fine
re 2) I expect a
re 3) no, the
re 1) logic return (true or false) would be fine
re 2) I expect a
true as return because the case fulfills the pattern ( ... )/TI and the brackets are balancedre 3) no, the
/TIshall not occur inside a larger pattern
Also:
source: trim/lines {
(abc OR def)/TI
(abc OR (def AND GHI))/TI
((abc AND JKL) OR (def AND GHI))/TI
((((abc AND JKL) OR (def AND GHI))))/TI
}
state: reactor [
counter: 0
bump: func [delta][counter: counter + delta]
balanced?: is [zero? counter]
]
rule: [
some [
some [
#"(" (bump +1)
| #")" (bump -1)
| not "/TI" skip
]
"/TI" if (balanced?)
]
]
probe parse/case source bind rule state
@AndreasWagnerBerlin if you could add the pattern and solutions to https://github.com/red/red/wiki/Parse-Cookbook, that would be great. Thanks!
Both solutions are important, because leveraging
load is always a win, but sometimes data is not loadable. Matching brackets is also fairly common.