World: r3wp

to = for

Robert cool

Janko: I was planning for some very simple console-based reporting 
like: 
testing signup...
testing check-page...
### test KO : <error description>


But I'll be glad to join forces when both our approaches would be 
really usable. I didn't wrote any specification so far, I'm still 
at the idea stage. My main concern is to reduce the cost of testing 
regression for our biggest web-based apps in production.

VID: It shouldn't be that hard to adapt it.

my report is json data rebol2json and then javascript displays it 
all ,... it's all single static html file with data and javascript 
(via my jsgoo library :) )

I think I will pic-up the project in a couple of weeks again and 
push a bit forward and than it get useable.

so if your test will generate some relatively compatible data and 
if it would make sense to be presented like this we can do it

Yes, I think we could come up with a compatible reporting format.

Robert: I would be interested in using it if it works with VID and 
also support keyboard simulation (especially VID hotkeys).

Here is a snippet of a test script:

new_company: [
	dt: "Eingabe/Firmeninformationen"

	with company [
		; reset data form
		press-right a

		check note = ""

		name: 		"Test Suite Company 1"
		address:	"Teststra§e. 10"

		; should bring up an ALERT
		check-window [press a][press ok]

		; country:	"Deutschland"
		; press a

		; select sector
		check-window [press req-sector][
			sector-table: ["27"]
		]
	]
]

Robert what you describe even if for GUI app sounds somewhat similar 
too.. I also take screenshots for example , and I also need some 
methods to chech and compare the state of app , that is still totally 
missing (and many other things)

you reference the CONTEXT the test should be executed in. Then you 
can use all GUI word. Using set-word! sets the GUI widget to the 
value, state etc. (the dialect makes the most useful setting). You 
can press widgets, check values in widgets (fields, tables, check, 
...) You can even use different paths depending on results.

company_tbl_test: [

	company_tbl: [61 "GFA-Motoren"]

	check company_tbl = [61 "GFA-Motoren"]
]


First line sets a line in a table, second line checks if the selected 
value matches.

Robert, maybe it should be the right time to switch to a "Testing" 
group (surprinsingly, there's no such group yet), we're going too 
OT.

ok

<SNAP!> and doc cracks the whip !!

;-)

Max, that sounds too hard, a ringing bell would be more accurate. 
;-)

I was doing a search on cheyenne the other day and came accross this. 
 Is she a relative of yours doc?   ;-)

http://en.wikipedia.org/wiki/Cheyenne_Kimball

hi doc, I'm trying to get cheyenne working on my new debian VPS. 
 so far I was able to get x11 working (thanks to henrik)  and its 
now happy about that (its not complaining about X11 anymore).

but its now complaining about libstdc++.so.5

ok cheyenne is working... sorry about being so jumpy... I did some 
googling and am now starting to understand some of the deeper linux 
administration concepts.

yess.... a glorious cheyenne built 404 page not found in my browser 
using firefox and my new VPS with shiny 6 letter domain name  :-)

now the fun part... building a new web site from scratch, using brand 
new technology  ;-)

Cheyenne Kimball: I often stumbled upon her fan pages searching for 
cheyenne keyword, pretty and talented woman.

Cheyenne's 404 : sounds like a victory scream. :-)

yes it is  :-D

doc, trying to understand the mod  'WORDS  dialect...   I am reading 
its parser, and I still don't get what the 'IN token does.  or what 
options I can use, or even why its needed.

can you give me a few pointers on how and why it should be used?

Q2:  within the mod, requests have a locals value of none, does any 
of the uniserve/cheyenne internals touch this or can I use this at 
will within any module, creating an object and appending/changing 
 attributes as needed?

in the above, I mean the req parameter sent to various phase handling 
callbacks.

Q3:  Are there any time-based call backs we can implement through 
mods?  sort of like a rate on a view face.

this would be very usefull:

-it could allow me to keep statistics on mod internals at regular 
intervals ex:  average load, high/low peaks, 

-perform cash cleanup/buildup, ping remote tools for "I am alive" 
monitors, etc.

I hope there is a simple trick I don't see at the moment:

As a result of an RSP script I want to return a new web-page that's 
on the file-system. I do it like this:

print read %payment/index.html


So far this works. What I need to do is, to insert some dynamic content 
into the read HTML file.

For this I see several options:

1. Somehow load this file as an RSP file and have it processed.

2. Somehow load this file as a SHTML file and have it processed as 
SSI file.

3. Add some marks and inser the stuff on the fly before delivering 
it.

Option 3 has the advantage, that I stay in my running RSP file context. 
On the other hand it's the "handmade" approach.

I'd say your RSP script should "be" the resulting web page; that's 
the normal way to generate dynamic pages. Why do you think of them 
as separate?

I use RapidWeaver to generate some files. And I need to inject HTML 
in one of these generated files. Hence options 1 to 3. The RSP is 
not generating the whole answer page.

Robert, see RESPONSE/FORWARD in the RSP API Reference page.

<% response/forward %payment/index.rsp %>

Q1 - WORDS dialect : this dialect allow defining new config keywords 
that can be used in the %httpd.cfg file for your mod. IN defines 
the config file sections where it can apply. Possible values are 
:
- globals : global config block used for server-wide options
- main : applies to a domain or webapp context
- location / folder : reserved for future use.

Q2 : The REQ argument is set to the current request object. If you 
get none instead of an object!, you've probably messed up something 
in Cheyenne/UniServe internals.

Q3 : Not yet. It's a planned feature that I need also to add a simple 
CRON-like task scheduler inside Cheyenne. Feel free to add your own 
in your mod, I don't that I'll have time to work on it before middle 
summer (low priority task).

thanks... wrt CRON... when you release the next version, I could 
drop that into it and send it back to you.  you don`t have to do 
everything yourself   :-D

I'd like to not do everything by myself, but it's not that easy. 
I have some deep concerns for Cheyenne core part such as speed, memory 
usage, stability and security. Cheyenne has become a *critical* part 
of our business, I have to garantee that a new version won't break 
our webapps in production, nor make them instable, insecure or noticeably 
slower. My responsibility also extends to other companies that are 
selling products or services based on Cheyenne.


I've already accepted small patches on Cheyenne core in the past, 
but it takes me a lot of time to study and test each line of code 
an rewrite them if required. If your code has only a local impact, 
I might use it, if it needs to patch a lot of parts of Cheyenne/UniServe, 
I probably won't. Anyway, you can send it to me, it's always a good 
inspiration to see how other developers solved some specific problem.

I can't disclose much right now, one of our Cheyenne based product 
is getting a lot of attention recently and in a couple of weeks, 
we will know if we need to hire a few more peoples at Softinnov. 
;-)

congrats

Actually what sort of Cheyenne apps are out there?  I don't think 
I know of any ...

Most of Janko's new products are Cheyenne based.

I don't think they're finished ...

Part of Will's company main product is using Cheyenne.