Skip to Content.
Sympa Menu

notify-dpml - svn commit: r2282 - development/central/site/src/docs/about/notepad/freight

notify-dpml AT lists.ibiblio.org

Subject: DPML Notify

List archive

Chronological Thread  
  • From: mcconnell AT dpml.net
  • To: notify-dpml AT lists.ibiblio.org
  • Subject: svn commit: r2282 - development/central/site/src/docs/about/notepad/freight
  • Date: Thu, 14 Apr 2005 18:08:12 -0400

Author: mcconnell AT dpml.net
Date: Thu Apr 14 18:08:09 2005
New Revision: 2282

Modified:
development/central/site/src/docs/about/notepad/freight/development.xml
development/central/site/src/docs/about/notepad/freight/observations.xml
development/central/site/src/docs/about/notepad/freight/recommendations.xml
Log:
housekeeping

Modified:
development/central/site/src/docs/about/notepad/freight/development.xml
==============================================================================
--- development/central/site/src/docs/about/notepad/freight/development.xml
(original)
+++ development/central/site/src/docs/about/notepad/freight/development.xml
Thu Apr 14 18:08:09 2005
@@ -222,8 +222,8 @@
component type we want to use. The <code>&lt;context&gt;</code>
element contains all of
the information describing the fulfillment of the components
dependencies. In the above
examples this is limited to the supply of an instance of Dimension.
The solution employed
- above is to create a simple constructed object using the
DimensionValue are defining the
- constructor parameters.
+ above is to create a simple constructed object using the
DimensionValue class by declaring the
+ classes constructor parameters as nested &lt;param&gt elements.
</p>

<p>
@@ -236,8 +236,8 @@
A second and equally important aspect of the above is that we have
removed any notion
from the component as to how the dependency is resolved (compared to
classic Metro where
dependencies were distinct from context entries). To demonstrate this
point, we could
- modify the above <code>&lt;component&gt;</code> to include an
alternative solution
- to the dimension dependency using a component strategy.
+ replace the above <code>&lt;value&gt;</code> with an alternative
solution using a
+ component strategy.
</p>

<source><![CDATA[
@@ -246,13 +246,7 @@
type="net.dpml.composition.testing.ExampleComponent"
name="demo">
<context>
- <component key="dimension"
- type="net.dpml.composition.testing.DimensionComponent">
- <context>
- <value key="width" value="12"/>
- <value key="height" value="100"/>
- </context>
- </component>
+ <component key="dimension"
type="net.dpml.composition.testing.DimensionComponent"/>
</context>
</component>
]]></source>

Modified:
development/central/site/src/docs/about/notepad/freight/observations.xml
==============================================================================
--- development/central/site/src/docs/about/notepad/freight/observations.xml
(original)
+++ development/central/site/src/docs/about/notepad/freight/observations.xml
Thu Apr 14 18:08:09 2005
@@ -102,6 +102,12 @@
<li>This should be moved down to Transit as part of the
net.dpml.transit.repository package.</li>
</ol>
</li>
+ <li>general observations on Magic
+ <ol>
+ <li>get some experience in on using links in
Transit/Magic/Metro </li>
+ <li>rebuild magic's index/module as this is currently Magic's
weakest link</li>
+ </ol>
+ </li>
<li>model serialization
<ol>
<li>model serialization is not implemented yet</li>

Modified:
development/central/site/src/docs/about/notepad/freight/recommendations.xml
==============================================================================
---
development/central/site/src/docs/about/notepad/freight/recommendations.xml
(original)
+++
development/central/site/src/docs/about/notepad/freight/recommendations.xml
Thu Apr 14 18:08:09 2005
@@ -10,20 +10,28 @@
<subsection name="Recommendations">

<ol>
- <li>consolidate current development and try to integration of FT
within classic</li>
+ <li>integration of FT within classic</li>
+ <li>consolidate current FT codebase (see <a
href="observations.html">issues</a> list)
+ <ol>
+ <li>update metro logging as a JRE system extension</li>
+ <li>resolve execution/management semantic model</li>
+ <li>add testcases in the composition builder and control
packages</li>
+ </ol>
+ </li>
<li>get a final number build of metro classic out the door on the
basis that the build will also mark freeze of the classic codebase</li>
<li>shift FT code into the main Metro development strategy
- <li>build task enhancement</li>
- <li>lots more testcases</li>
- <li>added tools and utilities</li>
- <li>trials on active deployment into a running metro
instance</li>
- <li>start thinking about IDE support for component patterns and
pattern validation</li>
+ <ol>
+ <li>code cleanup (removal of code not used by FT)</li>
+ <li>added tools and utilities (e.g. type and part
viewers)</li>
+ <li>migrate planet components to FT</li>
+ <li>trials on active deployment into a running metro
instance</li>
+ <li>start thinking about IDE support for component patterns
and pattern validation</li>
+ <li>complete non-critcal FT featues</li>
+ <li>take care of weakness in the Magic index/module
implementation </li>
+ <li>FT documentation and tutorials</li>
+ </ol>
</li>
- <li>rebuild magic's index/module logic somewhere along the
line</li>
- <li>completion of the FT codebase (see <a
href="observations.html">issues</a> list)</li>
- <li>migrate planet components</li>
- <li>documentation and tutorials</li>
- <li>articles</li>
+ <li>articles and media</li>
</ol>

</subsection>



  • svn commit: r2282 - development/central/site/src/docs/about/notepad/freight, mcconnell, 04/14/2005

Archive powered by MHonArc 2.6.24.

Top of Page