<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<style type="text/css">body{margin-left:10px;margin-right:10px;margin-top:0px;margin-bottom:0px;}</style>
</head>
<body marginleft="10" marginright="10" margintop="0" marginbottom="0">
<font face="Geneva" size="+0" color="#000000" style="font-family:Geneva;font-size:10pt;color:#000000;"><b>"Garrett Smith" wrote:</b><br>
<br>
</font><span style="background-color:#d0d0d0"><font face="Geneva" size="+0" color="#000000" style="font-family:Geneva;font-size:10pt;color:#000000;">I'd see this being something like a ValueChangedEvent that specified the<br>
object, schema, field name, old value, and new value. This would be a<br>
nice way to bolt on validation without modifying the schema.<br>
</font></span><font face="Geneva" size="+0" color="#000000" style="font-family:Geneva;font-size:10pt;color:#000000;"><br>
Yes, that's exactly what I need for versioning.<br>
<b><br>
</b></font><span style="background-color:#d0d0d0"><font face="Geneva" size="+0" color="#000000" style="font-family:Geneva;font-size:10pt;color:#000000;">Anyone needing more information in ObjectModified can just create a new<br>
event type with the additional info. This seems application specific to<br>
me.</font></span><font face="Geneva" size="+0" color="#000000" style="font-family:Geneva;font-size:10pt;color:#000000;"><br>
<br>
But there is a major problem: How can you reuse an existing infrastructure then? You have<br>
to write all editing views or other components that modify the content objects anew. <br>
In my view ValueChangedEvents are usefull in many applications and for<br>
many purposes (reindexing catalogs, updating views in standalone applications, triggering<br>
external processes etc.). Would it be too much overhead to have them in the framework from <br>
the beginning?<br>
<br>
Uwe</font>
</body></html>