Comments on: Live Coding, Continued http://disruption.ca/archives/live-coding-continued/ Thu, 05 Jan 2012 09:05:54 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Richard Tew http://disruption.ca/archives/live-coding-continued/comment-page-1/#comment-20 Richard Tew Sun, 03 Sep 2006 06:12:45 +0000 http://disruption.ca/?p=47#comment-20 This isn't exactly rocket science :) Step 1: Monitor for file changes. http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/215418 Step 2: Do the required wankery to get the instances using the new versions of the classes in the changed files. You can probably register with the operating system in some more optimal way for the same events. Lunix = http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/160164 Windows = http://tgolden.sc.sabren.com/python/win32_how_do_i/watch_directory_for_changes.html We do the equivalent in the framework we use in EVE Online, and have an embedded console. It is extremely convenient, and the number of times I need to restart the server in order make what I want to do work is few and far between. This isn’t exactly rocket science :)

Step 1: Monitor for file changes.
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/215418

Step 2: Do the required wankery to get the instances using the new versions of the classes in the changed files. You can probably register with the operating system in some more optimal way for the same events.
Lunix = http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/160164
Windows = http://tgolden.sc.sabren.com/python/win32_how_do_i/watch_directory_for_changes.html

We do the equivalent in the framework we use in EVE Online, and have an embedded console. It is extremely convenient, and the number of times I need to restart the server in order make what I want to do work is few and far between.

]]> By: Charlie http://disruption.ca/archives/live-coding-continued/comment-page-1/#comment-18 Charlie Sat, 02 Sep 2006 00:25:19 +0000 http://disruption.ca/?p=47#comment-18 I don't know if you know this, but the Jak & Daxter games were written in an in-house language (imperative but with Lisp-like syntax and function call semantics) that ran in a live-coding environment. Apparently it was done by maintaining a table of function pointers and doing a lookup for every function call. Word is it was a huge win, especially for gameplay tweaking and low-level optimization. I don’t know if you know this, but the Jak & Daxter games were written in an in-house language (imperative but with Lisp-like syntax and function call semantics) that ran in a live-coding environment. Apparently it was done by maintaining a table of function pointers and doing a lookup for every function call. Word is it was a huge win, especially for gameplay tweaking and low-level optimization.

]]>