On Tue, Oct 23, 2012 at 8:32 AM, Vsevolod Fedorov <[email protected]> wrote: > On 10/23/12 13:35, C Anthony Risinger wrote: > > Ajax calls under hulahop are not working any more! > They are working when called from user interaction (such as clicking > button), but not when called from timer or on application startup. > > is this still relevant/failing? > > Yes, nothing is changed. > > > what is the use case for using the > browser engine before entering the mainloop (run)? this detail has > been a pain point on so many levels that it may very well disappear to > support further growth... the engine should really not be used until > mainloop is running. > > My use case: first ajax call is made immediately on application startup, to > request initial data from server. > I can postpone this initial ajax call until pyjd.run() is called, if this is > what you mean. I can make a timer with short interval, and make ajax call > from it. But I need ajax working from timers then...
well if we were to move away from the __name__ == __main__ business, you would receive an "ignition" event so-to-speak, so you could do initialization there. way may be able to keep the __main__ stuff, and instead require something like: python -m pyjs ./myapp [...] ... not sure yet, need to investigate solutions. > are timers failing only when started early, or do they fail always? > > Ajax calls from timers always fail. > > I opened issue#778 for this: > https://github.com/pyjs/pyjs/issues/778 > with ready-to-use examples/tests. excellent! we'll go from there. thanks much Vsevolod, -- C Anthony --
