On 20-05-2005 22:33, Adam R. B. Jack [EMAIL PROTECTED] wrote:
That said, I was actually refering to plugins sharing the model (as
developers share the code, via SCM) and how one plugin's efforts, setting
properties, might (in plugin's real time) communicate. Just as we trust each
other to move
Adam, I had discussions like this for years and years over in avalon land.
Enuf said! ;-)
I was thinking of the update build document[to DB] chain (say) for
ant. Once done, are all the details of the build, that documentation
used,
still needed?
Once done, don't we just exit the gump
I think in these (early days, maybe through-out the life of Gump3) the
toughest part is the property messaging protocol(s). Basically Gump3
internals are based upon trust respect between plugins -- like a good
OSS
project :-) -- but it doesn't (yet) have the internal equivalents of
Adam Jack wrote:
Leo (primarily)
oi!
Relaxed and refreshed after a week on the beach, I'm putting other concerns
aside and am taking a day for me, to tinker w/ Gump3. So, I'm digging into
the fresh code (and still consuming the rest of it.) Hopefully after today
I'll be in the zone w/ this