Sunday, April 27, 2008

97k demo program

http://www.shamusyoung.com/twentysidedtale/?p=537

This blog describes a 97k game demo program. He writes that procedural programming helps make the game look good while keeping the usage of space minimal.

Sunday, April 20, 2008

more python information

http://socal-piggies.org/scp

There is a SoCal Python users group and they had a meeting at Disney in LA about how it is used by their animation people.

comp.lang.python

This newsgroup had some information about GUI kits.

They mentioned Qt & PyQt, wxPython, and Tkinter.

Thursday, April 17, 2008

python development continued

I found some links related to Python development with an IDE and a standalone debugger:

http://spyced.blogspot.com/2008/04/python-ides.html

http://prabhuramachandran.blogspot.com

I'm not sure where to start yet. There's idle and scite to keep it simple. Eclipse could be an option too because I've used it for some Java development before. Finally, some one at the first link commented about looking for an ide with a good gui designer. That sounds like it would be useful.

Sunday, April 13, 2008

Python related to computer graphics

I was given some Python related information about computer graphics.

After some more looking around, it turns out 3d buzz has some information about using it for scripting in Houdini and Maya, but it is not free.

Also the python.org site has an article about ILM using the language.

From the article it mentions how some companies developed their own software as an insurance policy for the future because of the possibility of needing custom extensions or improvements.

Basically, it sounds like they gradually used it for their toolset:
"As Python was applied in more ways, it slowly crowded out a plethora of competing technologies for shell scripting and batch control, embedded scripting, component software development, database application development, and so forth. Python's versatility ultimately simplified the developers' toolset and reduced the number of technologies that needed to be deployed to ILM's thousands of production computers. This new, simpler toolset translated directly into an easier to manage and more reliable development and production process."

So it does sound like they used it as a "glue" for their various software assets.

Saturday, April 12, 2008

Code metrics in Visual Studio 2008

MSDN blog entry about code metrics in Visual Studio 2008

Some other blogs have commented about this already. For example, here is an entry from a guy in Russia.

The blogger warns about problems with the lines of code metric. I was just reading Code Complete about the topic. The guideline given there is to limit the number of lines of code per routine to around one screen or one or two pages of program listing, or about 50 to 150 lines. He warns against routines longer than 200 lines and notes that there has been some inconclusive research on the quality of routines less than 200 lines. I've also heard of another guideline that an entire class should be less than 300 lines.