Re: Object created events

Kapil Thangavelu wrote:
> 
>> Well, there was a big discussion and this is the continuation of that
>> discussion. :)
>>
> 
> aye, like diving onto fish tail, and finding a whale ;-)
> 

Us Norwegians, we like wale. We harpoon.



> if we want to move to z3 concepts, i'm not sure thats its a good idea to  
> have a divergent concept here of the same name, ie. createdevent, which in  
> z3 is typically sans context (ie unattached ), and here we would take it  
> to mean attached and fired from initializeArchetype, ie. a lot of  
> lifecycle stuff has already happens between object instantion, adding to  
> the graph (firing add events), and getting an objectcreatedevent in that  
> case. i think it might be better to just choose a separate name to denote  
> the event.
> 
> so instead a separate ObjectAttachedEvent for initializeArchetype, and  
> have the factory do ObjectCreatedEvent.
> 

Where exactly would the created-event be fired? __init__()? createObject.py?

Cheers,
Martin
-- 
View this message in context: http://www.nabble.com/Object-created-events-tf2341226.html#a6530245
Sent from the Archetypes - devel mailing list archive at Nabble.com.


-------------------------------------------------------------------------
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