moodle/blocks
defacer bd1195678c Fix for bug 1320:
Upcoming events were not displayed before calendar_session_vars() was called
at least once. The upcoming events block did not do that, because once upon a
time it was displayed below the month view, which was known to do it :)

Solution: calendar_session_vars() is now called directly from lib.php.
2004-05-07 10:15:10 +00:00
..
activity_modules Files for postgresql 2004-04-19 04:30:55 +00:00
admin Removed obsolete function from pre-OO days. 2004-04-26 09:03:40 +00:00
calendar_month Fix for bug 1320: 2004-05-07 10:15:10 +00:00
calendar_upcoming Me being fussy :-) 2004-04-27 17:16:33 +00:00
course_list Files for postgresql 2004-04-19 04:30:55 +00:00
course_summary Added content "caching", same as all other blocks have. 2004-04-19 09:36:07 +00:00
db First versions for postgressql 2004-04-19 04:15:24 +00:00
news_items Files for postgresql 2004-04-19 04:30:55 +00:00
online_users Bold teachers 2004-04-27 10:18:11 +00:00
participants Files for postgresql 2004-04-19 04:30:55 +00:00
recent_activity Fix for bug #1280: the "showrecent" course setting has to go. 2004-04-29 10:29:23 +00:00
search_forums Files for postgresql 2004-04-19 04:30:55 +00:00
section_links Renamed "weeks_topics" to "section_links" 2004-05-07 02:27:56 +00:00
social_activities Files for postgresql 2004-04-19 04:30:55 +00:00
moodleblock.class.php Grand Bugslayer Eloy at work again: Hiding the blocks if they have no content 2004-04-20 08:38:56 +00:00
README.txt Fixed/added some things so that the instructions are mostly correct. 2004-04-19 07:39:43 +00:00
version.php Bump because some changes have arrived...:-) 2004-04-27 17:23:45 +00:00

-------------------------------------------------------------------------------
CREATING NEW BLOCKS
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
WARNING - PRELIMINARY DOCUMENTATION
This is designed to point new block developers in the right direction. At times
it may NOT be fully up-to-date with the source, or it may even contain some
tiny bit of misinformation that has slipped our notice. If you encounter such a
case, please:
    1. Use the existing block code as reference
    2. Come to the moodle.org forums and tell the world! :) We 'll help you!
-------------------------------------------------------------------------------

You have to derive a class that extends MoodleBlock.

The derived class MUST:

    * Implement a constructor that:
        1. Sets $this->content_type (BLOCK_TYPE_LIST or BLOCK_TYPE_TEXT)
        3. Sets $this->title
        4. Sets $this->version
        5. Sets $this->course equal to its only argument

The derived class MAY:

    * Declare that the block has a configuration interface.
      To do so:

        1. Define a method has_config() {return true;}
        2. Define a method print_config() that prints whatever
           configuration interface you want to have.
        3. Define a method handle_config($data) that does what
           is needed. $data comes straight from data_submitted().

    * Limit the course formats it can be displayed in.
      To do so:

        1. Define a method applicable_formats() which returns a bitwise
           OR of one or more COURSE_FORMAT_XXX defined constants. These
           are defined in lib/blocklib.php.

    * Select a "preferred" width which the course format will try to honor.
      To do so:

        1. Define a method preferred_width() which returns an integer.
           This is the block's preferred width in pixels.

    * Declare that the block is going to hide its header. This will result
      in a more lightweight appearance. Ideal for announcements/notices.
      To do so:

        1. Define a method hide_header() {return true;}