On Wed, Mar 06, 2013 at 06:22:02PM -0800, tim Rowledge wrote:
> 
> On 06-03-2013, at 5:32 PM, "David T. Lewis" <lewis at mail.msen.com> wrote:
> > 	^#(
> > 		#(	"internal plugins"
...

> > 		)
> > 		#(	"external plugins"
...

> > 		)
> 
> Crikey. I don't recognise half of those.
> 
> It does raise another interesting question; why internal? Why external? Given the option, what makes a good reason for either option?
> 
> On RISC OS I simply make everything external because it makes my build simpler and has no cost in space or performance. What about other platforms?

It probably makes no real difference at all, aside from packaging. Internal
plugins reduce clutter in the installation directory. External plugins can
be easily excluded from the runtime environment. For example, OSProcessPlugin
should be external so that it can be deleted if security is a concern.

IIRC, BitBltSimulation and BalloonEnginePlugin need to be built internal, but
aside from that all plugins can be either internal or external at the discretion
of the VM builder.

Dave