#123 ✓resolved
Micah Martin

Production events

Reported by Micah Martin | May 17th, 2009 @ 04:24 PM | in Limelight 0.4

The production need events/hooks to add behavior when the production is loaded and closed.

Comments and changes to this ticket

  • Micah Martin

    Micah Martin May 17th, 2009 @ 04:25 PM

    • State changed from “new” to “resolved”

    You may implement hooks in the production.rb file...

    This makes the init.rb file redundant.

    # Define this method if you want the production name to be different from the default, directory name.

    def name

    return !-PRODUCTION_NAME-!



    # Hook #1. Called when the production is newly created, before any loading has been done.

    # This is a good place to require needed files and instantiate objects in the busines layer.

    def production_opening



    # Hook #2. Called after internal gems have been loaded and stages have been instantiated.

    def production_loaded



    # Hook #3. Called when the production has fully opened.

    def production_opened



    # The system will call this methods when it wishes to close the production, perhaps when the user quits the

    # application. By default the production will always return true. You may override this behavior by re-implenting

    # the methods here.

    def allow_close?

    return true



    # Called when the production is about to be closed.

    def production_closing



    # Called when the production is fully closed.

    def production_closed


Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Elegant UI Framework for Ruby

People watching this ticket