I was wondering if anyone would have suggestions on the best way to have another Product create an event, an ATEvent that is, in a portal. I'm looking for an interface to the ATEvent object. I plan to modify PCNG 1.2.4 such that issues can be created as tasks that have a time-span. I'm going to use it as a scheduler for tasking my company's web hosting department. Basically, when a new issue is created, I will have it create an ATEvent if the user specifies that this issue should be a time-based task. I may end up creating a whole new Product to have this work as I would also like to have a click on an ATEvent take the browser to the PCNG issue tied to that event. Any ideas? Some times this editing of Products can be a mess and I'm just asking for any advice on how to keep it simple. -- Regards, Bryan Simmons -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. -- Rick Osborne -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
manage_afterAdd() is always the first place to perform post-creation operations. -aj --On Dienstag, 28. September 2004 16:24 Uhr -0400 Bryan Simmons <bryan.simmons@gmail.com> wrote:
I was wondering if anyone would have suggestions on the best way to have another Product create an event, an ATEvent that is, in a portal. I'm looking for an interface to the ATEvent object.
I plan to modify PCNG 1.2.4 such that issues can be created as tasks that have a time-span. I'm going to use it as a scheduler for tasking my company's web hosting department.
Basically, when a new issue is created, I will have it create an ATEvent if the user specifies that this issue should be a time-based task. I may end up creating a whole new Product to have this work as I would also like to have a click on an ATEvent take the browser to the PCNG issue tied to that event.
Any ideas? Some times this editing of Products can be a mess and I'm just asking for any advice on how to keep it simple. --
Regards,
Bryan Simmons -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. -- Rick Osborne -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
--On Mittwoch, 29. September 2004 6:50 Uhr +0200 Andreas Jung <lists@andreas-jung.com> wrote:
manage_afterAdd() is always the first place to perform post-creation operations.
-aj
As a goodie I have added a hook for PCNG 1.3 where you can put in all your 3rd-party post-creation operations in form of a PythonScript without the need to touch the PCNG core. -aj
participants (2)
-
Andreas Jung -
Bryan Simmons