Clarence wrote:
>That's bad news. I was hoping we had another worker on this
>particular job. <G>

Well, I don't know for a certain who does what in Arachne Labs but I know
it aint me ;)

>Does anyone else find it inconvenient that the compose window clears
>when you pop away for a bit ?

Yes, but then you do like this:

1. Save to outbox and open the mail there to finish it off later (alreasy
suggested by Sam Heywood).
2. If you just return from something else and all fields are blank then get
(in some manner) to the big area where you wrote your text earlier. Press
F3, change .txt into .tmp and press Enter.

>Help please, Michael ! <G>.

I think he's on vacation to Italy by now (or perhaps he is in France already).

In the meantime I would suggest this as a sollution (improvments are
probably neeeded and Michael must of course code it):
When leaving any page with a form save the form in a file (form.tmp) with
all field names and the value they have. When a form is in the current file
then try and use the file (form.tmp) for it, if it doesn't fit perfectly
then don't use any of the data from it.
And once again we are back to bloatware - now all forms will be proccessed,
not once but twice, by Arachne (including reading from/writing to a file).

MailIdea v. 1.1 <g>:
A new form tag just for the mailform (<mailform> or use the Arachne tag
<arachne form>) and all data entered into it will be written to a file
(mailform.tmp). When pressing the buttons that will take effect on the form
itself (send, reset) then the file should be removed. Otherwise it will not
be wise to read it for the next (mail) form - if it did every mail would
start as the one before it requiring it to be changed/deleted by the user.
Ok, this will slow down mail processing - but also all tags found will need
to be checked against this new one (or all words in the <arachne> tag). I
do not know if everyone here thinks that's a good idea, but I can't come up
with anything better right now.

Reply via email to