This is one of TimLegant's pages, not mine, so ignore it unless he resurfaces. I am adding my thoughts to TmdaOneDotTwoTodoList instead. -- JasonMastaler (2006-09-16 06:55:56)


This page is an overview of (and sometimes a rationale for) the internal design of TMDA moving forward from TMDA v1.0. The primary point of these choices is to enable the TmdaOneDotTwo features. We want to reorganize the internals of TMDA so that third-party utilities can more easily use core TMDA facilities. We want to eliminate redundant code by combining multiple code fragments performing similar tasks into single, more general interfaces.

Discussion related to any topic here should take place on the tmda-workers list. Expect this page to be reorganized and updated based on discussions that take place there.

1. General

These are areas that will affect more than one part of the design. They are grouped here for background and as pre-suppositions for some of the following ideas.


TmdaOneDotTwoDesign (last edited 2006-09-16 06:58:13 by JasonMastaler) Logo