Re: [Perl-workflow-devel] Making activity configs local to workflow/state?

[jonasbn <jo...@gm...>]

Hi Jim,

Yes these files are generated when building the distribution, so we  
are not interested in having these under revision control.

./Build dist

Should generate them for you,

You could work in trunk, but a branch would be preferred if you do not  
mind.

jonasbn
--
AIM: BjonasN      Gtalk: jo...@gm...
ICQ: 62401545   MSN: jo...@io...


On 10/12/2007, at 14.52, Jim Brandt wrote:

>
>
> jonasbn wrote:
>> Hi Jim,
>> This is not a bad suggestion at all.
>> I do not think the implementation of the suggested would spoil  
>> anything it is more addition that is it changing. I have not made a  
>> thorough analysis though.
>
> I took a look and I agree, this shouldn't be too intrusive to  
> implement.
>
> I'm going to spend some time working on it and see how far I get.
>
> Can I work in trunk, or would you prefer to set up a branch?
>
> FYI, I also noticed a few files appear to be missing from the  
> subversion checkout. Got this when I ran Build on the checkout:
>
> WARNING: the following files are missing in your kit:
>        Makefile.PL
>        META.yml
> Please inform the author.
>
> Maybe these get generated as part of the CPAN upload?
>
>> jonasbn
>> -- 
>> AIM: BjonasN      Gtalk: jo...@gm...
>> ICQ: 62401545   MSN: jo...@io...
>> On 27/11/2007, at 13.30, Jim Brandt wrote:
>>>
>>>
>>> Alexander Klink wrote:
>>>
>>>> Hmmm, on second thought, this does not really increase the  
>>>> readability
>>>> of the config file - anyone with a better idea?
>>>
>>> It does seem odd that you can have multiple workflow.xml files,  
>>> each with a type, but the remaining config files are not per type.
>>>
>>> Would it be possible to support a 'global' action.xml,  
>>> condition.xml, etc., and also allow users to load a 'typed'  
>>> action.xml? From the config side, the typed version would simply  
>>> add the <type> tags to the top.
>>>
>>> Evaluation would first look for a typed definition of an action,  
>>> if available, then go to the global definition. If not there, error.
>>>
>>> I haven't looked at the guts, so I'm not sure what would be  
>>> involved to get this sort of configuration loaded, but this seems  
>>> useful. There are cases where you might want global actions, and I  
>>> agree that there are many cases where you want type-specific ones.  
>>> The same applies to conditions, I think.
>>>
>>>
>>> Jim
>>>
>>> -- 
>>> Jim Brandt
>>> Administrative Computing Services
>>> University at Buffalo
>>>
>
> -- 
> Jim Brandt
> Administrative Computing Services
> University at Buffalo
>