The SharpHog Southern Pine Beetle Infestation Model and the related Spot-Growth Database Project were developed with eventual deployment online as the goal from the outset, and both are fully capable of flexible web deployment as they are right now.

The specific logistical requirements for various incarnations an online implementation of the SharpHog model or Spot-Growth Database deserve further exploration.

As the programmer of the two projects I have a special relationship with their capabilities and features--I love them all.  That's why when I wrote the desktop applications for interfacing with the model and database, I included a button or checkbox or tab or textbox for everything.  But any online implementation would inherently be exposing a subset of these features to the online user.  I wrote the desktop application for the power user, but it is neither advisable nor required to expose such power to the non-administrative user.

These matters concern the interface to the user and the interface to the administrator.  I don't mean to say I couldn't create whatever tools might be useful for such an online implementation, I just mean that if I'm going to spend the time, those tools should be specifically defined, designed, and requested by the people who will be using them.

But the two projects can also be implemented as web-services, which are online applications that exchange data much like a browser requests web-page html, but instead the messages are instructions for running the model or manipulating the database.  This approach achieves true platform-independance for the projects, meaning that although they must be hosted on a machine with the .NET Framework, other online applications, hosted in other environments, can interact with the model or database via pure text-strings (structured as ubiquitous xml).