Looks like this is going to have to be done with components. Didn't know until today that they even existed. Thank you chapter 13!
On Dec 24, 3:53 pm, weheh <[email protected]> wrote: > Argh. I'm struggling. The third arg to web2py_ajax_page is data. If > I'm ajaxing a multi-field form, can I make this > data=['field1','field2',...]? I'm trying it but it doesn't seem to be > working. > > On Dec 24, 1:36 pm, mdipierro <[email protected]> wrote: > > > The general solution is web2py_ajax_page in my previous example and > > return js using response.js. > > > On Dec 24, 11:22 am, weheh <[email protected]> wrote: > > > > Yes, I do have an ajax generated by code inside another ajax. But I'm > > > not married to that approach, especially if it doesn't work. I'm just > > > looking for anything that works -- doesn't have to be pretty. > > > > Bottom line, we need a general solution to this problem. User clicks > > > an ajax-ified widget/link/whatever. This generates a job-queue entry > > > and a callback. Callback checks status of job and returns one of two > > > responses. If job finished, returns final view. If job not finished, > > > returns wait message and ajax countdown to check queue status again > > > after prescribed time period. > > > > I've cracked my skull on this problem now on two different occasions > > > over the last 3 months. On many attempts, I feel like I've gotten > > > close, but in the end have made zero progress. As I said, this is > > > mission critical to my app, so any help is much appreciated. > > > > On Dec 24, 2:22 am, mdipierro <[email protected]> wrote: > > > > > Do you have an ajax generated by code inside another ajax request? > > > > I believe SCRIPT(...) is returned but never executed for the same > > > > reason as in your code at the beginning of the thread: <script>...</ > > > > script> inside ajax content are ignored by the browser. > > > > > On Dec 24, 12:16 am, weheh <[email protected]> wrote: > > > > > > Problem with my example above is that the setInterval is not being > > > > > executed after the callback. > >
