On Sun, Feb 26, 2012 at 10:58 AM, Gustaf Nilsson <[email protected]> wrote: > Aloha > > Ive finally switched to devving on pyjd, long overdue i know. Mainly > because i had the impression it was really difficult to get going, but > it turned out to be super easy (on windows).
yes. bloody ironic isn't it. one other dependency - a small python package (python-comtypes) and err... that's it. all the problems are actually related to the *free software* pyjd ports, due to the webkit _and_ the mozilla teams completely not getting it. > I might update/rewrite > the wiki to make it look as easy as it is. > > Anyways, are there any tips and tricks for pyjd? remember that it's still a browser engine. you're still constrained by XSS. and don't be tempted to go "oh lookie! i can do python! i can now put in threads and all sorts of shite into the application!" in other words, make damn sure that you still keep the application split across client-server (HTTP, AJAX and JSONRPC) principles. in other words, the MVC paradigm _still_ applies. don't be tempted to do the same kind of stupidity that you normally see in gui applications. > For example is there a way to get firebug-like functionality so i can > see network traffic and play around with css in realtime? you'll need to look up if that's even possible with the Trident Engine. but there's nothing to stop you creating a css "play around" system, in python. l.
