On Thu, Aug 16, 2012 at 5:52 AM, C Anthony Risinger <[email protected]> wrote: > On Tue, Aug 14, 2012 at 3:34 AM, C Anthony Risinger <[email protected]> wrote: >> On Mon, Aug 13, 2012 at 5:13 AM, Rene Maurer <[email protected]> wrote: >>> On 08/12/2012 at 19:08 C Anthony Risinger <[email protected]> wrote: >>>> On Sun, Aug 12, 2012 at 4:40 PM, C Anthony Risinger <[email protected]> >>>> wrote: >>>>> >>>>> i'll cook a small patch to fix then you can try again. >>>> >>>> i've corrected this now, but the link itself may still break ... this >>>> would have been a long-standing problem though and unrelated to the >>>> current issue. >>>> >>>> please test again! >>> >>> Yes! yes! yes! >>> >>> I have now: >>> >>> from pyjamas.ui.Calendar import DateField :: Working. >>> >>> from app import App :: Working. >>> >>> Even more: >>> >>> After (more than one year?!) i can start my real world application with >>> pyjd again! Of course there is a crash when calling GetXMLHttpRequest() >>> (as this is not yet working) but i can see the welcome screen :) >>> >>> This is an enormous step forward for pyjd, the desktop version! >> >> hooray! that's fantastic news :-D >> >> it seems i was a bit too optimistic in thinking i'd finish this >> weekend (wedding to attend among other obligations ...) but i still >> expect to wrap up GetXmlHttpRequest() in the next few days. the >> Timer() stuff i think will be simple enough ... i just haven't >> actually tried/confirmed yet. >> >> so ... TBC ... > > woo hoo! we have 100% working Timers and Intervals. > > it's implemented a little funky, [temporarily] relying on JS to create > the Timers, but still cancelled from python (i have > clearTimeout/clearInterval available, but not setTimeout/setInterval > ... bug for sure). > > however, i figured out a really badass/robust way to marshall > objects/data back and forth between python and JS ... so i may end up > implementing XmlHttpRequest this way too ... basically i add a single > node to the DOM, get a reference from BOTH python and JS, THEN > disconnect it -- the disconnected tree can still receive events and > stuff, is unlimited in size/structure, and ultimately functions like a > private channel between my objects. a little hacky, but still pretty > elegant IMO. eventually the gobject stuff will be fixed proper, but > it's not that critical for the time being. > > note: the work needs to be cleaned up a bit so i have not yet pushed > to Github (100% working, but code needs to be moved elsewhere). > updates should be published tomorrow.
Timers impl is feature complete and pushed to `feature/giwebkit`. if someone can spare a few minutes, i'd be very grateful to receive some feedback/tests on it (esp. regarding the TODO, see library/pyjamas/Timer.giwebkit.py). XmlHttpRequest() can now be focused on in entirety, as the final obstacle; once this lands and i'm reasonably satisfied with it's stability, it'll be about time to cut a release ... there have been many many updates since May. so, if there is anything you want to see in a 0.9.0 release (or possibly `2012.09.01` if we do time-based versions), please open some tickets and start some discussion! thanks, -- C Anthony --
