On Monday 05 January 2004 19:57, you wrote:
<snip reason="sounds good" />
> Maybe you could give just a initial "wish-list", so that some of the
> eggs are out of your brain :-)
Let's start with a "small" list (and no guarantee that the eggs are not
rotten).
More eggs follows later.
<chicken instance="niclas" >
<egg>
<title>Repository Browser</title>
<description>
I have started this. The GUI part is "kind-of" working but requires
improvements. should be made.
</description>
</egg>
<egg>
<title>Maven Repository Browser Plug-In</title>
<description>
The Repository Browser has a extension point defined, so that additional
repositories or "views" of repositories could be browsed. The Maven is the
first, but it is VERY CRUDE in its info, so I was planning to put in RDF
which DESCRIBES a Maven plugin, and the Repository can read.
</description>
</egg>
<egg>
<title>Component Packaging</title>
<description>
Currently, there is no official way to "package" a component for
publishing. All components now are too "code-centric" and doesn't go beyond
that, into the land of user accessible items.
</description>
</egg>
<egg>
<title>Specification Wizard</title>
<description>
I strongly believe in the separation of Interfaces from Implementations.
A lot stronger than Stephen (newly convert), and that the development cycle
for Specification is somewhat different from the Implementation.
Specification doesn't have UnitTests, it has Compatibility Tests, which
should "follow" the specification to the Implementation phase.
</description>
</egg>
<egg>
<title>Implementation Wizard</title>
<description>
The Implementation wizard asks for an Implementation to create the
skeleton for, and will generate quite a lot automatically, including the runs
of Compatibility Tests as well as Unit tests. And much more...
</description>
</egg>
<egg>
<title>Application Wizard</title>
<description>
This guys creates the Application project, which probably shouldn't have
any code at all (perhaps some glue), but where the top level block.xml
(basically) is tied together, with the Merlin runtime and even allow that it
is packaged fro distribution as a single entity (Merlin included).
</description>
</egg>
</chicken>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
