Hi guys,
We discussed this but I don't think we came to a conclusion.
Now, I've
discovered a real need for an object-created event that
really fires
when the object is created. I also see a good reason to have
an "object
initialised" event that fires when an object is first
saved out of the
factory.
Thus, I'd like to add the following:
IObjectCreatedEvent
-- instance brought to life - fire from
initializeArchetype()
IObjectModifiedEvent
-- any and all changes - fire from processForm() when the
creation flag
is False
IObjectInitializedEvent
-- first change - subclass of IObjectModifiedEvent - fire
from
processForm() when the creation flag is True
The current implementation fires IObjectCreatedEvent on the
first change
(where I'm proposing IObjectInitializedEvent) and
IObjectModifiedEvent
on subsequent edits (I wouldn't change this).
I can change this, if people agree. Also, this is on 1.4
branch and 1.5
branch - should we change both?
Martin
------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Archetypes-devel mailing list
Archetypes-devel lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/archet
ypes-devel
|