<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.2800.1505" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>All,</DIV>
<DIV> </DIV>
<DIV><BR>The MOOSE project has been working with essentially the same philosophy, with regards to normalizing the code into distinct Chunks, which make the mixing and matching very easy. Integrating services into it are very easy for example.</DIV>
<DIV> </DIV>
<DIV>I think our coding style is very much aligned with other groups, more actually than I thought a few weeks ago.</DIV>
<DIV> </DIV>
<DIV>This is a very thought provoking conversation for me too. It's getting me thinking about how to describe the MOOSE project a bit better and describe it's strengths.</DIV>
<DIV> </DIV>
<DIV>bobb</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><BR>**************** You can't be late until you show up. ***************<BR>************ You never learn anything by doing it right. ************<BR>*** War doesn't determine who's right. War determines who's left. ***<BR></DIV>
<DIV><BR>>>> Schuyler Erle <schuyler@nocat.net> wrote:<BR></DIV>
<DIV style="PADDING-LEFT: 7px; MARGIN: 0px 0px 0px 15px; BORDER-LEFT: #050505 1px solid; BACKGROUND-COLOR: #f3f3f3">* On 1-Mar-2007 at 2:11AM PST, Cameron Shorter said:<BR>> <BR>> As Chris noted, Mapbuilder is in the process of merging OpenLayers into <BR>> its codebase. This involves throwing away a lot of our original code, <BR>> but at the same time, makes Mapbuilder a more robust product because we <BR>> can focus on other areas.<BR><BR>And by that same token, we've tried very hard to make it possible to<BR>separate out only the pieces of OpenLayers you want, and leave out the<BR>parts you don't.<BR><BR></DIV></BODY></HTML>