avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berin Loritsch" <blorit...@apache.org>
Subject [Proposal] Minor config change--ease of use
Date Fri, 07 Jun 2002 19:13:35 GMT
I would like to add one method to the Configuration object to help make
using it a bit easier--or at least DefaultConfiguration.  It is the
addition of a branch() method.  The purpose is to create a new branch
of the configuration tree with a new name.

The need came up with using a C++ version of the Config object, and I
a templating library that I am converting to a new format.  I believe it
will become useful when we move to Java.  The change is relatively
and it does not have to alter the interface.  It can be a function of
DefaulatConfiguration object.

Configuration newBranch = config.branch("new-name");

I have a legacy template library that only captures a little bit of the
overall print page.  The printed strips have a header, and several
It needs to add in support for new strip types, and more controlled
of elements.  As a first step, I converted the loading scheme to create
a Configuration hierarchy.

After I create the legacy Strip template, I have to replicate all the
into new child configurations that are essentially the same--with the
that the root name is different.  Something along these lines:

Configuration family = processFamily(...);
Configuration strip = processStrip(...);


This frees me from being forced to do a lot of otherwise complex logic
at this

Do others think that this would be useful?

"They that give up essential liberty to obtain a little temporary safety
 deserve neither liberty nor safety."
                - Benjamin Franklin

To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>

View raw message