[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] Action output?
|
kenneth@xxxxxxxxx wrote:
Dang, I just realized something...
Given the current workings of the perform command, we can't have a
--output flag that does things the way just discussed. The reason is
that we have previously said that all properties defined is sent to
all actions. This means that *all* actions would see a
'buckminster.output' pointing to the same location...bad.
Is it? That's what I would have presumed anyway.
With my suggestion, the problem wouldn't be exactly the same since the
name of the actual property could then be much more specific and with
a reasonable chance not be interpretable by other components/actions.
Still, I now think I don't like that either - far to great a chance
that a property name is used by different actions for different
things; we pollute everyone's namespace.
I think we must come up with a way to qualify properties so that they
can be sent only to one, some or all actions. Yes, this can make a
command line really horrible, but there's no real alternative to
satisfy this problem.
Yes there is. We simply state that if you want different properties (or
output) for different actions, then issue multiple perform commands.
Well there is - maybe we should come up with a persisted xml format
that provides a 'command line' (i.e. so we'd be able to say 'perform
<pfile>' rather than a long and bulky commandline. Perhaps there
should be a way to do the bulky commandline also - in which case the
'pfile' could just be a commandline more nicely formatted in a file.
But a nice editable xml format is always nicer and could then be used
in the UI too as a quick way to load complete settings for a 'invoke
action' dialog.
Thoughts?
I prefer the KISS principle and user-friendliness in this case. The
use-case you are concerned about is not very common and it's no big deal
to issue more then one command when the need arises.
Regards,
Thomas Hallgren
