Update of task #3664 (project savane):
Should Start On: => mercredi 01.11.2006 à
00:00
Should be Finished on: => vendredi 08.12.2006 à
00:00
Category: None => Web Frontend
Priority: 3 - Normal => 2 - Low
Status: None => Postponed
For/By: None => CERN
_______________________________________________________
Follow-up Comment #3:
Some thoughts about this:
== option 1: ==
independant lock :
if field X = Z then lock field A
== option 2: ==
lock tied to transitions :
transition A => B allowed/forbidden if field X = Z.
or
transition A => B allowed unless field X = Z
field D = X
option 2 seems more powerful and secure (to avoid lockin situations) but
source of more headaches to be developped
maybe option 1 is the way to go because it probably covers users needs,
but that's less clean and even a bit confusing (because the current
transition stuff already allows to do some lock)
/This issue seems secondary for now, so I move on other prioritary things/.
_______________________________________________________
Reply to this item at:
<http://gna.org/task/?3664>
_______________________________________________
Message posté via/par Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
