Intro

• patches vs. plugins
• classic scenarios:
• object orientation
• accessing external libraries
• indexing gau
• spectral nodes
• recursion
• gui plugins
• game logic
• same need for good modularization/specification of IOs as with patching
• at the moment more convenient to textually code with real vector types + correct spreading of complex datatypes.

Sample I: ConnectAll < MaxDistance

• showing renderer of goal
• talking about algorithm
• patch it..indexing gau
• the templates
• cloning value template
• evaluate method
• for in for loop
• add inputpin

The code framework

• usings (references)
• namespace
• class (implementing interfaces)
• evaluate, ..
• fields, pins
• plugininfo attributes
• pins: types, attributes (subtypes), slicecount, accessing individual slices, modulo
• importing stuff: hdehost, pluginhost, logger
• evaluate/auto, spreadmax
• of projects, documents, references

Libraries

• compare node-library
• the utils library
• the .net library
• .net3.5 class library reference

the .NET Framework is:

• Common Language Runtime – provides an abstraction layer over the operating system
• Base Class Libraries – pre-built code for common low-level programming tasks
• Development frameworks and technologies – reusable, customizable solutions for larger programming tasks
• other libraries

Sample II: particle

• adding a particle class in a separate file

Debugging

• beep
• logger
• sharpdevelop

Sample III: version control

• start working from an existing plugin
• checkout
• contribution vs. addonpack
• commit/contribution