[IPOL discuss] BM3D ready in dev. server

[Nicolas Limare]

Hi,

> > I think it would be better to reserve the "standard" methods
> > (index(), input(), wait(), run(), result()) for their standard uses,
> > and add extra methods for things specific to a demo.
> 
> My algorithm has two steps, with some user interaction in between.
> How should the two different "wait" methods be named?
> 
> It seems reasonable to name them e.g.: "wait_first" and "wait_second".
> In that case the demo has no "wait" method at all.  Is it OK?

I'd like to keep the possibility to make stats on "wait/result" in
the future. If no one is supposed to stop before the second step,
maybe we can use this pattern:

input->params->wait->run->params_step2->wait_step2->run_step2->result

-- 
Nicolas LIMARE - CMLA - ENS Cachan    http://www.cmla.ens-cachan.fr/~limare/
IPOL - image processing on line                          http://www.ipol.im/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://tools.ipol.im/mailman/archive/discuss/attachments/20110507/a7a61be8/attachment.pgp>