> > Suppose I redid those 6000 words of text in (say) make-doc format. And > > embedded in them was a "click-stream" to run the application, add data, > > scroll, etc; and then capture the screen image and insert it in the > printed > > document. > > What a wonderful idea! I'd say everyone that uses Rebol/View would love it. > It seems to be to be very closely related to those training wizards that > demonstrate the actions and the results. It is probably also closely related > of those recruitment tests that meaure a user's performance in completing a > task in an application.
I agree. And would bow deeply ;-) <....> > Another alternative, ratbag idea, is to write a brute of a program that will > take a layout and replace every action function it can find in the layout > (all the way down) with a new function that (a) fires some recording event > and (b) calls the original action. The problem with this is what scheme can > be used to identify the action recorded so it can be saved and loaded later? > Your name idea might be useful here. I wonder if there are others - path to > face? Isn't it better to change the behaviour of View there? Make an action2 field that contains the action field, and set the action field to [record action2], where record records and does action2. Or is this what you mean? My 0.02 eurocents ;-) -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
