> Is it that you do not want to copy/paste a single line to each of your
> forms?
>
> [session create economy.transaction.{=value}]
Not exactly, no. If I could reduce the commands to one page, that
would be great. However, most of the pertinent data are stored as data
variables. What I wanted to do is almost exactly like this:
[session target ekonomi.transaktioner.#]
[session savedata {ekonomi.transaktioner:datalist}]
Which makes sure that all of my transactions carry the same format.
> > Question 2: How would you guys create a custom form script?
>
> You could do that with a script. You could place the script into the
> footer of the page with your form. If the user creates the data value
> that you want to store on your economy.transaction.# page you can try
> this:
> - let the user work on the form and store the data on the page
> - force reload (nextpage {p} ) and let the script in the footer grab
> the values stored on the page
Storing values in a page strikes me as unsafe from a threading
perspective, unless the page reload is atomic in regard to the
savedata. It might be, i dunnu, but my assumption has been that the
nextpage triggers the browser to make a seperate request.
I know the chance of failure is 1 in a million, but the system i'm
trying to make is eventually going to be linked to our official
accounting system.
I gnerally don't like using forward and nextpage, but for some things
I've had to cave since there doesnt seem to be a good way to store
variables as the boltwire code executes. I need in page list
generation, am I the only one?
> Just an idea.
Thank you, feeback is *always* good :)
>
> > Question 1:
>
> Site.embed pages are a kind of free zone where you can put whatever in
> it and it does not interfere with boltwire shortcuts and commands.
> That is what I use them for. If you want to use embed code in your
> form you have to write html, javascript or similar.
So no boltwire markup is done on them, and normal pages are stripped
of form markup out of security issues, so embedding a form or part of
a form on a page is almost impossible...
OK, I'm tired of creating a new topic just because I have a new topic
to discuss, as I feel like I'm spamming the board completly, so here
goes:
I find myself wanting to generate a list of text fields based on the
existence of pages in a group
[[#generator]]
[(template first)][form]
[(template each)][text {+p4} {?{+p4}}]
[(template last)][form]
simply enough. BUT.
{?{+p4}}
doesnt work, as the '?' markup doesnt accept inner variables.
I tried to extend the markup table by adding this to the end of my
index.php:
MarkUp('vars', 'request', '/\{\?{+([.a-zA-Z0-9]+)}\}/e',
"htmlspecialchars(\$_REQUEST[BOLTvars('$1', "$zone")], ENT_NOQOUTES,
'UTF-8')");
This doesnt work, which makes me a sad panda. Help?
While getting at default values in my text field isn't the most
important thing ever, generating a list of get-variables that
constitute entries whith non-empty text, IS. As such, I'm stuck with
this problem now or later.
Is there a way to dynamically generate get variables already, or must
I find some way of adding this?
Why doesnt my markup work? It's pretty! All pretty code should work.
There should be a law.
I guess what I'd really want is something more on the lines of
'/\{\?{([^\n]+)}\}/e'
\$_REQUEST[rerun bolt markup('$1')]
but I'll settle for anything.
If only function markup would work, but I tried storing the value of
+p4 into a counter and displaying that, and it just gave me {?4001}
(since, of course, '[' is an illegal value :()
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
