Move templates to their own directory structure.

Move templates to their own directory structure.

Templates are now looked up on a set of paths in the 'templates' directory.
This should be versatile enough to have separate templates for dom and
html and have some shared templates too.

BUG=
TEST=

Committed: https://code.google.com/p/dart/source/detail?r=3268

[vsm, 2012-01-12 23:42:20]

LGTM, but I think wrapping_dom.darttemplate should be the wrapping directory,
not the interface one.

Perhaps interface.darttemplate should be in the interface dir?

Also, consider eliminating wrapping_ and interface_ as they are redundant with
the directory names.

[sra1, 2012-01-13 00:25:20]

On 2012/01/12 23:42:20, vsm wrote:
> LGTM, but I think wrapping_dom.darttemplate should be the wrapping directory,
> not the interface one.

This reflects what templates we were actually using during generation.

The wrapping dom entire package is produced from the interfaces and the
implementation.
It is a variant of that weird convention where the interface library imports an
implementation, but in this case the impl lib is flattened into the interface
lib.

I'll see of the implementation can be made 'dominant'.  It will then have to
reach into the interface 'System' to get the classes that define what the whole
library is, which also feels weird.

> 
> Perhaps interface.darttemplate should be in the interface dir?

I expect to move it up and share it with html.


> 
> Also, consider eliminating wrapping_ and interface_ as they are redundant with
> the directory names.

Sure.  But I think the frog generator with interfaces might need templates for
both interfaces and classes in the same lookup path.  Depends on how we deal
with static methods - we might have to make some 'classes' be classes and other
interfaces.