Giacomo Pati wrote: > > Sure, no problem. How should it be named? > What does it do? :)
> Someone mentioned Crons JobScheduler as it has a fireJob() > method that could do it but would we want the cron block go > into the core? > Hmm, I think this depends on the effort it takes to create it. If we have to add/maintain 10 classes with hundreds of LOCs, I would say, let's use Cron - but if it is a simple class, we should imho avoid the dependency for the core. > > But why do we put it into the Context? Wouldn't it be > better to make a > > simple component out of it? > > It dosn't matter for me as long as a flow script ca do > .setupObject( foo ) and foo is able to get it. > Great :) Carsten
