Gary Shea wrote:
On Mon, 11 Nov 2002, at 11:03 [+0100], Stephen McConnell ([EMAIL PROTECTED]:
Gary:
Just a note - in a couple of hours time I'll be making some commits to
the excalibur/meta package. These commits extend the overall meta model
from the type level to include profiles of types (collecting
configuration, context directives, logging derictives, etc) together in
a single class. Understanding excalibur/meta is the first step to
understanding excalibur/assembly (Merlin 2). The meta additions are a
slimed down sub-set of the Merlin structures - I've basically sperated
out the container side from the component profile ensuring the widest
possible application.
Good timing, while I was deciding last week whether to build my own
deploying service (so I'd know how it worked!), I was considering the
same issue.
I don't know what I think about 'slimed down' structures... perhaps a
little soap and water is in order...
:-)
BTW - if I get a moment tommorow I'll take a look at that doc warning.
Cheers, Steve.
Gary
More on that after the commits are in.
Cheers, Steve.
Gary Shea wrote:
Hi Steve --
Just wanted to warn you of the upcoming wave of questions... I've set up
a fork of my current development to see if I can bring merlin2 in. Will
start first thing Monday.
This code has quite a few layers of containment. There's the overall
app which is a containder for a variety of asynchronous services in
constant operation (UI, order submission, order status updates, product
set update, etc.). The UI is a container, the UI representation of the
sets of orders and products are each held by subsidiary containers, the
UI representation of the set of items associated with each order is held
by a per-order container, as are the UI representations of the drawings
associated with each order. The Swing UI component tree is constructed
in Context space, hopefully that's the right way to go, and the
dependency tree is now (or can readily be persuaded to be) automatically
traversed.
Much of this code is currently componentized and hand-lifecycled, with
configuration built from xml strings in the code. Ugly, but at least I
can hold in my head how it all fits together!
I'm going to spend some time tomorrow doing a review of the most recent
definitions I can find of stuff like what a container is (I seem to
recall, not so long ago on the -dev list, an in-depth discussion that
semi-formalized the notion of container), etc, all the fine points that
I will need to have in mind in order to even begin understanding the why
of merlin's design.
Wish me luck!
Gary
--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
