Re: [Perl-workflow-devel] Typed conditions and perl config

[Jonas B. N. <jo...@gm...>]

Hello All,

I am releasing 0.32_1 now, I have attempted to briefly describe  
everything that has happened in Changes, but I have not really had  
time to pay attention to
the commit log :-/

0.32_1 Sun Apr  6 09:02:42 CEST 2008 (update not required)

- This is an alpha release introducing typed condition, implemented by
   Jim Brandt, we are very interested in feedback on this release, so  
please
   consider joining the mailing list or send feedback to  
jo...@cp...
   directly.

- Typed conditions makes it possible for different workflows to hold
   unique methods for workflow steps even with names coliding.

   Example workflow foo and bar can have a condition baz, but baz are  
two
   different implementations in foo and bar respectively

	Updated:
		t/cached_conditions.t
		t/factory.t
		t/state.t
		t/TestUtil.t
		t/condition.t
		t/workflow_type.t
		t/config.t
		t/workflow.t

		Workflow		
		Workflow::Factory
		Workflow::Config
		Workflow::Config::XML
		Workflow::Config::Perl
		Workflow::Action
		Workflow::State
		Workflow::Condition
		Workflow::Persister::DBI
		Workflow::History
		Workflow::Persister::SPOPS

	Introduced
		t/state_perl.t
		t/TestApp/Action/TicketCreateType.pm
		t/TestApp/Condition/HasUserType.pm
		t/workflow_action_type.perl
		t/workflow_action_type.xml
		t/workflow_condition_type.perl
		t/workflow_condition_type.xml
		t/workflow_persister.perl
		t/workflow_persister.xml
		t/workflow_type.perl
		t/workflow_type.xml
		
- This release also holds new tests of persister configs, there is  
however
   always room for more

- time_zone parameter can now be passer around for use by the Workflow
   DateTime objects internally


jonasbn

On 31/01/2008, at 15.58, Jim Brandt wrote:
> Hello all,
>
> I've checked in changes for the following:
>
> * conditions can now be typed, so if you have foo and a bar workflows,
> they can implement the condition AdminRequired with the same name, but
> different code for each.
>
> * I applied all the type changes to the perl config.
>
> Other notes:
>
> * I decided not to implement types for validators because I couldn't
> come up with a case where a validator would vary by type. I mean
> 'is_number' or 'is_email_address' should be the same regardless of a  
> type.
>
> * The tests for perl configuration were very light, so most of my time
> was spent trying to add testing infrastructure for perl configs.
>
> * There was no testing of persister configs, so I added some. There is
> room for more.
>
> * I discovered that the persister configuration isn't consistent with
> the other methods. For example, in the xml, actions look like:
>
> <actions>
>   <action>
>
> But persisters don't have that outer tag level. It would probably be
> good to add it at some point, but it would be tricky to do so and not
> break things for older installs.
>
> So if you get a chance, let me know if the new tests work on your
> systems. Even better, if you have real workflow systems in a dev area,
> let me know if anything is broken there. I'm going to continue testing
> on my systems.
>
> Jim
>
>
>
> -- 
> Jim Brandt
> Administrative Computing Services
> University at Buffalo
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Perl-workflow-devel mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel