Talk:Triloboat

Hi Folks,

Dave Zeiger, here, originator of the TriloBoat concept. I took the wiki instructions to heart and did a 'braindump' on the content page. I realize that it needs to be deeply edited to bring it into conformity with OSE and general wiki format. Please excuse my gaffes.

Due to time and access restrictions (we're about to sail off the edge, again), I won't be able to participate often or at length. I will, however, check in as often as I can.

If you have any particular questions I can help with, please visit my site at http://www.triloboats.com or blog at http://triloboats.blogspot.com, where I have a lot of information posted, or write me at triloboats AT gmail DOT com. I'll be slow getting back to you, but unless overwhelmed by volume, will eventually write back.

Dave Z

TriloBoat Design Decision Tree?

Boat concept strikes me as a bit unusual within the GVCS, in that it is scalable and adaptable to a far wider degree than, say, the Truck or Car.

Decisions that will go into a Boat include materials, method, size, intended conditions (eg, protected vs open waters), intended purpose, and propulsion methods. It will be outfitted with a far wider range of tools, and can be 'packaged' with other tools to a far greater degree.

TriloBoat narrows the range considerably by rules-of-thumb constraining shape, but still generates a class of thousands of instances. By the time even GVCS options are factored in, the class is... um... freaking huge!

I propose that a Design Decision Tree be given OS consideration, as a means of navigating the class of TriloBoats, to assist arrival at an instance of TriloBoat.

Questions include:

• Do we want to spend time/energy on this?
• How to prioritize the tree?
• How to represent the tree?
• Can navigating the tree be computer assisted?
• How best to integrate the tree with other materials?
• Can this approach be generalized to work with other OS development?

Dave Zeiger